SPRACS4 June 2020 TMS320F2800132 , TMS320F2800133 , TMS320F2800135 , TMS320F2800137 , TMS320F2800152-Q1 , TMS320F2800153-Q1 , TMS320F2800154-Q1 , TMS320F2800155 , TMS320F2800155-Q1 , TMS320F2800156-Q1 , TMS320F2800157 , TMS320F2800157-Q1 , TMS320F28384D , TMS320F28384D-Q1 , TMS320F28384S , TMS320F28384S-Q1 , TMS320F28386D , TMS320F28386D-Q1 , TMS320F28386S , TMS320F28386S-Q1 , TMS320F28388D , TMS320F28388S , TMS320F28P650DH , TMS320F28P650DK , TMS320F28P650SH , TMS320F28P650SK , TMS320F28P659DH-Q1 , TMS320F28P659DK-Q1 , TMS320F28P659SH-Q1
You can include security configuration as part of the C code itself so that it is embedded in the .out file and gets programmed when programming the .out file. This method is useful when the security configuration values are almost finalized or for production programming. In this case, all the security settings get programmed at once. Hence, if the JTAGLOCK (JLM) has been enabled, then CCS connection will be terminated after the .out file has been programmed and the CPU has been reset.
To see how to include security configurations in C code, see the DCSM example (<C2000Ware>\driverlib\f2838x\examples\c28x\dcsm ) in C2000Ware.