Computer System With a Bus Controller

1. Field of the Invention

This invention relates to computer processors, and more particularly to using programmable logic devices (PLDs) for a bus controller, a clock generator and a wait state controller for a V33 microprocessor.

2. Description of Related Art

The V33 microprocessor is described in .mu.PD70136 (V33) 16-Bit Microprocessors: High-Speed, CMOS, a publication available from NEC Electronics Inc., 401 Ellis Street, P.O. Box 7241, Mountain View, Calif. 94039. The V33 microprocessor has an internal clock rate of up to 16 MHz. As shown in FIG. 1, the V33 microprocessor 1 has data lines D.sub.0 -D.sub.15 which carry data between microprocessor 1 and, say, circuitry 1000 which may contain memory, I/O and other devices. Microprocessor 1 also has address lines A.sub.0 -A.sub.23 which can be used, for example, to carry the address of a memory location in circuitry 1000 to which location data on D.sub.0 -D.sub.15 must be written by microprocessor 1 or from which location data must be driven onto D.sub.0 -D.sub.15 to be subsequently read by microprocessor 1. Microprocessor 1 also has status lines BUSST0, BUSST1, M/IO, R/W, UBE, BCYST, and DSTB. These lines inform circuitry 1000 of the state of microprocessor 1. For example, DSTB is asserted low by microprocessor 1 when microprocessor 1 writes data on D.sub.0 -D.sub.15 or ,reads data from D.sub.0 -D.sub.15. Thus DSTB can be used to signal circuitry 1000 when to start or stop reading data from D.sub.0 -D.sub.15 or writing data onto D.sub.0 -D.sub.15.

Signals on some of the lines of microprocessor 1 can be skewed. For example, when microprocessor 1 writes data onto D.sub.0 -D.sub.15, it may assert DSTB before the address lines A.sub.0 -A.sub.23 and the status lines BUSST0, BUSST1, M/IO, R/W, UBE and BCYST become valid. If circuitry 1000 starts reading data from D.sub.0 -D.sub.15 when DSTB gets asserted, circuitry 1000 may end up reading the data to a wrong address indicated by invalid lines A.sub.0 -A.sub.23. Also, when microprocessor 1 reads data from D.sub.0 -D.sub.15, it may deassert DSTB too soon, i.e. before it has actually finished reading. As a result, if circuitry 1000 stops driving data onto D.sub.0 -D.sub.15 when DSTB gets deasserted, microprocessor 1 might get wrong data from D.sub.0 -D.sub.15.

Such skewing of signals is not unique to the V33 microprocessor. It occurs in other fast computer processors. The problems caused by the skewing in other processors have been solved by using a bus controller. FIG. 2 shows a block diagram for such a solution. Microprocessor 900 is a fast microprocessor, such as, for example, a type 80286 available from Intel Corporation, Santa Clara, Calif. A circuitry 1001, like circuitry 1000 in FIG. 1, may contain memory, I/O, and other devices. Lines 990 include data and address lines of microprocessor 900. A bus controller 901 is a logic device which accepts, as input, status lines 991 from microprocessor 900 and, perhaps, some other signals (not shown), for example, a clock signal. Bus controller 901 produces control signals 992 which inform circuitry 1001 of the state of microprocessor 900 and which are free from skewing problems of lines 990 and 991. An example of bus controller 901 is the type 82288 controller described in 82288 Bus Controller for iAPX 286 Processors (INTEL Corporation, 1985). Also known in the prior art is a PLD programmed to perform as bus controller 901 for INTEL 80286. Unfortunately, these bus controllers cannot be used with a type V33 microprocessor because the status lines, address lines and data lines of the type 80286 microprocessor have different characteristics from those lines of the type V33 microprocessor. A bus controller for a V33 microprocessor has not been so far provided.

To cause V33 microprocessor 1, FIG. 1, to operate at 16 MHz, a 16 MHz clock signal (processor clock) must be provided on input CLK of microprocessor 1. A diagram of such a signal 47 is shown in FIG. 3. The signal 47 is used to synchronize the operation of microprocessor 1. That is to say, microprocessor 1 detects when the processor clock 47 is high (segment 63, FIG. 3), when it is low (segment 64), and when the transitions 65 between the high and low states occur, and microprocessor 1 performs some well-defined operations when the processor clock is high, some operations when the processor clock is low, some operations during the transitions from the low level to the high level (i.e. on the rising edge of the processor clock 47), and some operations during the transitions from the high level to the low level (on the falling edge of the processor clock 47).

A 16 MHz clock signal can be generated by an oscillator. FIG. 3 shows a diagram of such a signal 48. Unfortunately, the rising and falling edges 62 of the oscillator signal 48 can be too long to be used with microprocessor 1. Microprocessor 1 requires these edges to be at most 5 ns (parameters tKR, tKF in FIG. 3). The oscillator signal edges 62 can be much longer. However, circuits are known that "waveshape" oscillator signal 48 to produce a "square" wave, i.e. a signal with shorter rising and falling edges.

In some computer systems, some devices connected to a 16 MHz processor may have to be synchronized by a faster "system" clock, say a 32 MHz clock. Such computer systems comprising, say, a 16 MHz microprocessor V60 (.mu.PD70616) are well-known in the art. Microprocessor V60 is described in the .mu.PD70616(V60) data sheet, 1986, available from NEC. In such a computer system, a 16 MHz processor clock may be generated from a 32 MHz system clock by, say, an NEC chip .mu.PD71611 described in .mu.PD71611 CMOS Clock Generator, September 1986. FIG. 4 shows a block diagram of part of such a computer system. Chip 2025 is a 16 MHz clock generator .mu.PD71611. Chip 2025 accepts a 32 MHz system clock EXFS from another clock generator 2026. From system clock EXFS, chip 2025 generates a 16 MHz processor clock CLK for a V60 microprocessor 2001. System clock EXFS is also used to synchronize devices 2003. Chip 2025 also generates an 8MHz clock PRCLK (not shown) for synchronizing other devices (not shown) connected to microprocessor 2001. FIG. 3 shows a diagram of system clock 46 (EXFS) and processor clock 49 (CLK).

Unfortunately, there exists a significant skew between the clocks EXFS and CLK. In other words, as is seen from FIG. 3, there is a significant time difference between the edges of EXFS and CLK. The time interval tDCKL between the falling edge 66 of the system clock EXFS and the falling edge 68 of the processor clock CLK can be up to 20 ns. The time interval tDCKH between the falling edge 67 of the system clock EXFS and the rising edge 69 of the processor clock CLK can also be up to 20 ns. Some computer systems need that skew to be much smaller.

