This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

u-boot.bin didn't start

Other Parts Discussed in Thread: TMS320C6747, OMAP-L137

Hi,

I have a OMAP-L137/TMS320C6747 Floating Point Starter Kit and want to run linux on the ARM.

So  I downloade the uboot u-boot-2012.07.tar.bz2 from denx and build it:

make da830evm_config

make

After this I copied the u-boot.bin to the same spi flash location like the eboot for windows ce with the same tool. Afters my bootloader copies the uboot from flash to ram and jumps to the address.

The result is nothing happens. Where I can have a look to find the problem?

regards

  • Hi,

    Please refer this link http://processors.wiki.ti.com/index.php/Restoring/Flashing_OMAP-L137_Bootloaders#Flashing_the_EVM for Restoring/Flashing OMAP-L137 Bootloaders.

    Thx,

    --Prabhakar Lad

  • Hi,

    I flash with the sft.exe to the same location as the EBOOT this should run. I compile the uboot with the eldk from denx. I think this should be a ram version for ARM if I configuer it with make da830evm_config.

    Or is there another option I have to set?

    regads

  • With the pre-built DSPUBL and ARMUBL, the UBOOT partition needs a 4 long word header block preceding the u-boot.bin. I've never used sft_OMAP-L137. The source appears to properly prepend the header to the u-boot.bin. Are you using a pre-built dspubl-ais.bin and armubl.bin? What is your sft command line?

  • Hi,

    I use my own DSPUBL which is almost the same like the DSBUBL because my board has the spi flash on SPI1. This UBL don't starts the ARMUBL it copies my EBOOT for Winc CE direct tho RAM and starts the ARM. I also mofified the sft to flash my program code on SPI1 and the sft generates this header for EBOOT. The EBOOT works correctly.

    Now I compiled the denx uboot (u-boot-2012.07.tar.bz2) with da830evm_config and tried it instead of the EBOOT. The uboot don't give any debug print. So I think there is a mistake in compiling options. What uboot options do I have to set?

    Or is there any thing imported I yust forgot?

    kind regards

  • after changing the start address in da830evm.h to real load address:

    #define CONFIG_SYS_TEXT_BASE        0xc1080000

    #define CONFIG_SYS_TEXT_BASE        0xc3F60000

    I got this print:

    U-Boot 2012.07 (Aug 30 2012 - 09:46:15)

    I2C:   ready
    DRAM:  64 MiB

    but the promt didn't come. Whre I have to look for?

    regards

  • Well...sounds like progress. I've used u-boot versions that came with the EVM (1.3.3) and DVSDK 3.21(2010.12). Maybe try the DVSDK. The one at Arago (http://www.arago-project.org" is supposed to be the same as the DVSDK. Never used the mainline version. The few lines should be:

    In:    serial
    Out:   serial
    Err:   serial
    ARM Clock : 300000000 Hz
    More than one PHY detected.
    Hit any key to stop autoboot:

    No idea why your system would hang after "DRAM". Another possibiliy is that the pre-built DSPUBL and ARMUBL configure something that U-Boot needs.

  • I have exactly the same problem. I figured out that the uboot hangs when the "relocate_code" function in "u-boot-2012.07/arch/arm/lib/board.c" in line 444 is called.

    I just found this function in the header file (u-boot-2012.07/include/common.h) but not in a c file where I can see what happens in there.

    My start address is 0xC3F60000 and the parameters are addr = 0xC3F7D000 and addr_sp = 0xC3E68F58. Where can I see the content of this funtion or does anyone have an

    idea what the problem is?

    Regards, Tom

  • Hi Tom,

    Where can I see the content of this funtion or does anyone have an

    This is the assembly level code specific to the architecture, For arm926 family

    you can find it in 'arch/arm/cpu/arm926ejs/start.S' file.

    Thx,

    --Prabhakar Lad