µVision User's GuideAbout µVision User Interface Creating Applications Debugging Using the Debugger Simulation 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 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 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 Tracepoint Expressions Tracepoint Intrinsics Tracepoint Limitations Configuring the Trace Hardware 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 Code Coverage Export MTB Trace Import for Code Coverage Debug Commands Debug Functions Simulation Flash Programming Dialogs Utilities Command Line Example Programs Appendix
The System Analyzer is a graphical analysis tool that shows:
System Analyzer can be used with any Arm Cortex-M based device that provides trace.
Open the System Analyzer from the toolbar or via the menu View - Analysis Windows - System Analyzer.
System Analyzer Window
The System Analyzer contains a number of buttons to change the way the data is displayed.
Elements of the display
The following elements are present in the System Analyzer window:
In the System Analyzer window you will find different sections that show power measurement values, events, interrupts, and variable changes.
Change the signal scale manually
To manually change the signal scale in System Analyzer, follow these steps:
Working with power consumption data
Selectable from the context menu, the power data can be filtered. Select 160 kHz filtering to have a great view on all spikes and their height or “special” noise, such as overshoots:
Select 5 kHz to have a great view of what’s hidden in the noise, for example current drain of the target's internal pull-up resistors:
You can calibrate the power measurement offset introduced by ULINKplus by using the Zero Point Adjustment in the context menu:
This will compensate for the offset and show 0 mA at the current position. You can also remove this adjustment at a later point in time, if required.
Working with signals
Running through the power measurement results, use the following hints to create a convenient signal display:
You can zoom in or out of signals using the mouse wheel or the zoom buttons:
Right-click on any signal to reach the context menu.
of your data.