Trace Status

The µVision Status Bar displays Trace progress and error messages whenever SW Trace is running.

Trace Status Message Display

A trace status message displays when:

The target processor is running.
The target stopped due to an error.

During normal, error-free operation, the Running... status is refreshed every 3 seconds. When the target stops without errors, the message area is blank. Any errors that do occur are displayed immediately and remain displayed until the Trace is restarted.

Trace Status Messages

Message	Description
Communication Error	Invalid communication is detected. Incorrect clock settings (based on Core Clock) or HW problems (Trace HW not working) can cause this. See Note below.
HW Buffer Overrun	USB cannot accept data at the speed ULINK is sending it. Try turning off Trace Events you may not really need, or PC Sampling.
SW Buffer Overrun	Internal SW buffer overrun on the PC (this should never happen).
No Synchronization	There are no synchronization packets received from the target. This indicates that the Trace hardware is either not connected or improperly configured.
Data Stream Error	Errors are detected in the Trace Data Stream.
Data Overflow	This indicates that Trace packets couldn't be transmitted because the Trace Port was too busy. The Trace Records dialog shows when the overflow occurred. This happens when too much Trace data is being captured.
Running ...	The target and Trace are both running without any of the above listed errors.
<no message>	The target is stopped with no previous errors.

Note

Applications that change the clock or clock setting in the main() portion of their program may see the Communication Error status. This happens when watch variable initialization (for the Logic Analyzer) occurs before the application sets the "running" clock rate (the Core Clock setting), resulting in the Trace data being received in error. Once the application sets the clock rate to match the Core Clock setting, this error message disappears.

To use Trace in your application before changing the clock setting, configure Trace with the startup (default) clock value then reconfigure Trace clock later (via dialog or by using the CORE_CLK VTreg directly from the command window or some custom load script).