µVision User's GuideAbout µVision User Interface Creating Applications Debugging Start Debugging Start Energy Measurement without Debug Application Program Execution Debug Windows and Dialogs Breakpoints Window Call Stack and Locals Window Code Coverage Command Window Component Viewer Disassembly Window Event Recorder Setup Event Recorder Event Recorder Window Events Filtering Event Statistics Window Event Viewer Execution Profiler Instruction Trace Window System Analyzer Usage tips Restrictions Logic Analyzer Setup Setup in Detail Restrictions Cortex-M Trace Configuration Memory Map Memory Window Performance Analyzer Registers Window Serial Window Debug (printf) Viewer Symbols Window System Viewer Adding System Viewer Windows System and Thread Viewer Thread States Toolbox Trace Data Window Trace Navigation Trace Exceptions Event Counters ULINKplus Window Watch Window Core Peripherals Cortex-M0 and Cortex-M0+ Nested Vector Interrupt Controller System Control and Configuration System Tick Timer Fault Reports (Cortex-M0+ only) Cortex-M3, Cortex-M4, and Cortex-M7 Nested Vector Interrupt Controller System Control and Configuration System Tick Timer Fault Reports Memory Protection Unit Cortex-M23 and Cortex-M33 Nested Vector Interrupt Controller System Control and Configuration System Tick Timer Fault Reports Memory Protection Unit Security Attribution Unit Debug Scripting Expressions Constants System Variables Peripheral Variables I/O Ports Serial Ports Program Variables (Symbols) Fully Qualified Symbols Non-Qualified Symbols Literal Symbols Using Symbols Line Numbers Bit Addresses Type Specifications Operators Differences between µVision and C Expression Examples Code and Data Trace (Cortex-M) Trace Features Configuring Trace Tracepoint Expressions Tracepoint Intrinsics Tracepoint Limitations Tracepoint Marks Tips and Tricks Review Peripherals and CPU Configuration Simulate I/O Ports Simulate Interrupts and Clock Inputs Simulate external I/O Devices Assign Serial I/O to a PC COM Port Check Illegal Memory Access Command Input from File Preset I/O Ports or Memory Contents Write Debug Output to a File Keyboard Shortcuts TPIU Initialization after RESET (Cortex-M) Prevent Opening Files Show Japanese Messages Debug Commands Debug Functions Simulation Flash Programming Dialogs Utilities Command Line Example Programs Appendix
The Event Viewer displays thread and exception execution over time. To display the timing information it uses trace information generated by Cortex-M3, M4, M7, M23, and M33 devices and requires a suitable debug adapter.
Prerequisites for using the Event Viewer
In order to view the thread execution over time, configure the target as described in:
Using the Trace Configuration dialog of these adapters you should configure the following:
ULINKpro and ULINKplus allow you to display interrupts and exceptions. In this dialog, enable Trace Events - EXCTRC: Exception Tracing to see the exception execution over time.
ULINK2 and J-Link do not offer exception tracing due to limited SWO trace bandwidth.
Using Event Viewer
Open the window with Debug - OS Support - Event Viewer.
Load... imports the thread- and exception-switching history previously saved in a file (*.UVTSK). Data can be analyzed off-line.
Save... stores the thread- and exception-switching history in a file (*.UVTSK) for future analysis.
? opens this help.
Time fields show:
Zoom buttons change the time scale:
Update Screen buttons control the screen output.
Jump to buttons synchronize the event with:
Transition buttons snap the Reference Line to the next transition point. Highlight a thread name and click:
All Threads graph
The All Threads graph shows event-switching occurrences with a blue X.
Blue opening brackets < (left red circle in the picture) indicate event-switching occurrences that cannot be resolved on the graphical scale. You can zoom-in at those points to view detailed event switches.
The red opening bracket < (right red circle in the picture) indicates event-switching occurrences that cannot be resolved on the graphical and time scale. Zooming in at those points will not deliver details on the time scale. The events are shown as if occurred at the same time. This is due to lack of timing information. Select a smaller number for Timestamps Prescaler in Options for Target - Debug - Settings - Trace.
Additional mouse and key commands
Related Knowledgebase Articles
of your data.