| |||
| Home > Getting Started with RealView Developer Kit > Help on creating RealView Debugger projects > Making a project and a connection interdependent | |||
RealView Debugger provides a mechanism that enables a project and a connection to be mutually dependent. This mutual dependence is controlled using the settings described in Table 4.4.
Table 4.4. Settings that control project and connection interdependence
| Level of control | Setting | Description |
|---|---|---|
| Connection | Project | This is a setting that you specify for a connection. It identifies one or more projects that are to be opened automatically when you connect to a target processor on that connection. For more details, see the appendix describing the connection properties in the RealView Developer Kit v2.2 Debugger User Guide. |
| Project | Specific_device | This is a setting that you specify for a project. It identifies a specific processor (for example, ARM946E-S) or processor family (for example, ARM7). This restricts the loading of the image for this project to a connection with the specified processor or processor family. RealView Debugger acts on this setting only when:
This close coupling of project and target processor is referred to as specific device binding or autobinding. It is particularly useful if you are working with multiple projects open. For more details, see the chapter on managing projects in the RealView Developer Kit v2.2 Debugger User Guide. Other project-related settings are provided that enable you to control what happens when a project interacts with a connection (see Automatic operations performed by a project). |