“Interrupts in 65xx processors”的意思、由来-开放百科全书

The 65xx family of microprocessors, consisting of the MOS Technology 6502 and its derivatives, the WDC 65C02, WDC 65C802 and WDC 65C816, and CSG 65CE02, all handle interrupts in a similar fashion. There are three hardware interrupt signals common to all 65xx processors and one software interrupt, the {{mono|BRK}} instruction. The WDC 65C816 adds a fourth hardware interrupt—{{mono|ABORT}}, useful for implementing virtual memory architectures—and the {{mono|COP}} software interrupt instruction (also present in the 65C802), intended for use in a system with a coprocessor of some type (e.g., a floating point processor).^[1]^[2]

Interrupt types

The detection of a {{mono|RESET}} signal causes the processor to enter a system initialization period of six clock cycles, after which it sets the interrupt request disable flag in the status register and loads the program counter with the values stored at the processor initialization vector ({{mono|$00FFFC}}–{{mono|$00FFFD}}) before commencing execution.^[2] If operating in native mode, the 65C816/65C802 are switched back to emulation mode and stay there until returned to native mode under software control.

The detection of an {{mono|NMI}} or {{mono|IRQ}} signal, as well as the execution of a {{mono|BRK}} instruction, will cause the same overall sequence of events, which are, in order:^[2]^[1]

The behavior of the 65C816 when {{mono|ABORT}} is asserted differs in some respects from the above description and is separately discussed below.

Note that the processor does not push the accumulator and index registers on to the stack—code in the interrupt handler must perform that task, as well as restore the registers at the termination of interrupt processing, as necessary. Also note that the vector for {{mono|IRQ}} is the same as that for {{mono|BRK}} in all eight bit 65xx processors, as well as in the 65C802/65C816 when operating in emulation mode. When operating in native mode, the 65C802/65C816 provide separate vectors for {{mono|IRQ}} and {{mono|BRK}}.^[15]

When set, the interrupt request disable flag (the {{mono|I}} bit in the status register) will disable detection of the {{mono|IRQ}} signal, but will have no effect on any other interrupts (however, see below section on the {{mono|WAI}} instruction implemented in WDC CMOS processors). Additionally, with the 65(c)02 or the 65C816/65C802 operating in emulation mode, the copy of the status register that is pushed on to the stack will have the {{mono|B}} flag set if a {{mono|BRK}} (software interrupt) was the cause of the interrupt, or cleared if an {{mono|IRQ}} was the cause.{{refn|The value of the {{mono|B}} flag in the status register itself is always {{mono|1}}, regardless of the interrupt type. {{mono|B}} is meaningful only in the copy of the status register that is pushed onto the stack in response to an interrupt.^[2]|group=nb}} Hence the interrupt service routine must retrieve a copy of the saved status register from where it was pushed onto the stack and check the status of the {{mono|B}} flag in order to distinguish between an {{mono|IRQ}} and a {{mono|BRK}}.^[2]^[3]^[4] This requirement is eliminated when operating the 65C802/65C816 in native mode, due to the separate vectors for the two interrupt types.^[3]

{{mono|ABORT}} interrupt

The 65C816's {{mono|ABORTB}} interrupt input is intended to provide the means to redirect program execution when a hardware exception is detected, such as a page fault or a memory access violation. Hence the processor's response when the {{mono|ABORTB}} input is asserted (negated) is different from when {{mono|IRQB}} and/or {{mono|NMIB}} are asserted. Also, achieving correct operation in response to {{mono|ABORTB}} requires that the interrupt occur at the proper time during the machine cycle, whereas no such requirement exists for {{mono|IRQB}} or {{mono|NMIB}}.

When {{mono|ABORTB}} is asserted during a valid memory cycle, that is, when the processor has asserted the {{mono|VDA}} and/or {{mono|VPA}} status outputs, the following sequence of events will occur:^[3]

As the address pushed to the stack is that of the aborted instruction rather than the contents of the program counter, executing an {{mono|RTI}} (ReTurn from Interrupt) following an {{mono|ABORT}} interrupt will cause the processor to return to the aborted instruction, rather than the next instruction, as would be the case with the other interrupts.

In order for the processor to correctly respond to an abort, system logic must assert (negate) the {{mono|ABORTB}} input as soon as a valid address has been placed on the bus and it has been determined that the address constitutes a page fault, memory access violation or other anomaly (e.g., attempted execution of a privileged instruction). Hence the logic must not assert {{mono|ABORTB}} until the processor has asserted the {{mono|VDA}} or {{mono|VPA}} signals. Also, {{mono|ABORTB}} must remain asserted until the fall of the phase-two clock and then be immediately released. If these timing constraints are not observed, the abort interrupt handler itself may be aborted, causing registers and/or memory to be changed in a possibly-undefined manner.^[3]

