03.01.2015 Views

80C186EC/80C188EC Microprocessor User's Manual

80C186EC/80C188EC Microprocessor User's Manual

80C186EC/80C188EC Microprocessor User's Manual

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.

OVERVIEW OF THE 80C186 FAMILY ARCHITECTURE<br />

First Instruction Fetch<br />

From Interrupt Routine<br />

Idle<br />

Read IP<br />

Idle<br />

Read CS<br />

Idle<br />

Push Flags<br />

Idle<br />

Push CS<br />

Push IP<br />

Idle<br />

Clocks<br />

5<br />

4<br />

5<br />

4<br />

4<br />

4<br />

3<br />

4<br />

4<br />

5<br />

Total 42<br />

A1030-0A<br />

Figure 2-27. Interrupt Response Factors<br />

2.3.5 Interrupt and Exception Priority<br />

Interrupts can be recognized only on valid instruction boundaries. If an NMI and a maskable interrupt<br />

are both recognized on the same instruction boundary, NMI has precedence. The<br />

maskable interrupt will not be recognized until the Interrupt Enable bit is set and it is the highest<br />

priority.<br />

Only the single step exception can occur concurrently with another exception. At most, two exceptions<br />

can occur at the same instruction boundary and one of those exceptions must be the single<br />

step. Single step is a special case; it is discussed on page 2-47. Ignoring single step (for now),<br />

only one exception can occur at any given instruction boundary.<br />

An exception has priority over both NMI and the maskable interrupt. However, a pending NMI<br />

can interrupt the CPU at any valid instruction boundary. Therefore, NMI can interrupt an exception<br />

service routine. If an exception and NMI occur simultaneously, the exception vector is taken,<br />

then is followed immediately by the NMI vector (see Figure 2-28). While the exception has higher<br />

priority at the instruction boundary, the NMI interrupt service routine is executed first.<br />

2-46

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

Saved successfully!

Ooh no, something went wrong!