ARM ARM DUI 0137A manual Other messages from RMHost, Yes

Page 37

Debugging with RMHost

3.2.1Other messages from RMHost

In addition to the messages described in Error messages on page 37, you can also receive a message similar to that shown in Figure 3-1when either of the following occurs:

•you write to the CPSR

•the debugger writes to the CPSR after an image load.

Figure 3-1 IRQ message

In this case, RealMonitor has detected that either you or the debugger are attempting to disable either IRQs or FIQs. Because RMTarget is IRQ-driven, and because one of the purposes of RealMonitor is to allow debugging without disabling FIQs, RMHost produces this warning before allowing the write to occur.

Caution

Failure to choose the correct response to this prompt can cause the target to crash, or the debug session to lock up.

 

If you receive this message, you must click one of the following:

 

 

Yes

Write the value and disable IRQs. The specified interrupts are disabled.

 

 

If there is no code in your application to re-enable IRQs, RMTarget

 

 

 

cannot respond to some debug requests.

 

 

 

You must click Yes if your application code relies on IRQs being disabled

 

 

during initialization, such as when it needs to install its own IRQ handler.

 

 

In this case, the application enables IRQs after initialization.

 

 

No

Write the value specified, with the exception of the IRQ/FIQ disable bits.

 

 

These interrupts remain enabled.

 

 

 

 

Note

 

 

 

 

 

 

 

 

 

 

The values shown in AXD will be incorrect in this case.

 

 

 

 

 

 

 

You must click No if your target application does not enable IRQs itself.

 

 

This allows RMTarget to service interrupts.

 

 

 

 

 

 

 

ARM DUI 0137A

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

311

Page 36 Page 38
Image 37
Page 36 Page 38
Contents ARM RMHost User Guide ARM RMHostChapter Debugging with RMHost User GuideContents About this book on PrefaceAbout this book Using this bookIntended audience Typographical conventionsARM publications Further readingOther publications Feedback on RMHost FeedbackFeedback on this book ARM DUI 0137A About RMHost on RMHost requirements on Overview of RMHostApplication/RTOS About RMHostOverview of RMHost RMHost package RMHost requirementsConnecting to RMHost Procedure for connecting to RMHost using AXD Debuggers chapter of the Multi-ICE User Guide Configure interface dialog box Select Configure Interface from the Options menuDescribes how to do this RealMonitor Configuration dialog box Jtag controller search dialog box Deselect the the option Fetch module information from target No pc write access message CancelNo pc read access message Lines 2 AXD connection messages212 Debugging with RMHost Nonstop debug Debugging with RMHostBackground memory access Nonstop startup CPU register accessData messaging ProfilingSemihosting Debugging with RMHost RDI Error messages Target does not include an ARM processor Memory map forbids reading from location RMHost could not load the specified Jtag controller Yes Other messages from RMHost312 Asic Using RMHost with Trace Debug ToolsPerformance of RMHost with TDT Configuring AXD to enable tracing with RMHostSelect Debugger Internals from the System Views menu Rmoptsdminfo IndexRmoptdatalogging Rmoptgetpc
Top Page Image Contents