4.1.2. Code window

When you run RealView Debugger for the first time after installation, the RealView Debugger Code window appears as shown in Figure 4.1.

When you exit RealView Debugger, it remembers the configuration of the panes or views by saving the current state in your workspace.

Figure 4.1. Default Code window

The Code window is your main debugging and editing window. The contents of this window change as you:

The appearance of the Code window also depends on your licenses. For example, the base product enables you to debug your images in single connection mode, that is where there is only one connection. If you are licensed to work in multiprocessor debugging mode, the title bar shows your current windows attachment. When you first display the default Code window in multiprocessor mode, this shows [Unattached].

Note

If you are not licensed to use the RealView Debugger multiprocessor extension, some of the buttons in your Code window are disabled. For example, the Connect control buttons for making connections in multiprocessor mode, shown in Figure 4.1.

Title bar

The Code window title bar gives details of the current project, the current connection, and any processes running on your debug target. In addition to the application icon, the title bar contains (from left to right):

RVDEBUG

Identifies the Code window. This changes as you open new windows, for example RVDEBUG_1, or RVDEBUG_2.

(project)

The project associated with the image that you loaded.

In RealView Debugger, a project can be associated with a connection, that is it is bound to that connection. This is indicated by enclosing the project name in parentheses, for example, (dhrystone).

Where a project is not associated with a particular connection, it is unbound. In this case, the project name is enclosed in angled brackets, for example <my_project>.

See the chapter that describes project binding in RealView Debugger v1.8 Project Management User Guide for more details.

Also see Automatic operations performed by a project.

@endpoint_connection:execution_vehicle

The connection, including the endpoint connection (usually the target processor) and the execution vehicle. For example, if you connect to an ARM7TDMI processor through RealView ICE the title bar shows:

@ARM7TDMI_0:ARM-ARM-NW

See Elements of the Connection Control window for more details on the execution vehicle and endpoint connection.

If you are using an RTOS, and you stop execution, details of the current thread replace the connection details. For example,

T0x19F84_ITCM.ARM

See the chapter that describes RTOS support in the RealView Debugger v1.8 Extensions User Guide for details.

[Unattached]

The attachment of the window to a specific connection or thread.

In you do not have a multiprocessor debugging license, this part of the title bar is blank and the option to attach windows to your connection is not available.

If you are working in multiprocessor debugging mode:

  • a Code window is unattached by default, shown by [Unattached].

  • you can attach a Code window to a specified connection, shown by [Board].

See the chapter that describes working with multiple targets in RealView Debugger v1.8 Extensions User Guide for details.

If you are using an RTOS, you can also attach a Code window to a thread. Only the debug information for the attached thread is displayed in that Code window. If a thread is attached to a Code window, the [Unattached] text is removed from the title bar.

See the chapter that describes RTOS support in RealView Debugger v1.8 Extensions User Guide for details.

Copyright © 2002-2005 ARM Limited. All rights reserved.ARM DUI 0181G
Non-Confidential