ARM ARM DUI 0137A manual Deselect the the option Fetch module information from target

Page 22

Connecting to RMHost

Caution

The module server does not work with the RMHost controller if you disabled support for the ExecuteCode packet when you built RMTarget. See the description of the RM_OPT_EXECUTECODE build option in the building the RMTarget chapter of the ARM RMTarget Integration Guide.

8.Provide the module server with information about the target system.

If RMTarget was built with this information embedded, select Fetch module information from target and click OK to obtain this information (see the build option RM_OPT_SDM_INFO in the building chapter of the ARM RMTarget Integration Guide). If you select this option, the fields Processor and Board are grayed out, as shown in Figure 2-4 on page 26.

If no information is returned when you select the option Fetch module information from target and click OK, you must provide information as follows:

a.Deselect the the option Fetch module information from target.

b.From the drop-down list in the Processor field, select the processor core being debugged, such as ARM966E-S. The list consists of processors supported by the RDI module server, including a blank entry that you must select if the system being debugged is not included in the list. See RMHost requirements on page 14 for details on hardware supported by the RealMonitor host controller.

c.From the drop-down list in the Board field, select the board you are using, such as CM966E-S + Integrator/AP. The list consists of boards supported by the RDI module server, including a blank entry that you must select if the system being debugged is not included in the list. See RMHost requirements on page 14 for details on hardware supported by the RealMonitor host controller.

Note

It is possible to specify only a processor without specifying a board. In this case, only the processor state (coprocessor 15) is displayed by AXD when the module server is enabled. If you specify only a board, and no processor, only the state of the board peripherals is displayed by AXD when the module server is enabled.

9.Click OK.

28

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

ARM DUI 0137A

Page 21 Page 23
Image 22
Page 21 Page 23
Contents ARM RMHost ARM RMHost User GuideUser Guide Chapter Debugging with RMHostContents Preface About this book onIntended audience Using this bookAbout this book 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