///HardwareNotes.tioga
Last Edited by: Barth, June 10, 1985 11:28:40 am PDT
DRAGON HARDWARE NOTES
DRAGON HARDWARE NOTES
DRAGON HARDWARE NOTES
DRAGON PROJECT — FOR INTERNAL XEROX USE ONLY
DRAGON PROJECT — FOR INTERNAL XEROX USE ONLY
DRAGON PROJECT — FOR INTERNAL XEROX USE ONLY
Dragon Hardware Notes
Description and Specifications
Release as[Indigo]<Dragon>Documentation>Hardware>HardwareNotes.tioga

© Copyright 1985 Xerox Corporation. All rights reserved.
Abstract: This memo describes some notes about the Dragon hardware.
XEROX  Xerox Corporation
   Palo Alto Research Center
   3333 Coyote Hill Road
   Palo Alto, California 94304



For Internal Xerox Use Only
Contents
1. Introduction
2. Action Items
3. Agenda
4. Topics
1. Introduction
This document describes some aspects of the Dragon hardware design. It excludes design aids (but not design aid hardware, e.g. Sage) and software above the level of diagnostics.
2. Action Items
These are sorted into an order in which they might be completed.
McCreight, Sindhu and Barth are working on the M bus compatibility issue.
Curry to write IC data sheet form.
Gunning to find out about pin grid arrays of greater than 144 pins.
5/1 - Bill promises first proposal by 5/22
Gunning and Hoel to describe pc board design rules.
5/1 - Jeff promises first cut PC document by 5/15
6/10 - Any comments for first draft PCB rules? Does Jeff consider them done?
Sindhu, Barth and Serlet are working on the architecture for the two level cache.
Gunther, McCreight and Barth are trying to find a fabrication second source.
Overton is getting the Sage PC board layed out and fabricated.
Gasbarro is working on an HP-IB driver for Sage.
Gasbarro and Barth will look into PC design systems, e.g. Expert or ChipnDale.
Hoel and Crow will have some specification for the display processor within a few weeks.
Gasbarro will redesign the calibrated delay line into 2 micron CMOS.
Barth will test more CrossRAM chips when they appear.
Wirth is working on a memory board controller chip.
Gunther is working on diagnostics for the EU.
Monier will have the first EU into fab by the end of June.
Sindhu claims he will have the map cache ready by June as well.
Some combination of Gasbarro, Barth and Gunther will have Sage running by the time Monier or Sindhu need it.
Pier is looking into the design of the IOP. He will investigate the Ethernet and disk controllers in the Andirondack.
Gunning has volunteered to design a prototype chip that can be plugged into a prototype chassis in order to test the bus drivers.
Fiala will write an instruction set diagnostic.
McCreight and Curry are working on the IFU. They may have something ready for fab by the end of the year.
Barth will work on the first level cache which connects a P bus to either an internal M bus or the main system bus.
Serlet will work on the second level cache which connects an internal M bus to the main system M bus.
3. Agenda
Probe cards, pad rings, bonding, packages.
Testing and diagnostic plan.
Chip specifications
Chip design verification test programs
Chip manufacture test programs
Chip design review requirements
System hardware diagnostics
Instruction set diagnostics
Integration plan
The EU is the forcing function to wring this out.
Who designed the ESS backplane?
Who is designing the ED IOP? MEM?
Have we given up on the ECL clock distribution scheme?
Could we farm out the IOP and memory board designs to an external design house in case ED does not come through?
We need a method that tracks the pinouts of the custom IC's, the layout of the processor and system controller boards, the commitment of backplane pins, what else? Who will do this? The processor board needs to be layed out soon to avoid surprises for Gunning and the people laying out processor components. The system controller can be deferred. We need pinouts of the custom chips to do trial board layouts. Who will volunteer for each of the chips?
Is a 1" board spacing enough for the display processor?
Power Rules of Thumb (Hoel)
What is our current assumption about clock distribution?
Should we worry about EMI? If so, how?
Shoud we build a dummy chip that can be configured to plug into any of our custom sockets and speak electrically to all of the wires in the system? If so when should we do this? Who should do it? Gunning has signed up for an M bus dummy rig. Do we want to go further than this?
4. Topics
Global Requirements
Noise
How much noise can an office Dragon generate? A comparison with Daybreak may be useful. Perhaps we should build a mockup of a Dragon system which dissipates the proper amount of heat and has a fake chip that can take the place of the custom chips (IFU, EU, Data Cache, Address Cache, Map Cache, Arbiter, Memory Controller) so that we can wring out the mechanical, electrical and cooling package bugs prior to silicon availability.
Power
We are constrained by the amount of power the room, the box the processor is wrapped up in, and the package the chips are bonded in, can each handle. We may be constrained by either air conditioning load or building wiring. We still need to discuss how power is measured, maximum power, typical power, "average" power (averaged over what?), surge power? A proposed limit is 600 watts. Could we have an office machine without forced air? Would heat sinks allow such a machine?
3/19/85 - Lee Anderson claims 400 watts is no problem, we could push him to 500 or 600 watts. Wiring is not a problem. Most system power is beyond our control. The power estimates we have so far indicate the small machine is feasible and the large one will have to be remote.
Cost
Basically we won't worry too much about this. Nonrecurring engineering costs dominate production costs for this machine. Anything that doesn't excede the space and power requirements is not likely to excede cost requirements.
Board Fabrication
Stichweld vs. Wirewrap vs. Direct to PC
We will implement the processor, memory, and display processor cards immediately with printed circuit cards, skipping the prototype step. These boards will be 4 layer, two outer signal layers so that we can reduce the capacitance and blue wire them, and two inner power layers. The bus coupler board and others will be implemented using a prototyping technology first. We have stichweld and a DA system for it already in house. Stichweld has slower turnaround for changes than wirewrap. Documentation is likely to be better with stichweld. Prototyping technology will be needed for the M bus and VME coupler boards plus whatever boards for the VME system are custom built.
Design Rules
We intend to use ED's 10.9" x 16" board format with 423 pin AMP HDI connector. We need rules for through hole pads, width and spacing. A specification of the baord layout with ejector and connector requirements is necessary. The size of the ZIF socket for the 144 pga's must be given. Dibbel is the vendor of choice. Gunning has a Xerox standard for PC board design.
We will assume that a single clock is distributed to the custom components and they will generate their own internal clocks from that using a calibrated delay line.
6/10/85 - Hoel has some design rules in: /Ivy/Hoel/Dragon/Packaging/PCB/ShortDesignRules.tioga
Design
A complete printed circuit board design methodology must be put in place. We could have this contracted out. We could use Expert systems from Versatec. We could create a ChipNDale technology. How are drill tapes, photoplots, parts lists, etc. created? We could put all the layers of all the boards on a photomask and then optically blow it up, Danny Cohen at MOSIS could tell us about that. We could use platemaker. Right now, we will wait for Stever Jackson to look at the Expert 1000 system and revisit this issue later.
Fabrication
The PC vendor must test the boards. Should we have the garage do it also? How does ED test their boards? (New tester for 100K?) Dibbel is a possible supplier. So is Circuit Works.
Board Types
Processor
The processor board will be designed to hold 20 PGAs, D bus logic, and perhaps clock distribution drivers.
4 Cache/Proc.
1 IFU/Proc.
1 EU/Proc.
2 Flt. pt./Proc.
---------------------
8 Chips/Proc * 2 Proc + 4 spare for extra cache chips = 20
Memory
The memory board will be designed assuming 1 Mbit RAMs, upgradable to 4 Mbit RAMs.
a) Because of the greater density, the Dragon system need not be designed for more than 2 memory boards.
b) The memory board will have iether 144 RAM DIPs or 288 RAM SIPs to be decided by the memory board designer.
c) Capacity of each board would be:
1. 16 MBytes with 1M bit DIPs
2. 32 MBytes with 1M bit SIPs
3. 64 MBytes with 4M bit DIPs
4. 128 MBytes with 4M bit SIPs
6/10/85 - The current plan has ED designing the memory board. It will support both narrow and wide formats. It will not interpret MHold.
Display Controller
This board probably contains 5 PGA's, a bunch of RAM, DACs and a little bit of ECL for seasoning.
Some people claim we should build a simple one for the masses instead of a fancy one for the few. However if we don't build the fancy one for the few the masses may never know what they are missing.
We need a remote video capability for fancy displays some day. For now the existing displays are good enough and we will defer work on this until some engineering resources are available.
We should consider using an ECL gate array for the video chain to reduce the board space and power requirements of this board. McCreight has been through the ED gate array class and is willing to act as consultant on this.
System Controller
a) Map Cache
b) M to processor bus coupler
M I/O space to bus memory space
bus memory space to M memory space
c) System clock generation and distribution
d) Arbiter
d) 68012 processor, RAM, ROM
d) labelled disk controller
e) ethernet controller
Should the IOP run Unix?
6/10/85 - ED is designing this board. Hopefully they will produce a requirements document so that we can determine if our needs will be met.
Package
Types
Two Dragon packages with compatible board types will be constructed. One is intended for office use and the other for installation in a machine room. Both include boards in the ED format as well as VME, at least one disk drive, and power supplies. Due to its excessive power consumption and noise, the machine room system must be installed in a machine room. Remote installation makes necessary the design for remote video transmission. The machine room version will be used for prototype debug because it is mechanically more flexible and it is electrically more difficult. Seperate fans and power supplies will be specified for each package.
We could design boards which fit into a Daybreak chassis and use the Daybreak IOP and memory boards. Then we only need design one processor board to have a machine which runs DragOps and can be mass manufactured at low cost. There may be board spacing problems with this. Peripherals may also be a problem.
Box size
The machine room package is only constrained by 19" rack format. How large is the office package? It must fit underneath standard height tables.
Board Counts
Office:
M bus: 2 Processor, 2 Display, 1 Memory, 1 System Controller, 2 Spare
8 Total
VME bus: 1 Ethernet, 1 Disk Controller, 2 Spare
4 Total
Machine Room:
M bus: 4 Processor, 4 Display, 2 Memory, 1 System Controller, 3 Spare
14 Total
VME bus: 1 Ethernet, 1 Disk Controller, ? Interim Display,
? Memory, ? Interim Processor, ? RS-232, ?Spare
? Total
Board Spacing
a. Board Thickness plus Pin-Side Height:
i. Stichweld: the wire mat, with mylar cover, might be 0.1" or 0.2". The board thickness might be 0.0625". Call the total 0.2"
ii. Etched PC: less.
b. Clearance between boards: say 0.2" (Card guides, slop, etc.)
c. Component Height:
i. PGA plus Socket: 0.5"
ii. PGA plus Socket plus Heatsink: 0.8"
d. TOTAL: looks like 1.2"
For reasons of airflow, perhaps it would be good to make the VME board spacing 1.2" as well. (The standard VME spacing is 0.8".)
Backplane
There are a number of options for the mechanical arrangement of the backplane:
a. Option A: One big board. Must be at least 19" x 26". (In fact, larger, by the time mounting holes, etc. are considered.) (M bus board height is 16.0"; VME board height is 9.16"; to facilitate air flow there might need to be a 3" seperation.)
b. Option B: Two boards, one for the M bus and one for VME, plus interconnecting cable. This option provides maximum flexibility, e.g., for others to use M bus with Multibus instead of VME.
c. Option C: One big board, made with built in flex connector betwen M bus and VME, folded so that the pin sides of the two backplanes face each other.
The VME specification limits bus length to 19 inches. The cable between backplanes either is or isn't counted as part of that length, depending upon exactly what role the cable is playing, e.g., whether signals are buffered or not.
We need to start a pin count for the backplane connector. We should include the various voltages to be supplied. At first cut we need pins for standard logic supply, nominally 5 volts, ground, ECL voltage?, bus terminating voltages for clamp diodes, bus high and low level voltages. We need to count I/O, M and D bus pins. Clock distribution?
Slot independence and slot ID's.
Two tier cache scheme cuts M bus capacitance by 30% and bus length by 16".
Let ED do it
3/27/85 - Requirements to ED:
Slot i.d.'s
Point to point wiring on backplane
3 slots, 1 for processor, 1 for color display controller, 1 for B&W controller
what is board spacing?
VME?
how many channels in the arbiter?
D bus driver
map cache
4/3/85 - We will take whatever IOP and memory board that ED builds for both the office and machine room versions of Dragon. In addition we will take the skins, frame, power supply, disk and backplane for the office machine. We will build a processor board and display board. We will require some modifications to the IOP. Supposedly a prototype of the C workstation with IOP, memory, and M bus is to be done by June, 1986.
The IOP has disk, ethernet, vanilla B&W display controller, keyboard and mouse interface. There may be a floppy interface and RS232 ports. We should push for one or two parallel ports as well. The board spacing is 1". There are 6 boards in the system, 1 for VME and 5 M bus. IOP, VME, and MEM take 3 leaving 3 for us.
VME M bus board has cutout to plug VME board into.
Chip Design
Sage
6/10/85 - We are having a PC board constructed. We plan to plug it into a Dandelion with a Multibus card cage on it.
Methodology
6/10/85 - The methodology favored by Curry consists of functional simulation followed by layout followed by final simulation from extracted layout. We are not currently setup to support such a methodology.
Miscellaneous
Arbiter Placement
Where does the arbiter go? On the backplane? On the coupler board? Defer until the local arbitration decision is known.
PGA's and Sockets
LIF sockets take less space. The extractor tool requires about 1/4" space on two sides. The additional overhead of ZIF sockets is not significant enough to consider eliminating them from the processor and memory boards. A seperate decision will be made for the display processor. The display processor could offer significant additional functionality if a few more pins were available. Power limits in 144 pin PGAs are 1.8, 2.6, 3 in convection, 200 ft./min forced air, and forced air + heat sinks respectively.
The PGA we may have made for us may have a 12mm cavity allowing for an 11mm die. It is optimal from a packaging point of view to have the die fill up the cavity. This is lousy from a die/wafer point of view.
6/10/85 - Bill Gunning has found a vendor that produces pc board like packages. He has a preliminary sketch of the layers for the package. Sealing and heat dissipation issues still have to be addressed. Currently thinking about a 200 pin array with two tier bonding.
Processing second source
We need an alternate to ICL. We have looked at GE. The rules they have given us so far are really for a 3 micron process. They have a 2 micron extension of those as well as a 1.25 micron process. ED has been looking at AT&T and National Semiconductor for second sources as well.
A. Appendix Initial Guesstimates
The following appendix contains some additional notes from an early packaging meeting that have not been adsorbed into the main body of this document.
We considered the cost of two configuration bounds: A minimally configured system and a maximally configured system. The following table summarizes the power and cost for each configuration.


Minimally Config Sys Maximally Config Sys
!
Item ! Definition !Power! Cost ! Definition! Power! Cost
! ! ! ! ! !
Memory ! 1 4MB Brd ! 20W!$1100 ! 8 4MB Brds! 90W !$8800
Board ! ! ! ! ! !
! ! ! ! ! !
Proc Brd! 1, 2-Proc. ! 30 ! 1500 ! 5, 2-Proc.! 150 ! 7500
! Brd ! ! ! Brds ! !
! ! ! ! ! !
Display ! 1 Board ! 80 ! 2300 ! 4 Boards ! 320 ! 9200
Proc. ! ! ! ! ! !
! ! ! ! ! !
System ! 1 Board ! 50 ! 500 ! Same ! 50 ! 500
Cntlr ! ! ! ! ! !
Board ! ! ! ! ! !
! ! ! ! ! !
VME ! 5 Boards ! 100 !15000 ! 9 Boards ! 170 !20000
Subsys ! ! ! ! ! !
! ! ! ! ! !
VDT ! 1 B&W High ! 150 ! 1000 ! Same+24b ! 345 ! 4000
! Resolution! ! ! Color ! !
! ! ! ! ! !
! ! ! ! ! !
Disk ! 1, 5-1/4" ! 25 ! 600 ! 2, 5-1/4" ! 50 ! 1200
! Winchester! ! ! Winchstr ! !
! ! ! ! ! !
Fans, ! 20 MBus & ! 5 ! 2000 ! Same ! 5 ! 2000
Pkg, ! 9 VMEBus ! ! ! ! !
BkPlns ! slots ! ! ! ! !
! ! ! ! ! !
Power ! 900W !{75%}! 1000 ! Same ! {75%}! 1000
Supply ! Delivered ! ! ! ! !
========!============!=====!======!===========!======!=====
Dragon ! Min Config ! 600 !25000 ! Max Config! 1560 !54200
System ! System ! ! ! System ! !


Considering the above data, the attendees at the 29-Jan-85 packaging meeting came to the following conclusions:

1) Since we are only willing to design one package, the package will be designed for a maximally configured system.

