I have 3 bricked Thunderboard BG22's sitting on the desk in front of me. I have no idea how they got in the state they're in. I've been using the TB-BG22 for several weeks, programming them with application code using mostly Simplicity Studio or the Commander as I've been doing on for nearly a year now on the earlier versions of the Thunderboard. Not sure how it happened, but when I try to connect to the TB in Commander, I get the "Could not access Debug Challenge Interface" pop-up below. When I click on "Recover Bricked Device", I get "Recover is only supported on Exx32 devices. Got device: "Cortex-M4"". When I try to download code to the device in Simplicity Studio, I get the "Click to Query Lock Status" screen at bottom, but clicking on that link it doesn't do anything.
Can anyone tell me how to un-brick my boards?
It's me checking in again. I now have 4 TBSBG22 bricks. Help!
Hi Gary Sugar,
Please try the device recover command from a terminal window. Open the terminal window and then change to the Commander directory inside of the Simplicity Studio installation. Using the default installation path the command would be:
cd "/Applications/Simplicity Studio.app/Contents/Eclipse/developer/adapter_packs/commander/Commander.app/Contents"
MacOS/commander device recover
If that does not work then please copy the output of executing that command and place it in your reply.
It is possible to brick boards in ways that cannot be recovered. The most common ways that is done are:
On series 1, these are unrecoverable:
Hopefully running device recover from the terminal window works for you.
Glad that the recover command worked from the command line. For the secure element information errors - have you updated the Secure Element firmware to the latest version? (version 1.2.6 as I write this). The Secure Element firmware can be updated from the Launcher perspective. Select the JLink line in the Debug Adapters window and then in the main launcher window click the link to read FW to get the current version, it should warn about resetting the device to read the secure element firmware and if the latest version is not installed there should be a link to update it.
I have similar - 6 bricked EFM32GG12 chips on our board, I tried commander device recover, it says
ERROR: Unlock failed with error code -19 (Device recovery failed.)
So, those mcu's are dead forever, correct?
They might be bricked, I would suggest rebooting the PC and trying again just to make sure there isn't a stall thread blocking access to the debug adapter.
Which debug adapter is being used?
Also, did all of the boards become unresponsive after programming them with the same application? Do any of the ways to brick a board I listed earlier seem like a possibility?