Keil Logo

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 Editor Window Event Recorder Setup Event Recorder Event Recorder Window Events Filtering Event Statistics Window Post-mortem Analysis Event Viewer Execution Profiler Instruction Trace Window System Analyzer Usage tips Save System Analyzer Contents Statistics 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/M33/M35P and Cortex-M55 Nested Vector Interrupt Controller System Control and Configuration System Tick Timer Fault Reports Memory Protection Unit Security Attribution Unit M-Profile Vector Extension (MVE) 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 Memory Attribution Specifiers 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

Program Variables (Symbols)

Symbols are representations of source code identifiers, such as the names of applications, modules, variables, functions, special function registers, or virtual registers. Usually, symbols are associated with debug information, for example: type, scope, or location of the identifier they represent. Symbols allow you to use the names of identifiers as defined in the original source code.

The general form of a symbol name is:

ExecName represents the application name as defined in the field Options for Target - Output - Name of Executable. Must be preceded with a double backslash (\\).
Path represents the path of the source code file. Separate folders from sub-folders with a slash (/). Must end with a slash (/). Path can have an absolute or relative notation.
Module represents the name of a source module ( *.c, *.cpp). Can be preceded with a Path. Must begin with a backslash (\). Module names can be queried from the Command Window with the debugging command: DIR module
Identifier represents a source code object. Must be separated from Module with a backslash (\). Can be used standalone and without backslash when unique in the application. Identifier can be a:
  • code line number.
  • scalar variable (char, int, long, float, double).
  • composite variable (array, structure, file).
  • function.
  • meaningful combination of the above.

Examples and further explanations:

Using Memory Attribution Specifiers

Accessing secure memory

Using different specifiers for example in the Memory Window, access to program variables located in secure memory may not be possible:

Accessing non-secure memory

When trying to access a program variable located in secure memory using the non-secure specifier (&NS:SystemCoreClock), access is denied.

  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.