Memory Protection for Texas Instruments-CC

Owned by Adam Czajkowski
Last updated: Nov 27, 2024
3 min read

Configuration options in this section are separated by a prefix:

  • The CC prefix limits the effect of these options to “CC 253x Series” MCUs.

  • The CC-26xx prefix limits the effect of these options to “CC 13xx/26xx Series” MCUs.

1. "CC_MemoryProtSource"

This configuration option specifies whether the configuration file should be used as the source of memory protection bit values, or if the code file should be used as the source. The options specified in the main GUI are the same ones saved in the configuration file (User-defined option). If the code file is used as the source, the protection bits must be specified at the correct address within the code file. Correct addresses can be obtained from device manuals. The GUI provides an option to inspect memory protection bits as read from the code file (From File option).

If the FILE_SOURCE value is chosen for this parameter, the only parameters in this section that will also be read are "CC_USER_DBG_WrEn".

  • USER_SOURCE (0) : Protection settings from the configuration file will be used (can be user defined in GUI).

  • FILE_SOURCE (1) : Protection settings from code file will be used (code file must include protection bits at proper addresses). (default)

2. "CC_USER_DBG_WrEn"

This configuration parameter enables writes to LOCKPAGE bit 255 that controls communication debug access.

Logically grouped together with “CC-LOCKPAGE7-Data”.

  • 1 : enabled

  • 0 : disabled (default)

3. "CC-LOCKPAGE0-Data" - "CC-LOCKPAGE7-Data"

Value that will be written to LOCKPAGE register 0-7 if “CC_MemoryProtSource” is set to USER_SOURCE. Ignored otherwise.

4. "CC 26xx MemoryProtSource"

This configuration option specifies whether the configuration file should be used as the source of memory protection bit values, or if the code file should be used as the source. The options specified in the main GUI are the same ones saved in the configuration file (User-defined option). If the code file is used as the source, the protection bits must be specified at the correct address within the code file. Correct addresses can be obtained from device manuals. The GUI provides an option to inspect memory protection bits as read from the code file (From File option).

If the FILE_SOURCE value is chosen for this parameter, the only parameters in this section that will also be read are "CC_26xx_GenOpt_WrEn", "CC_26xx_Prot_WrEn", and "CC_26xx_USER_DBG_WrEn".

  • USER_SOURCE (0) : Protection settings from the configuration file will be used (can be user defined in GUI).

  • FILE_SOURCE (1) : Protection settings from code file will be used (code file must include protection bits at proper addresses). (default)

5. "CC-26xx-CCFG-IMAGE-VALID"

Programming this value is always enabled if “WriteLockingBitsEn” is enabled. This value sets the IMAGE_VALID_CONF value in the MCU that allows the code to boot.

6. "CC_26xx_Prot_WrEn"

This configuration parameter enables writes to CCFG Program and Erase protection registers.

Logically grouped together with “CC-26xx-CCFG-BL-CONFIG”, and “CC-26xx-CCFG-ERASE-CONF” parameters in this section.

  • 1 : enabled

  • 0 : disabled (default)

6.1. "CC-26xx-CCFG-31-0"

Value that will be written to the CCFG_PROT_31_0 register if "CC_26xx_Prot_WrEn" is enabled, and “CC 26xx MemoryProtSource” is set to USER_SOURCE. Ignored otherwise.

6.2. "CC-26xx-CCFG-63-32"

Value that will be written to the CCFG_PROT_63_32 register if "CC_26xx_Prot_WrEn" is enabled, and “CC 26xx MemoryProtSource” is set to USER_SOURCE. Ignored otherwise.

6.3. "CC-26xx-CCFG-95-64"

Value that will be written to the CCFG_PROT_95_64 register if "CC_26xx_Prot_WrEn" is enabled, and “CC 26xx MemoryProtSource” is set to USER_SOURCE. Ignored otherwise.

6.4. "CC-26xx-CCFG-127-96"

Value that will be written to the CCFG_PROT_127_96 register if "CC_26xx_Prot_WrEn" is enabled, and “CC 26xx MemoryProtSource” is set to USER_SOURCE. Ignored otherwise.

7. "CC 26xx GenOpt WrEn"

This configuration parameter enables writes to CCFG BL_CONFIG, and ERASE_CONF registers.

Logically grouped together with “CC-26xx-CCFG-BL-CONFIG”, and “CC-26xx-CCFG-ERASE-CONF” parameters in this section.

  • 1 : enabled

  • 0 : disabled (default)

7.1. "CC-26xx-CCFG-BL-CONFIG"

Value that will be written to the BL_CONFIG register if “CC 26xx GenOpt WrEn” is enabled, and “CC 26xx_MemoryProtSource” is set to USER_SOURCE. Ignored otherwise.

7.2. "CC-26xx-CCFG-ERASE-CONF"

Value that will be written to the ERASE CONF register if “CC 26xx GenOpt WrEn” is enabled, and “CC 26xx_MemoryProtSource” is set to USER_SOURCE. Ignored otherwise.

8. "CC_26xx_USER_DBG_WrEn"

This configuration parameter enables writes to CCFG TI_BACKDOOR, TAP_DAP_0, and TAP_ DAP_1 registers.

Logically grouped together with "CC-26xx-CCFG-TI-BACKDOOR, "CC-26xx-CCFG-TAP-DAP0", "CC-26xx-CCFG-TAP-DAP1".

  • 1 : enabled

  • 0 : disabled (default)

8.1. "CC-26xx-CCFG-TI-BACKDOOR"

Value that will be written to the CCFG_TI_BACKDOOR register if "CC_26xx_USER_DBG_WrEn" is enabled, and “CC 26xx_MemoryProtSource” is set to USER_SOURCE. Ignored otherwise.

8.2. "CC-26xx-CCFG-TAP-DAP-0"

Value that will be written to the CCFG_TAP_DAP_0 register if "CC_26xx_USER_DBG_WrEn" is enabled, and “CC 26xx_MemoryProtSource” is set to USER_SOURCE. Ignored otherwise.

8.3. "CC-26xx-CCFG-TAP-DAP-1"

Value that will be written to the CCFG_TAP_DAP_1 register if "CC_26xx_USER_DBG_WrEn" is enabled, and “CC 26xx_MemoryProtSource” is set to USER_SOURCE. Ignored otherwise.