It should also be noted that chip 2025 is a customized, non-programmable chip.

A typical operation of microprocessor 1, such as reading data from memory or writing data to an I/O device, lasts one bus cycle. FIG. 5 shows a diagram of processor clock 47 (CLK) in a bus cycle. Each bus cycle starts on a falling edge of the processor clock 47 (point 85 in FIG. 5) and lasts for 2 or more periods of the clock 47 depending on how fast the memory or the I/O device is. Each such period of the clock 47 is called a bus state. The first bus state of a bus cycle is called T1, the second bus state T2. A bus cycle may consist of only two bus states--T1 and T2. Yet if a memory or I/O device needs more time to complete the operation, microprocessor 1 will insert additional bus states (called wait states) into the bus cycle. The bus cycle in FIG. 5 has 3 wait states--TW1, TW2 and TW3.

Devices connected to microprocessor 1, such as devices of circuitry 1000, inform microprocessor 1 that they are ready for the current bus cycle to terminate, by asserting the READY line of microprocessor 1 low. See FIG. 1. FIG. 5 shows a diagram of the READY signal 45 for a bus cycle with 3 wait states. Microprocessor 1 will sample its READY line at point 81 of T2, and since READY is high at that point, microprocessor 1 will insert the first wait state TW1. Microprocessor 1 will sample READY again at point 82 of TW1 and, seeing READY high, will insert another wait state, TW2. Microprocessor 1 will then sample READY at point 83 and, seeing READY high, will insert TW3. Microprocessor 1 will again sample READY at point 84. By this time, circuitry 1000 has asserted READY low, and microprocessor 1 will terminate the bus cycle. The next bus state will be T1 of the next bus cycle.

This way of terminating a bus cycle is not unique to the V33 microprocessor 1. V60 microprocessor 2001, FIG. 4, also has a READY line used similarly to the READY line of microprocessor 1. In prior art computer systems using the V60 microprocessor, it was found that READY generation could be simplified by using a wait state controller as shown in FIG. 4. Chip 2025, which acts as a clock generator for V60 microprocessor 2001, acts also as a wait state controller for microprocessor 2001. A device 2004 connected to chip 2000 does not itself assert the READY line of chip 2001. Instead the device 2004 provides on lines WAIT0, WAIT1, and WAIT2, the number of wait states which it wants to be inserted into the current bus cycle. This number can be any number between zero and seven. This number is provided to chip 2025 which asserts the READY line of microprocessor 2001 accordingly.

Unfortunately, chip 2025 is incompatible with V33.

Also, chip 2025 is not programmable.

This invention provides a bus controller for a V33 microprocessor. In one embodiment, the bus controller is implemented by a programmable logic device (PLD) which can be programmed by the user to closely fit the needs of a particular computer system using a V33 microprocessor.

The present invention provides also a clock generator generating both a 16 MHz clock and a 32 MHz clock with a skew between the clocks not more than 4ns. This skew is acceptable for many V33 microprocessor applications. In one embodiment, the clock generator is a PLD.

In addition, the present invention provides a programmable wait state controller.

Furthermore, the present invention provides a wait state controller for a V33 microprocessor. In one embodiment, the wait state controller and the clock generator are implemented as parts of the same PLD.

FIG. 1 shows a prior art V33 microprocessor system;

FIG. 2 shows a block diagram of a type 80286 microprocessor system with a bus controller;

FIG. 3 shows a diagram of an oscillator output signal, a diagram of a processor clock for a V33 microprocessor, and diagrams of a 32 MHz input EXFS and a 16 MHz output CLK of .mu.PD71611, a clock generator for a V60 microprocessor;

FIG. 4 shows a block diagram of a V60 microprocessor system with clock generator .mu.PD71611;

FIG. 5 shows diagrams of a processor clock and a READY line of a V33 microprocessor during a bus cycle;

FIG. 6 shows a block diagram of a V33 microprocessor system according to one embodiment of the invention;

FIG. 7 shows a more detailed block diagram of external circuitry of the embodiment of FIG. 6;

FIGS. 8, 9 and 10 show a schematic of one embodiment of the invention;

FIGS. 11(i-viii) presents PLD equations for a bus controller of the embodiment of FIGS. 8, 9, 10;

FIG. 12 shows timing diagrams of some V33 microprocessor and bus controller signals during a write cycle in one embodiment of the invention;

FIG. 13 shows timing diagrams of some V33 microprocessor and bus controller signals during a read cycle in one embodiment of the present invention;

FIG. 14 shows a state transition diagram for a state machine implemented by a bus controller according to one embodiment of the present invention;

FIG. 15(i-iv) presents PLD equations for a Ready/Clock generator of the embodiment of FIGS. 8, 9, 10;

FIG. 16 shows a block diagram of an I/O subsystem of the embodiment of FIGS. 8, 9, 10;

FIG. 17 shows a block diagram of a memory subsystem of the embodiment of FIGS. 8, 9, 10;

FIG. 18 presents a block diagram of a floating point subsystem according to one embodiment;

FIG. 19 presents a block diagram of a floating point subsystem according to another embodiment;

FIG. 20 presents a block diagram of a floating point subsystem according to a third embodiment.

FIG. 6 shows a block diagram of one embodiment of the present invention. V33 microprocessor 1 is connected to external circuitry 30 which may include I/O devices, memory devices, a floating point processor and other devices. Status lines BUSST0, BUSST1, M/IO, R/W, and BCYST of microprocessor 1 are inputs to a bus controller 20. From these and other inputs bus controller 20 produces control signals 40 which control external circuitry 30. External circuitry 30 reads data from or writes data onto data bus D.sub.0 -D.sub.15.

External circuitry 30 also accepts as input address lines A.sub.0 -A.sub.23 and status lines from microprocessor 1.

This embodiment also includes a Ready/Clock generator 25. Ready/Clock generator 25 generates a 16 MHz processor clock CLK and a 32 MHz system clock SYSCLK. The processor clock CLK is used by microprocessor 1. Both clocks are used by bus controller 20 and may be used by other parts of the system of FIG. 6.

Ready/Clock generator 25 also acts as a wait state controller for microprocessor 1. Ready/Clock generator 25 accepts on lines WC2, WC1, and WC0 from external circuitry 30 the number of wait states to be inserted into the current bus cycle. From this number, Ready/Clock generator 25 produces the READY signal for microprocessor 1.

