• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 398 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.

Verify failed when recoverying the factory image on TMDSEVM6670LE

nf bj
Prodigy 40 points

I just followed the steps in program_evm_userguide.pdf,using DSS script to recovery all the images in eeprom,nor and nand.

First,I met a question that:An invalid processor ID has been found.and unabe to start the debug server.And I got the key:just use CCS5.1 to generate a new ccxml to replace the one in the program_evm\binaries\evm6670l.it works.

And Now,a new question  come,all the writer return with a failure.Just like blow:

D:\C6670\program_evm>%DSS_SCRIPT_DIR%\dss.bat program_evm.js TMDSEVM6670LE-le

board: evm6670l

endian: Little

emulation: XDS560 mezzanine

binaries: D:\C6670\program_evm/binaries/evm6670l/

ccxml: D:\C6670\program_evm/configs/evm6670l/evm6670le.ccxml

Start writing eeprom50

Writer:D:\C6670\program_evm/binaries/evm6670l/eepromwriter_evm66

70l.out

Image:D:\C6670\program_evm/binaries/evm6670l/eeprom50.bin

EEPROM Writer Utility Version 01.00.00.04

Writing 52800 bytes from DSP memory address 0x80000000 to EEPROM bus address 0x0

050 starting from device address 0x0000 ...

Reading 52800 bytes from EEPROM bus address 0x0050 to DSP memory address 0x80010

000 starting from device address 0x0000 ...

Verifying data read ...

Failure at byte 11, expected 0x000000ef, read 0x000000ef

EEPROM read verify failed

When programming NOR: 

Flashing sector 125 (8192000 bytes of 8416822)
Flashing sector 126 (8257536 bytes of 8416822)
Flashing sector 127 (8323072 bytes of 8416822)
Flashing sector 128 (8388608 bytes of 8416822)
Reading and verifying sector 0 (0 bytes of 8416822)
Failure in sector 0, at byte 27, (at byte 0 in the data file) expected 0x000000e
f, read 0x00000000
NOR read verify failed
End programming NOR

So,can anybody tell me if the EVM is bad.And why the label on the EVM is TMDS- while the documents on the CD are all TMDX-

What's the differences between them?

  • 0
    TI__Mastermind 23525 points

    The TMDS just means that the device has completed qualification.  "X" devices are considered samples until they are qualified.  You can no longer buy a TMDX EVM, as they are all TMDS now.  There should be no difference between the two.

    Which MCSDK version are you using?  Please update to the latest at:  http://software-dl.ti.com/sdoemb/sdoemb_public_sw/bios_mcsdk/latest/index_FDS.html

    You should not have to create your own ccxml file.  The MCSDK support CCS5.1 and should run out of the box.  Please try this.  Note that you have to be in "no boot" mode, as described in the program_evm_userguide.  The program_evm directory from the BIOS-MCSDK will not have a NAND.bin file, you would have to get that from the DVD you have, or the Linux-MCSDK.

    When you created your own ccxml file, you can either point to it with the PROGRAM_EVM_TARGET_CONFIG_FILE environment variable, or simply put it in the \program_evm\configs directory with the appropriate name.  Again, this shouldn't be needed if you are using the latest MCSDK though.

    Regards,

    Travis