+ u-boot@lists.denx.de
I am not sure how I drop the list in my last email, sorry.
On 01-19 12:56, Jens Maus wrote:
Hi Ivan,
Am 19.01.2024 um 12:22 schrieb Ivan T. Ivanov iivanov@suse.de:
On 01-19 11:49, Jens Maus wrote:
Am 19.01.2024 um 10:20 schrieb Stefan Wahren wahrenst@gmx.net:
Another idea could be to dump the runtime DT of both variants via sysfs (using official RPi OS) and compare them with each other. In the past there was a lot DT firmware hackery for the Raspberry Pi 4.
Good idea indeed. I just did that and executed "dtc -I fs /sys/firmware/devicetree/base“ in a quick RaspberryPiOS installation.
See [1] for the corresponding output. Hopefully Ivan can do the same so that we can see if there are any differences that might explain why his u-boot patches are working for him while they does not for me.
Best Regards, Jens
[1] https://gist.github.com/jens-maus/497e03cf1305ffe8a07e3196c27d6ebd
Thanks! Unfortunately at least first 2 memory banks looks the same as in 4GB version:
memory@0 { device_type = "memory"; reg = <0x00 0x00 0x3f800000 0x00 0x40000000 0xc0000000>; };
Jens, could you please, disconnect HDMI cable and capture devicetree file again.
Sure. Here the diff against the other device tree at gist:
— cut here — --- device-tree 2024-01-19 11:33:41.831797039 +0100 +++ device-tree2 2024-01-19 12:53:11.333845039 +0100 @@ -2,7 +2,7 @@
/ { #address-cells = <0x02>;
- memreserve = <0x3f800000 0x800000>;
- memreserve = <0x3fc00000 0x400000>; model = "Raspberry Pi 5 Model B Rev 1.0"; serial-number = "6b206ca09127ae99"; #size-cells = <0x01>;
@@ -41,7 +41,7 @@
memory@0 { device_type = "memory";
reg = <0x00 0x00 0x3f800000 0x00 0x40000000 0xc0000000 0x01 0x00 0x80000000 0x01 0x80000000 0x80000000>;
reg = <0x00 0x00 0x3fc00000 0x00 0x40000000 0xc0000000 0x01 0x00 0x80000000 0x01 0x80000000 0x80000000>;
Same here, expect that they are more memory banks, of course. It is really strange that you don't seen even single message from the U-Boot..
Hm... Ivan