[go: up one dir, main page]

Jump to content

Q-Bus

From Wikipedia, the free encyclopedia
Q-Bus
Q-Bus
DEC MicroVAX II CPU card (quad height)
Created byDigital Equipment Corporation
SupersedesUnibus
Superseded byVAXBI bus (1986)
Width in bits8 or 16-bit data, 16-bit address extended to 22-bit
No. of devices127 in theory, ~20 in practice
StyleParallel
Hotplugging interfaceNo
External interfaceNo

The Q-bus,[1] also known as the LSI-11 Bus, is one of several bus technologies used with PDP and MicroVAX computer systems previously manufactured by the Digital Equipment Corporation of Maynard, Massachusetts.

The Q-bus is a less expensive version of Unibus using multiplexing so that address and data signals share the same wires.[2] This allows both a physically smaller and less-expensive implementation of essentially the same functionality.

Over time, the physical address range of the Q-bus was expanded from 16 to 18 and then 22 bits. Block transfer modes were also added to the Q-bus.[2]

Main features of the Q-bus

[edit]
LSI-11/23 Q-Bus expansion cards and slots
DEC BA213 cabinet; 12 Q-Bus-22 slots

The Q-bus is arranged as a series of modules installed in one or more backplanes.

Like the Unibus before it, the Q-bus uses:[3][4]

Memory-mapped I/O means that data cycles between any two devices, whether CPU, memory, or I/O devices, use the same protocols. On the Unibus, a range of physical addresses are dedicated for I/O devices. The Q-bus simplifies this design by providing a specific signal (originally called BBS7, Bus Bank Select 7 but later generalized to be called BBSIO, Bus Bank Select I/O) that selects the range of addresses used by the I/O devices.

Byte addressing means that the physical address passed on the Unibus is interpreted as the address of a byte-sized quantity of data. Because the bus actually contains a data path that is two bytes wide, address bit [0] is subject to special interpretation and data on the bus has to travel in the correct byte lanes.

A strict Master-Slave relationship means that at any point in time, only one device can be the Master of the Q-bus. This master device can initiate data transactions which can then be responded to by a maximum of one selected slave device. (This had no effect on whether a given bus cycle is reading or writing data; the bus master can command either type of transaction.) At the end of the bus cycle, a bus arbitration protocol then selects the next device to be given mastery of the bus.

Asynchronous signaling means that the bus has no fixed cycle time; the duration of any particular data transfer cycle on the bus is determined solely by the master and slave devices participating in the current data cycle. These devices use handshake signals to control the timing of the data cycle. Timeout logic within the master device limits the maximum allowed length of any given bus cycle.

Depending on its generation, the Q-bus contains 16, 18, or 22 BDAL (Bus Data/Address Line) lines. 16, 18, or 22 BDAL lines are used for the physical address portion of each bus cycle. Eight or 16 DBAL lines are then re-used for the data portion(s) of each bus cycle. Newer generations of the bus allow block mode transfer where a single bus address can be followed by more than one data cycle (with the transfers taking place at consecutive bus addresses). Because the address portion of each bus cycle can not transfer data, the use of block mode means fewer address cycles and more time for data cycles, allowing increased bus data transfer bandwidth.

Bus mastery is awarded based on an I/O card's topological proximity to the bus arbitrator (at the logical front of the bus); closer cards are granted priority over further cards.

Interrupts can be delivered to the Interrupt Fielding Processor at any of four interrupt priority levels. Within a given level, the cards closer to the IFP (at the front of the bus) take priority over cards further back on the bus. Interrupts are vectored: a card requesting an interrupt has its interrupt vector read by the IFP. In this way, the interrupts from all I/O cards in the system can be distinguished with no ambiguity.

Physical characteristics

[edit]

Q-bus modules are configured as printed-circuit boards with gold-plated card-edge connectors which mate with corresponding slots on a backplane. The edge connectors on the modules are split into individual "fingers," similarly to Unibus modules, but are limited to four connectors, compared to the six of Unibus. Modules are available in either double-height (two connectors) or quad-height (four connectors) sizes. This nomenclature is somewhat non-intuitive, as the difference between the two is actually the width of the PCB. Quad-height modules tend to be used for CPUs, memory, video processors, and other high-bandwidth components, whereas double-height modules tend to be used for interface cards, connector breakout boards, real-time clocks, ROM/microcode, and other relatively low-bandwidth components. Some exceptions are the double-height LSI-11/2, KDF11-A, and KDJ11-A CPUs, and many early small-capacity memory modules.

Logic minimization

[edit]

As with the Unibus, the signaling was carefully optimized so that the minimum amount of logic is required across the entire bus system. Asynchronous signaling is used but de-skewing of addresses and data is the responsibility of the current bus master, minimizing the complexity of the bus slave devices. The responsibility for timing-out failed bus cycles also is placed in the master devices. Similarly, the complexities of handling interrupt transactions are concentrated into the single Interrupt-Fielding Processor (the PDP-11 or VAX-11 computer) in the system.

Compatibility

[edit]

The design of the Q-bus was very closely related to the design of the Unibus both in spirit and in detailed implementation. Adapters were available from Digital and from third parties that allow Q-bus devices to be connected to Unibus-based computers and vice versa.[5] A number of I/O devices were available in either Unibus or Q-bus flavors; some of these devices have minor differences while many others were essentially identical.

Soviet clones

[edit]

In Soviet systems (see 1801 series CPU), the Q-Bus architecture is called МПИ (Магистральный Параллельный Интерфейс, or parallel bus interface). Its main difference is that it supports up to four processors on the same bus. Otherwise it is completely binary and electrically compatible with the standard Q-Bus, except for the physical layout of connectors.

Cycle Types

[edit]

The Q-Bus supports 6 basic transaction types:[2]

DATI Data in - master read - note no DATIB (not required)
DATO Data out - master write
DATOB Data out (byte)
DATIO Data in/out
DATIOB Data in/out (byte)
IAK Interrupt Acknowledge

Device Types

[edit]

A wide range of module types are available for the Q-Bus. Generally, they can be categorized as:

  • CPU modules
  • Memory modules
  • Interface modules
  • System modules (grant continuity cards, connector breakout boards, etc)

Interfaces

[edit]
1 MBit Bubble memory dual-width Q-Bus expansion card
8K × 19 bit core memory quad-width Q-Bus expansion card
DEC MicroVAX II memory card (quad widhth)

A wide range of interface cards are available for the Q-Bus. Various Q-bus modules can be dual-width (two sets of fingers, half the total width of the mounting), or quad-width (four sets of fingers, the full width of the mounting), indicating that the module occupies one-half of or all of the Q-bus mounting slot, respectively.


[edit]
  • "HP OpenVMS :: Q-Bus Hardware". HoffmanLabs. Archived from the original on 11 March 2021.
  • "The Lab - Q-Bus Beispielplatine, Selbstgebaute Q-BUS Platinen". RunningServer.com (in German). Archived from the original on 14 February 2017.
  • DEC STD 160: LSI-11 Bus Specification

References

[edit]
  1. ^ Schmidt, Atlant G. (1990). "Unibus, Q-Bus and VAXBI Bus". In Di Giacomo Joseph (ed.). Digital bus handbook. McGraw Hill. ISBN 0070169233.
  2. ^ a b c digital Microsystems Handbook 1985. 1985.
  3. ^ digital Microcomputer Products Handbook (PDF). 1985.
  4. ^ PDP-11 Bus Handbook (PDF). 1979.
  5. ^ PDP-11/84 System Technical and Reference Manual (PDF). December 1987. pp. 1‐2, 2‐52–2‐69.