• State
  • Locked Locked
  • Replies 15 replies
  • Subscribers 100 subscribers
  • Views 1526 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TI DM646x Serial Loading and Flashing Utilities

Schulle
Prodigy 180 points


Hi,

i use the the sfh_DM646x.exe to boot tu-boot to my DM6464 EVM.

(sfh_DM646x.exe -nandflash -p com14 ubl_dm646x_297.bin u-boot-1.2.0-dm6467.bin)

After download i see the following.

...................................................................

Booting PSP Boot Loader

Starting NAND Copy

NAND Boot failed. Starting UART

...................................................................

I use the ubl and u-boot which i found in the dvsdk_2_00_00_140.

any idea what im doing wrong? wrong u-boot image?

 

Regards,

Steffen

 

  • 0
    TI__Mastermind 37340 points

    What is your end-goal?  Please note that serial loader will temporarily copy image to DDR, whereas serial flashing utility will burn image into NAND flash.

    That said, in either case you want to set your switch settings (SW3 on EVM) to configure hardware for UART boot mode; it appears your hardware is not in UART boot mode from the message above.

  • 0 in reply to Juan Gonzales
    Prodigy 180 points

    My plan is to boot u-boot into the flash. That's why i switch SW3 to UART for the seriell flashing tool and after that back to NAND boot.

  • 0 in reply to Schulle
    TI__Mastermind 37340 points

    Great, looks like you are in the right path then.  I thought the log above (suggesting NAND boot attempt) was the output generated by the uart utility; anyway, if you are in UART mode, then you should be good to go.  Also, make sure you use flashing utility as opposed to loading utility.  Finally, I take it you are tryung this on our DM6467 EVM as opposed to proprietary hardware with perhaps a different NAND part, correct?

  • 0 in reply to Juan Gonzales
    Prodigy 180 points

    I use the 6467 DVEVM with the orginal ST flash. Nothing was changed.

    I've tested the FlashAndBootUtils_1_10. The download to flash also failed (with sfh_DM646x.exe).

    The download to DDR-RAM with slh_.. is working. If i download the u-boot to DDR-RAM i'm able to load files with tftp an write them to the flash. But if i use the UBL and u-boot bin files the board don't start from flash. The u-boot is ok because i can load and run the file from DDR.  

    I see two possible reasons. First, the UBL file is wrong. Second, the u-boot offset is wrong, i use 0x20000. In case of the secound i should see the debug messages from the UBL, right?

  • 0 in reply to Schulle
    Prodigy 185 points

    I am having a similar problem.  I accidentally erased the NAND flash and would just like to restore U-Boot 1.2.0 to the NAND device on my DM6467 (Rev H) EVM.  When I use the sfh_DM646x utility, I don't get a working boot.  When I use slh_..., I get the following error after loading u-boot-1.2.0-dm6467.bin to DDR:

            Target:    DONE
    DONE received.  All bytes of image data received...
            Target:    DONE
            Target: U-Boot 1.2.0 (May 20 2009 - 01:04:07)
            Target: I2C:   ready
            Target: DRAM:  256 MB
            Target: unknown vendor=0 Flash:  0 kB
            Target: NAND:  NAND device: Manufacturer ID: 0x20, Chip ID: 0xf1 (ST Mic
    ro NAND 128MiB 3,3V 8-bit)
            Target: No oob scheme defined for oobsize 256
            Target: BUG: failure at nand_base.c:3398/nand_scan()!
            Target: BUG!
            Target:  BOOTME

    I am using the DVSDK 2.00 provided u-boot .bin file (from REL_LSP_02_00_00_140\PSP_02_00_00_140\bin\dm6467).  I am using the Flash and Boot Utils v1.50.

    I looked at the u-boot source indicated in the error message, and it would appear that this version of u-boot, which supports nand_oob sizes of 8, 16, and 64, is not compatible with the ST NAND device that is on the board, which reports a nand_oob size of 256.  Without a nand_oobinfo struct for this type of device, I don't see how this u-boot bin file is compatible with this board.

    Did you (Schulle) get your u-boot bin from another source?

  • 0 in reply to Schulle
    Intellectual 740 points

    Hi Schulle,

    Use the UBL_DM646x_NAND.bin(20KB size ) which locate in "DM646x_FlashAndBootUtils_1_50\DM646x\CCS\UBL" floder,

    then burn UBL and U-Boot via  sfh_DM646x.exe.

    It works fine on my EVM board.

    PS: My goal is to boot from NAND flash. (UBL+UBOOT+KERNEL+FS)

     

  • 0 in reply to EricR
    Intellectual 740 points

    Hi EricR,

    I got the same symptom on my u-boot.

    When I run: nand read 0x80700000 0x120000 0x200000

    It shows read error ....

     

    Tai

  • 0 in reply to EricR
    Prodigy 180 points

    I have no problems with the slh_... tool. I use the uboot version 1.2.0 which you find in the DVSDK 2.00 (PSP_02_00_00_140/board_utilities/)

    Which NAND device do you have on the REV H board?  I have the NAND01GW3B2A device on my REV F board.

  • 0 in reply to Tai Chang
    Prodigy 180 points
    >Use the UBL_DM646x_NAND.bin(20KB size ) which locate in "DM646x_FlashAndBootUtils_1_50\DM646x\CCS\UBL" floder,

    >then burn UBL and U-Boot via  sfh_DM646x.exe.

    sfh_DM646x.exe -nandflash -p com14 ubl_DM646x_nand.bin u-boot.bin

    -> the board dont boot from flash:-(

    The same u-boot.bin runs if i boot it with slh to DDR RAM.

  • 0 in reply to Schulle
    Intellectual 740 points

    HI,

    Out NAND flash is ST NAND01GW3B2BN6F.

    Please refer to this link if you have any idea about it ..thanks!!

    http://e2e.ti.com/forums/p/8340/32467.aspx#32467

     

    Tai

     

  • 0 in reply to Schulle
    Prodigy 185 points

    My Rev H board has ST part number NAND01GW3B2BZA6  (this is U38 on the Rev H board, in case of any layout changes).

    The full markings on the part are:

    NAND01GW3B2BZA6

    GK2BR  8Y

    CHN  99 834

    <ST Logo>  <e2 logo>

     

  • 0 in reply to EricR
    Prodigy 185 points

    So, I noticed on our other (working) Rev H board that the working version of U-Boot 1.2.0 that was burned on the board at the factory is NOT dated May 20, 2009 as above.

    Instead, the working U-Boot 1.2.0 is dated Jul 17 2008 - 16:55:20).

    Summary:

    OK:  U-Boot 1.2.0 from the factory NAND burn, dated Jul 17 2008 - 16:55:20

    NG:  U-Boot 1.2.0 from DVSDK 2.00, path REL_LSP_02_00_00_140\PSP_02_00_00_140\bin\dm6467, which is dated May 20 2009 - 01:04:07

    I hope this is helpful in identifying the 'No oob scheme defined for oobsize 256' type errors when using the U-Boot from DVSDK 2.00.

    Since the board came with LSP 1.30 (I believe), I'll look at that version of U-Boot to see if it works, and includes definitions for nand_oob = 256 in nand_base.c.

     

  • 0 in reply to EricR
    Intellectual 740 points

    Hi EricR,

     

    Do you know the exactly burn offset of U-Boot and uImage on NAND flash ?

     

    Tai

  • 0 in reply to Tai Chang
    Prodigy 180 points

    as far as i know ther are these offsets.

    UBL -> 0x20

    uboot -> Block 6 (6x128k -> 0xc0000)

    the offset of the kernel depends on the settings in board-dm6467-evm.c

     

    is there anybody who can confirm these values?

  • 0 in reply to Schulle
    Intellectual 740 points

    Hi ,

     

    I think the UBL is from Block1, page2 according to this article: Using the TMS320DM6467 DMSoC Bootloader (http://focus.ti.com/lit/an/spraas0c/spraas0c.pdf) page 12.

    U-boot:

    I saw the write meaasge from "Serial Boot and Flash Loading Utility",

    shows from block6 to block30, but I wonder that each block is 128KB,

    so 0x30 -0x6 +1=43..   

    43x128k=5636096 bytes=5.xxMB !!!!!

    It can't be that large about u-boot !!!

    How ??

    Tai