Hi Steve,
Thanks for the response. The processor is OMAP4 and I am in the last stage of bringing up the board. I took the source code from the omapzoom git tree.
How do I know if pre or post relocation changes?
Regards,
john
On Fri, Oct 1, 2010 at 8:43 PM, Steve Sakoman sakoman@gmail.com wrote:
On Fri, Oct 1, 2010 at 4:27 PM, John Tobias jtobias@viaas.com wrote:
Hi Guys,
I have a bit problem here and may be you can help some idea to debug x-loader (please see the log messages below). I am using a micro-sd card with FAT16 partition. I boot my board using the the sd card, the
x-loader
execute and loads the u-boot.bin at address location 0x80e80000. But,
after
executing this ((init_fnc_t *)CFG_LOADADDR)(); instead of executing the u-boot, it executed the hang function. Any clues?
I think you'll need to give a lot more information if anyone is to be able to help.
What type of processor is on the board? I suspect OMAP4 based on the 0x80e80000 load address.
What source tree is the x-load built from, and also what version of u-boot -- particularly whether this is pre or post the relocation changes.
It appears that x-load is loading u-boot properly and then something goes wrong. You'll get the "X-Loader hangs" message if there is ever a return from the ((init_fnc_t *)CFG_LOADADDR)() function call, so obviously something goes wrong once the downloaded u-boot starts executing.
Steve