Difference between revisions of "Tracing on NXP LPC1758"

From SEGGER Wiki
Jump to: navigation, search
(Created page with "__TOC__ This article describes how to get started with trace on the NXP LPC1758 series. This article assumes that there is already a basic knowledge about trace in general (w...")
 
(Sample project)
Line 15: Line 15:
 
[[Media:NXP_LPC1758_Trace_Example_pex.zip | NXP_LPC1758_Trace_Example.zip]]
 
[[Media:NXP_LPC1758_Trace_Example_pex.zip | NXP_LPC1758_Trace_Example.zip]]
   
'''Note:''' The example is shipped with a compiled .JLinkScriptfile, should you need the original source it can be requested at [mailto:support@segger.com support@segger.com]
+
'''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 project as reference: [https://wiki.segger.com/Tracing_on_ST_STM32F407_(SEGGER_Cortex-M_Trace_Reference_Board) Tracing on SEGGER_Cortex-M_Trace_Reference_Board]
 
To create your own .JLinkScriptfile you can use the following project as reference: [https://wiki.segger.com/Tracing_on_ST_STM32F407_(SEGGER_Cortex-M_Trace_Reference_Board) Tracing on SEGGER_Cortex-M_Trace_Reference_Board]

Revision as of 15:56, 13 August 2020

This article describes how to get started with trace on the NXP LPC1758 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 LPC1758 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 LPC1758 series devices, the following minimum requirements have to be met:

  • J-Link software version V6.40 or later
  • Ozone V2.60h 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 MCB 1700 Rev. 1.0. 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.

NXP_LPC1758_Trace_Example.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 project as reference: Tracing on SEGGER_Cortex-M_Trace_Reference_Board

Tested Hardware

KEIL MCB 1700 Rev. 1.0

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