|
||
| Products Download Events Support Videos | ||
Technical Support
On-Line Manuals
ULINKpro User's Guide
Introduction
Hardware Description
Setup ULINKpro
Using ULINKpro
Configure Cortex-M Devices for Tracing
µVision Windows
Trace Status
Component Viewer
Event Recorder
System Analyzer
Debug (printf) Viewer
Performance Analyzer
Instruction Trace
Trace Data (Cortex-M)
Trace Navigation (Cortex-M)
Trace Exceptions
Event Counters
Troubleshooting
Appendix
Trace Status
The µVision Status Bar displays trace status messages whenever tracing has been enabled. Additional information is available in the general description of the Status Bar for CPUs that have enabled TrustZone for Armv8-M.
The trace status:
- Displays progress and error messages when the target processor is running.
- Refreshes the Running... message every 3 seconds during error-free operations.
- Is blank, when tracing is stopped without an error.
- Displays the error message in red when the target stopped with an error.
- Keeps the error message displayed until tracing is restarted.
| Trace Status | Description |
|---|---|
| Communication Error | An invalid communication has been detected. Incorrect clock settings or hardware problems cause this message. Applications that change the Core Clock in the main() program may throw this message when data are captured incorrectly. This error message disappears once the Core Clock has been adjusted to the system settings. |
| HW Buffer Overrun | The USB port cannot accept data at the speed the adapter is sending them. Turn off trace events you do not need, or skip PC Sampling. |
| SW Buffer Overrun | Internal SW buffer overrun on the PC. Adjust the SWO Clock Prescaler of the trace port or the Max Clock of the debug port. |
| No Synchronization | Synchronization packets are not received from the target. The trace hardware is either not connected or configured improperly. Help can be found in Configure Cortex-M Devices for Tracing. Hints might be available in the device data sheet. |
| Data Stream Error | Errors are detected in the Trace Data Stream. |
| Data Overflow | The Trace Port was too busy, and not all trace packets could be transmitted. This happens when too many trace data are captured. Decrease the number of trace events. The Instruction Trace Window shows where the overflow occurred. |
| Running ... | The target system itself and tracing operations are running without errors. |
| <is blank> | The target stopped without throwing an error. |
ProductsDevelopment Tools |
Hardware & Collateral |
Downloads |
Support |
Contact |
 |
||||