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
The Dual Code Security Module (DCSM) baseline architecture provides a barrier to someone trying to gain unauthorized access to important intellectual property in the form of firmware (FW). A resource like memory can be left unsecured or allocated to either of the two secure zones. Additionally, it can be marked as execute-only (EXEONLY) to raise the barrier even higher. Through special hardware features, firmware stored in EXEONLY flash can even be copied to and run from EXEONLY RAM. Each of the secure zone is protected by a 128-bit CSM password and security configurations are programmed into the one-time programmable (OTP) area of the Flash. The configuration governs, among other items, which flash sectors and RAM blocks (memory) are allocated to which zone. Security logic protects un-authorized access to each zone's secure resources. For detailed information about device security features, please refer to Dual Code Security Module (DCSM) section in the device-specific Technical Reference Manual (TRM).