Tracing on NXP Kinetis MKL25
This article describes how to get started with trace on the NXP Kinetis MKL25 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 NXP Kinetis MKL25 MCU implements tracing via via on-chip trace buffer (MTB), so a J-Link can be used for tracing. Tracing over pins is not supported by this target device.
In order to use trace on the NXP Kinetis MKL25 MCU devices, the following minimum requirements have to be met:
- J-Link software version V6.30k or later
- Ozone V2.56i 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.
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 FRDM-KL25Z 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. The recommended version to rebuild the projects is ES V6.30. But the examples are all pre-build and work out-of-the box with Ozone, so rebuilding is not necessary.
Note: The MTB does not support stream tracing.
Streaming trace is not supported on this particular target device.