OM11077 NXP Semiconductors, OM11077 Datasheet - Page 752

• Manufacturer Part Number: OM11077
• Description: MODULE DIMM LPC2478 ARM7
• Manufacturer: NXP Semiconductors

Specifications of OM11077

• Accessory Type: Module Card
• For Use With/related Products: ARM-57TS-LPC2478
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Other names: 568-4742

NXP Semiconductors
UM10237_4
User manual
4.9.1 RealMonitor exception handling
4.5 Prefetch Abort mode
4.6 Data Abort mode
4.7 User/System mode
4.8 FIQ mode
4.9 Handling exceptions
RealMonitor uses four words on entry to its Prefetch abort interrupt handler.
RealMonitor uses four words on entry to its data abort interrupt handler.
RealMonitor makes no use of this stack.
RealMonitor makes no use of this stack.
This section describes the importance of sharing exception handlers between
RealMonitor and user application.
To function properly, RealMonitor must be able to intercept certain interrupts and
exceptions.
itself, or shared between RealMonitor and application. If user application requires the
exception sharing, they must provide function (such as app_IRQDispatch ()). Depending
on the nature of the exception, this handler can either:
In a simple case where an application has no exception handlers of its own, the
application can install the RealMonitor low-level exception handlers directly into the vector
table of the processor. Although the irq handler must get the address of the Vectored
Interrupt Controller. The easiest way to do this is to write a branch instruction (<address>)
into the vector table, where the target of the branch is the start address of the relevant
RealMonitor exception handler.
•
•
Pass control to the RealMonitor processing routine, such as rm_irqhandler2().
Claim the exception for the application itself, such as app_IRQHandler ().
Figure 35–151
Rev. 04 — 26 August 2009
illustrates how exceptions can be claimed by RealMonitor
Chapter 35: LPC24XX RealMonitor
UM10237
© NXP B.V. 2009. All rights reserved.
752 of 792