Interrupt anomalies

In the NMOS 6502 and derivatives (e.g., 6510), the simultaneous assertion of a hardware interrupt line and execution of {{mono|BRK}} was not accounted for in the design—the {{mono|BRK}} instruction will be ignored in such a case. Also, the status of the decimal mode flag in the processor status register is unchanged following an interrupt of any kind. This behavior can potentially result in a difficult to locate bug in the interrupt handler if decimal mode happens to be enabled at the time of an interrupt. These anomalies were corrected in all CMOS versions of the processor.^[3]

Interrupt handler considerations

A well-designed and succinct interrupt handler or interrupt service routine (ISR) will not only expeditiously service any event that causes an interrupt, it will do so without interfering in any way with the interrupted foreground task—the ISR must be "transparent" to the interrupted task (although exceptions may apply in specialized cases). This means that the ISR must preserve the microprocessor (MPU) state and not disturb anything in memory that it is not supposed to disturb. Additionally, the ISR should be fully reentrant, meaning that if two interrupts arrive in close succession, the ISR will be able to resume processing the first interrupt after the second one has been serviced. Reentrancy is achieved by using only the MPU hardware stack for storage.

Preserving the MPU state means that the ISR must assure that whatever values were in the MPU registers at the time of the interrupt are there when the ISR terminates. A part of the preservation process is automatically handled by the MPU when it acknowledges the interrupt, as it will push the program counter (and program bank in the 65C816/65C802) and status register to the stack prior to executing the ISR. At the completion of the ISR, when the {{mono|RTI}} instruction is executed, the MPU will reverse the process. No member of the 65xx family pushes any other registers to the stack.^[3]

In most ISRs, the accumulator and/or index registers must be preserved to assure transparency and later restored as the final steps prior to executing {{mono|RTI}}. In the case of the 65C816/65C802, consideration must be given to whether it is being operated in emulation or native mode at the time of the interrupt. If the latter, it may also be necessary to preserve the data bank ({{mono|DB}}) and direct (zero) page ({{mono|DP}}) registers to guarantee transparency. Also, a 65C816 native mode operating system may well use a different stack location than the application software, which means the ISR would have to preserve and subsequently restore the stack pointer ({{mono|SP}}). Further complicating matters with the 65C816/65C802 is that the sizes of the accumulator and index registers may be either 8 or 16 bits when operating in native mode, requiring that their sizes be preserved for later restoration.^[3]

The methods by which the MPU state is preserved and restored within an ISR will vary with the different versions of the 65xx family. For NMOS processors (e.g., 6502, 6510, 8502, etc.), there can be only one method by which the accumulator and index registers are preserved, as only the accumulator can be pushed to and pulled from the stack.^[5] Therefore, the following ISR entry code is typical:

The {{mono|CLD}} instruction is necessary because, as previously noted, NMOS versions of the 6502 do not clear the {{mono|D}} (decimal mode) flag in the status register when an interrupt occurs.

Once the accumulator and index registers have been preserved, the ISR can use them as needed. When the ISR has concluded its work, it would restore the registers and then resume the interrupted foreground task. Again, the following NMOS code is typical:

A consequence of the {{mono|RTI}} instruction is the MPU will return to decimal mode if that was its state at the time of the interrupt.^[5]

The 65C02, and the 65C816/65C802 when operating in emulation mode, require less code, as they are able to push and pull the index registers without using the accumulator as an intermediary.^[3] They also automatically clear decimal mode before executing the ISR.^[3] The following is typical:

As previously stated, there is a little more complexity with the 65C816/65C802 when operating in native mode due to the variable register sizes and the necessity of accounting for the {{mono|DB}} and {{mono|DP}} registers. In the case of the index registers, they may be pushed without regard to their sizes, as changing sizes automatically sets the most significant byte (MSB) in these registers to zero and no data will be lost when the pushed value is restored, provided the index registers are the same size they were when pushed.^[3]

The accumulator, however, is really two registers: designated {{mono|.A}} and {{mono|.B}}.^[3] Pushing the accumulator when it is set to 8 bits will not preserve {{mono|.B}},^[3] which could result in a loss of transparency should the ISR change {{mono|.B}} in any way. Therefore, the accumulator must always be set to 16 bits before being pushed or pulled if the ISR will be using {{mono|.B}}. It is also more efficient to set the index registers to 16 bits before pushing them. Otherwise, the ISR has to then push an extra copy of the status register so it can restore the register sizes prior to pulling them from the stack.

