Simplicity Studio V4 - Debugging an EFM8/EFM32 product on a custom board using a Starter kit

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Hero Employee</font></font> </a> marao on ‎10-07-2016 10:26 AM

If Simplicity Studio V3.3 is being used, then the following knowledge base articles explain how one can debug an EFM8/EFM32 product on a custom board:

Debugging for EFM8 devices

Debugging for EFM32 devices

 

For SS V4, the hardware set up for the EFM8 and EFM32 devices remains the same and can be referred to from the Knowledge Base articles listed above. The Simplicity Studio configuration, however, has been modified to make changing debug modes easier. There is no Kit Manager in V4, and debug modes can be changed directly from the Launcher perspective. 

 

To prepare your setup:

1. Connect the debug pins between the debugger and the target board as described in the Knowledge Base articles above.

2. Power the custom board.

3. Connect the STK to the host and move the switch to the AEM or Debug position or connect a JLink debugger to the host.

 

In Simplicity Studio, perform the following steps to connect to a target board using an STK in debug OUT mode:

 

1. Launch Simplicity Studio V4 and select the root element in the Device view of the STK.debug_1.PNG

 

2. The Launcher perspective shows the Debug mode, and there is a link next to it to change the debug mode.

 

debug_2.PNG

 

3. Click on Change. In the subsequent J-link window, under the Adapter Configuration tab, change Debug Mode to OUT.

 

debug_3.PNG

 

 

4. Go to the Device Hardware tab in the same window. Change the Target Part to the target MCU. Leave the Target Interface as SWD. Click OK.

 

debug_4.png

 

5. The device information will be updated in the Device view in the Launcher perspective.

 

debug_5.png

 

6. These steps may need to be repeated after closing and reopening Simplicity Studio.

 

An alternative way to get the J-link window (Step 3) open would be to right click the root element and select Device Configuration. Steps 3 - 6 will remain the same. 

debug_6.png

 

Now you can debug the external EFM8/EFM32 MCU using Simplicity Studio V4. 

 

Comments
by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Super Star</font></font> </a> OMogenot
on ‎10-08-2016 08:05 AM

Hi,

 

This does not work for me anymore since my upgrade to Simplicity Studio 4. I can't change Debug mode of the STK board (whatever type of STK LG,GG or TG), the Debug OUT led on the board does not switch on and the Studio Launcher screen still shows MCU.

(All this worked fine with Studio 3)

What can I do?

 

Regards,

 

OM.

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Hero Employee</font></font> </a> marao
on ‎10-10-2016 12:00 PM

Hi OM,

 

What exactly are you seeing when you try to change the Debug Mode through V4? Can you share some screenshots?

 

Manasa

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Super Star</font></font> </a> OMogenot
on ‎10-11-2016 09:41 AM

Easy: Nothing !

In other words, the screen shows that the SDK Debug mode is MCU mode. You click on 'change' link to see the 'Adapter Configuration' dialog box that contains a listbox to change the Debug Mode (see attached screen1 file).

screen1.PNG

Choose OUT, after a little while the listbox becomes valid again and the word 'applied' is shown beside it (see attached screen 2 file), however the SDK did not change mode and the OUT led on the SDK is not on.

screen2.PNG

Obviously, this means that the SDK debug mode is not in OUT mode and trying to debug an external board with it does not work.

 

Hope this helps,

 

Regards,

OM.

 

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Star Employee</font></font> </a> ryanco
on ‎10-18-2016 05:10 PM

I experienced this issue, but it was resolved by updating the adapter firmware from the launcher in SS4.

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Hero Employee</font></font> </a> marao
on ‎10-18-2016 05:17 PM

@ryanco Are you using Studio V4 on an XP machine?

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Star Employee</font></font> </a> ryanco
on ‎10-18-2016 05:22 PM

nope, windows 7

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Super Star</font></font> </a> OMogenot
on ‎10-19-2016 04:01 AM

I could not upgrade STK firmware from SS4 as well. It just does not work and is just ignored by the STK board.

Is there a way to "uncompress" the .emz package and copy it directly on the STK "virtual disk" to manually upgrade it?

 

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Hero Employee</font></font> </a> marao
on ‎10-19-2016 05:23 PM

You are seeing this issue because an executable which is responsible for changing the debug mode of the MCU is not working as expected on XP. This is happening because one of the visual studio c runtime files in XP is of an incompatible version on V4. For now, I would suggest you to continue using V3.3 on your system. We are looking into this internally and once we have an update I will let you know. 

 

~Manasa

by edu69
on ‎11-25-2016 04:11 AM

Hi, marao

 

Which EFM32 family devices is it possible to externally debug with an specific Starter Kit? For instance, a Tiny Gecko Starter Kit (STK3300) can debug an external EFM32LG micro?

 

Best regards,

Eduardo

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Super Star</font></font> </a> OMogenot
on ‎12-09-2016 03:58 AM

Hi Marao,

 

Any news regarding V4 version and XP?

 

Best Regards,

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Hero Employee</font></font> </a> marao
on ‎12-09-2016 11:39 AM

Hi @OMogenot

 

