Keil Logo

Status Bar

The Status Bar displays information and messages about the current µVision command. The Status Bar is located at the bottom of the µVision screen and must be enabled through the menu View - Status Bar.

Status Bar

The following message types are displayed:

Debugging and tracing messages depend on the currently used debug adapter and are described in:

Client mode is shown for the secondary debug connection in a multi-core environment.

Debug channel is the active debug adapter. Can be the name of the AGDI Debug Driver or Simulation when debugging with the Simulator.

Execution timers display time information. Hover the mouse over the field to view all available timers. Right click on the field to switch to another one or reset a timer. Execution timers are reset the following way:

  • Simulator: All Execution Timer values are reset upon CPU RESET.
  • HW Target; In particular for Cortex-M:
    Elapsed Time (t0) is not reset upon CPU RESET, but for each new debugging session. The value cannot be reset manually. This information is identical to the register field SEC of the Registers Window.
    Stop Watch(tx) are reset upon CPU RESET; Can be reset manually. You may use these timers to measure the time spent for a specific portion of the code.

Cursor position shows the cursor position in the current editor file (L: line number, C: column number).

Editor and keyboard Status:

  • CAP: keyboard is in Caps-Lock status.
  • NUM: keyboard is in Num-Lock status.
  • SCRL: keyboard is in Scroll-Lock status.
  • OVR: keyboard is in over-type mode overwriting characters while typing.
  • R/W or R/O: current editor file attribute. R/W full read/write access. R/O read-only access preventing text modifications.

Status Bar for Armv8-M Architecture

The Status Bar shows additional information for devices based on the Armv8-M architecture that have enabled the TrustZone for Armv8-M.

Status Bar

The Status Bar shows whether the application, debugger, or trace is running in the Secure or Non-Secure memory area. All combinations are possible. The red color of a message should raise your attention that limitations exist for the debug connection. For example, when the debugger has no rights to access a secure memory area and the application is executing that code.

The CPU State corresponds to the Secure or Non-Secure entry in the Registers Window.

CPU:... Description
Secure Application code is in a secure memory area.
Non-Secure Application code is in a non-secure memory area.

The Debugger State shows the access rights of the debugger.

Debug:... Description
Secure Debugger can access application code placed in secure and non-secure memory areas.
Non-Secure Debugger can access application code placed in non-secure memory area. The color of the message turns red when debugging code in the secure memory area. Then, debug information is not available.

The Trace Message shows the access rights of the trace unit and the trace status. For a description of the trace status, refer to the documentation of your debugger.

... Trace: Description
Secure Trace unit can access application code placed in secure and non-secure memory areas.
Non-Secure Trace unit can access application code placed in non-secure memory area. The color of the message turns red when tracing code in the secure memory area. Then, trace information is not available.

Related Knowledgebase Articles

  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.