
INTERRUPTS
11-9
11
11.6.3
Timer Interrupts
Each of the two timer units has an associated interrupt to allow the application to accept or post the
interrupt request. Timer unit interrupt requests are always handled as dedicated-mode interrupt
requests.
11.6.4
Software Interrupts
The application program may use the
sysctl
instruction to request interrupt service. The vector that
sysctl
requests is serviced immediately or posted in the interrupt table’s pending interrupts section,
depending upon the current processor priority and the request’s priority. The interrupt controller
caches the priority of the highest priority interrupt posted in the interrupt table. The processor can
request vector 248 (NMI) as a software interrupt; however, the interrupt vector will be read from
the interrupt table, not from the internal vector cache.
11.6.5
Posting Interrupts
Interrupts are posted to the processor by a number of different mechanisms; these are described in
the following sections.
•
Software interrupts: interrupts posted through the interrupt table, by software running on
the i960 Jx processor.
•
External Interrupts: interrupts posted through the interrupt table, by an external agent to
the i960 Jx processor.
•
Hardware interrupts: interrupts posted directly to the i960 Jx processor through an imple-
mentation-dependent mechanism that may avoid using the interrupt table.
11.6.5.1
Posting Software Interrupts via sysctl
In the i960 Jx processor,
sysctl
is typically used to request an interrupt in a program (see
Example 11-1
). The request interrupt message type (00H) is selected and the interrupt vector
number is specified in the least significant byte of the instruction operand. See
section 6.2.67,
“sysctl” (pg. 6-114)
for a complete discussion of
sysctl
.
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: ......