We are still working on this issue. I will keep you updated on the progress made. 

 

Manasa

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Hero Employee</font></font> </a> marao
on ‎12-09-2016 11:41 AM

Hi @edu69

 

Sorry, I must have missed your message. As long as your have the right debug cables you should be able to debug LG with the TG STK. Once you set the TG STK to debug out mode, you are bypassing the Tiny Gecko MCU and using the routed debug pins on the STK to flash the LG device.

 

Manasa

by edu69
on ‎12-12-2016 02:29 AM

Hi marao,

 

Thank you very much for the answer.

 

Best regards

Eduardo

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Super Star</font></font> </a> spd
on ‎12-12-2016 08:19 AM - last edited on ‎12-13-2016 09:58 AM by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Hero Employee</font></font> </a> BrianL

marao wrote:

If Simplicity Studio V3.3 is being used, then the following knowledge base articles explain how one can debug an EFM8/EFM32 product on.............




 

 

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Super Star</font></font> </a> spd
on ‎12-12-2016 08:20 AM

hi,

 

emf32 giant gecko kit is not able to detect/debug external EFM32 on custom board. pl. find attached schematic and simplicty commander screen shot attached herewith. debug led is detecting while selectign DEBUG OUT mode but no conttoller info. is displaying.

what should be the problem.

 

on custome board, i have just given 3.3V to MCU VDD pin. reset circult is connected as per giant gecko kit schematic. giant gecko kit is powered by j-link usb connector.

 

do i need to connect any other component?

doi need to connect crytal?

 

pl. guide.

 

 

schm.jpgdebug mcu.jpgdebug out.jpg

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Hero Employee</font></font> </a> marao
on ‎12-12-2016 03:22 PM

 Hi @spd,

 

You did not specifically mention this - is your target board powered by a supply voltage? Note that the VTARGET pin on the STK or JLink debugger is an input and does not power the target board.

 

Best,

 

Manasa

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Super Star</font></font> </a> spd
on ‎12-13-2016 12:21 AM

@@Manasa, target board is supplied by external power supply thrugh 12V to 3.3V LDO. 

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Ninja</font></font> </a> Marco42
on ‎12-13-2016 01:36 AM

Hi @marao,

 

I am trying to use the "EFR32™ Mighty Gecko Wireless Starter Kit SLWSTK6000A" to debug/program the "EM3585 Connected Lighting Reference Design".

 

I am using the Debug Adapter SLSDA001A for my development kit as described in AN958.

 

The EM3585 board is using the ISA3 - Connector for debugging. I've connected the ISA3 on the EM3585 board with the ISA3 adapter on the SLSDA001A. I've measured all necessary debug connection between the development kit and the EM3585 (SWDIO, SWCLK, RSTN, GND, (Vtarget))

 

The EM3585 is powered by the development kit (provided by the ISA3 connector). The voltage at pin 1 of the debug connector on the development kit is 3.3V. So the Vtarget is definitely connected to the power supply of the EM3585 board. I've measured both SWDIO and SWCLK with my oscilloscope and when uploading the software I can see the CLK provided by the board and the data on SWDIO (which is a digital signal with the voltage levels 3.3V and 0V. Usual it is on 3.3V).

 

So I think my hardware setup is fine.

 

In Simplicity Studio v4 I've changed the "Device hardware" to EM3585 and the "Debug Mode" to OUT.

 

DeviceConfig.png

 

Then I've tried to upload an exmaple application (here: Sniffer, but I've tried more) on the EM3585.

 

uploadedApplication.png

 

When uploading the application there occurs an "Error: Upload failed: -1".

 

EM3585UploadFailed.png

 

Is it even possible to program/debug the EM3585 with my Mighty Gecko Development Kit?

 

Is it possible to read out the device signature with another tool in Studio v4? I'm missing some tools that can give you more information about the errors when trying to upload applications.

 

I hope you can help me out.

 

 

 

Best regards,

 

Marco

 

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Hero Employee</font></font> </a> marao
on ‎12-13-2016 09:59 AM

@Marco42

 

I am not completely sure about this issue, but the app note says that the ISA3 Packet Trace Port Connector interface is not yet supported by the WSTK (Note in Table 2.1 Page 2). So that is most likely why you are seeing these errors. 

What do you mean by reading out the device signature? Can you give more information on what exactly you want to see?

 

 

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Hero Employee</font></font> </a> marao
on ‎12-13-2016 01:02 PM

@spd

Here are a few things you could try:

 

1. Instead of giving an external 3.3V to Vdd on your custom board, you can route the Vmcu pin to the Vtarget on your custom board and then connect it to the GG STK

2. Make sure the cable between the STK and the custom board is short

3. Slow down the jlink speed

 

Let me know if that works. 

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Hero Employee</font></font> </a> marao
on ‎12-13-2016 01:05 PM

@OMogenot

Right now, we don't do any testing on Windows XP and we support only what Microsoft supports officially. Since XP has falled off Microsoft's own list of supported OSes, I don't think we will be able to come up with a resolution for this issue. Since V3 is still available, I would suggest using that for now and then an upgrade of OS would be the best path to take. 

 