2) The package will support 20 M-Bus boards, 9 VME-Bus boards, and 2 5-1/4" Winchester disk drives.

3) The package will be built around a 19" rack.

4) Due to the size, noise, and power consumption of a maximally configured system, it will have to be designed for a remote machine room. (A minimally configured system in the office, however, might still be viable. Also, Deutsch suggested that multiple minimally configured systems might be put in one Dragon package.)

5) Due to the cost of vendor VME cards, Gasbarro suggested that we build our own.

6) There is an interest in building a smaller Dragon (call it Dragon-II). Dragon-II would have less expansibility and computational power than Dragon-I. It would use most of the same chips as Dragon-I, but have new board and package designs. A desk-top version was suggested by Barth and a Dove-like (wireless) package was suggested by Overton.
Supporting Calculations:
Note: All cost calculations assume custom CMOS ICs from ICL are free.
Memory Board:
Active Board Power Inactive Board Power
4W = 2 Cntl Chips * 2W 4W = 2 Cntl Chips * 2W
12.6 = 36 ActiveChps * 0.35W 0 = 0 ActiveChps * 0.35W
3.8 = 108 InactChps * 0.035W 5 = 144 InactChps * .035W
---- ---
20.4W 9W

Cost Per Board
$300 Board
720 RAM chips
20 Misc
60 2, PGA sockets & chip carriers
------
$1100


