[U-Boot] x-loader question
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?
Regards,
john
X-Loader 1.41 (Oct 1 2010 - 16:13:39) mmc_read_cardsize: mmc_dev_data->mode =0, SECTOR_MODE = 1, mmc_dev_data->card_type = 1, SD_CARD = 1 else: cur_csd->c_size_mult = 7,cur_csd->read_bl_len = 10 size = 1977614336 blknr = 0, blkcnt = 1, MCSD_SECTOR_SIZE = 512 Calling mmc_get_dev... Calling fat_register_device... blknr = 0, blkcnt = 1, MCSD_SECTOR_SIZE = 512 Reading u-boot.bin... mem location = 0x80060000 Section size = 512, mydata->fatsize = 0 Reading boot sector blknr = 63, blkcnt = 1, MCSD_SECTOR_SIZE = 512 FAT16, fatlength: 141 Rootdir begins at sector: 283, offset: 23600, size: 32 Data begins at: 307 Cluster size: 4 Copying filename u-boot.bin to fnamecopy blknr = 346, blkcnt = 4, MCSD_SECTOR_SIZE = 512 fnamecopy = u-boot.bin, s_name = mlo, l_name = RootMismatch: |mlo|| fnamecopy = u-boot.bin, s_name = u-boot.bin, l_name = RootName: u-boot.bin, start: 0xb1, size: 0x25f94 buffer address = 0x80060000 Filesize: 155540 bytes Reading: 155540 bytes blknr = 64, blkcnt = 6, MCSD_SECTOR_SIZE = 512 blknr = 1078, blkcnt = 300, MCSD_SECTOR_SIZE = 512 blknr = 1378, blkcnt = 3, MCSD_SECTOR_SIZE = 512 blknr = 1381, blkcnt = 1, MCSD_SECTOR_SIZE = 512 Size: 155540, got: 155540 ret = 155540 file_fat_read: do_fat_read_ret = 155540 mmc_read_bootloader: file_fat_read: ret_size = 155540 mmc_read_bootloader: seems got the data... CFG_LOADADDR Address = 80e80000, fnamecopy = u-boot.bin Starting OS Bootloader from MMC/SD1 ... X-Loader hangs
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
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
On Fri, Oct 1, 2010 at 10:59 PM, John Tobias jtobias@viaas.com wrote:
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?
If you took the code from the omap4-dev branches of omapzoom then the recent relocation changes are not an issue, since that code is based on a u-boot release from 4 years ago!
Given that, folks here on the u-boot list aren't too likely to be the right resource for help on such an old code base. If you want to stick with that code, then TI's E2E site is probably your best bet for support.
However, I recommend you switch to mainline u-boot v2010.09, released just this week. I have added support for the OMAP4 Panda and SDP4430, so these should serve as good examples for your board.
Steve
Steve Sakoman <sakoman <at> gmail.com> writes:
On Fri, Oct 1, 2010 at 10:59 PM, John Tobias <jtobias <at> viaas.com> wrote:
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?
If you took the code from the omap4-dev branches of omapzoom then the recent relocation changes are not an issue, since that code is based on a u-boot release from 4 years ago!
Given that, folks here on the u-boot list aren't too likely to be the right resource for help on such an old code base. If you want to stick with that code, then TI's E2E site is probably your best bet for support.
However, I recommend you switch to mainline u-boot v2010.09, released just this week. I have added support for the OMAP4 Panda and SDP4430, so these should serve as good examples for your board.
Steve
Hi Steve, I was having a similar problem on a TI Blaze (OMAP4) board, and took your advice. Moved up to the v2010.12, configured it for omap4_sdp4430_config, and was able to boot into Android successfully. Thanks! Matthew
participants (3)
-
John Tobias -
Matthew Barton -
Steve Sakoman