Difference between revisions of "EFM32"
(→SWO) |
(→Minimum requirements) |
||
| (6 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| + | This article describes device specifics of the Silicon Labs EFM32 series devices |
||
| + | |||
__TOC__ |
__TOC__ |
||
| − | This article describes device specifics of the Silicon Labs EFM32 series devices |
||
== SWO == |
== SWO == |
||
Auto SWO speed calculation of J-Link does not work for the Silicon Labs EFM32 series devices. |
Auto SWO speed calculation of J-Link does not work for the Silicon Labs EFM32 series devices. |
||
| − | + | *Normal SWO Speed calculation: <CPUFreq> / n |
|
| − | + | *EFM32 specific:Chip-internally wired to a fixed 14 MHz clock (AUXHFRCO) |
|
For utilities like J-Link SWOViewer or similar: |
For utilities like J-Link SWOViewer or similar: |
||
| − | Select 14 MHz as CPU speed (no matter what the CPU is really running at) to make the normal calculation working |
+ | *Select 14 MHz as CPU speed (no matter what the CPU is really running at) to make the normal calculation working |
| + | |||
| + | == Tracing on EFM32 == |
||
| + | This section describes how to get started with trace on the Silicon Labs EFM32 MCUs. 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). |
||
| + | |||
| + | === EFM32TG11 === |
||
| + | The Silicon Labs EFM32TG11 MCUs implement tracing via on-chip trace buffer (MTB), so a J-Link can be used for tracing. |
||
| + | This feature is supported out-of-the-box from V6.64 and later. |
||
| + | Tracing over pins is not supported by this target device. |
||
| + | |||
| + | ==== Tested Hardware ==== |
||
| + | [[File:EFM32_Tiny_Gecko.jpg|none|thumb|EFM32 Tiny Gecko]] |
||
| + | |||
| + | ==== Minimum requirements ==== |
||
| + | In order to use trace on the Silicon Labs EFM32TG11, the following minimum requirements have to be met: |
||
| + | * J-Link software version V6.64 or later |
||
| + | * Ozone V3.10c or later (if trace and / or the sample project from below shall be used) |
||
| + | * J-Link Plus V10 or higher |
||
| + | |||
| + | 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 ==== |
||
| + | The following sample project is designed to be used with J-Link Plus and Ozone to demonstrate MTB trace. The project has been tested with the minimum requirements mentioned above and a Silicon Labs EFM32 Tiny Gecko evaluation board. The sample project comes with a pre-configured project file for Ozone that runs out-of-the-box. In order to rebuild the sample project, [https://www.segger.com/embedded-studio.html SEGGER Embedded Studio] can be used. |
||
| + | |||
| + | [[Media:SiLabs_EFM32TG11_TraceBuffer.zip | SiLabs_EFM32TG11_TraceBuffer.zip]] |
||
| + | |||
| + | {{Note|The MTB does not support stream tracing.}} |
||
| + | |||
| + | ==== Streaming trace ==== |
||
| + | Streaming trace is not supported on this particular target device. |
||
| + | |||
| + | == EFM32TG11B == |
||
| + | For the device specifics of the Silicon Labs EFM32TG11B device series, please refer to the following article: |
||
| + | [[Silicon_Labs_EFM32TG11B | Silicon Labs EFM32TG11B]] |
||
Latest revision as of 16:24, 15 June 2022
This article describes device specifics of the Silicon Labs EFM32 series devices
Contents
SWO
Auto SWO speed calculation of J-Link does not work for the Silicon Labs EFM32 series devices.
- Normal SWO Speed calculation: <CPUFreq> / n
- EFM32 specific:Chip-internally wired to a fixed 14 MHz clock (AUXHFRCO)
For utilities like J-Link SWOViewer or similar:
- Select 14 MHz as CPU speed (no matter what the CPU is really running at) to make the normal calculation working
Tracing on EFM32
This section describes how to get started with trace on the Silicon Labs EFM32 MCUs. 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).
EFM32TG11
The Silicon Labs EFM32TG11 MCUs implement tracing via on-chip trace buffer (MTB), so a J-Link can be used for tracing. This feature is supported out-of-the-box from V6.64 and later. Tracing over pins is not supported by this target device.
Tested Hardware
Minimum requirements
In order to use trace on the Silicon Labs EFM32TG11, the following minimum requirements have to be met:
- J-Link software version V6.64 or later
- Ozone V3.10c or later (if trace and / or the sample project from below shall be used)
- J-Link Plus V10 or higher
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
The following sample project is designed to be used with J-Link Plus and Ozone to demonstrate MTB trace. The project has been tested with the minimum requirements mentioned above and a Silicon Labs EFM32 Tiny Gecko evaluation board. The sample project comes with a pre-configured project file for Ozone that runs out-of-the-box. In order to rebuild the sample project, SEGGER Embedded Studio can be used.
SiLabs_EFM32TG11_TraceBuffer.zip
The MTB does not support stream tracing.
Streaming trace
Streaming trace is not supported on this particular target device.
EFM32TG11B
For the device specifics of the Silicon Labs EFM32TG11B device series, please refer to the following article: Silicon Labs EFM32TG11B
