1.1.1. RealView Debugger concepts and terminology

The following terminology is used throughout the RealView Debugger documentation suite to describe debugging concepts:

Debug target

A piece of hardware or simulator that runs your application image. A hardware debug target might be a single processor, a multiprocessor core, or a development board containing a number of processors.

Target Access

A piece of hardware or software simulator that provides the interface between the debugger and the debug target.

Connection

The link between the debugger and the debug target.

Single connection access

The RealView Debugger base product enables you to carry out debugging tasks in single-processor debugging mode, that is you can connect only to a single processor. For a multiprocessor core, such as MPCore™, you can connect to only one processor on that core.

Multiprocessor access

RealView Debugger has been developed as a fully-featured debugger for working with multiprocessor debug target systems. Multiprocessor access enables you to maintain one or more connections to debug targets. Multiprocessor access is a separately licensed feature of RealView Debugger.

DSP

RealView Debugger has been developed to provide full debugging functions when working with a range of debug target systems including Digital Signal Processors (DSPs). DSP-based debugging is a separately licensed feature of RealView Debugger. You must also have a multiprocessor debugging license.

OS

Operating systems (OSs) provide software support for applications running on a target. For example, Real Time Operating Systems (RTOSs) are operating systems that are designed for systems that interact with real-world activities where time is critical.

Multithreaded operation

When RealView Debugger is used with a suitable OS-aware plugin it can present thread information and scope some debugging operations to specific threads.

Copyright © 2002-2006 ARM Limited. All rights reserved.ARM DUI 0181H
Non-Confidential