| Copyright © 2003-2011 ARM. All rights reserved. | ARM DUI 0255M |
| Non-Confidential | |
 PDF version | |
| Home > Glossary |
| |||
| Home > Glossary | |||
The following terminology is used in the documentation provided with ARM® RealView® Development Suite (RVDS):
See Procedure Call Standard for the ARM Architecture.
The ABI for the ARM Architecture is a collection of specifications, some open and some specific to ARM architecture, that regulate the inter-operation of binary code in a range of ARM architecture-based execution environments. The base standard specifies those aspects of code generation that must be standardized to support inter-operation and is aimed at authors and vendors of C and C++ compilers, linkers, and runtime libraries.
A technique used by RealView ICE (RVI) where it sends out a clock signal and then waits for the returned clock before generating the next clock pulse. The technique enables the RVI debug unit to adapt to differing signal drive capabilities and differing cable lengths.
A bus protocol that supports separate address/control and data phases, unaligned data transfers using byte strobes, burst-based transactions with only start address issued, separate read and write data channels to enable low-cost DMA, ability to issue multiple outstanding addresses, out-of-order transaction completion, and easy addition of register stages to provide timing closure.
The AXI protocol also includes optional extensions to cover signaling for low-power operation.
AXI is targeted at high performance, high clock frequency system designs and includes a number of features that make it very suitable for high speed sub-micron interconnect.
On-chip communications standard for high-performance 32-bit and 16-bit embedded microcontrollers.
A bus protocol with a fixed pipeline between address/control and data phases. It only supports a subset of the functionality provided by the AMBA AXI protocol. The full AMBA AHB protocol specification includes a number of features that are not commonly required for master and slave IP developments and ARM recommends only a subset of the protocol is usually used. This subset is defined as the AMBA AHB-Lite protocol.
See Also Advanced Microcontroller Bus Architecture and AHB-Lite.
See Advanced High-performance Bus.
CoreSight™ supports access to a system bus infrastructure using the AHB Access Port (AHB-AP) in the Debug Access Port (DAP). The AHB-AP provides an AHB master port for direct access to system memory. If an alternate bus protocol is implemented, you can use an AHB bridge to map transactions. For example, you can use an AHB to AXI bridge to enable access to an AXI bus matrix.
CoreSight also supports AHB bus tracing using an AHB Trace Macrocell (HTM).
See Also Advanced eXtensible Interface, AHB Trace Macrocell, CoreSight, and Debug Access Port.
See AHB Access Port.
A subset of the full AMBA AHB protocol specification. It provides all of the basic functions required by the majority of AMBA AHB slave and master designs, particularly when used with a multi-layer AMBA interconnect. In most cases, the extra facilities provided by a full AMBA AHB interface are implemented more efficiently by using an AMBA AXI protocol interface.
The AHB Trace Macrocell is a trace source that makes bus information visible that cannot be inferred from the processor trace using an ETM:
An understanding of multi-layer bus utilization.
Software debug. For example, visibility of access to memory areas and data accesses.
Bus event detection for trace trigger or filters, and for bus profiling.
See Also Advanced High-performance Bus.
See Advanced Microcontroller Bus Architecture.
The AMBA Trace Bus transfers trace data through CoreSight infrastructure in a SoC. Trace sources are ATB masters, and sinks are ATB slaves. Link components provide both master and slave interfaces.
See Also CoreSight.
See Debug Access Port.
The ARM librarian, that enables you to create libraries of files, such as object files.
See Also ARM Compiler toolchain and RealView Compilation Tools (RVCT).
The ARM assembler.
See Also ARM Compiler toolchain and RealView Compilation Tools (RVCT).
The ARM compiler for C and C++ code.
See Also ARM Compiler toolchain and RealView Compilation Tools (RVCT).
The ARM linker.
See Also ARM Compiler toolchain and RealView Compilation Tools (RVCT).
ARM Advanced SIMD Extension is an optional component of ARMv7 architecture. It is a 64/128 bit hybrid SIMD technology targeted at advanced media and signal processing applications and embedded processors. It is implemented as part of the ARM core, but has its own execution pipelines and a register bank that is distinct from the ARM core register bank.
ARM Advanced SIMD Extension supports integer, fixed-point, and single-precision floating-point SIMD operations. These instructions are available in both ARM and Thumb®-2.
ARM Advanced SIMD Extension is also known as ARM NEON Technology (NEON™).
The ARM Compiler toolchain is a suite of tools, together with supporting documentation and examples, that enables you to write and build applications for the ARM family of processors. The ARM Compiler toolchain supersedes RealView Compilation Tools
See Also armar, armasm, armcc, armlink, fromelf, and RealView Compilation Tools (RVCT).
A word that encodes an operation for an ARM processor operating in ARM state. ARM instructions must be word-aligned.
See Also Thumb instruction, Thumb-2 instruction, and Thumb-2EE instruction.
A plug-in to the ARM Workbench IDE that enables non-intrusive analysis of embedded software over long periods of time, on targets running at operational frequencies of up to 400 MHz. Targets can be Real-Time System Models (RTSMs) and hardware targets. ARM Profiler is provided with RVDS Professional edition.
This is not the same as the older ARM Profiler tool, armprof.
See Also Real-Time System Model (RTSM), RealView ICE (RVI), and RealView Trace (RVT) and RealView Trace 2 (RVT2).
A processor that is executing ARM instructions is
operating in ARM state. The processor switches to Thumb state (and
to recognizing Thumb instructions) when directed to do so by a state-changing
instruction such as BX or BLX.
See Also Jazelle® state, Thumb state, and ThumbEE state.
The hardware and software that enables security features to be integrated throughout a SoC device.
ARM Workbench IDE is based around the Eclipse IDE, and provides additional features to support the ARM development tools provided in RVDS.
See Also RealView Development Suite (RVDS).
See AMBA Trace Bus.
See Advanced eXtensible Interface.
See Board/Chip Definition (BCD) file.
In the context of the ARM architecture, big-endian is defined as the memory organization in which the least significant byte of a word is at a higher address than the most significant byte.
See Also Little-endian.
RealView Debugger uses this term to refer to the
top-level configuration file, normally called rvdebug.brd,
that references one or more other configuration files. A board file contains:
the Debug Configuration (connection-level) settings
references to the Debug Interface configuration file that identifies the targets on the development platform
references to any Board/Chip Definition (BCD) files assigned to a Debug Configuration.
See Also Board/Chip Definition (BCD) file, Debug Configuration, Debug Interface, Development platform, and Target.
In the context of RealView Debugger, a BCD file
enables you to define the memory map and memory mapped registers
for a target development board or processor. Various BCD files are
provided with RVDS for ARM development boards (for example CP.bcd for
the Integrator®/CP development
board) and processor core modules (for example CM940T.bcd for
the ARM940T™ processor).
See Also Board file and Debug Configuration.
In the context of RealView Debugger, a unit within a Chained breakpoint that combines with other breakpoint units to create a complex hardware breakpoint.
See Also Chained breakpoint and Hardware breakpoint.
See ABI for the ARM Architecture (base standard).
In DWARF, this is an address on the stack specifying where the call frame of an interrupted function is located.
Captive threads are all threads that can be brought under the control of RVDS. Special threads, called non-captive threads, are essential to the operation of Running System Debug (RSD) and so are not under debugger control. Non-captive threads are grayed out in the GUI.
See Also Running System Debug.
See Canonical Frame Address.
In the context of RealView Debugger, a complex breakpoint that comprises multiple hardware breakpoint units.
See Also Breakpoint unit, Conditional breakpoint, Data breakpoint, and Hardware breakpoint.
In the context of RealView Debugger, a complex tracepoint that comprises multiple tracepoint units.
See Also Tracepoint and Tracepoint unit.
A breakpoint that has one or more condition qualifiers assigned. The breakpoint is activated when all assigned conditions are met, and either stops or continues execution depending on the action qualifiers that are assigned. The condition normally references the values of program variables that are in scope at the breakpoint location.
See Also Chained breakpoint, Data breakpoint, Hardware breakpoint, Instruction breakpoint, Software breakpoint, and Unconditional breakpoint.
In the context of an ARM Integrator development board, an add-on development board that contains an ARM architecture-based processor and local memory. Core modules can run standalone, or can be stacked onto Integrator development boards.
See Also Integrator.
CoreSight is an infrastructure that enables the debugging, monitoring, and optimization of performance of a complete System on Chip (SoC) design.
See Also CoreSight ECT, CoreSight ETB, CoreSight ETM, Trace Funnel, and Trace Port Interface Unit.
CoreSight ECT is a control and access component that supports the interaction and synchronization of multiple triggering events within a SoC:
See Also CoreSight, Cross Trigger Interface, Cross Trigger Matrix, and Embedded Cross Trigger.
CoreSight ETB is a trace sink that provides on-chip storage of trace data using a configurable sized RAM.
See Also CoreSight, CoreSight ETB, Embedded Trace Buffer, and Embedded Trace Macrocell.
CoreSight ETM is a trace source that provides processor driven trace through an ATB compliant trace port.
See Also AMBA Trace Bus, CoreSight, CoreSight ETB, and Embedded Trace Macrocell.
See Current Program Status Register.
The Cross Trigger Interface provides the interface between a component or subsystem and the Cross Trigger Matrix. The system requires a CTI for each subsystem that supports cross triggering.
See Also CoreSight, CoreSight ECT, Cross Trigger Matrix, and Embedded Cross Trigger.
The Cross Trigger Matrix combines the trigger requests generated from CTIs and broadcasts them to all CTIs as channel triggers. This enables subsystems to interact, cross trigger, with one another. CTMs can be connected together to increase the number of CTIs
See Also CoreSight, CoreSight ECT, Cross Trigger Interface, and Embedded Cross Trigger.
See Cross Trigger Interface.
See Cross Trigger Matrix.
A register containing the current state of control bits and flags.
See Also Program Status Register and Saved Program Status Register.
See Debug Access Port.
A hardware breakpoint that activates when a given location is accessed in a specific way. The breakpoint can also check for a specific data value being access at the given location, if required.
See Also Chained breakpoint, Conditional breakpoint, Hardware breakpoint, Instruction breakpoint, Software breakpoint, and Unconditional breakpoint.
See Debug Communications Channel.
The Debug Agent resides on the target to provide target-side support for Running System Debug (RSD) in RealView Debugger. The Debug Agent can be a thread or built into the RTOS. The Debug Agent and RealView Debugger communicate with each other using the Debug Communications Channel (DCC). This enables data to be passed between the debugger and the target using the ICE interface, without stopping the program or entering debug state.
See Also Running System Debug and Debug Communications Channel.
The Debug Access Port is a control and access component that enables debug access to the complete SoC through system master ports.
External read/write access to the internal interface is provided by the JTAG Debug Port (JTAG-DP). The JTAG-DP is a standard JTAG interface for debug access and provides standard JTAG access to an SoC through the DAP. It interfaces to the DAP internal bus.
Internal access to on-chip busses and other interfaces is provided by the Access Ports (APs). The three APs are:
the AHB Access Port (AHB-AP) that provides an AHB-Lite master for access to a system AHB bus
the APB Access Port (APB-AP) that provides an AMBA 3 APB master for access to the Debug APB that configures all CoreSight components
the JTAG Access Port (JTAG-AP) that provides JTAG access to on-chip components and operates as a JTAG master port to drive JTAG chains throughout the SoC.
See Also CoreSight.
A debug communications channel enables data to be passed between RealView Debugger and the EmbeddedICE logic on the target using the JTAG interface, without stopping the program flow or entering debug state.
In the context of RealView Debugger, a Debug Configuration defines a debugging environment for the development platform that is accessed through a particular Debug Interface. Multiple Debug Configurations can be created for a Debug Interface, each providing a separate debugging environment to different development platforms, or different debugging environments to the same development platform.
All Debug Configurations are stored in the main RealView Debugger board file. Each configuration might reference one or more BCD files.
See Also Board file, Board/Chip Definition (BCD) file, Debug Interface and Target.
The experience that a debugger creates in the mind of the software developer. The key features of debug illusion include:
mixed source code and disassembly
a function call stack showing symbolic function prototypes with names and argument types
display of variables using their source code name
source level stepping and breakpoints.
This illusion is created by the debugger using data from the system being debugged and symbolic debug information from the code generation tool chain.
In the context of RealView Debugger, 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 piece of hardware or a software simulator.
See Also Debug Configuration and Target.
Contains the components, either hardware or simulated, that you are using to develop your application. It can include:
a development board, such as an Integrator/CP
peripherals
one or more ARM architecture-based processors
CoreSight components
one or more DSPs.
See Also CoreSight and Target.
In the context of the ARM architecture, a 64-bit unit of information. Contents are taken as being an unsigned integer unless otherwise stated.
The ARM DSTREAM debug and trace unit enables powerful software debug and optimization on any ARM processor-based hardware target.
Profiling and tracing from the external trace port of a SoC with DSTREAM is not supported.
See Embedded Cross Trigger.
Embedded assembler is assembler code that is included in a C or C++ file, and is separate from other C or C++ functions.
The Embedded Cross Trigger provides a standard interconnect mechanism to pass debug or profiling events around the SoC. It comprises:
Cross Trigger Interface (CTI)
Cross Trigger Matrix (CTM).
See Also CoreSight and CoreSight ECT.
The Embedded Trace Buffer provides logic inside the core that extends the information capture functionality of the Embedded Trace Macrocell.
See Also CoreSight ETB and Embedded Trace Macrocell.
A block of logic, embedded in the hardware, that is connected to the address, data, and status signals of the processor. It broadcasts branch addresses, and data and status information in a compressed protocol through the trace port. It contains the resources used to trigger and filter the trace output.
See Also CoreSight ETM and Embedded Trace Buffer.
The EmbeddedICE logic is an on-chip logic block that provides TAP-based debug support for ARM architecture-based processors. It is accessed through the TAP controller on the ARM architecture-based processor using the JTAG interface.
See Also IEEE1149.1.
In the context of target connection hardware, an emulator provides an interface to the pins of a real core (emulating the pins to the external world) and enables you to control or manipulate signals on those pins.
See Embedded Trace Buffer.
See Embedded Trace Macrocell.
See Extended Target Visibility.
Part of the debug target interface, execution vehicles process requests from the client tools to the target.
See Also Debug Interface.
The address of regions and sections after the image has been loaded into memory and started execution.
Extended Target Visibility enables RealView Debugger to access features of the underlying target, such as chip-level information provided by the hardware manufacturer or SoC designer.
In the context of RealView Debugger Trace, a facility that enables you to refine the results of a trace capture that has already been performed in RealView Debugger. This is useful if you want to refine your area of interest within the display.
Fast Interrupt.
The ARM image conversion utility. This accepts ELF format input files and converts them to a variety of output formats. fromelf can also generate text information about the input image, such as code and data size.
See Also ARM Compiler toolchain and RealView Compilation Tools (RVCT).
In the context of the ARM architecture, defined as a 16-bit unit of information. Contents are taken as being an unsigned integer unless otherwise stated.
Usually used for OS aware debugging, Halted System Debug (HSD) means that a target can only be debugged when it is not running. Any target must be stopped before carrying out any analysis of the system. With the target stopped, RealView Debugger presents OS awareness information by reading and interpreting target memory.
See Also Running System Debug (RSD).
A breakpoint that is implemented using non-intrusive additional hardware. Hardware breakpoints are the only method of halting execution when the location is in Read Only Memory (ROM) or Flash. Using a hardware breakpoint often results in the processor halting completely. This is usually undesirable for a real-time system.
See Also Chained breakpoint, Conditional breakpoint, Data breakpoint, Instruction breakpoint, Software breakpoint, and Unconditional breakpoint.
A hint instruction provides information to the hardware
that the hardware can take advantage of. An implementation can choose
whether to implement hint instructions or not. If they are not implemented,
they execute as NOP.
See Halted System Debug.
See AHB Trace Macrocell.
A hardware extension to the EmbeddedICE logic that provides more breakpoint units.
The IEEE Standard that defines TAP. Commonly, but incorrectly, referred to as JTAG.
Values that are encoded directly in the instruction and used as numeric data when the instruction is executed. Many ARM and Thumb instructions enable small numeric values to be encoded as immediate values within the instruction that operates on them.
In the context of the ARM architecture, this means that the behavior is not architecturally defined, but must be defined and documented by individual implementations.
A device enabling access to and modification of the signals of a circuit while that circuit is operating.
Contains code or initialized data or describes a fragment of memory that must be set to zero before the application starts.
A location in the image containing an instruction that, if executed, activates a breakpoint. The breakpoint activation can be delayed by assigning condition qualifiers, and subsequent execution of the image is determined by any actions assigned to the breakpoint.
See Also Conditional breakpoint, Data breakpoint, Hardware breakpoint, Software breakpoint, and Unconditional breakpoint.
When referring to a TAP controller, a register that controls the operation of the TAP.
In the context of RVDS, a set of models that simulate the ARM Cortex™ family of processors. These models are provided with RVDS.
See Also Real-Time System Model (RTSM), RealView ARMulator ISS, Simulator, and SoC Designer Simulator.
A range of ARM hardware development platforms. Core modules are available that contain the processor and local memory.
See Also Core module.
A method of working that enables branches between ARM and Thumb code.
Interrupt Request.
See Instruction Set System Model (ISSM).
A block of up to four instructions following the
16-bit Thumb-2 If-Then (IT) instruction. Each
instruction in the block is conditional. The conditions for the
instructions are either all the same, or some can be the inverse
of others.
The Jazelle architecture extends the existing ARM architecture to enable direct execution of selected Java Virtual Machine (JVM) opcodes.
A processor that is executing Jazelle bytecode instructions is operating in Jazelle state.
See Also ARM state, Thumb state, and ThumbEE state.
See Debug Access Port.
See Debug Access Port.
In the context of ARM RealView tools, a protocol converter that converts low-level commands from RVDS debuggers into JTAG signals to the processor, for example to the EmbeddedICE logic and the ETM.
See Also RealView Debugger.
In the context of the ARM architecture, little-endian is defined as the memory organization in which the most significant byte of a word is at a higher address than the least significant byte.
See Also Big-endian.
The address of regions and sections when the image has been loaded into memory but has not yet started execution.
In the context of the ARM architecture, a memory hint instruction enables a programmer to provide advance information to memory systems about future memory accesses, without actually loading or storing any data.
An integrated Symmetric Multiprocessor System (SMP) delivered as a traditional uniprocessor core. The chip contains up to four ARM1136J-S™ based CPUs with cache coherency.
Multi-Processor Unit.
See ARM Advanced SIMD Extension.
Effectively two virtual processors on a single physical processor. The Normal World processes operations that are not security-critical, and it delegates security-critical operations to the Secure World. Client applications reside and execute in the Normal World. Native services reside and execute in the Secure World. The secure parts of TrustZone Software run in the Secure World.
See Also Secure monitor.
See Normal and Secure Worlds.
A contiguous sequence of input sections that have the same RO, RW, or ZI attributes. The sections are grouped together in larger fragments called regions. The regions are grouped together into the final executable image.
See Also Region.
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.
See PreCompiled Header.
A header file that is precompiled. This avoids the compiler having to compile the file each time it is included by source files.
Procedure Call Standard for the ARM Architecture defines how registers and the stack will be used for subroutine calls.
In the context of RealView Debugger Trace, the accumulation of statistics during execution of a program being debugged, to measure performance or to determine critical areas of code.
In the context of the ARM architecture, integer register R15.
Contains some information about the current program and some information about the current processor. Also referred to as Current PSR (CPSR), to emphasize the distinction between it and the Saved PSR (SPSR). The SPSR holds the value the PSR had when the current function was called, and which will be restored when control is returned.
An Enhanced Program Status Register (EPSR) contains an additional bit (the Q bit, signifying saturation) used by some ARM architecture-based processors, including the ARM9E.
See Also Current Program Status Register and Saved Program Status Register.
A collection of RealView Debugger and RVCT configuration files for specific target development platforms. These templates enable you to create a target-specific development project in the ARM Workbench IDE.
See Also RealView Compilation Tools (RVCT), RealView Debugger, and ARM Workbench IDE.
See Program Status Register.
Protection Unit.
In the context of the ARM architecture, code or read-only data that can be placed at any address.
In the context of the ARM architecture, read/write data addresses that can be changed at runtime.
A small program that, when integrated into your target application or Real-Time Operating System (RTOS), enables you to observe and debug your target while parts of your application continue to run.
An RTSM contains a hard-coded system containing one or more specific simulated processors and an emulation baseboard. Some RTSMs are provided with RVDS Professional edition.
See Also Instruction Set System Model (ISSM), RealView ARMulator ISS (RVISS), ARM Profiler, Simulator, and SoC Designer Simulator.
One of the ARM simulators supplied with RVDS.
RVISS is a collection of programs that simulate the instruction sets and architecture of various ARM processors. This provides instruction-accurate simulation and enables ARM and Thumb executable programs to be run on non-native hardware.
RVISS provides modules that model:
the ARM processor core
the memory used by the processor.
There are alternative predefined models for each of these parts. However, you can create your own models if a supplied model does not meet your requirements.
See Also Instruction Set System Model (ISSM), Real-Time System Model (RTSM), Simulator, and SoC Designer Simulator.
RVCT is a suite of tools, together with supporting documentation and examples, that enables you to write and build applications for the ARM family of processors.
See Also armar, armasm, armcc, armlink, fromelf, and ARM Compiler toolchain.
The latest debugger software from ARM that enables you to make use of a debug agent in order to examine and control the execution of software running on a debug target. RealView Debugger is supplied in both Windows and Red Hat Linux versions.
Part of the RVDS product that extends the debugging capability with the addition of real-time program and data tracing. It is available from the RealView Debugger Code window.
See Also RealView ICE (RVI) and RealView Trace (RVT) and RealView Trace 2 (RVT2).
The suite of software development applications, together with supporting documentation and examples, that enable you to write and debug applications for the ARM family of processors. RVDS v3.1 and later can be obtained in both Professional and Standard editions. RVDS supersedes ARM Developer Suite™.
See Also Real-Time System Model (RTSM).
A JTAG-based debug solution to debug software running on ARM architecture-based processors. RVI host software is provided with RVDS. The RVI debug unit must be purchased as a separate product.
See Also RealView Debugger Trace, and RealView Trace (RVT) and RealView Trace 2 (RVT2).
Works in conjunction with RVI to provide real-time trace functionality for software running in leading edge System-on-Chip devices with deeply embedded processor cores. RVT2 also enables data streaming directly to ARM Profiler to perform real-time hardware platform profiling. The RVT and RVT2 hardware units must be purchased as separate products.
See Also RealView Debugger Trace, ARM Profiler, and RealView ICE (RVI).
In an image, a region is a contiguous sequence of one to three output sections (RO, RW, and ZI). A region typically maps onto a physical memory device, such as ROM, RAM, or peripheral.
See Also Root region.
See Read-Only Position Independent.
In an image, regions having the same load and execution address. A non-root region is a region that must be copied from its load address to its execution address.
See Running System Debug.
See Real-Time System Model (RTSM).
Used for OS-aware debugging, Running System Debug (RSD) means that a target can be debugged when it is running. This means that the debug target does not have to be stopped before carrying out any analysis of the system. RSD gives access to the application using a Debug Agent (DA) that resides on the target. The Debug Agent is scheduled along with other tasks in the system.
See Also Debug Agent and Halted System Debug (HSD).
See RealView Compilation Tools (RVCT).
See RealView Development Suite (RVDS).
See RealView ICE (RVI).
See RealView Trace (RVT) and RealView Trace 2 (RVT2).
See RealView Trace (RVT) and RealView Trace 2 (RVT2).
See Read Write Position Independent.
A register that holds a copy of what was in the Current Program Status Register before the most recent exception. Each exception mode has its own SPSR.
Assigning the address and grouping of code and data sections individually rather than using single large blocks.
In the context of applications targeted at ARM architecture-based processors, a block of software code or data for an Image.
See Also Input section and Output section.
Reliably switches the ARM processor between Normal World and Secure World execution environments. The Secure monitor is transparent to TrustZone Software developers.
See Normal and Secure Worlds.
A mechanism whereby the target communicates I/O requests made in the application code to the host system, rather than attempting to support the I/O itself.
Serial Wire Debug is a two-pin, bi-directional, data signal plus clock that replaces the 5-pin or 6-pin JTAG interface. The Serial Wire/JTAG debug port provides access to system memory peripherals and debug configuration registers.
A type of tracepoint that enables you to set trigger points, trace start and end points, or trace ranges for memory and data accesses.
See Also Tracepoints.
In the context of the ARM tools, a simulator executes non-native instructions in software (simulating a core).
See Also Instruction Set System Model (ISSM), Real-Time System Model (RTSM), RealView ARMulator ISS, and SoC Designer Simulator.
SoC Designer Simulator is part of the Carbon SoC Designer Plus toolset that can be used for fast modeling, simulation and debugging of complex System-on-Chip (SoC) designs. System and processor models created with the Carbon SoC Designer Plus tools can be debugged with Carbon SoC Designer Simulator in conjunction with RealView Debugger.
See Also Instruction Set System Model (ISSM), Real-Time System Model (RTSM), RealView ARMulator ISS, and Simulator.
A breakpoint that is implemented by replacing an instruction in memory with one that causes the processor to take exceptional action. Because instruction memory must be altered software breakpoints cannot be used where instructions are stored in read-only memory. Using software breakpoints can enable interrupt processing to continue during the breakpoint, making them more suitable for use in real-time systems.
See Also Chained breakpoint, Conditional breakpoint, Data breakpoint, Hardware breakpoint, Instruction breakpoint, Software breakpoint, and Unconditional breakpoint.
Saved Program Status Register.
See Also Program Status Register.
Integer register R13.
An instruction that causes the processor to call a programmer-specified subroutine. Used by the ARM standard C library to handle semihosting. This replaces software interrupt (SWI).
See Supervisor Call.
See Supervisor Call.
Logic on a device which enables access to some or all of that device for test purposes. The circuit functionality is defined in IEEE1149.1.
See Also Test Access Port and IEEE1149.1.
In the context of RealView Debugger, 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.
See Also CoreSight, Debug Configuration, and Debug Interface.
Target vehicles provide RVDS with a standard interface to disparate targets so that the debugger can connect easily to new target types without having to make changes to the debugger core software. The interface can be a hardware or software interface.
See Also Instruction Set System Model (ISSM), Real-Time System Model (RTSM), RealView ARMulator ISS, RealView ICE (RVI), and SoC Designer Simulator.
Tightly Coupled Memory.
Test Data Input.
Test Data Output.
One halfword or two halfwords that encode an operation for an ARM architecture-based processor operating in Thumb state. Thumb instructions must be halfword-aligned.
See Also ARM instruction, Thumb-2 instruction, and Thumb-2EE instruction.
A processor that is executing Thumb instructions
is operating in Thumb state. The processor switches to ARM state
(and to recognizing ARM instructions) when directed to do so by
a state-changing instruction such as BX, BLX.
See Also ARM state, Jazelle state, and ThumbEE state.
Thumb-2 is a major enhancement of the Thumb instruction set, and is defined by ARMv6T2 and ARMv7M architectures. Thumb-2 provides almost exactly the same functionality as the ARM instruction set. It has both 16-bit and 32-bit instructions, and achieves performance similar to ARM code, but with code density similar to Thumb code.
See Also ARM instruction, Thumb instruction, and Thumb-2EE instruction.
Thumb-2 Execution Environment (Thumb-2EE) is defined by ARMv7 architecture. The Thumb-2EE instruction set is based on Thumb-2, with some changes and additions to make it a better target for dynamically generated code, that is, code compiled on the device either shortly before or during execution.
See Also ARM instruction, Thumb instruction, and Thumb-2 instruction.
A processor that is executing Thumb-2EE instructions is operating in ThumbEE state. In this state, the instruction set is almost identical to the Thumb instruction set. However, some instructions have modified behavior, some instructions are not available, and some new instructions become available.
See Also ARM state, Jazelle state, and Thumb state.
Trace Port Analyzer.
See Trace Port Interface Unit.
The Trace Funnel combines up to eight trace sources (ETM or HTM) on a single funnel. However, in this release, trace data can be captured only from a single ETM at a time.
See Also AHB Trace Macrocell, CoreSight, CoreSight ETM, and Embedded Trace Macrocell.
The Trace Port Interface Unit is a trace sink that drains trace data off-chip to a TPA, such as RealView Trace.
See Also CoreSight, CoreSight ETB, CoreSight ETM, and RealView Trace.
A tracepoint can be set on a line of source code, a line of assembly code, or a memory address. In RealView Debugger, you can set a variety of tracepoints to determine exactly what program information is traced.
See Also Chained tracepoint and Tracepoint unit.
In the context of RealView Debugger, a unit within a Chained tracepoint that combines with other tracepoint units to create a complex tracepoint.
See Also Chained tracepoint and Tracepoint.
In the context of breakpoints, a trigger is the action of noticing that the breakpoint has been reached by the target and that any associated conditions are met.
In the context of tracing, a trigger is an event that instructs the debugger to stop collecting trace and display the trace information around the trigger position, without halting the processor. The exact information that is displayed depends on the position of the trigger within the buffer.
A secure software framework that enables best use of security extensions built into the ARM architecture. Used in single-processor ARM cores that can operate as two virtual CPUs.
A breakpoint that does not have a conditional qualifier assigned. The breakpoint activates immediately it is hit, but subsequent image execution is determined by any actions assigned to the breakpoint.
See Also Conditional breakpoint, Data breakpoint, Hardware breakpoint, Instruction breakpoint, Software breakpoint, and Unconditional breakpoint.
In the context of the ARM architecture, an attempt to execute an undefined instruction causes an Undefined Instruction exception.
In the context of the ARM architecture, the result of an unpredictable instruction cannot be relied upon. Unpredictable instructions or results must not represent security holes. Unpredictable instructions must not halt or hang the processor, or any parts of the system.
In the context of the ARM architecture, a small block of code used with subroutine calls when there is a requirement to change processor state or branch to an address that cannot be reached in the current processor state.
A standard for floating-point coprocessors where several data values can be processed by a single instruction.
In RealView Debugger, a watch is a variable or expression that you require the debugger to display at every step or breakpoint so that you can see how its value changes. The Watch pane is part of the RealView Debugger Code window. It displays the watchpoints you have defined.
In RVDS, this is a hardware breakpoint.
In the context of the ARM architecture, a word holds a value held in four contiguous bytes. A 32-bit unit of information. Contents are taken as being an unsigned integer unless otherwise stated.
| Copyright © 2003-2011 ARM. All rights reserved. | ARM DUI 0255M |
| Non-Confidential | |
| PDF version | |
| Home > Glossary |