Tracing on Silicon Labs EFM32GG990

From SEGGER Wiki
Jump to navigation Jump to search

This article describes how to get started with trace on the Silicon Labs EFM32GG990 MCU. This article assumes that there is already a basic knowledge about trace in general (what is trace, what different implementations of trace are there, etc.). If this is not the case, we recommend to read Trace chapter in the J-Link User Manual (UM08001). The Silicon Labs EFM32GG990 MCU implements tracing via pins , so a J-Trace can be used for tracing.

Minimum requirements

In order to use trace on the Silicon Labs EFM32GG990 devices, the following minimum requirements have to be met:

  • J-Link software version V6.20f or later
  • Ozone V2.50c or later (if streaming trace and / or the sample project from below shall be used)
  • J-Trace PRO for Cortex-M HW version V1.0 or later

To rebuild the project our IDE Embedded Studio can be used. The recommended version to rebuild the projects is V6.30. But the examples are all prebuild and work out-of-the box with Ozone, so rebuilding is not necessary.

Sample project

Streaming trace

The following sample project is designed to be used with J-Trace PRO and Ozone to demonstrate streaming trace. The project has been tested with the minimum requirements mentioned above and a EFM32GG-DK3750 evaluation board. The sample project comes with a pre-configured project file for Ozone that runs out-of-the box. Please note that this particular needs additional hardware settings to enable external trace probes, see section Specifics/Limitations. In order to rebuild the sample project, SEGGER Embedded Studio can be used.


The example is shipped with a compiled .JLinkScriptfile, should you need the original source, please get in touch with SEGGER directly via our support system:

To create your own .JLinkScriptfile you can use the following guide as reference: How_to_configure_JLinkScript_files_to_enable_tracing


The EFM32GG-DK3750 evaluation board comes with a development kit user interface consisting of the TFT-LCD display together with the buttons PB1 to PB4 and the 5-way joystick located below. This interface needs to be used to enable ETM trace and external debug probes. Per default the evaluation board is set to use the internal J-Trace OB. To enable streaming trace on your external J-Trace PRO folow these steps:

  1. Press button PB2 below the menu point "CFG"
  2. Navigate to the entry "Debug Control" with the joystick and select "IN"
  3. Navigate to the entry "ETM Trace" with the joystick and select "ON"
  4. Press PB4 ("Save") to save this settings
  5. Press PB1 ("Back") twice to return to the main screen
  6. If everything was successfull in the top left corner it should read "Debug: TRACE IN"

For more information see the "Development Kit EFM32GG-DK3750" user manual.

Tested Hardware


Reference trace signal quality

The following pictures show oscilloscope measurements of trace signals output by the "Tested Hardware" using the example project. All measurements have been performed using a Agilent InfiniiVision DSO7034B 350 MHz 2GSa/s oscilloscope and 1156A 1.5 GHz Active Probes. If your trace signals look similar on your trace hardware, chances are good that tracing will work out-of-the-box using the example project. More information about correct trace timing can be found at the following website.

Rise time

The rise time of a signal shows the time needed for a signal to rise from logical 0 to logical 1. For this the values at 10% and 90% of the expected voltage level get used as markers. The following picture shows such a measurement for the trace clock signal.

TCLK rise time

Setup time

The setup time shows the relative setup time between a trace data signal and trace clock. The measurement markers are set at 50% of the expected voltage level respectively. The following picture shows such a measurement for the trace data signal 0 relative to the trace clock signal.

TD0 setup time