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 with RealView ICE you must perform the following sequence of actions:
Review the information in:
If you have an existing RealView ICE Debug Configuration for your target, then continue at the next step. Otherwise, create a new RealView ICE Debug Configuration.
This is to be the Debug Configuration you use for debugging your RealMonitor-integrated application.
Change the name of the Debug Configuration. For this example, change the name to RVI_RM_Debug, shown in Figure 3.3.
Make a copy of the Debug Configuration.
This new Debug Configuration is the one you use to enable RealMonitor on the target. For this example, change the name of the Debug Configuration to RVI_RM_Run, shown in Figure 3.4.
Customize the original (
RVI_RM_Run) Debug Configuration as described in Customizing the Debug Configuration used for enabling RealMonitor.Customize the new (
RVI_RM_Debug) Debug Configuration as described in Customizing the Debug Configuration used for debugging with RealMonitor.For the Debug Configuration used to enable RealMonitor:
Expand the Debug Configuration (
RVI_RM_Runin this example).Connect to the target.
Load the image.
Run the image.
Disconnect from the running target.
For the Debug Configuration used to debug your application:
Expand the Debug Configuration (
RVI_RM_Debugin this example).Connect to the running target.
Load only the symbols for the image.
Stop execution.
This enables RealView Debugger to get the context so that you can begin debugging. RealView Debugger might prompt you for the location of the source file that contains the current context.
Restart execution.
You can now debug your application as described in Working with RealMonitor.
the following in the RealView Debugger User Guide:
RealView ICE and RealView Trace User Guide.
PDF version