We have an EFM32ZG210F16 on a custom board, and we are unable to debug or program it using EFM32 Wonder Gecko Starter Kit (EFM32WG-STK3800) in Simplicity Studio v3. We have followed the Knowledge Base article Debugging an EFM32 Product on a Custom Board, making sure that:
Even with these settings, no matter what we do, the Kit Manager MCU Information area still shows "EFM32WG990F256" for the MCU name and "Unknown" in the architecture, flash size, and locked fields.
We have also tried Segger's J-LINK Commander, and, surprisingly, it is able to detect the EFM32ZG210F16. So, we went back to Simplicity Studio v3 and tried "Select Target..." from the drop down menu next to the EFM32 Wonder Gecko Starter Kit board entry under Detected Hardware, but all we got was a "Failed to detect device" message. What are we doing wrong?
This problem can be attributed to the old version of the firmware running on the starter kit's board controller. It is not possible to connect to target devices with a Cortex M0+ core, like Zero Gecko or Happy Gecko, with a board controller running firmware 0v10p0 and earlier. Starter kits with a Cortex M3- or M4-based MCU are affected by this problem, even though it is the board controller, not the MCU, which handles the debug out functionality.
An update to the board controller firmware for starter kits that have a Cortex M3- or M4-based MCU fixes this problem. Follow this procedure to update a starter kit's board controller firmware:
Should target detection fail for some reason, re-check the connections between the debug header on the starter kit and the debug interface on the target board. In particular, be sure that the debug interface VTARGET pin is connected to the IOVDD supply on the target board. Make sure the starter kit is still in debug out mode, and, of course, make sure the target board is powered. All supply pins on the MCU should be at the expected voltage levels and nothing should be asserting the nRESET pin when the debug interface is disconnected.
Update: In Simplicity Studio v4, if a kit board controller firmware update is available, it will be indicated in the launcher as shown below.