uImage Load Address Issue

[Matthias Lange]

Hi Daniel,

On 07/21/2017 08:19 PM, Daniel (Xiaolong) Wang wrote:
> Hi All,
> 
> I’m testing L4re on a customized I.MX6 Solo-X-4 board. I found that the fiasco kernel (the simple hello world example built into an uimage) cannot be load by the U-boot. It shows “data abort". The reason I guess it is due to different loading address. The U-boot’s default $loadaddr is 0x80800000, but the uimage I build using the L4re buildsystem has:
> 
> Load Address: 11000000
> Entry Point:  11000000
>   ==> Installing bootstrap.uimage in image directory
>   Image size(s) in bytes:
>         bootstrap_hello-cfg.elf:  1470844
>                   bootstrap.raw:  1437696
>                bootstrap.uimage:  1437760
>   Start address: 0x11000000
> 
> 
> I used the RAM_BASE=0x8080000 option to change the starting address when I made the image (as shown below), the boot did not crash but the kernel hangs at “Starting kernel..."

Did you provide the correct platform type when you built the image? You
should do something like this

make PLATFORM_TYPE=imx6 RAM_SIZE_MB=1024 UART_NR=1 E=hello uimage

Change the values of RAM_SIZE_MB and UART_NR according to your platform.

Best,
Matthias.

> 
> Load Address: 01000000
> Entry Point:  01000000
>   ==> Installing bootstrap.uimage in image directory
>   Image size(s) in bytes:
>         bootstrap_hello-cfg.elf:  1470844
>                   bootstrap.raw:  1437696
>                bootstrap.uimage:  1437760
>   Start address: 0x801000000
> 
> I think it is still related to the different load address. But I do not know how to fix it. I would really appreciate if someone can point me to a right direction.
> 
> Thanks
> -Dan
> 
> 
> _______________________________________________
> l4-hackers mailing list
> l4-hackers at os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
> 


-- 
Matthias Lange, matthias.lange at kernkonzept.com, +49-351-41 888 614

Kernkonzept GmbH.  Sitz: Dresden.  Amtsgericht Dresden, HRB 31129.
Geschäftsführer: Dr.-Ing. Michael Hohmuth