• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 602 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

CC2652P: Prevent bootloader from reading flash

CC2652P: Flash security capabilities of CC2652R1

Andrzej Kostyk
Prodigy 70 points

Part Number: CC2652P
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi all,
as in Aug1 2025 in EU the RED DA regulation will be enforced which means the EN-18031-1 list of requirements has to be meet by many products.

Some of requirements are about Secure Storage Mechanism that must be provided in product.

Question: Can CC2652R1F provide confidential and integrity of binary image on internal flash?
Please provide CC2652R1F features which can be used to create such mechanism.

Regards,
Andrzej

  • 0
    TI__Guru**** 223677 points

    Hi Andrzej,

    You can disable the CPU DAP Debug Access, among others, from the CCFG (controlled in the Device Configuration module of SysConfig from your CC2652P project) and this would prevent JTAG from accessing and reading the device's memory.  There is a Bootloader Command which allows memory reading so you will likely want to leave the Bootloader disabled in your Device Configuration as well. 

    Unfortunately disabling both JTAG and the ROM Bootloader will entirely lock out further device memory access so you will want to only do this procedure for field devices which do not require further debugging/programming. 

    Technically you could put a fail-safe in your application which would re-write the CCFG flash area (assuming the last flash sector is left unprotected) to either 1) set CCFG with bootloader and JTAG enabled, or 2) invalidate all of the CCFG with 0xFF so that the FCFG on reset.  Of course this would then make the device once more susceptible to memory reading, and the proposal is an uncommon use case so user discretion is advised.

    Regards,
    Ryan