FIG. 7 shows external circuitry 30 in greater detail. External circuitry 30 contains a computer subsystem 31, data buffers 1619, and address latches 369. Subsystem 31 contains an I/O subsystem 50, a memory subsystem 70, and a floating point subsystem 90. Some parts of subsystem 31 may be connected to data bus D.sub.0 -D.sub.15 by lines 41 directly. Other parts of subsystem 31 may be connected to data bus D.sub.0 -D.sub.15 through data buffers 1619 by lines 42(a) and 42(b). Data buffers 1619 may electrically connect or disconnect lines 42(a) and lines 42(b) from each other thus connecting or disconnecting those parts of subsystem 31 from data bus D.sub.0 -D.sub.15. Data buffers 1619 are controlled by control signals 40 from bus controller 20.

Some parts of subsystem 31 may be connected to address lines A.sub.0 -A.sub.23 and status lines directly by lines 43, other parts may be connected to address lines A.sub.0 -A.sub.23 and status lines through address latches 369 by lines 44(a) and 44(b). Address latches 369 can latch the values of the address and status lines of microprocessor 1 and maintain those values on lines 44(b) even after the values of the address and status lines of microprocessor 1 have changed. Address latches 369 are controlled by control signals 40 from bus controller 20.

V33 Microprocessor Bus Cycles

As noted above, each bus cycle of microprocessor 1 starts on a falling edge of processor clock 47 (CLK). The type of each bus cycle is determined by microprocessor 1 outputs M/IO, R/W, BUSST0, and BUSST1 according to the following table:

Microprocessor 1 bus cycles can be categorized as follows.

Read Cycles

(1) memory read group of cycles consisting of:

(i) memory read cycles (microprocessor 1 reads data from memory);

(ii) coprocessor data read cycles (coprocessor reads from memory into an internal register of the coprocessor); and

(iii) instruction fetch cycles;

(2) I/O read group consisting of:

(i) I/O read cycles (microprocessor 1 reads from an I/O device); and

(ii) coprocessor read cycles (microprocessor 1 reads from a coprocessor internal register).

Write Cycles

(1) Memory write group of cycles consisting of:

(i) memory write cycles (microprocessor 1 writes into memory); and

(ii) coprocessor data write cycles (coprocessor writes from its internal register into memory).

(2) I/O write group consisting of:

(i) I/O write cycles (microprocessor 1 writes to an I/O device); and

(ii) coprocessor write cycles (microprocessor 1 writes to an internal register of a coprocessor).

Interrupt Acknowledge Cycle

Halt Acknowledge Cycle

The following is a brief functional description of some pins of microprocessor 1. For a more complete description, see .mu.PD70136 (V33) 16-Bit Microprocessors: High-Speed, CMOS, supra, which publication is incorporated herein by reference.

Lines A.sub.0 -A.sub.23 form the address bus. These outputs become valid during T1 of every bus cycle and remain valid until the end of the bus cycle. Lines D.sub.0 -D.sub.15 form the data bus. During read cycles, microprocessor 1 latches the value of these lines on the trailing edge of the last bus state of the cycle (T2 or the last wait state). During write cycles, D.sub.0 -D.sub.15 become valid after the rising edge of T1 and remain valid through the rising edge of the CLK following the bus cycle.

Line R/W indicates whether the current bus cycle will be a read or a write cycle. If R/W is high, then the cycle will be a read cycle; if low, a write cycle.

Line M/IO indicates whether the current bus cycle will access memory or I/O; if M/IO is high, then memory; if low, I/O. Line BCYST (Bus Cycle Start) indicates the start of a bus cycle. It is asserted low during T1 of every bus cycle, and only for the first CLK period of each bus cycle.

Line DSTB (Data Strobe) indicates the status of the data bus D.sub.0 -D.sub.15. When it is asserted low during a write cycle, microprocessor 1 drives the data on D.sub.0 -D.sub.15. When microprocessor 1 asserts this output during a read cycle, external logic should drive the data onto D.sub.0 -D.sub.15. DSTB is asserted following the rising edge (middle) of T1, and stays asserted through T2 and all wait states (if any) of the bus cycle. During write cycles, DSTB is deasserted after the rising edge of the last bus state of the bus cycle. During read cycles, DSTB is deasserted after the trailing edge of the last bus state.

READY. Devices connected to microprocessor 1 assert READY low to inform microprocessor 1 that they are ready for the current bus cycle to terminate. As long as READY is not asserted, microprocessor 1 will add wait states to the current bus cycle. The bus state in which microprocessor 1 samples READY low will be the last state of the bus cycle. Microprocessor 1 samples READY on the rising (middle) edge of T2 and all wait states.

FIGS. 8, 9, and 10 show a schematic of a V33 microprocessor system. FIG. 8 shows microprocessor 1, bus controller 20, Ready/Clock generator 25, data buffers 16 and 19 corresponding to data buffers 1619 of FIG. 7, address latches 3, 6 and 9 corresponding to address latches 369 of FIG. 7, and floating point subsystem 90. Each of the address latches 3, 6 and 9 in this embodiment is implemented by chip 74AC373 well known in the art. Each of the data buffers 16 and 19 in this embodiment is implemented by chip 74AC245 also well known in the art. Control signals 40 consist of bus controller 20 outputs AEN/DEN, IOWR, IORD, MWR, MRD, ST1, ST0 and INTAK. Output AEN/DEN controls data buffers 16 and 19 and address latches 3, 6 and 9.

Address latches 3, 6 and 9 latch address lines A.sub.0 -A.sub.19 and maintain the latched values on lines BA0-BA19 respectively. Address latch 3 latches also status lines BUSST1 and M/IO and maintains their values on its outputs LBS1 and LM/IO respectively. Lines BA0-BA19, LBS1 and LM/IO form lines 44(b) of FIG. 7.

Data buffers 16 and 19 can connect data lines D.sub.0 -D.sub.15 to or disconnect them from lines BD0-BD15 respectively. Lines BD0-BD15 form lines 42(b) of FIG. 7.

Floating point subsystem 90 of FIG. 7 is implemented by an NEC floating point processor AFPP well known in the art.

Other parts of the system of FIG. 7 are implemented in this embodiment according to FIGS. 9 and 10 and are described below.

Bus Controller

Bus controller 20, FIG. 8, is implemented by a PLD, a 7.5 ns programmable array logic device 16R8 available from AMD corporation and well known in the art. FIGS. 11(i)-(viii) show PLD equations for bus controller 20 in "ABEL" assembler available on the market ("ABEL" is a registered trademark of DATA IO Corporation). Methods of using "ABEL" assembler to program PLDs are known in the art. The inputs of bus controller 20 are:

BUSST0, BUSST1, M/IO, R/W, BCYST, READY, RESET, and HLDAK (CMDEN pin 11 of bus controller 20) from microprocessor 1;

CLK, a 16 MHz processor clock, generated by Ready/Clock generator 25 as described below; and

