INTERRUPTS
11-17
11
11.6.8.3
Mixed Mode
In mixed mode, pins XINT0 through XINT4 are configured for expanded mode. These pins are
encoded for the five most-significant bits of an expanded-mode vector number; the three
least-significant bits of the vector number are set internally to 010
2
. Pins XINT5 through XINT7
are configured for dedicated mode.
Do not write to the low-order four bits of IMAP0 as these bits are used to buffer the
expanded-mode interrupt internally. XINT[4:1] are placed in IMAP0[3:0]; XINT0 is latched in a
special register for use in further arbitrating the interrupt and in selecting the interrupt handler.
IMSK register bit 0 is a global mask for the expanded-mode interrupts; bits 5 through 7 mask the
dedicated interrupts from pins XINT5 through XINT7, respectively. IMSK register bits 1-4 must
be set to 0 in mixed mode. The IPND register posts interrupts from the dedicated-mode pins
XINT[7:5]. IPND register bits that correspond to expanded-mode inputs are not used.
11.6.9
Saving the Interrupt Mask
Whenever an interrupt requested by XINT[7:0] or by the internal timers is serviced, the IMSK
register is automatically saved in register r3 of the new local register set allocated for the interrupt
handler. After the mask is saved, the IMSK register is optionally cleared. This allows all interrupts
except NMIs to be masked while an interrupt is being serviced. Since the IMSK register value is
saved, the interrupt procedure can restore the value before returning. The option of clearing the
mask is selected by programming the ICON register as described in
section 11.7.4, “Interrupt
Control Register (ICON)” (pg. 11-22)
. Several options are provided for interrupt mask handling:
•
Mask unchanged
•
Cleared for dedicated-mode sources only
•
Cleared for expanded-mode sources only
•
Cleared for all hardware-requested interrupts (dedicated and expanded mode)
The second and third options are used in mixed mode, where both dedicated-mode and
expanded-mode inputs are allowed. Timer unit interrupts are always dedicated-mode interrupts.
Note that when the same interrupt is requested simultaneously by a dedicated- and an
expanded-mode source, the interrupt is considered an expanded-mode interrupt and the IMSK
register is handled accordingly.
Summary of Contents for i960 Jx
Page 1: ...Release Date December 1997 Order Number 272483 002 i960 Jx Microprocessor Developer s Manual ...
Page 24: ......
Page 25: ...1 INTRODUCTION ...
Page 26: ......
Page 35: ...2 DATA TYPES AND MEMORY ADDRESSING MODES ...
Page 36: ......
Page 46: ......
Page 47: ...3 PROGRAMMING ENVIRONMENT ...
Page 48: ......
Page 73: ...4 CACHE AND ON CHIP DATA RAM ...
Page 74: ......
Page 85: ...5 INSTRUCTION SET OVERVIEW ...
Page 86: ......
Page 111: ...6 INSTRUCTION SET REFERENCE ...
Page 112: ......
Page 233: ...7 PROCEDURE CALLS ...
Page 234: ......
Page 256: ......
Page 257: ...8 FAULTS ...
Page 258: ......
Page 291: ...9 TRACING AND DEBUGGING ...
Page 292: ......
Page 309: ...10 TIMERS ...
Page 310: ......
Page 324: ......
Page 325: ...11 INTERRUPTS ...
Page 326: ......
Page 369: ...12 INITIALIZATION AND SYSTEM REQUIREMENTS ...
Page 370: ......
Page 412: ......
Page 413: ...13 MEMORY CONFIGURATION ...
Page 414: ......
Page 429: ...14 EXTERNAL BUS ...
Page 430: ......
Page 468: ......
Page 469: ...15 TEST FEATURES ...
Page 470: ......
Page 493: ...A CONSIDERATIONS FOR WRITING PORTABLE CODE ...
Page 494: ......
Page 502: ......
Page 503: ...B OPCODES AND EXECUTION TIMES ...
Page 504: ......
Page 515: ...C MACHINE LEVEL INSTRUCTION FORMATS ...
Page 516: ......
Page 523: ...D REGISTER AND DATA STRUCTURES ...
Page 524: ......
Page 550: ......
Page 551: ...GLOSSARY ...
Page 552: ......
Page 561: ...INDEX ...
Page 562: ......
Page 578: ......