Processor Board (2 Processors):

Processor Board Power
6W = 2 Floating Point chip sets * 3W each
16 = 8 Cache chips * 2W
4 = 2 IFU chips * 2W
4 = 2 EU chips * 2W
----
30W

Cost Per Board
$300 Board
700 Floating Point chips
480 16, PGA sockets & chip carriers
20 Misc
------
$1500


Display Processor Board:

Board Power
10W = 5 CMOS Chips * 2W
32.0 = 64 ActiveChps * 0.5W
3.2 = 64 InactChps * 0.05W
10 = Color maps
10 = Video shift Regs.
----
65.2W

Cost Per Board
$300 Board
1700 RAM chips
100 Color map, DAC
150 5, PGA sockets & chip carriers
50 Misc
------
$2300


System Controller Board:

Board Power
4W = 2 Map Chips * 2W
12 = Clock generation and distribution
2 = Cache for M-Bus/VME-Bus interface
20 = Vendor chips for M-Bus/VME-Bus interface
10 = Diagnostic Bus
2 = Arbiter
----
50W

Cost Per Board
$300 Board
150 5, PGA sockets & chip carriers
50 Misc
------
$500


VME Subsystem:

Subsystem Power
15W = 68020 Board
15 = Winchester disk controller board
30 = Ethernet controller board
10 = 1MByte memory board
20 = Keyboard & mouse interface board
----
90W = Total for minimally configured system

80 = 4 Misc. boards (eg, audio, speech, tape)
----
170W Total for maximally configured system

Cost Per Subsystem (assuming vendor boards)
$15000 Total for minimally configured system
20000 Total for maximally configured system


VDTs:

VDT Power
150W = High Res. black & white
250W = High Res. 24-bit color

Cost Per VDT
$1000 High Res. black & white
$3000 High Res. 24-bit color


Disk Drives:

Drive Power
25W = 1, 5-1/4" Winchester drive >100 MByte

Cost Per Drive
$600


Mechanical Package & Fans:

Fans Power
5W =

Cost Per Package
$2000


Power Supply:

Power Efficiency
75%

Power Supply Cost
$1000 900 W delivered