• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 82 subscribers
  • Views 146 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.

RE: TMS320F2800132: TMS320F2800132 SCI firmware update

Manu36
Expert 1410 points

Other Parts Discussed in Thread: UNIFLASH

I have an additional question, please let me know if I need to open a new issue.

I have used this document to perform software controlled firmware update :  Application Report SPRACN1–May 2019

This works as expected but when I try to program the boards several times using the flash kernel, i get the following:

Bit rate /s of transfer was: 7436.716309
Application load successful!
Done waiting for application to download and boot...
SUCCESS of Command
ERROR Status: Not Recognized Error
ERROR Address: 0x78008
Error not recognized
Please refer to the Flash API documentation for further explanation of the error.
FMSTAT Register contents: 011

0x78008 is the adress of the BOOTPIN_CONFIG in OTP memory which was changed as described in the Application report.

SO what does ths error means? That the OTP was already programmed or that the flash kernell can not access OTP?

Is it ok to run with this error? 

Regards

  • 0
    TI__Mastermind 20380 points

    Hello,

    I've gone ahead and split this question from the old thread to keep the topics coherent.

    According to the FMSTAT (aka STATCMD) register contents, program failed due to a write/erase protection violation:

    Looking at the F280013x SCI Kernel example, it doesn't look like the implementation is setup to program the DCSM OTP regions:

    The WEPROT_UO register is responsible for setting the write/erase protection attributes:

    Source: https://www.ti.com/lit/ug/spruj96/spruj96.pdf

    The best solution is to detect if the address being programmed is within the user OTP region, only then disable write/erase protection for the OTP. Importantly, note that only 64-bits can be programmed to the link pointer locations at a time (not 128-bits as done in the example).

    Best,
    Matt

  • 0 in reply to Matt Kukucka
    Expert 1410 points

    Thank you for the analysis.

    If we consider:

    -FIrst programing of the board will be done using JTAG (using uniflash or equivalent), so OTP will be programmed at this step.

    -Firmware update using SCI should has no reason to modify OTP.

    Is there any issue not to modify something?

    Regards.

  • 0 in reply to Manu36
    TI__Mastermind 20380 points

    Hello,

    There should be no issue if you only use CCS/UniFlash to program the OTP.

    Best,
    Matt