ARM ARM DUI 0137A Configuring AXD to enable tracing with RMHost, Performance of RMHost with TDT

Page 40

Debugging with RMHost

3.3.1Configuring AXD to enable tracing with RMHost

The process of connecting to a target system using both RMHost and TDT is similar to connecting to a target system using only RMHost. The only difference is that you must enable tracing when you configure your JTAG controller to be used with RealMonitor.dll, as described in step 6 of Procedure for connecting to RMHost using AXD on page 22. For details on enabling tracing, see the appendix on setting up the trace software in the Trace Debug Tools User Guide.

3.3.2Performance of RMHost with TDT

When using TDT with Multi-ICE only, and not RMHost, TDT cannot read the target memory without halting the processor. However, it must be able to view the instructions that were executed by the processor to decode the trace data. It therefore implements an image cache in the host, and fetches the instructions from this cache, rather than from the target.

Note

If your image is already loaded onto the target, you can select Load Debug Symbols from the File menu to place the image into the image cache (even while your application is currently running).

Caution

If you are using self-modifying code, you must disable the image cache in the debugger because when the image cache is in use, the debugger cannot detect any modifications the code makes to itself. To disable the image cache in AXD:

1.Select Debugger Internals from the System Views menu.

2.Change the value of the variable image_cache_enable from 0x01 to 0x00.

With RMHost, it is possible to read memory without halting the target, and TDT can decode the trace data by reading memory on the target. Therefore, a trace stream can be displayed without having to use the image cache.

However, because the link between the host and the target is limited by the JTAG connection, and the performance of the debug communications channel when using RMHost, decoding trace in this way is slow compared to using the image cache.

314

Copyright © 2000 ARM Limited. All rights reserved.. All rights reserved.

ARM DUI 0137A

Page 39 Page 41
Image 40
Page 39 Page 41
Contents ARM RMHost ARM RMHost User GuideUser Guide Chapter Debugging with RMHostContents Preface About this book onUsing this book About this bookIntended audience Typographical conventionsFurther reading ARM publicationsOther publications Feedback on RMHost FeedbackFeedback on this book ARM DUI 0137A Overview of RMHost About RMHost on RMHost requirements onAbout RMHost Application/RTOSOverview of RMHost RMHost requirements RMHost packageConnecting to RMHost Procedure for connecting to RMHost using AXD Debuggers chapter of the Multi-ICE User Guide Select Configure Interface from the Options menu Configure interface dialog boxDescribes how to do this RealMonitor Configuration dialog box Jtag controller search dialog box Deselect the the option Fetch module information from target Cancel No pc write access messageNo pc read access message AXD connection messages Lines 2212 Debugging with RMHost Debugging with RMHost Nonstop debugBackground memory access CPU register access Nonstop startupData messaging ProfilingSemihosting Debugging with RMHost Error messages RDITarget does not include an ARM processor Memory map forbids reading from location RMHost could not load the specified Jtag controller Other messages from RMHost Yes312 Using RMHost with Trace Debug Tools AsicPerformance of RMHost with TDT Configuring AXD to enable tracing with RMHostSelect Debugger Internals from the System Views menu Index RmoptsdminfoRmoptdatalogging Rmoptgetpc
Top Page Image Contents