In the above code fragment, the symbol {{mono|%}} is MOS Technology and WDC standard assembly language syntax for a bitwise operand.

If the ISR has its own assigned stack location, preservation of the stack pointer ({{mono|SP}}) must occur in memory after the above pushes have occurred—it should be apparent why this is so. The following code, added to the above sequence, would handle this requirement:

Note that upon executing {{mono|RTI}}, the 65C816/65C802 will automatically restore the register sizes to what they were when the interrupt occurred, since pulling the previously–saved status register sets or clears both register size bits to what they were at the time of the interrupt.^[3]

While it is possible to switch the 65C816/65C802 from native mode to emulation mode within an ISR, such is fraught with peril.^[3] In addition to forcing the accumulator and index registers to 8 bits (causing a loss of the most significant byte in the index registers), entering emulation mode will truncate the stack pointer to 8 bits and relocate the stack itself to page 1 RAM.^[3] The result is the stack that existed at the time of the interrupt will be inaccessible unless it was also in page 1 RAM and no larger than 256 bytes. In general, mode switching while servicing an interrupt is not a recommended procedure, but may be necessary in specific operating environments.

Using {{mono|BRK}} and {{mono|COP}}

As previously noted, {{mono|BRK}} and {{mono|COP}} are software interrupts and, as such, may be used in a variety of ways to implement system functions.

A historical use of {{mono|BRK}} has been to assist in patching PROMs when bugs were discovered in a system's firmware. A typical technique often used during firmware development was to arrange for the {{mono|BRK}} vector to point to an unprogrammed "patch area" in the PROM. In the event a bug was discovered, patching would be accomplished by "blowing" all of the fuses at the address where the faulty instruction was located, thus changing the instruction's opcode to {{mono|$00}}. Upon executing the resulting {{mono|BRK}}, the MPU would be redirected to the patch area, into which suitable patch code would be written. Often, the patch area code started by "sniffing the stack" to determine the address at which the bug was encountered, potentially allowing for the presence of more than one patch in the PROM. The use of {{mono|BRK}} for PROM patching diminished once EPROMs and EEPROMs became commonly available.

Another use of {{mono|BRK}} in software development is as a debugging aid in conjunction with a machine language monitor. By overwriting an opcode with {{mono|BRK}} ({{mono|$00}}) and directing the {{mono|BRK}} hardware vector to the entry point of the monitor, one can cause a program to halt at any desired point, allowing the monitor to take control. At that time, one may examine memory, view the processor's register values, patch code, etc. Debugging, as advocated by Kuckes and Thompson, can be facilitated by liberally sprinkling one's code with {{mono|NOP}} instructions (opcode {{mono|$EA}}) that can be replaced by {{mono|BRK}} instructions without altering the actual behaviour of the program being debugged.^[5]^[6]^[7]

A characteristic of the {{mono|BRK}} and {{mono|COP}} instructions is that the processor treats either as a two byte instruction: the opcode itself and the following byte, which is referred to as the "signature."^[3] Upon execution of {{mono|BRK}} or {{mono|COP}}, the processor will add two to the program counter prior to pushing it to the stack. Hence when {{mono|RTI}} (ReTurn from Interrupt) is executed, the interrupted program will continue at the address immediately following the signature. If {{mono|BRK}} is used as a debugging device, the program counter may have to be adjusted to point to the signature in order for execution to resume where expected. Alternatively, a {{mono|NOP}} may be inserted as a signature "placeholder," in which case no program counter adjustment will be required.

The fact that {{mono|BRK}} and {{mono|COP}} double-increment the program counter before pushing it to the stack facilitates the technique of treating them as supervisor call instructions, as found on some mainframe computers. The usual procedure is to treat the signature as an operating system service index. The operating system {{mono|BRK}} or {{mono|COP}} handler would retrieve the value of the program counter pushed to the stack, decrement it and read from the resulting memory location to get the signature.^[8]^[9] After converting the signature to a zero-based index, a simple lookup table can be consulted to load the program counter with the address of the proper service routine. Upon completion of the service routine, the {{mono|RTI}} instruction would be used to return control to the program that made the operating system call. Note that the signature for {{mono|BRK}} may be any value, whereas the signature for {{mono|COP}} should be limited to the range {{mono|$00}}-{{mono|$7F}}.^[3]

