U-boot bootelf starts at wrong entry point

[Babylone]

Hello,

I'm currently developping an application for IMX6 SOLO processor embedded on custom board.

It uses U-boot to launch the application. When U-Boot start application I see that the entry point is not correct : 0x00000000 instead of 0x10100000 (see folowing image).

U-boot prompt

If I look into the .map file is see that _start is correctly defined :

Babylone_0-1695383159071.png

And in the linkerscript :

Babylone_0-1695383816812.png

Gdb information :

Babylone_0-1695385285989.png

The other thing is that I'm able to run the application via Debugger.

So my question is : From where this could be coming from ?

Thanks in advance for your help,

Regards,

[Chavira]

Hi @Babylone!

Thank you for contacting NXP Support!

What kernel version are you using?

Are you using our BSP?

How are you running the program?

We have a variable on the environment called "load_addr" In that direction you can load your program and run it.

For example:

=>fatload mmc 0:1 $load_addr hello_world.bin

=>go $load_addr

In that way, we can run the hello_word.bin allowed on MMC 0:1

Note: The commands used are only used as an example the Hello_world.bin is not loaded in the memory by default.

Best Regards!

Chavira

[Babylone]

Hello Chavira,

Sorry to be late.

We use a custom U-boot available here. Our application runs under SafeRTOS. 

We get the elf file through USB or NAND and then run it with the bootelf command.

Our elf file is correct since it can be runned via JTAG, telling me that it could be a U-boot issue.

Best Regards,

Babylone

[Chavira]

Hi @Babylone!

Sorry, we can't provide support due to you are not using our source code.

Please try to use our source code available here:

https://github.com/nxp-imx/uboot-imx

Best Regards!

Chavira