Manasa

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Ninja</font></font> </a> Marco42
on ‎12-14-2016 02:33 AM

@marao

 

I saw that on the app note too. But I've measured the physical connection between the development kit debug adapter (SWDIO, SWLCK, RESETN, VTARGET, GND) and the EM3585 debug pins. I could also see a digital signal on SWDIO when trying to upload an application.

 

Here is the pin cofiguration for debug pins at the EM3585 board:

EM3585DebugPins.png

 

Here is the debug connector on the development kit:

 

DevKitDebugCon.png

 

 

I could verify the connection between the controller and the development kit.

 

As far as I know the ISA3 Packet Trace Connector is a debugger that can be used via Ethernet. So I thought that the development kit isn't supporting this feature.

 

"Reading out the device signature" is a feature I know from programming Atmel uC. In the Atmel Studio you can read the device signature. This is an ID to know which device is connected to the programmer/debugger. So when you have read the signature you can be sure to have the correct hardware setup. The Studio gives you more information about failures when trying to program/debug the uC. E.g. when your uC is not powered the Studio is showing you that the target supply voltage is 0V.

 

Best regards,

 

Marco

 

 

 

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Super Star</font></font> </a> spd
on ‎12-15-2016 04:55 AM

@marao,

 

1. Instead of giving an external 3.3V to Vdd on your custom board, you can route the Vmcu pin to the Vtarget on your custom board and then connect it to the GG STK

>>

I tried below both ways but commander did not detect custom board MCU through STK 3700 Kit.

(A) i disconnected VDD_DREG of my custom board from VTAGET and left it open. STK kit VMCU connected to VTARGET 

(B) i reconnected VDD_DREG of my custom board MCU back to VTARGET of STK Kit. 

Now i disconnected VDD_DREG from external 3V3 of my custom board and connected it to VMCU of STK kit.

 

 

2. Make sure the cable between the STK and the custom board is short

>>cable length is max. 10cm.

 

3. Slow down the jlink speed

>> i tried to keep the Jlink slow but could not select it. when i click on connect button on commander, it change the speed selected in combobox and it automatically select and display 12K speed. 

 

do i need to connect crystal ocs or will it work with internal osc by default?

pl.let me know further.

 

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Hero Employee</font></font> </a> marao
on ‎12-16-2016 09:22 AM

@Marco42

 

Yes, the EM35x and EFR32 both use SerialWire for programming and debugging, and, yes, the WSTK is a SerialWire/JTAG debugger.  However, there is no Simplicity Commander or EMDLL support for EM35x parts, so the WSTK really doesn’t know how to talk to an EM35x chip.  I don’t think you are going to be successful here.  If you have access to an ISA3 debugger/programming device,you can use that because Simplicity Studio supports it just like the WSTK via the Devices view.

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Hero Employee</font></font> </a> marao
on ‎12-16-2016 12:01 PM

@spd

 

No, you will not need any external oscillators. Can you send me a screenshot of what you see on the commander with the Flash tab open?

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Super Star</font></font> </a> spd
on ‎12-17-2016 01:46 AM

marao,

 

PFA screenshot of commander flash tab as required. 

Commander_OUT_MODE_FLASH.png

 

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Hero Employee</font></font> </a> marao
on ‎12-19-2016 09:13 AM

Could you have accidentally locked debug access on your device? Can you try unlocking debug access? Also, can you double check your connections and make sure you have connected your pins between custom board and the STK correctly? Please send over a copy of your schematic if you have done all the above and it still does not work. 

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Super Star</font></font> </a> Gio63
on ‎04-22-2017 05:05 AM

 Hi

I have a problem with Simplicity Studio ver 4. I can't configure debug mode with Evaluation Board BRD4001A. In the LAUNCHER perspective of Simplicity doesn't appear any item about DEBUG MODE. In oldest version of Simplicity there was a tool called KIT Manager which allowed me to change DEBUG MODE from MCU MODE  to OUT MODE.

I have attached an imagine about my problem

I hope someone can help me. Thank you

Giovanni

debugmode.jpg

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Hero Employee</font></font> </a> marao
on ‎04-26-2017 11:24 AM

Hi @Gio63,

 

Have you updated simplicity studio v4 to the latest version?

 

Manasa

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Super Star</font></font> </a> pixeltamer
on ‎06-11-2017 01:52 PM

Try using "Simplicity Commander".

You will need to either connect by serial number or by USB .

If by USB you will need to assign a number 0 to 3 using the "Address mode" selection. 

Once you get past this, you can upgrade the programmer firmware to the version of development tools you are using. This is done in the "KIT" section.

At this point, unplug and re-plug-in the programmer (SDK) and the option to use the."Debug Mode" for  IN, OUT, MCU, and OFF should be available to you.

 

by <a href="http://community.silabs.com/t5/Welcome-and-Announcements/Community-Ranking-System-and-Recognition-Program/m-p/140490#U140490"><font color="#000000"><font size="2">Star</font></font> </a> may
on ‎06-21-2017 11:02 AM

 Good day I would like to know if the debugger P & E micro is compatible with silmplicity studio V4