SYSCLK, a 32 MHz system clock generated by Ready/Clock generator 25 as described below. DSTB is not an input to bus controller 20.

Outputs of bus controller 20.

ST1, ST0--identify the state of a 4-state state machine implemented by bus controller 20 and described below.

IOWR--active low. During I/O write and coprocessor write cycles, instructs an I/O device or a coprocessor, as the case may be, to read from the data bus.

IORD--active low. During I/O read and coprocessor read cycles, instructs an I/O device or a coprocessor to write onto the data bus.

MWR--active low. During memory write and coprocessor data write cycles, instructs a memory device to read from the data bus.

MRD--active low. During memory read, coprocessor data read, and instruction fetch cycles, instructs a memory device to write onto the data bus.

AEN/DEN (ADR.sub.-- DAT in PLD equations of FIGS. 11(i)-11(viii)) controls address latches 3, 6 and 9 and data buffers 16 and 19. When high, enables inputs of address latches 3, 6, and 9 to latch A.sub.0 -A.sub.19, BUSST1 and M/IO and disables inputs of data buffers 16, 19 to isolate D.sub.0 -D.sub.15 from lines BD0-BD15. When low, disables inputs of address latches 3, 6 and 9 (so that their outputs maintain A.sub.0 -A.sub.19, BUSST1 and M/IO on lines BA0-BA19, LBS1 and LM/IO respectively) and enables inputs of data buffers 16 and 19 so that D.sub.0 -D.sub.15 are electrically connected, respectively, to BD0-BD15.

INTAK--active low. During interrupt acknowledge cycles, instructs an external interrupt controller to write an interrupt vector onto the data bus.

Bus controller 20 is synchronized by the 32 MHz system clock SYSCLK. Bus controller 20 outputs change, if at all, on the rising edge of SYSCLK. See for example FIGS. 12, 13 providing timing diagrams of some of the outputs of bus controller 20.

State Machine

Bus controller 20 generates a 4-state state machine that describes the state of microprocessor 1. Bus controller outputs AEN/DEN, IOWR, IORD, MWR, MRD, and INTAK are computed with respect to that state machine. The current state of the state machine is identified by outputs ST1, ST0 of bus controller 20 as follows:

FIG. 14 shows the state transition diagram of the state machine. FIG. 12 shows the diagrams of signals ST0 and ST1 during a write cycle with no wait states. FIG. 12 shows also the diagrams of the system clock 39 (SYSCLK) and the processor clock 47 (CLK) during such a cycle. Each state transition occurs on the rising edge of system clock 39. On RESET, the state machine is in state S0. During T1 of read, write, and interrupt acknowledge cycles, BCYST gets asserted low, i.e. BCYST becomes high, and so on the falling edge of T1, the state machine enters state S1. The state machine remains in state S1 until READY is asserted, which signals the last bus state of the current bus cycle. In the middle of this last bus state, the state machine enters state S2. At the end of this last bus state, the state machine enters state S3, and on the next rising edge of system clock 39 (i.e., in the middle of T1 of the next bus cycle), it returns to S0. The PLD equations for,the state machine outputs ST0 and. ST1 appear in FIG. 11B, lines 18-21, 25-34; FIG. 11C; FIG. 11D, lines 1-4.

Write Cycles

FIG. 12 presents a timing diagram of some of bus controller 20 outputs during a write cycle with 0 wait states. Mem/IO Write represents:

IOWR during an I/O write or a coprocessor write cycle;

MWR during a memory write or coprocessor data write cycle.

