RealView® Developer Kit Debugger User Guide 15.2.2. Creating a new RTOS-enabled connection

15.2.2. Creating a new RTOS-enabled connection

It is recommended that you create a new connection in the board file to specify your RTOS-enabled target. Although this is not necessary, it means that it is easy to identify the RTOS target and maintains other custom targets that you might configure. This section describes how to set up the new connection.

This example defines a new RVI-ME connection. You can do this by creating a new connection entry or by copying an existing entry. Here, you create a new connection entry.

The example assumes that a correctly configured .rvc file exists for the new target and this has been saved in the default RVI-ME installation directory. If you do not have this file, you can follow the example. However, before you can connect to the new target, you must also follow the instructions describing how to configure an RVI-ME interface unit in Chapter 14 Configuring Custom Connections.

To set up the new connection:

Start RealView Debugger but do not connect to a target.
Select Target → Connect to Target... to display the Connection Control window, shown in Figure 2.1.
You can also click the Connection Control button in the Connect toolbar to display the Connection Control window quickly. If the window is hidden, click the button twice.
Figure 15.2. Connection Control window
Figure 2.1 shows the default connections set up after you first install RealView Debugger. The contents of this window depend on the autodetected targets available to you. If you have installed a Custom configuration your window looks different.
Note
If the RVI-ME target vehicle is not visible in the Connection Properties window, you must add it before continuing with this section. See Chapter 14 Configuring Custom Connectionsfor full details on how to do this.
Right-click on the connection that you want to use. This example uses RVI-ME to access the ARM^® JTAG debug tool.
Select Connection Properties... from the context menu to display the Connection Properties window, shown in Figure 15.3.
Figure 15.3. CONNECTION groups in the Connection Properties window
Right-click on the CONNECTION=RVI-ME entry, in the left pane.
Select Make New... from the context menu.
This displays the Group Type/Name selector dialog box, shown in Figure 14.3.
Figure 15.4. Specifying a new CONNECTION group
Leave the type of the new entry unchanged as CONNECTION.
In the Group Name data field change the name from RVI-ME to something suitable for your target, for example RVI-ME_OS_tst.
Click OK to confirm your settings and to close the Group Type/Name selector dialog box.
The new entry appears in the left pane of the Connection Properties window. It is automatically selected, and its details are displayed in the right pane. These details are the default for a new CONNECTION and you must change at least the Connect_with/Manufacturer, the Configuration filename, and target Description. The next steps explain how to make these changes.
In the right pane of the Connection Properties window, right-click on the Configuration entry and select Edit as Filename from the context menu.
The Enter New Filename dialog box is displayed to enable you to locate the required .rvc file, for example rvi_ARM_2.rvc.
Click Save to confirm your entries and to close the Enter New Filename dialog box.
The new pathname is displayed in the right pane.
In the right pane of the Connection Properties window, right-click on the Description field, and select Edit Value from the context menu.
Type RVI-ME to RTOS test board in the entry area and press Enter.
This is the description displayed in the Connection Control window and Connection Properties window to identify the new target.
In the right pane of the Connection Properties window, right-click on the Connect_with entry and select Explore from the context menu.
In the right pane of the Connection Properties window, right-click on the Manufacturer entry and select the required connection type from the context menu, that is ARM-ARM-USB.
If you do not specify this setting, the new connection appears in the Connection Control window but, when you try to connect, RealView Debugger prompts for the connection type.
Select File → Save and Close to save your changes and close the Connection Properties window.
Your new RVI-ME target is now displayed in the Connection Control window, shown in Figure 15.5.
Figure 15.5. New connection in the Connection Control window

Configuring an RVI/RVI-ME interface unit

Ensure that the RVI/RVI-ME unit is configured as described in the chapter on configuring custom connections in Chapter 14 Configuring Custom Connections before you continue with this section.

Remember the following when specifying settings for your hardware:

Autoconfiguring the RVI/RVI-ME unit does have side-effects and might be intrusive. Where this is not acceptable, you must configure manually.
Be aware that clicking the option Reset on Connect might interfere with the initialization sequence of your application or target hardware.
The RVI/RVI-ME scan chain configuration lists devices in ascending order of TAP ID.

Note

For more information on the tasks described here, and for full details on how to configure targets and create new connections, see Chapter 13 Configuring Custom Targets and Chapter 14 Configuring Custom Connections.

Now you must configure RTOS support for the new connection:

If you have an RTOS-specific .bcd file, you can enable RTOS support on your target by referencing the .bcd file from your board file. Do this using the BoardChip_name entry as described in Configuring an RTOS-enabled connection to reference a vendor-supplied .bcd file.
If you do not have an RTOS-specific .bcd file, configure the RTOS on your target as described in your RTOS documentation coupled with the information in Configuring an RTOS-enabled connection without a vendor-supplied .bcd file.

Copyright © 2005, 2006 ARM Limited. All rights reserved.	ARM DUI 0281C
Non-Confidential
PDF version