|
||
| Products Download Events Support Videos | ||
Technical Support
On-Line Manuals
µVision User's Guide
About µ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
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
Debug Commands
Debug Functions
Simulation
Flash Programming
Dialogs
Utilities
Command Line
Example Programs
Appendix
Start Energy Measurement without Debug
In debug mode, a connection to the target is required, which implies that the CoreSight™ debug logic consumes additional energy. For pure energy measurement (without CoreSight energy consumption), use the Energy Measurement without Debug mode .
Debug — Energy Measurement without
Debug starts the energy measurement without a debug connection.
In this mode, you can safely remove the debug cable.
Click the Run button or press
F5 to start the energy measurement
Click the Stop button to stop the
energy measurement.
Available debug functionality
In this mode, there is no target debug functionality available. This means that all debug related windows are either empty or show no data (for example Registers, Disassembly, Call Stack + Locals, Memory, Watch, Event Recorder, and Component Viewer).
The following windows are active and accessible:
- The Command window accepts VTREG commands for ULINKplus. It is possible to change the states of I/O pins, retrieve the current and voltage values, and to enable or disable power measurement. This also works using a debug script.
- The ULINKplus window shows the values of all ULINKplus VTREGs and will accept changes for the I/O configuration, pin levels, and power measurement enable/disable.
- The System Analyzer window displays the current and voltage measured.
Note
This option is only available if you have specified the ULINKplus debug adapter in the dialog Options for Target — Debug. Using any other debug adapter, will show the option greyed out:
ProductsDevelopment Tools |
Hardware & Collateral |
Downloads |
Support |
Contact |
 |
||||