28.10.2014 Views

MMC2107 - Freescale Semiconductor

MMC2107 - Freescale Semiconductor

MMC2107 - Freescale Semiconductor

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Freescale</strong> <strong>Semiconductor</strong>, Inc.<br />

Interrupt Controller Module<br />

Functional Description<br />

If an interrupt is pending at a given priority level and both the<br />

corresponding FIER and NIER bits are set, then both the corresponding<br />

FIPR and NIPR bits are set, assuming these bits are not masked.<br />

Fast interrupt requests always have priority over normal interrupt<br />

requests, even if the normal interrupt request is at a higher priority level<br />

than the highest fast interrupt request.<br />

If the fast interrupt signal is asserted when the normal interrupt signal is<br />

already asserted, then the normal interrupt signal is negated.<br />

nc...<br />

<strong>Freescale</strong> <strong>Semiconductor</strong>, I<br />

IPR, NIPR, and FIPR are read-only. To clear a pending interrupt, the<br />

interrupt must be cleared at the source using a special clearing<br />

sequence defined by each source. All interrupt sources to the interrupt<br />

controller are to be held until recognized and cleared by the interrupt<br />

service routine. The interrupt controller does not have any edge-detect<br />

logic. Edge-triggered interrupt sources are handled at the source<br />

module.<br />

In ICR, the MASK[4:0] bits can mask interrupt sources at and below a<br />

selected priority level. The MFI bit determines whether the mask applies<br />

only to normal interrupts or to fast interrupts with all normal interrupts<br />

being masked. The ME bit enables interrupt masking.<br />

ISR reflects the current vector number and the states of the signals to<br />

the M•CORE processor.<br />

The vector number and fast/normal interrupt sources are synchronized<br />

before being sent to the M•CORE processor. Thus, the interrupt<br />

controller adds one clock of latency to the interrupt sequence. The fast<br />

and normal interrupt raw sources are not synchronized to allow these<br />

signals to be used to wake up the M•CORE processor during stop mode<br />

when all system clocks are stopped.<br />

7.8.3 Autovectored and Vectored Interrupt Requests<br />

The AE bit in ICR enables autovectored interrupt requests to the<br />

M•CORE processor. AE is set by default, and all interrupt requests are<br />

autovectored. An interrupt handler may read FIPR or NIPR to determine<br />

the priority of the interrupt source. If multiple interrupt sources share the<br />

same priority level, then it is up to the interrupt service routine to<br />

determine the correct source of the interrupt.<br />

<strong>MMC2107</strong> – Rev. 2.0<br />

Technical Data<br />

MOTOROLA Interrupt Controller Module 169<br />

For More Information On This Product,<br />

Go to: www.freescale.com

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!