ULINK: TRACE DATA LOST OR WRONG

Information in this article applies to:

• Serial-Wire Debug and Realtime Trace on Cortex-M3 based devices

SYMPTOM

Trace data is lost or wrong when using Serial-Wire Realtime Trace on a Cortex-M3 based device and Trace: Communication Error is displayed in µVision Status Bar.

CAUSE

The main reason for wrong or lost trace data or Trace Communication Error is a misconfigured Core Clock under Cortex-M Target Driver Setup. The Core Clock must be the same as the CPU clock to get correct time values in the µVision Status Bar and register window. It is also essential to get correct trace information over Serial-Wire Output (SWO) when Trace Enable is selected.

RESOLUTION

Configure Core Clock under Cortex-M Target Driver Setup with the correct value. The value is related to the CPU clock. For example if the CPU runs at 72 MHz then the Core Clock must also be set to 72 MHz. When Trace is configured correctly, then Trace: Running ..." is displayed in µVision Status Bar during Target Debug Session.

Core Clock corresponds to the VTReg CORE_CLK. Within a Target Debug Session it is possible to adjust the Core Clock by changing the value of VTReg CORE_CLK. This can also be done in a debugger script.

MORE INFORMATION

• Refer to Trace Configuration in the ULINK2 User's Guide.
• Application Note 197: Serial-Wire Debug and Realtime Trace on STM32 Devices.

Last Reviewed: Tuesday, November 25, 2008