| Copyright © 2002-2011 ARM. All rights reserved. | ARM DUI 0181N |
| Non-Confidential | ID052111 |
 PDF version | |
| Home > About RealView Debugger > RealView Debugger concepts and terminology |
| |||
| Home > About RealView Debugger > RealView Debugger concepts and terminology | |||
RealView Debugger enables you to debug your embedded applications and to have complete control over the flow of the execution so that you can quickly isolate and correct errors.
The following terminology is used throughout the RealView Debugger documentation suite when describing debugging concepts:
The Code window is the starting point for all your debugging tasks and gives you access to features in the product. It displays connection state information and source code views, gives access to other windows, handles CLI commands, and displays debugger messages.
The link between the debugger and the target. RealView Debugger enables you to connect to one or more targets, depending on your application debugging requirements.
A Debug Configuration defines a debugging environment for your development platform.
The Debug Interface identifies the targets on your development platform, and provides the mechanism that enables RealView Debugger to communicate with those targets. The Debug Interface corresponds directly to a hardware run control unit or a software interface to simulated targets.
The Development Platform contains the components, either hardware or simulated, that you are using to develop your application. It can include:
a base board, such as an Integrator/CP
peripherals
one or more ARM architecture-based processors
CoreSight™ components.
OS-awareness is a feature provided by RealView Debugger that enables you to:
debug applications running on an embedded OS development platform, such as a Real-Time Operating System (RTOS)
present thread information and scope some debugging operations to specific threads.
You must obtain and install the required OS-awareness plug-in.
A Target is the part of your development platform to which RealView Debugger can connect, and on which debugging operations can be performed. A target can be:
A runnable target, such as an ARM architecture-based processor. When connected to a runnable target, you can perform execution-related debugging operations on that target, such as stepping and tracing.
A non-runnable CoreSight component. CoreSight components provide a system-wide solution to real-time debug and trace.
These can be hardware or software targets.
See also
the following in the RealView Debugger User Guide:
| Copyright © 2002-2011 ARM. All rights reserved. | ARM DUI 0181N |
| Non-Confidential | ID052111 |
| PDF version | |
| Home > About RealView Debugger > RealView Debugger concepts and terminology |