Part Number: CC2652R Hi,
I locked jtag and defined SET_CCFG_ERASE_CONF_CHIP_ERASE_DIS_N 0x0 in ccfg.c :
#define SET_CCFG_ERASE_CONF_CHIP_ERASE_DIS_N 0x0
#define SET_CCFG_CCFG_TAP_DAP_0_CPU_DAP_ENABLE 0x00
#define SET_CCFG_CCFG_TAP_DAP_0_PWRPROF_TAP_ENABLE…
You can do it through Uniflash or reprogramming after changing the SysConfig Device Configuration settings (remove CPU DAP option shown below)
The mass erase command carried out by the JTAG WUC TAP should be successful considering that the CHIP_ERASE_DIS_N…
Hi Dirik,
If a random flash could have overwritten the CCFG, the device might be bricked. For instance if the bit CHIP_ERASE_DIS_N was set to 0, you won't be allowed to do a mass erase from the JTAG. Please refer to the Technical Reference Manual section…
Hi J, this is what I needed to know. When you were modifying the ccfg settings did you define "SET_CCFG_ERASE_CONF_CHIP_ERASE_DIS_N" as "0x0" ? Kind regards, Theo
Hi Marie,
I cannot find a reference to CHIP_ERASE_REQ. I have found:
#define SET_CCFG_ERASE_CONF_CHIP_ERASE_DIS_N 0x1 // Any chip erase request detected during boot will be performed by the boot FW #define SET_CCFG_ERASE_CONF_BANK_ERASE_DIS_N 0x1…
Hey Nikolaj,
Thanks for the reference. It looks like I may have disabled the CHIP_ERASE_DIS_N bit as well as some of the TAP/DAP settings. Do you know if there is any way to recover from here?
Yes the 2nd board also had the CCFG overwritten in…
Hello Roman,
Romans Pezenkovs said: I have set following registers to 0x00
How have you applied these CCFG changes to your project? They should be configured using the SysConfig -> Device Configuration -> Debug Access module
Romans Pezenkovs said…
Hello Sanket,
This is mainly accomplished through the CCFG, the details of which are provided in Chapter 11 of the TRM .
1. Several SET_CCFG_CCFG_TAP_DAP_* definitions should be set to 0x00 to disallow access to the JTAG. They can be reversed (unlocked…
Hello Art,
If the JTAG is locked but SET_CCFG_ERASE_CONF_CHIP_ERASE_DIS_N is set to 1 in the CCFG then they will be able to force a mass erase to recover device access, however they will lose the ability to debug the errant firmware. https://e2e.ti…
