 µVision User's Guide legacy | |
| Home Products Events Support | |
Technical Support
On-Line Manuals
µVision User's Guide
µVision3 Overview User Interface Creating Applications Utilities 
Debugging Using the Debugger 
CPU Simulation Start Debugging Application Program Execution Debug Windows and Dialogs Breakpoints Code Coverage CPU Registers Disassembly Window Logic Analyzer Setup Setup in Detail Restrictions Memory Window Memory Map Output Window - Command Debug Commands Variables and Registers Debug Functions Execution Profiler Performance Analyzer Serial Window Symbol Window Toolbox Watch Window Expressions Constants System Variables Peripheral Variables I/O Ports Serial Ports Program Variables (Symbols) Line Numbers Bit Addresses Type Specifications Operators Differences Between µVision3 and C Expression Examples 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 Accesses Command Input from File Preset I/O Ports or Memory Contents Write Debug Output to a File Keyboard Shortcuts Debug Commands Debug Functions Simulation Flash Programming Dialogs Example Programs Command Line AppendixCode Coverage
The µVision3 debugger provides a code coverage function that marks the code that has been executed. Code coverage helps to ensure you have thoroughly tested your application and helps you tune your testing strategy. You can use this feature to determine the sections of code that have not yet been exercised.
The Code Coverage dialog provides information and statistics. You can output this information in the Output Window – Command page using the COVERAGE debug command.
In the debug window, lines of code that have been executed are marked as follows in the left column:
No Code - Lines with no code are marked with a light gray block.
Unexecuted Code - Unexecuted lines (instructions) are marked with a dark gray block.
Executed Code - Fully-executed lines (instructions) are marked with a green block.
Branch Condition True - A cyan (blue) block indicates that the condition for this branch instruction has only been true and the branch was always taken.
Branch Condition False - An orange block indicates that the condition for this branch instruction has never been true and the branch was never taken.
Note
- A green block on a branch instruction indicates that both the true and false conditions have occurred.
| Contact Site Map Press Privacy | Copyright © 2010 Keil™, An ARM® Company. All rights reserved. |
