| |||
| Home > Configuring Custom Targets > Using RealMonitor > Using RealMonitor with RealView ICE | |||
This section describes how to set up RealView Debugger with RealView ICE to run a RealMonitor-integrated application.
RealMonitor is compatible with RealView ICE v1.1, and later.
RealView Debugger does not support the following RealMonitor functionality:
Semihosting.
Synchronizing the caches after memory writes.
On-the-fly switching between run-mode (through RealMonitor) and stop-mode debug (halting the core through RealView ICE) is not possible. In particular, RealView Debugger makes no attempt to recover if the RealMonitor connection is lost during a debug session.
Because of floating signal levels on the JTAG connector, you must be aware of the following rules when using a RealView ICE unit with running targets:
Do not do any of the following actions, because they can cause the target to stop:
power up the RealView ICE unit when it is connected to a running target
connect a running RealView ICE unit to a running target
power down the RealView ICE unit when it is connected to a running target.
Configuring the RealView ICE unit stops the target you are connected to. In particular auto-configuring does this.
Incorrect RealView ICE settings can result in your target being stopped or the core staying in halt-mode debug. As a result, hardware breakpoints stop the core. RealView Debugger does not warn you if this happens.
If your target has stopped when the RealView ICE unit is configured or booted, reset your target before connecting to the RealMonitor connection with RealView Debugger.
RealMonitor support for RealView Debugger is not enabled if you connect to a halted target.
Debugging a RealMonitor-integrated application with RealView ICE requires that you connect with the RMHost controller while the program is running. To debug a RealMonitor-integrated application RealView ICE you must perform the following sequence of actions:
Configuring a RealMonitor-compatible RealView ICE connection.
Set up RealMonitor with RealView ICE using one of the following methods:
If the RealMonitor image resides in Flash or ROM, configure the main settings for the connection.
See Configuring a RealMonitor connection for details.
If you have to upload your image to the target, see Loading an image before using RealMonitor.
To make a copy of your original RealView-ICE connection:
Select Target ? Connect to Target... to display the Connection Control window, shown in Figure 2.17.
Right-click on the RealView-ICE Target
Access to display the context menu.
Select Properties... from the context menu to display the Connection Properties window, shown in Figure 2.18.
Right-click on the CONNECTION=RealView-ICE group
in the left pane to display the context menu.
Select Make Copy... from the context menu.
The Group Type/Name selector dialog box is displayed.
Change the name to RealView-ICE_RM.
The name must not include spaces.
Click OK.
Select File ? Save to save your changes.
Follow the instructions in the next section to configure the RealView ICE connection for RealMonitor.
The instructions in this section assume that you have completed the instructions in Making a copy of the original RealView ICE connection.
To configure the RealView ICE connection for RealMonitor (see the RealView ICE and RealView Trace User Guide for more details):
Select the CONNECTION=RealView-ICE_RM group
you created in Making a copy of the original RealView
ICE connection.
Edit the value of *Configuration in
the right pane and change it to rvi_rm.rvc.
Right-click on the *Configuration setting
to display the context menu.
Select Edit Configuration-File Contents... from the context menu.
A prompt dialog box is displayed.
Click Empty to create an empty configuration.
The Select Name of new file dialog box is displayed.
Create the configuration file:
Locate your home directory.
Set the File type to All Files (*).
Enter an appropriate filename for the configuration file.
For example, enter rvi_rm.rvc.
Click Save.
This saves the RealView ICE configuration file rvi_rm.rvc in
your home directory, and displays the RVConfig configuration window.
Select your RealView ICE hardware from the list of devices.
Click Connect... to connect to RealView ICE.
If your Target Access has targets that:
can be halted and do not contain any DSPs, then click Auto Configure Scan Chain
must not be halted or has DSPs, then add the devices manually (see the RealView ICE and RealView Trace User Guide for more details on how to do this).
Click Advanced, and change the
settings as shown in Table 2.1.
Leave all other settings unchanged.
Table 2.1. RealView ICE settings for RealMonitor
| Setting | Value |
|---|---|
Reset Type | nTRST |
Default Post Reset State | Running |
TAP reset via State Transitions | unchecked |
The intention here is to make sure that the system is not reset, and that the target is always running. Some targets might require different settings.
Select File ? Save to save the changes.
To set up RealMonitor for your RealView ICE connection, follow the instructions in Configuring a RealMonitor connection.
To configure a RealMonitor connection, there are some settings
for the connection that you must configure. You must configure these
settings at the CONNECTION level.
The instructions in this section assume that you have completed the instructions in Making a copy of the original RealView ICE connection and Configuring a RealMonitor-compatible RealView ICE connection.
To configure the mandatory settings for a RealMonitor connection:
Expand the following entries in turn:
CONNECTION=RealView-ICE
Advanced_Information
Default
Select Default in the left pane,
and set the following in the right pane:
Connect_mode to no_reset_and_no_stop
Disconnect_mode to as_is_without_debug.
Specify the monitor:
Select Monitor in
the left pane.
Set Type in the right pane to RealMonitor.
Disable vector catch:
Select ARM_config in
the left pane.
Set Vector_catch in the right
pane to False.
Disable semihosting:
Expand ARM_config.
Select Semihosting in the left
pane
Set Enabled in the right pane
to False.
Select File ? Save and Close to save your changes and close the Connection Properties window.
You can now connect to the target that is running RealMonitor. No additional configuration is required.
Typically, RealMonitor resides in Flash or ROM. However, if you have to upload your image, you must:
Create a standard connection to upload the image to the target and set it running:
for details on how to create a standard connection, see the RealView Debugger v3.0 User Guide.
for details on how to load an image, see the chapter that describes loading images and binaries in the RealView Debugger v3.0 User Guide.
Use the RealView-ICE_RM connection
you created in Making a copy of the original RealView
ICE connection,
and that you configured as described in Configuring a RealMonitor-compatible
RealView ICE connection.