Hello Pirmin,
I was on vacation, so sorry for my late response.
On Mon, Jul 22, 2019 at 08:09:47AM +0200, Duss Pirmin wrote:
Heello Stefan
Thanks for the information.
On 19.07.19 10:24, Stefan Kalkowski wrote:
can you check whether you might get an overlap of your uImage when loaded to memory (from sd-card or network) and the final system image copied to bootstrap's linking address?
You might check your final uImage with: 'mkimage -l uImage' and the 'loadaddr' your u-boot boot-script finally uses as argument for 'bootm'.
'mkimage -l uImage' Data Size: 27421011 Bytes = 26778.33 KiB = 26.15 MiB Load Address: 10001000 Entry Point: 10001000
Load address (u-boot): 0x14000000 (320MiB) => end of loaded uImage in memory: 0x15a26953 (347MiB) => uncompressed modules in memory: 0x10130000 (257MiB) ... 0x13354000 (308MiB)
If I interpret this numbers correct, then there seems to be no overlap.
I don't know exactly what the last two lines denote, but given that the link address of bootstrap is 0x10001000 and you load the uImage via u-boot to 0x14000000, there is only ~64MiB for the uncompressed system image including all boot modules left. Your (normally compressed) uImage is more than 26 MiB in size, so uncompressed probably much bigger than 64 MiB. So in my eyes there is a big chance for an overlap. Sadly, u-boot won't warn you about it.
To exclude an overlap, please change your uImage loadaddr to something like 0x30000000.
Best regards Stefan
Best regards, Pirmin
Genode users mailing list users@lists.genode.org https://lists.genode.org/listinfo/users