• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 83 subscribers
  • Views 115 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.

TMS320F2800157: User program cannot write 2800157 USEROTP field properly

Jack he
Prodigy 30 points
Part Number: TMS320F2800157
Other Parts Discussed in Thread: C2000-GANG

Tool/software:

Hello sir，

Can you advice how we can solvethe problem.

We want to encrypt the chip through the user program, need to program the PSDWLOCK & JTAGLOCK field in the USER OTP. CCS Debugging with the simulator is normal, but when running offline and performing encryption operations, the program crash, and cannot connect to the simulator. The only is to replace the chip.

Regards,

Jack

  • 0
    TI__Mastermind 28300 points

    What encryption operations is the device performing when it is running offline? Is it programming custom CSM passwords to itself? If so this could prematurely lock the DCSM and prevent any further operations if the GRABSECT/GRABRAM fields have not already been programmed

  • 0 in reply to Luke Jones
    Prodigy 30 points

    Hi Luke,

    Thank you for response.

    The background of the issue:

    We plan to use the C2000-GANG for batch programming of the F2800157. When the HEX file to be programmed does not include the CSM and JTAGLOCK functions, the C2000-GANG works normally; however, as long as the HEX file contains code for chip encryption, an "Verification Error" will be displayed after the program is downloaded.

    Therefore, we write the encryption code in the application program using the FLASH API. Sequentially in accordance with addresses writing the relevant Settings into the Zone1 HEADER the Zone1 LINKPOINTER. Nevertheless, after performing this operation, we found that the chip was permanently locked, and the only solution was to replace it with a new chip.

    Could you please advise on the correct sequence for programming the ZONE1 HEADER and ZONE1 LINKPOINTER?

    Jack

  • 0 in reply to Jack he
    TI__Mastermind 28300 points

    I expect this issue is caused by programming the JLM_ENABLE field and reading it back via the flash API, which will immediately enable JTAGLOCK before programming the desired passwords. For the bricked units, I would attempt to connect with a target configuration file whose JTAG passwords use the default JTAG passwords in DCSM OTP, described in the TRM.

    An easier method rather than programming via the flash API may be to program the entire hex file including DCSM settings first with verification disabled. Then perform a verify operation on the whole hex application.

    Thank you,

    Luke