The bus controller state machine enters S1 when microprocessor 1 enters T1. By this time, 62.5 ns from the start of T1, the address lines A.sub.0 -A.sub.23 and the status lines BUSST0, BUSST1, M/IO, R/W, and UBE have become valid (it takes the address and status lines up to 40ns to settle. During T1, AEN/DEN is high. At the start of T2, in all write cycles except coprocessor write cycles, when the state machine enters state S1, AEN/DEN goes low disabling the inputs of address latches 3, 6, and 9 and enabling the inputs of data buffers 16 and 19, so that the outputs of the address latches 3, 6 and 9 maintain the address and status lines, and the data buffers 16 and 19 electrically connect lines D.sub.0 -D.sub.15 to lines BD0-BD15. AEN/DEN stays low through the first half of T1 of the next bus cycle (the address lines A.sub.0 -A.sub.23 and the status lines may change during that time)

In the coprocessor write cycles, AEN/DEN stays high through the whole bus cycle. In these cycles, data from data bus D.sub.0 -D.sub.15 is read by floating point subsystem 90 directly, through lines 41 (FIG. 7), not through data buffers 16 and 19. AEN/DEN remains high and so isolates the data bus D.sub.0 -D.sub.15 from lines BD0-BD15. In these cycles, address lines A.sub.0 -A.sub.23 are not used, and so the condition of address latches 3, 6, and 9 is unimportant.

Mem/IO Write goes low, and so enables an I/O or memory device to read, when the state machine enters state S1 of a write cycle. Mem/IO Write remains low through the end of the write cycle.

Read Cycles

FIG. 13 shows a timing diagram of bus controller 20 outputs during a read or interrupt acknowledge cycle. Mem/IO Read represents:

IORD during a cycle of the I/O read group;

MRD during a cycle of the memory read group;

INTAK during an interrupt acknowledge cycle.

Mem/IO Read, when asserted low, enables a memory or peripheral device to write data onto the data bus. Mem/IO Read is asserted low at the end of T1, when the state machine enters S1, and stays low until the start of the next bus cycle, allowing microprocessor 1 up to 10 ns to read data on the data bus.

AEN/DEN is asserted low when the state machine enters S2 and is thus delayed from the assertion of Mem/IO Read. The reason for the delay is as follows. After a write cycle, microprocessor 1 requires up to 50 ns to tristate the data bus D.sub.0 -D.sub.15. Therefore, in case the cycle preceding the read cycle was a write cycle, AEN/DEN is kept high through state S1, isolating D.sub.0 -D.sub.15 from BD0-BD15 and giving microprocessor 1 more than 50 ns to tristate its data bus. AEN/DEN is then asserted low and kept low, like Mem/IO Read, through T1 of the next bus cycle, maintaining the latched address and status lines on the outputs of address latches 3, 6, and 9 while V33 reads the data on the data bus. FIGS. 11D and 11E show bus controller 20 PLD equations for IORD, IOWR, INTAK, MRD, MWR, and ADR.sub.-- DAT, the inverse of AEN/DEN.

Timing diagrams of read and write cycles with one or more wait states can .be easily constructed from the PLD equations in FIGS. 11D-11E and the timing diagrams in .mu.PD70136 (V33) 16-bit Microprocessors: High-Speed, CMOS, supra.

Clock and READY Generation

The present invention uses Ready/Clock generator 25, FIG. 8, to generate 32 MHz SYSCLK, 16 MHz CLK and READY for microprocessor 1 and bus controller 20. This Ready/Clock generator 25 is a PLD, a 7.5ns programmable array logic device 16R6 available from AMD corporation and well known in the art. FIGS. 15A-15D show the PLD equations for Ready/Clock generator 25 in "ABEL" assembler.

Clock Generation

Ready/Clock generator 25 accepts as input a 32 MHz oscillator signal OSCI. Ready/Clock generator 25 "waveshapes" this signal and produces this waveshaped signal asynchronously as a 32 MHz system clock SYSCLK on its pin 19. See FIG. 15A, line 19; FIG. 15B, lines 5-7.

Ready/Clock generator 25 uses SYSCLK as an input clock (pin 19 of Ready/Clock generator 25 is connected to pin 1, the CLOCK input) to synchronize Ready/Clock generator 25 itself.

Ready/Clock generator 25 also generates, on its pin 18, the 16 MHz processor clock CLK which is SYSCLK divided by 2. The PLD equations for processor clock CLK (V33CLK in FIGS. 15A-15D appear in FIG. 15A, line 20; FIG. 15B, lines 8-10.

Ready/Clock generator 25 has a maximum delay of 7.5 ns and a minimum delay of 3.5 ns, so the skew between processor clock CLK and system clock SYSCLK is at most 4 ns. This skew is small enough to be acceptable for many V33 applications.

READY Generation

Ready/Clock generator 25 also acts as a wait state controller for microprocessor 1. To generate READY, Ready/Clock generator 25 uses the following inputs:

BCYST--from microprocessor 1. Signals the start of the bus cycle as described above.

WC0, WC1, WC2--a 3-bit number of wait states to be inserted into the current bus cycle. Generated by external circuitry 30.

XRDY1, XRDY2--signal that assertion of READY must be delayed no matter what WC0, WC1, WC2 are. Generated by other circuitry (not shown) connected to microprocessor 1.

Ready/Clock generator 25 implements a counter counting down from the number of wait states as defined by WC0, WC1 and WC2 to 0 on every bus state after T1; Ready/Clock generator 25 asserts READY low during the bus state in which the counter reaches 0. The PLD equations for the counter and the READY signal appear in FIG. 15B, line 11 through FIG. 15C, line 20 .

The rest of the outputs of Ready/Clock generator 25 are as follows.

WS0, WS1, WS2--WS0, WS1, WS2 form a 3-bit number which is the current value of the counter implemented by Ready/Clock generator 25 and described above.

LOAD is asserted low during the first SYSCLK period of T2. It is used to initialize WS0, WS1, WS2 to the value of WC0, WC1, WC2 before the counter begins downcount. See FIG. 15(ii), lines 16 et seq.

WRDY is asserted low one SYSCLK cycle before READY is asserted low. See FIG. 15B, lines 12-15; FIG. 15C, lines 1-19.

In the embodiment of FIGS. 8, 9, 10, WC2 is always kept at 0 because external circuitry 30 of this embodiment requires at most 3 wait states.

I/O, Memory and Floating Point Processor Interface

I/O Interface

The I/O subsystem 50, FIGS. 7, 16, comprises an I/O control circuit 51, a DMA controller 53, on-board I/O devices 52, and an off-board I/O subsystem 54 which in turn may contain other I/O devices (not shown). I/O control circuit 51 accepts control signals 40 from bus controller 20 (FIG. 6), DMA acknowledge lines DMAAK0 and DMAAK1 from DMA controller 53, and other input as described below, and produces control signals for on-board I/O devices 52.

FIG. 9 shows a schematic of part of I/O subsystem 50, including I/O control circuit 51 and on-board I/O devices 52. On-board I/O devices 52 include a serial controller 18 (NEC chip .mu.PD72001) and other peripheral devices. The interface between microprocessor 1 and the peripheral devices will be explained on the example of the serial controller 18 which is described, for example, in NEC Microcomputer Products-Microprocessors, Peripherals, & DSP Products, Vol. 2, 1987 incorporated herein by reference.

I/O control circuit 51 in this example consists of an I/O decode chip 8 and a PLD 13. I/O decode chip 8 is implemented by a programmable array logic device 20L8, and PLD 13 is implemented by a programmable array logic device 16L8, both available from AMD corporation and well known in the art.

I/O decode chip 8 accepts the following inputs: IORD, IOWR, ST1--three of the control signals 40 from bus controller 20.

BA2-BA9--latched address lines from address latch 6. These lines identify the I/O device for the current I/O operation.

LM/IO, LBS1--latched versions of M/IO and BUSST1,

respectively. Latched by address latch 3 (FIG. 8).

DMAAK0, DMAAK1--DMA acknowledge lines from DMA controller 53, FIG. 16.

I/O decode chip 8 is programmed to generate chip select signals to the on-board I/O devices 52. (A chip select signal of a device enables that device to perform an I/O operation.) In addition, I/O decode chip 8 generates a signal IOWAIT. IOWAIT is asserted during cycles accessing on-board I/O devices 52 and is deasserted during all other bus cycles. IOWAIT is used in connection with READY generation by memory control circuit 71 as described below.

Note that NEC chip .mu.PD7001 (serial controller 18) does not have a chip select line. Instead, it has RD and WR lines for read and write signals that enable serial controller 18 to read and write, respectively. These lines are connected to I/O decode chip 8 outputs RD72 and WR72, respectively. When latched address lines BA2-BA9 select serial controller 18, I/O decode chip 8 determines from IORD, IOWR whether reading or writing is to be performed and generates the read and write signals on RD72, WR72 as needed.

Some embodiments may contain an I/O device that requires chip select signal timing which cannot be provided by IORD and IOWR. To accommodate such a device, I/O decode chip 8 can be programmed to generate an appropriate chip select signal directly from control signals ST0 and/or ST1 of bus controller 20. In the embodiment of FIG. 9, I/O decode chip 8 uses ST1 to generate such a chip select signal for chip 14, a programmable timer 8254 well known in the art.

The I/O subsystem 50 in FIG. 9 uses PLD 13 to generate other control signals for on-board I/O devices 52. In particular, PLD 13 accepts as inputs DMA acknowledge lines DMAAK0 and DMAAK1 from DMA controller 53 and generates output signals PRI, PA1, and PA0 used as control input signals PRI, B/A, and C/D, respectively, for serial controller 18, so that serial controller 18 can be used with DMA. (DMA, Direct Memory Access, is a mode of operation in which an I/O device such as serial controller 18 writes to or reads from memory directly as opposed to writing to or reading from microprocessor 1 and then having microprocessor 1 write to or read from memory.)

Output pin 13 of PLD 13 is connected to input line BS8/BS16 of microprocessor 1, FIG. 8. Input line BS8/BS16 informs microprocessor 1 whether, in the current bus cycle, the data bus is 16-bit wide, i.e. it consists of all the 16 lines D.sub.0 -D.sub.15, or 8-bit wide, i.e. consists of only 8 lines D.sub.0 -D.sub.7. In the latter case, microprocessor 1 will read data from or write data to D.sub.0 -D.sub.7 only. When the line BS8/BS16 is high, the data bus is 16-bit wide. When the line BS8/BS16 is low, the data bus is 8-bit wide. See .mu.PD70136 (V33) 16-bit Microprocessors: High-Speed, CMOS, supra.

PLD 13 is programmed to generate a signal on its pin 13 from its input signals on pins 1, 2 and 3. Pin 1 is connected to an output (not shown) of the I/O decode chip 8. During bus cycles accessing on-board I/O devices 52, I/O decode chip 8 generates on pin 1 an appropriate signal for the microprocessor 1 line BS8/BS16 , i.e. it sets pin 1 high if the data bus must be 16-bit wide, and low if it must be 8-bit wide. During all other bus cycles, I/O decode chip 8 keeps pin 1 low. Pin 2 is connected to an output (not shown) of memory subsystem 70. During bus cycles accessing memory subsystem 70, memory subsystem 70 generates on pin 2 an appropriate signal for line BS8/BS16 -high for a 16-bit wide data bus, low for an 8-bit wide data bus. During all other bus cycles, memory subsystem 70 keeps pin 1 low. Pin 3 is kept low (by being connected to a pull-up resistor (not shown)) all the time in this embodiment. It could be used in other embodiments by other devices to generate a signal for line BS8/BS16.

PLD 13 is programmed to produce on its output pin 13 the logical OR of the inputs on its pins 1, 2 and 3. As a result, if at least one of pins 1, 2 and 3 is high, line BS8/BS16 of microprocessor 1 will be high, and microprocessor 1 will treat its data bus as being 16-bit wide. If all the pins 1, 2 and 3 are low, line BS8/BS16 will be low, and microprocessor 1 will treat its data bus as being 8-bit wide.

Methods of programming I/O decode chip 8 and PLD 13 to provide the functionality described above are well known in the art.

The I/O subsystem 50 of FIG. 9 uses buffered address lines BA0-BA19 and buffered status lines LM/IO and LBS1 rather than their unbuffered versions. As a result, the I/O subsystem 50 itself does not have to latch those lines. Using the buffered signals is possible because assertion of IORD and IOWR is delayed by bus controller 20 until transition to state S1, by which time the address and status lines have already been latched by address latches 3, 6, and 9. This delay in asserting IORD and IOWR is acceptable in most applications, since the I/O interface will usually require at least one wait state. Using chip 74AC373 (approx. 10 ns delay, see Fairchild FACT Logic Data Book, 1985) for address latches 3, 6, and 9 leaves more than 40 ns of address decode time available.

Memory Interface

The memory subsystem 70, FIGS. 7, 17, comprises a memory control circuit 71 and memory devices 72. Memory control circuit 71 accepts control signals 40 from bus controller 20 (FIG. 6) and some other input as described below, and produces control signals for memory devices 72.

FIG. 10 shows a schematic of a preferred embodiment of memory subsystem 70. Memory control circuit 71 is implemented by a PLD. Memory devices 72 include RAM devices 4, 7, 10 and 12 and an EPROM device 5. Each of RAM devices 4, 7, 10 and 12 is implemented by a RAM chip 4362, and EPROM device 5 is implemented by an EPROM chip 27512, both well known in the art.

Inputs of memory control circuit 71 include:

A.sub.0, A.sub.15 -A.sub.23 --unbuffered address lines from microprocessor 1;

M/IO, UBE from microprocessor 1;

AEN/DEN--one of control signals 40 from bus controller 20;

WC0.sub.-- IN, WC1.sub.-- IN--number of wait states. Generated by off-board I/O subsystem 54 (FIG. 16) as described below;

IOWAIT--generated by I/O decode chip 8 (FIG. 9) as described below.

From these and some other inputs, memory control circuit 71 generates:

chip select signals for memory devices 72; and

WC0, WC1--number of wait states--input to

Ready/Clock generator 25.

The unbuffered address lines A.sub.0, A.sub.15 -A.sub.23 and status lines UBE from microprocessor 1 are placed directly into memory control circuit 71. Using the unbuffered lines allows the greatest possible address decode time (22.5 ns). If buffered address and status lines are used instead by memory control circuit 71, then the delay of address latches 3, 6 and 9 must be subtracted from the available address decode time.

RAM chips 4, 7, 10 and 12 and EPROM chip 5 are connected to data bus D.sub.0 -D.sub.15 through lines BD0-BD15 and data buffers 16 and 19. Each RAM chip is connected to 4 data lines only:

RAM chip 4--to lines D.sub.0 -D.sub.3 (through lines BD0-BD3);

RAM chip 7--to lines D.sub.4 -D.sub.7 (through lines BD4-BD7);

RAM chip 10--to lines D.sub.8 -D.sub.11 (through lines BD8-BD11);

RAM chip 12--to lines D.sub.12 -D.sub.15 (through lines BD12-BD15).

EPROM chip 5 is connected to 8 data lines D.sub.0 -D.sub.7 (through lines BD0-BD7).

Each of the RAM chips 4, 7, 10 and 12 accepts as input:

BA1-BA14, buffered address lines from microprocessor 1 (through address latches 3, 6 and 9). These buffered address lines select 4 bits in the RAM chip to connect to the 4 corresponding data lines (data lines BD0-BD3 for RAM chip 4, BD4-BD7 for RAM chip 7, BD8-BD11 for RAM chip 10, and BD12-BD15 for RAM chip 12).

CS (chip select pin 10 of each RAM chip; when low, enables the chip) is connected to an output pin of memory control circuit 71 as follows:

CS of RAM chips 4 and 7--to RAMCS.sub.-- L (pin 20) of memory control circuit 71;

CS of RAM chips 10 and 12--to RAMCS.sub.-- H (pin 21) of memory control circuit 71.

WE (write enable pin 12 of each RAM chip; when low enables the chip to read from the corresponding data lines) is connected to the MWR signal from bus controller 20.

EPROM chip 5 accepts the following input:

BA0-BA15--buffered address lines from microprocessor 1 (through address latches 3, 6 and 9). They select 8 bits in EPROM chip 5 to connect to the 8 data lines BD0-BD7.

CE (chip enable pin 20 of EPROM chip 5; when low, enables the chip) is connected to ROM.sub.-- CS (pin 17) of memory control circuit 71.

OE (output enable pin 22 of EPROM chip 5; when low, enables output onto BD0-BD7) is connected to the MRD signal from bus controller 20.

Memory subsystem 70 operates as follows. The address line A.sub.0 and the status line UBE are outputs of microprocessor 1 which determine whether microprocessor 1 will access, during the current bus cycle, the whole data bus D.sub.0 -D.sub.15, only its lower half D.sub.0 -D.sub.7, or only its upper half D.sub.8 -D.sub.15, according to the following table:

The high level of status line M/IO indicates to memory control circuit 71 that memory is being accessed. Address lines A.sub.0, A.sub.15 -A.sub.23 indicate to memory control circuit 71 whether RAM or EPROM is being accessed. A.sub.0 and UBE indicate whether the whole data bus D.sub.0 -D.sub.15, only D.sub.0 -D.sub.7 or only D.sub.8 -D.sub.15 are being accessed. If RAM is accessed, then

if the whole D.sub.0 -D.sub.15 is accessed, memory control circuit 71 asserts both RAMCS.sub.-- H and RAMCS.sub.-- L low thus selecting all the RAM chips 4, 7, 10 and 12;

if only D.sub.0 -D.sub.7 is accessed, memory control circuit 71 asserts RAMCS.sub.-- L low and keeps RAMCS.sub.-- H high, thus selecting only RAM chip 4 connected to BD0-BD3 and RAM chip 7 connected to BD4-BD7;

if only D.sub.8 -D.sub.15 is accessed, memory control circuit 71 asserts RAMCS.sub.-- H low and keeps RAMCS.sub.-- L high thus selecting only RAM chip 10 connected to BD8-BD11 and RAM chip 12 connected to BD12-BD15.

At the same time, if the bus cycle is a memory write cycle, bus controller 20 asserts MWR low thus driving pins WE of the RAM chips low and thereby enabling the RAM chips selected by their CS pins to read data from the corresponding data lines.

If EPROM is being accessed, then memory control circuit 71 asserts its ROM.sub.-- CS output low thus driving the CE pin of EPROM chip 5 low and so enabling EPROM chip 5. At the same time, if the bus cycle is a memory read cycle (note that EPROM is read only memory), then bus controller 20 asserts its line MRD thus driving pin OE of EPROM chip 5 low and thereby enabling EPROM chip 5 to write data onto the data lines BD0-BD7. Note that EPROM 5 is not connected to data lines D.sub.8 -D.sub.15 of microprocessor 1. When EPROM 5 is accessed, line BS8/BS16 of microprocessor 1 must be asserted low to inform microprocessor 1 that its data bus is 8-bit wide. This construction allows to use only one EPROM 27512 (as opposed to using two EPROMs, one for D.sub.0 -D.sub.7 and one for D.sub.8 -D.sub.15).

Since the inputs A.sub.15 -A.sub.23, M/IO, and UBE of memory control circuit 71 are unbuffered, its chip select outputs ROM.sub.-- CS, RAMCS.sub.-- H and RAMCS.sub.-- L must be latched to guarantee that they will hold their values until the end of the current memory operation. The chip selects are latched inside the memory control circuit 71 using feedback to provide an asynchronous transparent latch. The operation of the latch is such that when AEN/DEN is high the latch is open (transparent), and when AEN/DEN goes low the latch is closed and the chip selects hold their values.

Asynchronous latching can be performed by any PLD that has internal feedback lines from the outputs. In this case, users must be careful not to assign chip select lines to outputs which do not have internal feedback. The PLD equations for memory control circuit 71 can easily be obtained by a person reasonably skilled in the art. For example, the following equations can be used for the output ROM.sub.-- CS (using "ABEL" assembler format):

memaddr=[A19,A18,A17,A16,A15]

ROM=(memaddr==[H,H,H,H,H]& M/IO

!ROM.sub.-- CS=(ROM & AEN.sub.-- DEN) #(!ROM.sub.-- CS & !AEN.sub.-- DEN) #(ROM & !ROM.sub.-- CS)

Notes: !=not (inverse), #=logical OR, &=logical AND

The term (ROM & !ROM.sub.-- CS) is redundant and is included to help prevent glitching. Care must be taken that the assembler does not eliminate this term, i.e. lower levels of logic reduction may be required (check assembler documentation).

Memory control circuit 71 also generates, on its output lines WC0, WC1, the number of wait states to be inserted into the current bus cycle. WC0, WC1 are inputs to Ready/Clock generator 25 (FIG. 8). Memory control circuit generates WC0, WC1 for both I/O bus cycles (i.e. bus cycles of the I/O read and the I/O write groups) and memory bus cycles (i.e. bus cycles of the memory read and the memory write groups). Memory control circuit 71 determines from M/IO if the current cycle is memory or I/O and generates WC0, WC1 according to the following requirements of this embodiment.

Bus cycles accessing RAM chips 4, 7, 10 and 12 require zero wait states.

Bus cycles accessing EPROM chip 5 require one wait state.

Bus cycles accessing on-board I/O devices 52 require two wait states. Bus cycles accessing off-board I/O subsystem 54 may require any number of wait states between 0 and 3, and during these bus cycles, the off-board I/O subsystem 54 must provide the required number of wait states on inputs WC0.sub.-- IN, WC1.sub.-- IN of memory control circuit 71. Memory control circuit 71 sets, during these cycles, WC0=WC0.sub.-- IN, WC1=WC1.sub.-- IN. Memory control circuit 71 recognizes cycles accessing on-board I/O devices 52 from cycles accessing off-board I/O subsystem 54 by IOWAIT which is asserted by I/O decode chip 8 (FIG. 9) only during cycles accessing on-board I/O devices 52.

PLDs like that implementing memory control circuit 71 and methods of their programming to provide the functionality described above are well known in the art.

Floating Point Processor Interface

In the embodiment of FIG. 8, floating point subsystem 90 is implemented by an NEC floating point processor AFPP (Advanced Floating Point Processor) also known as .mu.PD72291. Processor AFPP is described in the AFPP User Manual available from NEC. Processor AFPP is a very high performance floating point processor that has been designed to be used with the V33 microprocessor (and the V53 microprocessor). It is connected directly to the V33 microprocessor 1 data bus D.sub.0 -D.sub.15. Coprocessor read and write cycles are two bus states each and coprocessor data read ,and write cycles are three bus states each. The connection of processor AFPP to microprocessor 1 is shown in FIG. 8.

FIG. 18 illustrates another embodiment of the floating point subsystem 90. Here the floating point subsystem 90 includes INTEL 80287 numeric processor extension 110, a latch 100, and a static decode PLD 101. Latch 100 is a chip 74AC573 well-known in the art. PLDs like static decode PLD 101 are also well-known in the art. INTEL 80287 numeric processor extension is described in 80287 80-BIT HMOS NUMERIC PROCESSOR EXTENSION (80287-3, 80287-6, 80287-8, 80287-10) available from INTEL corporation, 3065 Bowers Ave., Santa Clara, Calif. 95051. This publication is incorporated herein by reference. How to connect 80287 numeric processor extension to a V33 microprocessor is described in V33 System Design Application Note (August 1989) available from NEC and incorporated herein by reference.

In FIG. 18, Lines CPBUSY, CPERR and CPREQ of microprocessor 1 are connected the lines BUSY, ERROR and PEREQ of 80287 numeric processor extension 110 respectively. Lines CKM and PEACK of 80287 numeric processor extension 110 are connected to a voltage supply V.sub.cc (about 5V; see 80287 80-BIT HMOS NUMERIC PROCESSOR EXTENSION (80287-3, 80287-6, 80287-8, 80287-10), supra, for more details). Lines NPRD and NPWR of 80287 numeric processor extension 110 are connected to bus controller 20 outputs IORD and IOWR respectively. Lines CMD0 and CMD1 are connected, respectively, to latched address lines BA1, BA2 from address latches 3 and 6, respectively.

On reset, microprocessor 1 samples its CPBUSY and CPERR lines to determine if a coprocessor is attached and if the attached coprocessor is a processor AFPP or an 80287 numeric processor extension. Microprocessor 1 needs to differentiate a processor AFPP from an 80287 numeric processor extension because the processor AFPP "handshake" signals and software interface are entirely different from those of the 80287 numeric processor extension. The processor AFPP is NOT software compatible with the 80287 numeric processor extension. On reset, the CPBUSY line is low if a coprocessor is attached, in which case microprocessor 1 samples the CPERR line (all during the reset state) to determine whether the attached coprocessor is a processor AFPP or an 80287 numeric processor extension. Listed below are the possible values of CPBUSY and CPERR and their meanings.

Line NPS1, NPS2 of 80287 numeric processor extension 110 effectively serve as chip select inputs enabling 80287 numeric processor extension 110. Lines CMD0, CMD1 select internal registers of numeric processor extension 110. Numeric processor extension 110 is synchronized by its own clock (not shown) that does not have to be synchronous with the microprocessor 1 processor clock CLK.

Bus controller 20 asserts IORD or IOWR in coprocessor bus cycles (i.e. coprocessor read, coprocessor write, coprocessor data read, and coprocessor data write cycles) as needed. During coprocessor cycles, I/O decode chip 8 disables chip selects of on-board I/O devices 52 which eliminates the possibility of bus contention.

As shown in FIG. 18, each of microprocessor 1 status lines BUSST0, BUSST1, and M/IO is connected to a D input of latch 100. Output signal AEN/DEN of bus controller 20 is connected to the EN input of latch 100. AEN/DEN, when high, enables the three D inputs of latch 100, and when low, disables those inputs so that latch 100 latches the signals on those inputs and maintains them on its three Q outputs. These latched signals are inputs to static decode PLD 101 which is programmed to generate, from these inputs, signals WC0 and WC1 for Ready/Clock generator 25 and NPS1, NPS2 for numeric processor extension 110.

Chips like static decode PLD 101 and methods of their programming to provide the functionality described above are well known in the art.

FIG. 19 illustrates another embodiment of the floating point subsystem 90. This embodiment is similar to that of FIG. 18, but it does not have latch 100 and it does not latch status lines of microprocessor 1. Instead, it uses the status lines latched versions LBS1, LM/IO latched by address latch 3. LBS1 (latched version of BUSST1), LM/IO (latched version of M/IO) and bus controller 20 output signal AEN/DEN are inputs to a static decode PLD 103. Static decode PLD 103 is programmed to produce, from these inputs, outputs WC0, WC1 for Ready/Clock generator 25 and NPS1, NPS2 for numeric processor extension 110.

BUSST0 is not an input to static decode PLD 103. As a result, numeric processor extension 110 gets selected during HALT acknowledge cycles. This is because the status lines M/IO, R/W and BUSST1 have the same values during HALT acknowledge cycles and coprocessor write cycles (the values are 0, 0 and 1 respectively; see Table 1 above), so static decode PLD 103 does not differentiate between HALT acknowledge cycles and coprocessor write cycles and generates signals NPS1, NPS2 to select numeric processor extension 110 during both types of cycles (rather than during coprocessor write cycles only). But this is not objectionable in most applications.

Chips like static decode PLD 103 and methods of their programming to provide the functionality described above are well known in the art.

FIG. 20 illustrates one more embodiment of the floating point subsystem 90. This embodiment is also similar to that of FIG. 18, but here decode/latching PLD 104 performs both the latching function of latch 100 and the function of static decode PLD 101 of FIG. 18.

Chips like decode/latching PLD 104 and methods of their programming to provide the functionality described above are well known in the art.

The present invention is not limited to the embodiments described above. Other embodiments of the external circuitry 30 may be created to operate with microprocessor 1, bus controller 20, and Ready/Clock generator 25. Furthermore, bus controller 20 can be modified to generate different control signals as required by a particular implementation of the external circuitry 30 without departing from the spirit of this invention. Also, bus controller 20 outputs ST0, ST1 may be used by external circuitry 30 to create other control signals as needed by external circuitry 30. Ready/Clock generator 25 can also be modified without departing from the spirit of this invention. For example, other embodiments of Ready/Clock generator 25 may use only one of signals XRDY1, XRDY2, no such signals, or more than two such signals to override the signals WC2, WC1, WC0. Furthermore, more than three input lines such as lines WC2, WC1, and WC0 may be used to allow more than seven wait states to be inserted into a bus cycle of microprocessor 1. The counter implemented by Ready/Clock generator 25 may count not from the number of wait states down to zero but, say, from 1 up to the number of wait states or according to some other scheme. Also, Ready/Clock generator 25 and bus controller 20 may be implemented by, say, one PLD chip, three PLD chips, or any other number of PLD chips. For example, the clock generator function of Ready/Clock generator 25 may be implemented by a separate PLD chip. Many other variations of this invention are and will be obvious to persons of ordinary skill in the art.