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.

Am3517 Technixon Standard Board..U-boot loader issue.[x-loader hangs]

Other Parts Discussed in Thread: FLASHTOOL, AM3517

Dear All,

I had a Standard bootloader flashed with x-loader and u-bootloader .

But to flash my application code i had erased the complete flash.

Now i need to port the x-loader and u-bootloader again to flash.

I am to download them to flash location 0x00000000 : X-loader.bin(signed) and 0x00020000 : u-boot.bin.

but the processor is able to boot only x-loader..this is what i can see on terminal. seeking for any suggestions help .


Texas Instruments X-Loader 1.47 (May  9 2011 - 16:49:13)
Booting from nand . . .
Starting OS Bootloader...[hangs after this]


  • hi hrishikesh,

    Do one thing flash u-boot.bin at address : 0x00080000,

    Then see , and Let me know!

    Regards,

    santosh vastrad

  • Dear Santosh,

    Thanks for your reply ..but this is the output ..after changing the Location

    Texas Instruments X-Loader 1.47 (May  9 2011 - 16:49:13)
    Booting from nand . . .
    ECC Failed, page 0x00080100
    e8 24 e8 80 0 0 a0 e3 17 f 8 ee 15 f 7 ee 10 f 11 ee 2 a c0 e3 7 0 c0 e3 2 0 80
    e3 2 b 80 e3 10 f 1 ee e c0 a0 e1 b3 6 0 eb c e0 a0 e1 e f0 a0 e1 0 0 a0 e1 0 0
    a0 e1 4 d1 1f e5 12 d8 4d e2 88 d0 4d e2 0 e0 8d e5 0 e0 4f e1 4 e0 8d e5 13 d0
    a0 e3 d f0 69 e1 f e0 a0 e1 e f0 b0 e1 48 d0 4d e2 ff 1f 8d e8 34 21 1f e5 12 28
     42 e2 88 20 42 e2 c 0 92 e8 48 0 8d e2 34 50 8d e2 e 10 a0 e1 f 0 85 e8 d 0 a0
    e1 c0 9 0 eb 0 0 a0 e1 0 0 a0 e1 4 d0 4d e2 0 0 8d e5 6c 1 1f e5 12 8 40 e2 88 0
     40 e2 0 e0 80 e5 0 0 4f e1 4 e0 80 e5 0 0 9d e5 4 d0 8d e2 48 d0 4d e2 ff 1f 8d
     e8 94 21 1f e5 12 28 42 e2 88 20 42 e2 c 0 92 e8 48 0 8d e2 34 50 8d e2 e 10 a0
     e1 f 0 85 e8 d 0 a0 e1 b1 9 0 eb 0 0 a0 e1 0 0 a0 e1

  • hi,

    First erase the nand flash once again, and try

    x-loader.bin : 0x00000000 address

    u-boot.bin     : 0x00080000 address

    !!!!!!!!!!!!

    Regards,

    santosh vastrad

  • Dear Santosh,

    I have already tried this but still the same error persist.Any suggestions.

    Thanks and regards

    Hrishikesh.

  • Hi Hrishikesh, 

    how you are flashing , by flashtool or some other way?

    If by flashtool,

    may be ecc selection is wrong,

    x-loader.bin : 1 bit hwecc,

    u-boot.bin : 1 bit swecc,

    uImage      : 1 bit swecc,

    and also check out the below link!!!!!!!!!

    http://e2e.ti.com/support/dsp/sitara_arm174_microprocessors/f/416/t/105605.aspx#371984

    Regards,

    santosh vastrad

  • Hi, 

    I've had the same problem before, (x-load hangs) while working with default u-boot image from TI SDK for AM3517. 

    I had to manually compile x-load and u-boot for my eval board ( which is Craneboard ), from git repository. 

  • Dear Santosh & Bartek thanks for your reply !

    @Santosh : I am using the flashtool provided by TI ..i tried the setting suggested by you but this time the Error did not appear but the x-loader still hangs at the previous point.

    @Bartek : I am using code sourcery tool chain for compilation of x-loader and u-boot loader ..i have not downloaded the images ..i have compiled them for "tams3517_twister_config"  custom board configuration.

    Any more suggestions are welcomed !!!! Is there any script file in the Flash.placed by manufacture  ?

  • Dear Santosh & Bartek thanks for your reply !

    @Santosh : I am using the flashtool provided by TI ..i tried the setting suggested by you but this time the Error did not appear but the x-loader still hangs at the previous point.

    @Bartek : I am using code sourcery tool chain for compilation of x-loader and u-boot loader ..i have not downloaded the images ..i have compiled them for "tams3517_twister_config"  custom board configuration.

    Any more suggestions are welcomed !!!! Is there any script file in the Flash.placed by manufacture  ?

    Thanks and Regard's

    Hrishikesh.

  • Should i use the "ONFI compliant NAND ?"  option.

  • Hi,

    ONFI complaint not needed,

    Otherwise do one thing try using sdram selecting instead of nand and try to display the u-boot information, if executes then no problem with u-boot.bin image,

    In flashtool, you have an option to select SDRAM okay!!!!!!!!!!!!!

    If not executes means, may be some problem in u-boot code, and also check any printf statements you have added in board.c

    file in start_armboot function!!!!!!!!!!!

    Regards,

    santosh vastrad

  • Dear Santosh,

    ¯ -stdout

    ¯ -omap 3

    ¯ -no_force_package_alignment

    ¯ -com 1

    ¯ -t 60

    ¯ -p EVM_MDDR_MICRON_2G_EMIF

    ¯ -2

    ¯ chip_download SDRAM F:\Linux\Images final\Working Images\u-boot.bin

    ¯ command branch SDRAM 0x80e80000

    ¯ Leaving parameter file:temp_script.txt

    ¯ @temp_script.txt

    ¯ Looking for device (omap com1)

    ¯ Please turn off device, then turn it on again

    ¯ Awaiting ASIC id

    ¯ AsicId items 04

    ¯ AsicId id 01 05 01 34 30 07 58

    ¯ AsicId secure_mode 13 02 01 00

    ¯ AsicId public_id 12 15 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

    ¯ AsicId root_key_hash 14 15 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

    ¯ Searching 2nd for: EVM_MDDR_MICRON_2G_EMIF 343007 58 GP

    ¯ Loading second file Targets\2nd-Downloaders\dnld_startup_omap3_gp_2g.2nd

    ¯ Entering parameter file:omapflash2nd.txt at line: 15

    ¯ -pheriphalboot_reopen

    ¯ Reading board configuration file Targets\Configurations\configuration_am35xxevm_micron_2g.txt

    ¯ Reading definition file .\targets\definitions\definitions_omap3.txt

    ¯ -board_config Targets\Configurations\configuration_am35xxevm_micron_2g.txt

    ¯ Leaving parameter file:omapflash2nd.txt

    ¯ Sending size of second file (0x00006804 bytes)

    ¯ Transferring second file to target (0x6804 bytes)

    ¯ Closing boot connection

    ¯ Found device (omap com1)

    ¯ Waiting for 2nd

    ¯ Found 2nd

    ¯ Looking for a driver for 'SDRAM'

    ¯ No driver required for 'SDRAM'

    ¯ Downloading

    ¯ Operation FAILED (Remote: : offset parameter larger than device size)

    ¯ Elapsed time: 0:00.000

    Console program failed, exit code: 3

    This is the output when i choose to load the code in SDRAM...

    Memory Location to Download : 80e80000

    And i have not touched the u-boot code .

  • Dear Hrishikesh,

    I think you have given wrong address,

    Follow like this,

    First custom_am37xx_board.txt option,

    second SDRAM,

    Download option,

    offset : 0x000300000,

    Browse the u-boot.bin location,

    Regards,

    santosh vastrad

  • Dear santosh ..thanks for your co-ordination ..bt i have started the other way through ..sd card..the output is same..

    here it is ..wht do you think...

    Texas Instruments X-Loader 1.47 (Jan 12 2012 - 17:09:36)

    Starting X-loader on MMC

    Reading boot sector

     

    352648 Bytes Read from MMC

    Starting OS Bootloader from MMC...

    Starting OS Bootloader...

    Thanks and Regard's

    Hrishikesh.

  • Lets maintain one thread,  I have already replied to your another post -

    http://e2e.ti.com/support/dsp/sitara_arm174_microprocessors/f/416/t/157932.aspx#574256

    Thanks,

    Vaibhav