• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 583 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.

Flash tool V1.3 connection fail on OMAP35x and AM/DM37X EVM

Shine Kao
Intellectual 405 points
Other Parts Discussed in Thread: AM3517, AM3505, AM3703, AM3715, DM3730, DM3725, OMAP3525, OMAP3515, OMAP3530, OMAP3503

Hi,

I use Flash V1.3 to erase EVM Nand flash, but get some error. The message list below and attached file.

 

-stdout

-omap 3

-com 4

-t 60

-p EVM_MDDR_HYNIX_2G

-2

chip_erase NANDINFO 0

Leaving parameter file:temp_script.txt

@temp_script.txt

Looking for device (omap com4)

Please turn off device, then turn it on again

Awaiting ASIC id

AsicId items 04

AsicId id 01 05 01 36 30 07 07

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_HYNIX_2G 363007 07 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_evm37xx_hynix_2g.txt

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

-board_config Targets\Configurations\configuration_evm37xx_hynix_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 com4)

Waiting for 2nd

Reception failed - timeout after 60 s during peripheral boot (waiting for 2nd)

 

 

Console program failed, exit code: 2

 

  • 0
    TI__Expert 6735 points

    Shine:

    Flash Tool v1.3 does not work with UART peripheral boot.  But it does work with

    USB peripheral boot.

    Flash Tool v1.4 suporting AM3517 is now available for download by customers here:

     http://focus.ti.com/docs/toolsw/folders/print/flashtool.html

    (See release notes below, the UART peripheral problem has not yet been fixed, but

    preliminary AM3517 support has been added.)

      

     

    R E L E A S E  N O T E S

     1. See User's Guide on this Wiki page:

        http://processors.wiki.ti.com/index.php/Flash_v1.4_User_Guide

     2. Supports the following devices:

       AM3505, AM3517

       AM3703, AM3715

       DM3725, DM3730

       OMAP3503, OMAP3515, OMAP3525, OMAP3530

     3. Flash Programming via UART is not supported in this release.

     4. Support for AM35xx is added by this release.  On-chip ECC is not

       yet supported.

    Regards,

    Michael T

    PS: Please mark this post as answered via the Verify Answer button below if you think it answers your question.  Thanks!

  • 0 in reply to Michael T
    Intellectual 640 points

    Hi Mike,

    We have the same problem now with flash tool 1.6 on AM37x customized board. Could you advise what could be wrong? Attached is the log. Thanks. Frank.

    ¯ -stdout

    ¯ -omap 3

    ¯ -no_force_package_alignment

    ¯ -com 5

    ¯ -t 60

    ¯ -p CUSTOM_AM37XX_BOARD

    ¯ -2

    ¯ chip_erase NANDINFO1BITBOOT 00008000

    ¯ Leaving parameter file:temp_script.txt

    ¯ @temp_script.txt

    ¯ Looking for device (omap com5)

    ¯ Please turn off device, then turn it on again

    ¯ Awaiting ASIC id

    ¯ AsicId items 04

    ¯ AsicId id 01 05 01 36 30 07 07

    ¯ 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: CUSTOM_AM37XX_BOARD 363007 07 GP

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

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

    ¯ -pheriphalboot_reopen

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

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

    ¯ -board_config Targets\Configurations\configuration_custom_am37xx.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 com5)

    ¯ Waiting for 2nd

    ¯ Reception failed - timeout after 60 s during peripheral boot (waiting for 2nd)

    Console program failed, exit code: 2

     

  • 0 in reply to Bigtree
    TI__Expert 6735 points

    Frank:

    Usually this means that the board configuration is not correct.  The board configuration

    defines the register sequence used to bring up clocks, SDRAM and GPMC.

    Do you have different part numbers (than the AM3715 EVM) for NAND or DDR devices.

    What is your crystal clock freq?

    Regards,

    Michael T

     

  • 0 in reply to Michael T
    Intellectual 640 points

    Hi Michael,

    Thanks for the reply.

    Here are the particulars for our custom board:

     

    Processor:  AM3703 (800MHz version), clock freq = 12MHz (crystal).

    SDRAM, LPDDR, 32 Meg x 32, 5.0nS                                         MT46H32M32LFB5-5 AT:B            Micron

    NAND FLASH, 2Gb (x16), 1.8V                                                    MT29F2G16ABBEAH4                     Micron

     

    I have attached the configuration and definitions files.  Thank you in advance for your help.7827.configuration_custom_am37xx.txt6052.definitions_gnc.txt