Tracing on ST STM32F437

From SEGGER Wiki
Jump to navigation Jump to search

This article describes how to get started with trace on the ST STM32F437 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 ST STM32F437 MCU implements tracing via pins, so a J-Trace can be used for tracing.

Minimum requirements

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

  • J-Link software version V6.20d or later
  • Ozone V2.46a 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 STM32437I-ES Evalboard. 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.

ST_STM32F437_90MHz_TraceExample.zip


Note: 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: https://www.segger.com/ticket/.

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

Specifics/Limitations

The ST STM32F437 MCU supports traceclockspeeds up to 90 MHz. The evaluation board used for the example project has a board specific limitation, that the jtag pins on the trace debug connector are connected to ground and thus this specific board cannot be debugged over the trace connector. So please make sure the hardware you are using has the trace debug interface wired correctly as described on our webpage or the J-Link User Manual (UM08001).

Tested Hardware

STM32437I-ES