If anyone has some input on this, I would appriceate it!
We have been using the CC-Debugger for over 2yrs to do programming of our custom PCB containing a CC111X SoC. We have seen a pattern develop where the debugger (and SmartRFProgrammer) will say that the chip successfully erased-programmed-verified-debug interfaced locked, we then see no action from the newly programmed hardware. It looks like it is still erased or partially programmed. Attempting to reprogram fixes the issue eventually.
This week, we are seeing this on 7 out of 10 attempts.
Anyone have some insight on why it is not working all the time? The debuggers are 2yrs old? Could it be old debugger-FW? old software?
Thanks
