SPRACP8A March   2020  – May 2021 TMS320F280021 , TMS320F280021-Q1 , TMS320F280023 , TMS320F280023-Q1 , TMS320F280023C , TMS320F280025 , TMS320F280025-Q1 , TMS320F280025C , TMS320F280025C-Q1 , TMS320F280033 , TMS320F280034 , TMS320F280034-Q1 , TMS320F280036-Q1 , TMS320F280036C-Q1 , TMS320F280037 , TMS320F280037-Q1 , TMS320F280037C , TMS320F280037C-Q1 , TMS320F280038-Q1 , TMS320F280038C-Q1 , TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-Q1 , TMS320F280040-Q1 , TMS320F280040C-Q1 , TMS320F280041 , TMS320F280041-Q1 , TMS320F280041C , TMS320F280041C-Q1 , TMS320F280045 , TMS320F280048-Q1 , TMS320F280048C-Q1 , TMS320F280049 , TMS320F280049-Q1 , TMS320F280049C , TMS320F280049C-Q1 , TMS320F28075 , TMS320F28075-Q1 , TMS320F28076 , TMS320F28374D , TMS320F28374S , TMS320F28375D , TMS320F28375S , TMS320F28375S-Q1 , TMS320F28376D , TMS320F28376S , TMS320F28377D , TMS320F28377D-EP , TMS320F28377D-Q1 , TMS320F28377S , TMS320F28377S-Q1 , TMS320F28378D , TMS320F28378S , TMS320F28379D , TMS320F28379D-Q1 , TMS320F28379S , TMS320F28384D , TMS320F28384D-Q1 , TMS320F28384S , TMS320F28384S-Q1 , TMS320F28386D , TMS320F28386D-Q1 , TMS320F28386S , TMS320F28386S-Q1 , TMS320F28388D , TMS320F28388S , TMS320F28P650DH , TMS320F28P650DK , TMS320F28P650SH , TMS320F28P650SK , TMS320F28P659DH-Q1 , TMS320F28P659DK-Q1 , TMS320F28P659SH-Q1

 

  1.   Trademarks
  2. 1Introduction
  3. 2Supplementary Online Information
  4. 3DCSM Security Tool Example Project
  5. 4DCSM Security Tool Configurable Options
    1. 4.1 ZONE1/ZONE2 Per LINKPOINTER Submodule
    2. 4.2 ZONE1/ZONE2 Header Submodule
  6. 5DCSM Security Tool Generated Content
  7. 6Adding DCSM Security Tool Support to an Existing Driverlib Project
  8. 7Summary
  9. 8References
  10. 9Revision History

Adding DCSM Security Tool Support to an Existing Driverlib Project

Use the following steps to add DCSM Security Tool support to an existing C2000WARE DriverLib Project:

  1. Add the "dcsm_security_tool.syscfg" file
    1. For F2837xD: <C2000Ware_Install_Location>\driverlib\f2837xd\examples\cpu1\dcsm\empty.syscfg
    2. For F2838x: <C2000Ware_Install_Location>\driverlib\f2838x\examples\c28x\dcsm\empty.syscfg
    3. For F28004x: <C2000Ware_Install_Location>\driverlib\f28004x\examples\dcsm\empty.syscfg
    4. For F28002x: <C2000Ware_Install_Location>\driverlib\f28002x\examples\dcsm\empty.syscfg
    from the DCSM examples folder to the project by copying the file into the project.
  2. CCS will ask whether or not to enable SysConfig. Accept and select "Yes".
    GUID-7DEC4655-AE04-44A5-9787-82824A8C2E70-low.png Figure 6-1 Enable SysConfig
  3. Open the "Project Properties" and open the Resources → Linked Resources. Add the following Variable Paths:
    1. DCSMTOOL_SYSCFG_ROOT
      <C2000Ware_Install Location>\utilities\dcsm_tool\dcsm_syscfg
  4. Open Build → SysConfig → Basic Options.
  5. Add the following to the Root system config meta data list:
    1. ${DCSMTOOL_SYSCFG_ROOT}/.metadata/product.json
  6. In the Name of device (-d, --device) option, enter your device name (F2838x, F2837xD, F2807x, F2837xS, F28002x, F28004x), as shown in Figure 6-2.
    GUID-E9636A7E-07C9-4F18-B1DA-C8BDE0F7864F-low.png Figure 6-2 SysConfig SDK Path