12.12.3. Forcing binding

Select Project → Project Control... from the default Code window main menu to display the Project Control dialog box where you can force project binding and so change your project environment.

Note

See Working with the Project Control dialog box for details on other controls in this dialog box.

In Figure 12.13, there are two projects in the open project list. The last project to open is shown at the top of the list and is selected by default. The dhrystone project is bound to the connection, using default binding.

In this case, dhrystone is the active project because it was the last project to bind successfully to the connection. This means that you can access the project properties from the Project menu or from the Process Control pane, if this is visible.

To bind the interworking project to the connection:

  1. The interworking project is shown ticked. Therefore, the projecty is selected for action.

  2. Click Re-Bind to force RealView Debugger to bind the selected project. This displays a list selection box showing the connection, shown in Figure 12.19.

    Figure 12.19. Connection selection box

    Connection selection box
  3. Select the connection so that it is ticked. You must do this even where the list contains only one connection.

  4. Click OK to confirm your choice and close the selection box. Otherwise, click Cancel if you want to abort the binding operation.

    This updates the contents of the Project Control dialog box to show the new binding.

  5. Click Close to close the Project Control dialog box.

See Effects of binding for what happens when a project binds.

Autobound projects

You can use the Project Control dialog box to force binding for autobound projects. If, for example, the open project list contains four projects where three have a Specific_device entry set and one uses default binding, you can select all four projects and then click Re-Bind to force binding. Each project is then bound in turn. You can, therefore, use this dialog box to force default binding to displace an autobound project.

You cannot use the Project Control dialog box to force an autobound project to bind to a device that does not match. You must change the Specific_device setting first, see Adding Specific_device settings for details.

Forcing unbinding

You do not have to unbind a project before you rebind another project to the same connection. However, you might want to unbind a project so that you can open a new project and ensure that it binds to the connection, for example if you have an autobound project bound to the connection and you want to open a project that uses default binding. Use the Project Control dialog box to unbind projects. Do this in the same way as rebinding but click Un-Bind to unbind the selected project(s). See Effects of unbinding for what happens when a project unbinds.

If you unbind a user-defined project where the image associated with that project is loaded to the debug target, RealView Debugger tries to use an auto-project to store settings for the image. If you then open and bind another project to this connection, RealView Debugger displays both projects in the Process Control pane. In this case, the Project Control dialog box shows three projects:

  • the auto-project associated with the current image

  • the second user-defined project bound to the connection

  • the user-defined project opened first.

See Managing multiple projects for details on working with multiple projects in this way.

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