Other Parts Discussed in Thread: UNIFLASH, LAUNCHXL-CC2640R2, SEGGER
Hello TI Experts,
We are using a LAUNCHXL-CC2640R2 eval board for development. Yesterday we faced an issue where the controller seems to be locked. We know about CCGF register configuration and to handle it carefully, but we did not modify the project in that area. We used the onboard XDS110 when the device entered the "bricked" state. We try several tools (SmartRF Flash Programmer 2, Uniflash, SEGGER J-Flash, CCS 9) to unlock the device again without success.
I attached some SmartRF Flash Programmer 2 logs. What we did is:
1. Try to flash an image
2. Forced mass erase
3. Try to flash an image
Onboard XDS110:
>Initiate access to target: XDS-L50014OG.
>Debug interface is locked. Aborting action. Only forced mass erase is possible.
>Reset target ...
>Reset of target successful.
>Initiate access to target: XDS-L50014OG.
>Start flash erase ...
>Erase finished successfully.
>Reset target ...
>Reset of target successful.
>Initiate access to target: XDS-L50014OG.
>Debug interface is locked. Aborting action. Only forced mass erase is possible.
>Reset target ...
>Reset of target successful.
XDS200:
>Initiate access to target: COM26.
>Debug interface is locked. Aborting action. Only forced mass erase is possible.
>Reset target ...
>Reset of target successful.
>Initiate access to target: COM26.
>Start flash erase ...
>Erase finished successfully.
>Reset target ...
>Reset of target successful.
>Initiate access to target: COM26.
>Get EB Info failed. Device list locket by other process/thread.
>Debug interface is locked. Aborting action. Only forced mass erase is possible.
>Reset target ...
>Reset of target successful.
As I mentioned earlier, we don't know exactly what happened.
Is there any advice to prevent that behavior?
How can we recover the devices?
Regards
Tobias
