Difference between revisions of "EFR32"

From SEGGER Wiki
Jump to: navigation, search
(Created page with "This article covers the Silicon Labs (SiLabs) EFR32 series device. __TOC__ = EFR32MG21xxx family = The SiLabs EFR32MG21xxx are Cortex-M33 MCUs. == Tracing on EFR32MG21xxx s...")
(No difference)

Revision as of 14:52, 25 March 2020

This article covers the Silicon Labs (SiLabs) EFR32 series device.

EFR32MG21xxx family

The SiLabs EFR32MG21xxx are Cortex-M33 MCUs.

Tracing on EFR32MG21xxx series

This section describes how to get started with trace on the SiLabs EFR32MG21xxx MCUs. This section 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).

Note:

  • The sample projects come with a pre-configured project file for Ozone that runs out-of-the box.
  • The following sample project is designed to be used with J-Trace PRO for streaming trace, J-Link Plus for buffer tracing (TMC/ETB trace) and Ozone to demonstrate streaming trace.
  • In order to rebuild the sample project, SEGGER Embedded Studio can be used.
  • All examples are shipped with a compiled .JLinkScriptfile (.pex), should you need the original source it can be requested at support@segger.com.
  • The EFR32MG21xxx device only support 1-bit tracing (1-pin trace). Therefore, overflows can happen when tracing this chip.
    Keep in mind: The higher the MCU clock speed, the higehr is the chance to get overflows.
  • In future, a stalling mode version of the project will be added, using ARM stalling mode to halt the MCU in case of an overflow.
    Please note, that any kind of stalling mode will affect the real time behavior.

Tracing on SiLabs EFR32MGM210 (SiLabs Wireless Gecko xGM210P022)

Minimum requirements

In order to use trace on the ST EFR32MGM210 MCU devices, the following minimum requirements have to be met:

  • J-Link software version V6.64c or later
  • Ozone V3.10f 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 for streaming trace

Streaming trace

The project has been tested with the minimum requirements mentioned above and a SiLabs Wireless Gecko xGM210P022 which can be purchased on the SEGGER Website.

Example project: SiLabs_EFR32MG21_TracePin.zip

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.

Trace clock signal quality

The trace clock signal quality shows multiple trace clock cycles on the tested hardware as reference.

Trace clock signal quality
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