The use of {{mono|BRK}} and/or {{mono|COP}} to request an operating system service means user applications do not have to know the entry address of each operating system function, only the correct signature byte to invoke the desired operation. Hence relocation of the operating system in memory will not break compatibility with existing user applications. Also, as executing {{mono|BRK}} or {{mono|COP}} always vectors the processor to the same address, simple code may be used to preserve the registers on the stack prior to turning control over to the requested service. However, this programming model will result in somewhat slower execution as compared to calling a service as a subroutine, primarily a result of the stack activity that occurs with any interrupt. Also, interrupt requests will have been disabled by executing {{mono|BRK}} or {{mono|COP}}, requiring that the operating system re-enable them.

{{mono|WAI}} and {{mono|STP}} instructions

{{mono|WAI}} (WAit for Interrupt, opcode {{mono|$CB}}) is an instruction available on the WDC version of the 65C02 and the 65C816/65C802 microprocessors (MPU) that halts the MPU and places it into a semi-catatonic state until a hardware interrupt of any kind occurs.^[3] The primary use for {{mono|WAI}} is in low-power embedded systems where the MPU has nothing to do until an expected event occurs, minimal power consumption is desired as the system is waiting and a quick response is required. A typical example of code that would make use of {{mono|WAI}} is as follows:

In the above code fragment, the MPU will halt upon execution of {{mono|WAI}} and go into a very low power consumption state. Despite interrupt requests (IRQ) having been disabled prior to the {{mono|WAI}} instruction, the MPU will respond to any hardware interrupt while waiting. Upon receipt of an interrupt, the MPU will "awaken" in one clock cycle and resume execution at the instruction immediately following {{mono|WAI}}. Hence interrupt latency will be very short (70 nanoseconds at 14 megahertz), resulting in the most rapid response possible to an external event.

Similar in some ways to {{mono|WAI}} is the {{mono|STP}} (SToP, opcode {{mono|$DB}}) instruction, which completely shuts down the MPU while waiting for a single interrupt input.^[3] When {{mono|STP}} is executed, the MPU halts its internal clock (but does retain all data in its registers) and enters a low power state. The MPU is brought out of this state by pulling its reset input pin ({{mono|RESB}}, which is classified as an interrupt input) low. Execution will then resume at the address stored at locations {{mono|$00FFFC-$00FFFD}}, the hardware reset vector. As with {{mono|WAI}}, {{mono|STP}} is intended for use in low power embedded applications where long periods of time may elapse between events that require MPU attention and no other processing is required. {{mono|STP}} would not be used in normal programming, as it would result in total cessation of processing.

Footnotes

1. ^¹{{cite web|url=http://www.obelisk.demon.co.uk./6502/architecture.html|date=2002-01-02|title=Basic Architecture|work=6502}}
2. ^¹²³⁴{{cite book|title=Microprocessor Technology|author=J. S. Anderson|pages=143–144|publisher=Butterworth-Heinemann|date=1994|isbn=9780750618397}}
3. ^¹²³⁴⁵⁶⁷⁸⁹¹⁰¹¹¹²¹³¹⁴¹⁵¹⁶¹⁷¹⁸¹⁹²⁰²¹²²²³²⁴²⁵²⁶{{cite paper|title=Programming the 65816|author=David Eyes and Ron Lichty|date=1992-04-28|publisher=The Western Design Center, Inc.|format=PDF|url=http://westerndesigncenter.com/wdc/datasheets/Programmanual.pdf}}
4. ^¹{{cite book|pages=172–173|title=6502 Software Design|author=Leo J. Scanlon|publisher=H. W. Sams|date=1980|isbn=9780672216565}}
5. ^¹²{{cite book|title=6502 Assembly Language Programming|author=Lance A. Leventhal|publisher=Osborne/McGraw-Hill|date=1986|isbn=9780078812163}}
6. ^{{cite book|title=Microprocessors and Microcomputers: Hardware and Software|author=Ronald J. Tocci and Lester P. Laskowski|publisher=Prentice-Hall|date=1979|isbn=9780135813225|page=379}}
7. ^{{cite book|title=Apple II in the Laboratory|author=Arthur F. Kuckes and B. G. Thompson|publisher=UP Archive|date=1987|isbn=9780521321983|page=93}}
8. ^{{cite magazine |last= Harrod |first= Dennette A. |url= http://www.wiz-worx.com/resume/byte8010.htm |title= 6502 Gets Microprogrammable Instructions |magazine=BYTE |date=October 1980 |publisher= McGraw Hill |volume= 5 |issue= 10 |pages=282–285}}
9. ^{{cite book|title=Microprocessor Programming and Applications for Scientists and Engineers|author=Richard R. Smardzewski|publisher=Elsevier|date=1984|isbn=9780444424075|page=125}}