Hi Juan Pablo, Thanks for your clarification, I am however still struggling with understanding what exactly you want to achieve.
This is my understanding of what you want: In production (no JTAG connection): - An ID is stored in (internal) flash, and this…
Part Number: CC1352R Other Parts Discussed in Thread: SEGGER Hi TI and other CC1352R enthusiasts,
We have an issue regarding locking the CC1352R1F3 during our (mass-)production. We want that the chip will be not-readable, not writeable, and also not…
Hi Srinivas,
Have you disabled flash erase in ccfg.c? I.e. set:
#define SET_CCFG_ERASE_CONF_CHIP_ERASE_DIS_N 0x0 // Any chip erase request detected during boot will be ignored
-Simon
So, for disable chip erase, we can define this in ccfg.c?
SET_CCFG_ERASE_CONF_CHIP_ERASE_DIS_N=0x00
What is the difference when defining in predefined symbols? Last time, I use all predefined symbols for my defines lije this not ccfg.c..
Regards,
…
Could you attach the xml files showing the setup instead of copy/ paste them into the post?
As long as you haven't changed SET_CCFG_ERASE_CONF_CHIP_ERASE_DIS_N you should be able to do a mass erase. But if the chip comes up as unknown you have bricked…
Do you have more details? It sounds like you have by accident have changed the setting of CHIP_ERASE_DIS_N in the CCFG and hence locked yourself out of the chip. Please refer to chapter 9 in www.ti.com/.../swcu117h.pdf for more details.
As long as you have set #define SET_CCFG_ERASE_CONF_CHIP_ERASE_DIS_N 0x1 it should be possible to do a mass erase. As YK suggested, please try with Flash Programmer 2. If that seems not to work, could you report the symptoms?
I see that I referred to 7) and not 6).
6) under the section I linked to state: "Optionally, the SET_CCFG_ERASE_CONF_CHIP_ERASE_DIS_N define in ccfg.c can be set to 0x0 to disallow erasing of the Flash when Chip Erase is requested by JTAG." …
