12.12.2. Viewing project binding

If you create or open a user-defined project without previously connecting to a debug target, then the project is unbound. This also applies if you create or open a project, and the specified processor family for that project does not correspond to the connection.

For example, if your debug target does not match the specific device setting, and you then create a user-defined project for another processor, this new project is shown as unbound in the default Code window title bar, for example:

RVDEBUG<Project_1> = @ARM7TDMI_0:ARM-ARM-USB [Unattached]

If you are connected to a target when you create or open a user-defined project, RealView Debugger binds the project to the connection if it can. When you load an image to create an in-memory auto-project, or if RealView Debugger opens the saved auto-project associated with the image, the auto-project binds automatically.

The Code window title bar shows that the project is bound to the connection by including the project name in parentheses, for example:

RVDEBUG(Project_2) = @ARM7TDMI_0:ARM-ARM-USB [Unattached]

Note

For an auto-project, the name in the title bar is not the image name, but the project name created from the image name.

The title bar updates if you change the project environment, for example if you:

Where you are working with multiple projects, the project environment depends on:

Use the Project Control dialog box to see the open project list and how projects are bound. See the example in Figure 12.13.

Viewing autobound projects

The Code window title bar shows if a project is bound to the connection. The title bar does not show if the project is autobound. If you do not want to examine the project properties, you can use the Project Control dialog box to see if a project has specific device binding set.

Any open projects that are autobound have (DEV) appended to the entry in the open project list, shown in Figure 12.18.

Figure 12.18. Autobound projects in the Project Control

Autobound projects in the Project Control

In Figure 12.18, there are two projects in the open project list. The last project to open is at the top of the list and is selected by default. The dhrystone project is autobound to the connection, ARM7TDMI_0:ARM-ARM-USB. You can see that the project is autobound because (DEV) is appended to the entry to show that the project has specific device binding set.

In this case, dhrystone is the active project because it was the last project to bind successfully to the connection.

Note

If the dhrystone project is unbound, the entry changes to dhrystone - <none> (DEV).

Copyright © 2003, 2004 ARM Limited. All rights reserved.ARM DUI 0234B
Non-Confidential