Difference between revisions of "nRF52833"
(Created page with "This article features the Nordic nRF52833 MCU. __TOC__ =Tracing on nRF52833= This article describes how to get started with trace on the Nordic nRF52833 MCU. This article ass...")
Latest revision as of 10:51, 29 November 2019
This article features the Nordic nRF52833 MCU.
Tracing on nRF52833
This article describes how to get started with trace on the Nordic nRF52833 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 Nordic nRF52833 MCU implements tracing via pins, so a J-Trace can be used for tracing.
In order to use trace on the Nordic nRF52833 n M2351 MCU devices, the following minimum requirements have to be met:
- J-Link software version V6.56a or later
- Ozone V2.70a 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
The following sample project (for Nordic nRF52833-DK) 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 nRF52833-DK 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.
- As for many other MCUs from Nordic, the trace clock for this MCU is not linked to the CPU clock.
- The Nordic nRF52833-DK comes without a trace pin header. It has to be soldered onto the board by the user.
- To make trace work correctly on this evaluation board, the SW7 switch needs to be set to "Alt.".
This sample project was tested on a Nordic nRF52833-DK evaluation board.
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.
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.
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.