The custom boot configurations in Section 5.5 can also be written into DCSM OTP using the compiler’s RETAIN and DATA_SECTION pragmas outlined in [31]. The steps below follow the example in Example 2: Two Boot Modes Select Pins.

1. Open any of the C2000Ware examples in CCS and add the following code snippet above the main function (it can be anywhere in the file just outside the functions). These lines program the BOOTPIN-CONFIG and BOOTDEF-LOW registers,device respectively.

   #pragma RETAIN(otp_z1_data_1) 
   #pragma DATA_SECTION(otp_z1_data_1,"dcsm_zsel_z1"); 
   const long otp_z1_data_1 = 0x5AFF582A; 
   
   #pragma RETAIN(otp_z1_data_2)
   #pragma DATA_SECTION(otp_z1_data_2,"dcsm_zsel_z1_2"); 
   const long otp_z1_data_2 = 0xFF41226A;
   

2. In the linker command file for the project, add the following lines defining the DCSM OTP BOOTPIN-CONFIG and BOOTDEF-LOW memory map locations as defined in the Boot ROM Configuration Registers section of the device-specific TRM. The addresses below are for the DCSM user OTP boot configuration registers on F280015x devices.

   MEMORY { 
      PAGE 0:
         DCSM_ZSEL_Z1_P0: origin = 0x078008, length = 0x000002 // Z1-OTP-BOOTPIN-CONFIG
         DCSM_ZSEL_Z1_P1: origin = 0x07800C, length = 0x000002 // Z1-OTP-BOOTDEF-LOW
   }  
   SECTIONS { 
      dcsm_zsel_z1_1 : > DCSM_ZSEL_Z1_P0, PAGE = 0 
      dcsm_zsel_z1_2 : > DCSM_ZSEL_Z1_P1, PAGE = 0 
   }
   

3. Rebuild the example and load to the target by JTAG in CCS. The program loader and Flash API plugin in CCS handles the writing of these values into OTP locations. These values have to be selected and written carefully as the OTP locations cannot be reprogrammed.