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.

TMS320F28388D: Writing OTP Memory with Sysconfig

Part Number: TMS320F28388D
Other Parts Discussed in Thread: SYSCONFIG

Hi Dear TI Members,


I read TI E2E threads about writing OTP and  I have read also application report -SPRACN1. 

I think there is 3 way to writing OTP. 

- with sysconfig,

- with Project Properties -> Debug -> Flash Settings,

- with code snippets which are mentioned Application reports SPRACN1

I have questions about sysconfig method :

After building "led1_ex1_blinky" project with above DCSM settings, "dcsm.asm" and "dcsm.cmd" files are generated. 

Are these files enough to write OTP ? 

Do we need to merge "dcsm.cmd" and already existing "2838x_RAM_Ink_cpu1.cmd" file ?
Do we need to merge "dcsm.asm" and already existing "f2838x_codestartbranch.asm" file ?

Do we need to add any code to "led_ex1_blinky.c" for writing OTP memory (as in SPRACN1) 

Thank you,

Best regards,

Mehmet.

  • Hi Mehmet,

    Are these files enough to write OTP

    You need to have the 2838x_RAM_Ink_cpu1.cmd also. The dcsm.cmd linker command file works as an addendum to the already existing Flash/RAM linker command file that the project has, both the files are required.

    Do we need to merge "dcsm.cmd" and already existing "2838x_RAM_Ink_cpu1.cmd" file ?

    No, you can keep them as separate.

    Please have a look at the DCSM secure memory partition example in the DCSM folder, this example demonstrates how to configure and use DCSM.

    Thanks

    Aswin