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

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