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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

INTERRUPT CONTROL UNIT<br />

Register Name:<br />

Register Mnemonic:<br />

Register Function:<br />

Timer Interrupt Request Latch<br />

TIMIRL<br />

Latches Timer/Counter Unit interrupt requests.<br />

15 0<br />

M<br />

S<br />

K<br />

3<br />

M<br />

S<br />

K<br />

2<br />

M<br />

S<br />

K<br />

1<br />

M<br />

S<br />

K<br />

0<br />

<br />

T<br />

I<br />

R<br />

2<br />

T<br />

I<br />

R<br />

1<br />

T<br />

I<br />

R<br />

0<br />

A1235-0A<br />

Bit<br />

Mnemonic<br />

Bit Name<br />

Reset<br />

State<br />

Function<br />

TIR2:0<br />

Timer<br />

Interrupt<br />

Request<br />

0H<br />

The corresponding timer sets a bit in this<br />

register to post an interrupt request. These bits<br />

must be cleared to deassert the IR signal to the<br />

8259A module.<br />

MSK2:0<br />

IR Latch<br />

Clear Mask<br />

XH<br />

This bit must be set to modify the state of the<br />

associated TIR2:0 bit. The MSK2:0 bits are<br />

safeguards against accidentally clearing a<br />

pending interrupt request. These bits are write<br />

only.<br />

NOTE:<br />

Reserved register bits are shown with gray shading. Reserved bits must be written<br />

to a logic zero to ensure compatibility with future Intel products.<br />

Figure 8-26. Timer Interrupt Request Latch Register<br />

8.6 HARDWARE CONSIDERATIONS WITH THE INTERRUPT CONTROL UNIT<br />

This section covers hardware interface information for the Interrupt Control Unit. Specific timing<br />

values are not presented, as these are subject to change. Consult the most recent version of the<br />

data sheet for timing information.<br />

8-42

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

Saved successfully!

Ooh no, something went wrong!