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

TMS320F28034: Locked After Build Cancelled

Mark Ackerson
Genius 10190 points
Part Number: TMS320F28034
Other Parts Discussed in Thread: UNIFLASH,

Customers having problems flashing TMS320F28034 after stopping Build operation by pressing the ‘cancel’ button.  The ‘cancel’ doesn’t really cancel anything; it continues to build an erroneous image, then proceeds to burning it into flash.  Since then, they have not been able to erase/program flash on this F28034 using Uniflash or CCS 6.1.3.

The CSM isn’t locked; it can still load code into all SRAM (secured and unsecured) sections on the F28034.

Do you have any suggestions other than replacing the F28034?

Thanks,
Mark

  • 0
    TI__Mastermind 42195 points

    Mark,

    when CCS starts a build operation it deletes the old .out file, if you then stop a build part way through no .out will have been generated. Even if the Flash programmer is set to automatically program a device after a build, assuming the build was stopped partway through, there is no .out file for the Flash programmer to load, something sounds amiss.

    No matter how the customer arrived at this configuration, we need to be completely sure that the device is unlocked, and not stuck in a bad configuration.

    1. The Customer should remove all power sources from the board. This includes any JTAG connection or anything else that may provide the board with power.

    2. The customer should then let the board "rest" for a minute or two to drain off any energy stored as capacitance.

    3. At this point I would like the customer to reconnect, see if they can write to secure RAM. If they can then the device is likely unlocked. And they should continue to step 4. If not, then it seems somehow the device became locked.

    4. Finally they should attempt to erase the flash, do not try to erase and program, only erase the flash.

    5. Read the contents of the flash and make sure it has been correctly erased.

    6. Attempt to program the flash as normal.

    I hope this helps, and I eagerly await your response.

    Regards,
    Cody