• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 82 subscribers
  • Views 117 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F28035: TMS320F28035: Exception when burning a program using dslite.bat

? ?
Prodigy 10 points
Part Number: TMS320F28035
Other Parts Discussed in Thread: UNIFLASH,

Tool/software:

After using dslite.bat for burning if the verification step, the command line returns the result of burning success.However, when an address is read using CCS, only the erasure is performed, and it is uncertain whether the erasure process is complete.What causes abnormal burning but returns a successful burning result.The following diagram shows ccs reading burned address data

  • 0
    TI__Guru* 76510 points

    Can you try and use Uniflash GUI directly to program the device?  I just want to verify that the flash contents are correct using that method. DSlite should just be invoking the same processes as the GUI, if that is the only difference we need to look at the command line arguments that are passed when using the .bat file.

    Best,
    Matthew

  • 0 in reply to MatthewPate
    Prodigy 10 points

    This problem in the burning of hundreds of blocks will occasionally appear a few blocks have this situation, after the discovery we tried to use the command line to burn, again burning the result is successful, it is very strange that the burning anomaly at that time did not monitor. This was the command line instruction at the time. "dslite --mode flash -c TMS320F28035_XDS2xx_Default.ccxml -s FlashKey4=DD21 -s FlashKey5=912B -s FlashKey6=110A -s FlashKey7=0007 -e -f -v C:\Users\7043\Desktop\F28035_DC2630X_APP(1).hex"

  • 0 in reply to ? ?
    TI__Guru* 76510 points

    I'm checking with some others if this issue has been seen before and any remedy.  What is odd is that the -v flag is set, which should be running a post flash verify on the image. 

    Is there any other commonalities on the devices that fail, i.e. the host PC or JTAG connection is always the same one?  

    Best,

    Matthew

  • 0 in reply to MatthewPate
    Prodigy 10 points

    Did not find the abnormal point, after the re-burn and other one-time burn through no difference.