CONSIDERATIONS FOR WRITING PORTABLE CODE
A-6
A.8
MEMORY CONFIGURATION
The i960 Jx processors employ Physical Memory Control (PMCON) and Logical Memory
Control (LMCON) registers to control bus width, byte order and the data cache. This capability is
analogous to the MCON register scheme employed by the i960 Cx processor. Memory
configurations, like the bus control unit, are implementation specific.
A.9
INTERRUPTS
The i960 architecture defines the interrupt servicing mechanism. This includes priority definition,
interrupt table structure and interrupt context switching that occurs when an interrupt is serviced.
The core architecture does not define the means for requesting interrupts (external pins, software,
etc.) or for posting interrupts (i.e., saving pending interrupts).
The method for requesting interrupts depends on the implementation. The i960 Jx processors have
an interrupt controller that manages nine external interrupt pins. The organization of these pins
and the registers of the interrupt controller are implementation specific. Code that configures the
interrupt controller is not directly portable to other i960 implementations.
On the i960Jx processors, interrupts may also be requested in software with the
sysctl
instruction.
This instruction and the software request mechanism are implementation specific.
Posting interrupts is also implementation specific. Different implementations may optimize
interrupt posting according to interrupt type and interrupt controller configuration. A pending
priorities and pending interrupts field is provided in the interrupt table for interrupt posting.
However, the i960 Jx processors post hardware-requested interrupts internally in the IPND
register instead. Code that requests interrupts by setting bits in the pending priorities and pending
interrupts field of the interrupt table is not portable. Also, application code that expects interrupts
to be posted in the interrupt table is not object-code portable to all i960-based products.
The i960 Jx processors do not store a resumption record for suspended instructions in the interrupt
or fault record. Portable programs must tolerate interrupt stack frames with and without these
resumption records.
A.10 OTHER i960 Jx PROCESSOR IMPLEMENTATION-SPECIFIC FEATURES
Subsections that follow describe additional implementation-specific features of the i960 Jx
processors. These features do not relate directly to application code portability.
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: ......