Difference between revisions of "Tracing on NXP LPC4357"
| Line 1: | Line 1: | ||
__TOC__ |
__TOC__ |
||
| − | [[File:KEIL_MCB4300_v1.2.jpg|thumb |
+ | [[File:KEIL_MCB4300_v1.2.jpg|thumb]] |
This article describes how to get started with trace on the NXP LPC4357 series. 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.).<br /> If this is not the case, we recommend to read '''Trace''' chapter in the J-Link User Manual (UM08001).<br /> |
This article describes how to get started with trace on the NXP LPC4357 series. 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.).<br /> If this is not the case, we recommend to read '''Trace''' chapter in the J-Link User Manual (UM08001).<br /> |
||
The NXP LPC4357 series implements tracing via pins only, so a J-Trace is needed to perform tracing on these devices. |
The NXP LPC4357 series implements tracing via pins only, so a J-Trace is needed to perform tracing on these devices. |
||
Revision as of 14:16, 7 April 2017
Contents
This article describes how to get started with trace on the NXP LPC4357 series. 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 LPC4357 series implements tracing via pins only, so a J-Trace is needed to perform tracing on these devices.
Minimum requirements
In order to use trace on the NXP LPC4357 series devices, the following minimum requirements have to be met:
- J-Link software version V6.14a or later
- Ozone V2.22o 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
Sample project
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 on a KEIL MCB4300 v1.2.
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.
Note: The NXP LPC4357 MCU does not support traceclocks higher than 60 MHz due to hardware limits. The CPU clock can be set to 180 MHz, but then a functioning trace setup is not guaranteed.
