Return to Bill's Page
THE SUN HARDWARE REFERENCE
compiled by James W. Birdsall
(jwbirdsa@picarefy.com)
PART I
======
OVERVIEW
CPU/CHASSIS
OVERVIEW
========
This primary focus of this document is to cover Sun-badged hardware
in detail sufficient to be useful to buyers and collectors of used Sun
hardware, much of which comes without documentation. Details on
hardware commonly used with Suns, especially hardware specifically
designed for Suns, are also included where available. The focus is
generally on older equipment, since information on newer equipment is
more readily available, from Sun itself if nowhere else. In particular,
no effort is made to keep up with Sun's introduction of new SPARC
models.
Note that there is no warranty of any kind on the information in this
document. It has been assembled from a variety of sources of varying
reliability. Efforts have been made to exclude information known to be
incorrect, and to include only information deemed reasonably reliable,
but there is no guarantee on any of it, especially since official Sun
documents occasionally contradict each other.
This document is copyright (c) 1995 by James W. Birdsall. You may
distribute it freely in unmodified form.
THIS DOCUMENT IS A WORK IN PROGRESS. I still have a lot of
information which I have not had time to integrate yet. In addition, if
you have documentation for systems or boards not listed here, speak up!
I would really like to get ahold of an *old* Sun Field Engineer's Handbook.
Henry Bryant of Sun's Atlanta office kindly donated one that covers
Sun-3's, 386i's, and Sun-4's, but I'm still looking for an old one that
covers Sun-2's. Even the opportunity to borrow one would be appreciated.
This document is available via anonymous FTP from ftp.netcom.com:
/pub/ru/rubicon/sun.hdwr.ref. The file reference.zip contains all the
parts; individual parts are available in the reference.parts directory.
This document is organized into the following sections:
*** PART I ***
OVERVIEW
CPU/CHASSIS
Sun-1, Sun-2, Sun-3, Sun 386i, Sun-4/SPARC
General descriptions of the models, including
processor/fpu/speed, bus, chassis type, OS support, etc.
Processor Data
Info on SuperSPARC, microSPARC, etc.
*** PART II ***
FAQ
ROM Monitors
How to use the ROM monitor built into every Sun (boot
instructions and other tips).
Using a Terminal as Console
Notes on using a serial terminal instead of a Sun framebuffer
and keyboard.
Memory Display on Startup
How much memory a system has.
Miscellaneous Questions and Answers
Facts in Search of a Home
Miscellaneous Pinouts
SIMM Compatbility Chart
*** PART III ***
BOARDS
CPU, memory, video
Descriptions of boards by type and part number, including
pinouts, jumpers, DIP switch settings, and LEDs.
*** PART IV ***
BOARDS (cont'd)
SCSI, non-SCSI disk controllers, tape controllers, Ethernet,
serial/parallel/other commo, floating-point/system accelerator,
backplanes, other, crossreference by bus
Descriptions of boards by type and part number, including
pinouts, jumpers, DIP switch settings, and LEDs.
DISKS
SMD, MFM, ESDI, SCSI
Descriptions of models commonly used, including jumpers and
switch settings.
KEYBOARDS
Types 1-5c
Descriptions of types of keyboards, what CPUs they work with,
and any configuration information.
Alternatives
Ergonomic keyboards.
MICE
Sun-1, Sun-2, Sun-3, Sun-4
Descriptions of types of mice, what CPUs they work with, and any
configuration information.
Alternatives
Trackballs, etc.
MONITORS
TTL mono, ECL/TTL mono, color
Descriptions of types of monitors, what video boards they work
with, and any configuration information.
FLOPPY DRIVES
Descriptions of models commonly used, including jumpers and
switch settings.
TAPE DRIVES
9-track, QIC-11, QIC-24
Descriptions of models commonly used, including jumpers and
switch settings.
*** PART V ***
APPENDICES
Cardcage configuration tables
What cards go in which slots in which machines.
Part number index
Index of all known part numbers, with references to larger
descriptions, if any, in the main body
Repairs and Modifications
Repair and modification information as contributed by various
net.people.
Announcement Dates/List Prices
Announcement dates and list prices for various configurations.
Author's Notes
Miscellanea.
Bibliography/Acknowledgments
Contributors, and documents used in compiling this reference.
CPU/CHASSIS
===========
For each model listed below, whatever information is available is
given, in the following order:
Processor: The microprocessor followed by its clock speed in MHz. The
floating point coprocessor (FPU), if any, followed by whatever
information is available about the MMU, including the number of hardware
contexts. Lastly, various speed ratings, as available: MIPS (Millions of
Instructions Per Second, aka Meaningless...), MFLOPS (Millions of
FLoating-point OPerations per Second), SPECmark89, and/or
SPECint92/SPECfp92/SPECintRate92/SPECfpRate92. Note that some SPARC
processors are referred to by name; information on these is available in
the "Processor Data" section.
CPU or motherboard: The Sun part number of the CPU board or
motherboard.
Chassis type: "Rackmount" chassis, as the name suggests, are designed
to fit into a standard 19" equipment rack. They usually require
clearance over and under the chassis for cooling. "Pizza box" chassis
are intended to sit on a desktop, typically underneath the monitor; they
are low, wide, and deep. Older pizza boxes (2/50, 3/75, 3/50, and 3/60)
are much wider than they are deep; newer ones are square (3/80,
SPARCstation 1, 1+, 2, etc.). Some older pizza boxes (mostly the 3/50)
have a 'dimple top', a case top with a circular depression that allows
the chassis to serve as a tilt/swivel monitor base directly. 9-slot
Multibus and 12-slot VME (and probably 6-slot VME as well) "deskside"
chassis are wide towers that must stand on the floor. 3-slot VME
"deskside" chassis can stand on the floor as narrow towers or lie on
their sides on a desktop as tallish pizza boxes. "Lunchbox" chassis are
small rectangular boxes the size of a couple large hardcover books
stacked. "Monitor" chassis (SPARCstation SLC, etc.) have the motherboard
in the back of the monitor.
Bus: Whatever bus or busses the machine has. Sun has, at various
times, used Multibus, VMEbus, ISA, SBus, Mbus, and XDBus.
Memory: The amount of physical memory the machine can take, if known,
followed by the maximum size of the machine's virtual memory space, if
known, followed by the cycle time for physical memory, if known, and
finally details of any on-chip or off-chip caches, if known. The caches
on the Motorola 68020 and 68030 and the Intel 80386 are not described,
since information on these chips is widely known. To save space, the
on-chip caches of various common SPARC processors are described in the
"Processor Data" section.
Notes: General information which does not belong under other
headings.
Not all models shown in the Announcement Date/List Price section in
the appendix are described in this section. In particular, models which
differ only in peripherals have been excluded.
Sun-1
-----
OVERVIEW
Sun-1's were the very first models ever produced by Sun. The earliest
ran Unisoft V7 UNIX; SunOS 1.x was introduced later. According to some
sources, fewer than 200 Sun-1's were ever produced; they are certainly
rare. The switch from Motorola 68000's to 68010's occurred during the
Sun-1's reign. Some models are reported to have 3Mbit Ethernet taps as
well as 10Mbit.
68000-based Sun-1's are not supported by SunOS. The last version of
SunOS to support Sun-1's may be the same as the last version to support
Sun-2's, since the 100U CPU boards are the same part.
From bjork@rahul.net (../Steven):
[The Sun-1] did not have the DVMA of the sun-2 architecture.
There was an even earlier board that had the 68000, not the
68010. The 68000 board was licensed by Stanford to several folks
(can't recall names). The original cisco cpu was a slightly
upgraded 68000 version. Andy Bechtolsheim was using SUDS on the
triple-I in the CS Dungeon (Margaret Jacks Hall) when my boss
asked him to modify the sun board to accept 256k ram chips. I
handed Andy a pencil and the schematics and he scribbled the
mods on it. I took the mods, and with exacto knife and jumpers,
modified a sun board for the 256k chips. Len Bosack then took
the mods and relaid out the PC. That board was the first cisco
cpu, and was also produced internally to Stanford.
[...]
The original sun lacked the DVMA and thus needed Multibus
memory. Their "ar" tape controller design thus included 256k of
Multibus memory. When upgraded to a sun2, one had to switch this
ar-resident memory off since it would conflict with the DVMA
memory on the sun2 P2 (memory bus).
MODELS
Sun-1
Processor(s): 68000
Notes: Large black desktop boxes with 17" monitors.
Uses the original Stanford-designed video board
and a parallel microswitch keyboard (type 1) and
parallel mouse (Sun-1).
100
Processor(s): 68000 @ 10MHz
Bus: Multibus, serial
Notes: Uses a design similar to original SUN (Stanford
University Network) CPU. The version 1.5 CPU can
take larger RAMs.
100U
Processor(s): 68010 @ 10MHz
CPU: 501-1007
Bus: Multibus, serial
Notes: "Brain transplant" for 100 series. Replaced CPU
and memory boards with first-generation Sun-2
CPU and memory boards so original customers
could run SunOS 1.x. Still has parallel kb/mouse
interface so type 1 keyboards and Sun-1 mice
could be connected.
170
Processor(s): 68010?
Bus: Multibus?
Chassis type: rackmount
Notes: Server. Slightly different chassis design than
2/170's
Sun-2
-----
OVERVIEW
Sun-2's were introduced in the early 1980's and were Sun's first
major commercial success. While not as popular or as common as the later
Sun-3's, they did well and there are still quite a few in circulation in
the home/collector-used market.
All Sun-2's are based on the Motorola 68010 and run SunOS. The last
version of SunOS to support Sun-2's was 4.0.3. Early Sun-2's were
Multibus; later models were VME, which Sun continued to use through the
Sun-3 era and well into the Sun-4 line.
One of the hardest parts of restoring a Sun-2 is finding OS tapes for
it. The hardware is usually still in fine working order, but tapes -- if
you can even find any -- are sometimes unreadable after so many years.
See author's notes in the appendices.
MODELS
2/120
Processor(s): 68010 @ 10MHz
CPU: 501-1007/1051
Chassis type: deskside
Bus: Multibus, 9 slots
Memory: 7M physical with mono video, 8M without
Notes: First machines in deskside chassis. Serial
microswitch keyboard (type 2), Mouse Systems
optical mouse (Sun-2).
2/170
Processor(s): 68010 @ 10MHz
CPU: 501-1007/1051
Chassis type: rackmount
Bus: Multibus, 15 slots
Memory: 7M physical with mono video, 8M without
Notes: Server.
2/50
Processor(s): 68010 @ 10MHz
CPU: 501-1141/1142/1143
Chassis type: wide pizza box
Bus: VME, 2 slots
Memory: 7M physical with mono video, 8M without
Notes: Optional SCSI board (model name is SCSI-2
because it is the second SCSI design; the first
was for 2/1xx's) sits on memory expansion board
in second slot. CPU board has 1, 2, or 4M,
Ethernet, two serial ports. The (type 2)
keyboard and mouse attach via an adapter that
accepts two modular plugs and attaches to a DB15
port.
2/130
2/160
Processor(s): 68010
CPU: 501-1144/1145/1146
Chassis type: deskside
Bus: VME, 12 slots
Memory: 7M physical with mono video, 8M without
Notes: First machine in 12-slot deskside VME chassis.
Has four-fan cooling tray instead of six as in
later machines, which led to cooling problems
with lots of cards. Also has only four P2 memory
connectors bussed instead of six. 2/160
upgradeable to a 3/160 by replacing the CPU
board. No information on the differences between
the 2/130 and the 2/160.
Sun-3
-----
OVERVIEW
Sun switched to using the Motorola 68020 with the introduction of the
Sun-3's. A few later models had 68030's, but by that time Sun was
already moving toward SPARC processors. All models either have a 68881
or 68882 FPU installed stock or at least have a socket for one. All
models which are not in pizza box chassis are VMEbus. Two out of three
pizza box models have a "P4" connector which can take a framebuffer; the
exception is the 3/50.
Support for Sun-3's was introduced in SunOS 3.0. The last version of
SunOS to support Sun-3's was 4.1.1U1.
During the Sun-3 era, Sun introduced the handy practice of putting
the model number on the Sun badge on the front of the chassis.
There are two different kernel architectures in the Sun-3 model line.
All 68020-based models are "sun3" architecture; 68030-based models (the
3/80 and 3/4xx) are "sun3x" architecture.
MODELS
3/160
Processor(s): 68020 @ 16.67MHz, 68881, Sun-3 MMU, 8 hardware
contexts, 2 MIPS
CPU: 501-1163/1164 (1074/1094/1208 ?)
Chassis type: deskside
Bus: VME, 12 slots
Memory: 16M physical (documented), 256M virtual, 270ns cycle
Notes: First 68020-based Sun machine. Uses the
"Carrera" CPU, which is used in most other Sun
3/1xx models and the 3/75. Sun supplied 4M
memory expansion boards; third parties had up to
32M on one card. SCSI optional. One variant of
the memory card holds a 6U VME SCSI board; there
is also a SCSI board which sits in slot 7 of the
backplane and runs the SCSI bus out the back of
the backplane to the internal disk/tape (slot 6
in very early backplanes). CPU has two serial
ports, Ethernet, keyboard. Type 3 keyboard plugs
into the CPU; Sun-3 mouse plugs into the
keyboard. Upgradeable to a 3/260 by replacing
CPU and memory boards.
3/75
Processor(s): 68020 @ 16.67MHz, 68881, Sun-3 MMU, 8 hardware
contexts, 2 MIPS
CPU: 501-1163/1164 (1074/1094 ?)
Chassis type: wide pizza box
Bus: VME, 2 slot
Memory: 16M physical (documented), 256M virtual, 270ns cycle
Notes: Optional SCSI sits on memory expansion board in
second slot.
3/140
Processor(s): 68020 @ 16.67MHz, 68881, Sun-3 MMU, 8 hardware
contexts, 2 MIPS
CPU: 501-1164 (1074/1094/1163/1208 ?)
Chassis type: deskside
Bus: VME, 3 slots
Memory: 16M physical (documented), 256M virtual, 270ns cycle
3/150
Processor(s): 68020 @ 16.67MHz, 68881, Sun-3 MMU, 8 hardware
contexts, 2 MIPS
CPU: 501-1074/1094/1163/1164/1208
Chassis type: deskside
Bus: VME, 6 slots
Memory: 16M physical (documented), 256M virtual, 270ns cycle
3/180
Processor(s): 68020 @ 16.67MHz, 68881, Sun-3 MMU, 8 hardware
contexts, 2 MIPS
CPU: 501-1163/1164 (1074/1094/1208 ?)
Chassis type: rackmount
Bus: VME, 12 slots
Memory: 16M physical (documented), 256M virtual, 270ns cycle
Notes: Rackmount version of 3/160. Upgradeable to a
3/280 by replacing the CPU and memory boards.
Very early backplanes have the special SCSI
hookup on slot 6 rather than 7.
3/110
Processor(s): 68020
CPU: 501-1134/1209
Chassis type: deskside
Bus: VME, 3 slots
Notes: Similar to the "Carerra" CPU, but has 8-bit
color frame buffer on board and uses 1M RAM
chips for 4M on-CPU memory. Code-named "Prism".
3/50
Processor(s): 68020 @ 15.7MHz, 68881 (socket), Sun-3 MMU,
8 hardware contexts, 1.5 MIPS
CPU: 501-1075/1133/1162/1207
Chassis type: wide pizza box
Bus: none
Memory: 4M physical (documented), 256M virtual, 270ns cycle
Notes: Cycle-stealing monochrome frame buffer. 4M
memory maximum stock, but third-party memory
expansion boards were sold, allowing up to at
least 12M. No bus or P4 connector. Onboard SCSI.
Thin coax or AUI Ethernet. Code-named "Model
25".
3/60
Processor(s): 68020 @ 20MHz, 68881 (stock), Sun-3 MMU,
8 hardware contexts, 3 MIPS
CPU: 501-1205/1322/1334/1345
Chassis type: wide pizza box
Bus: P4 connector (not same as P4 on 3/80)
Memory: 24M physical, 256M virtual, 200ns cycle
Notes: VRAM monochome frame buffer. Optional color
frame buffer (could run mono and color from same
board) on P4 connector. Onboard SCSI. SIMM
memory (100ns 1M x 9 SIMMs). High (1600 * 1100) or
low (1152 * 900) resolution mono selectable by
jumper. Thin coax or AUI Ethernet. Code-named
"Ferrari".
3/60LE
Processor(s): 68020 @ 20MHz, 68881 (stock), Sun-3 MMU,
8 hardware contexts, 3 MIPS
CPU: 501-1378
Memory: 12M physical, 256M virtual, 200ns cycle
Notes: A version of the 3/60 with no onboard
framebuffer and limited to 12M of RAM (4M of
256K SIMMs and 8M of 1M SIMMs).
3/260
Processor(s): 68020 @ 25MHz, 68881 @ 20MHz (stock), Sun-3 MMU,
8 hardware contexts, 4 MIPS
CPU: 501-1100/1206
Chassis type: deskside
Bus: VME, 12 slot
Memory: 64M (documented) physical with ECC, 256M virtual;
64K write-back cache, direct-mapped,
virtually-indexed and virtually-tagged, with
16-byte lines; 80ns cycle
Notes: Two serial ports, AUI Ethernet, keyboard, and
video on CPU. Video is mono, high-resolution
only. Sun supplied 8M memory boards. Sun 4/2xx
32M boards work up to 128M. First Sun with an
off-chip cache. Upgradeable to a 4/260 by
replacing the CPU board. Code-named "Sirius".
3/280
Processor(s): 68020 @ 25MHz, 68881 @ 20MHz (stock), Sun-3 MMU,
8 hardware contexts, 4 MIPS
CPU: 501-1100/1206
Chassis type: rackmount
Bus: VME, 12 slot
Memory: 64M (documented) physical with ECC, 256M virtual;
64K write-back cache, direct-mapped,
virtually-indexed and virtually-tagged, with
16-byte lines; 80ns cycle
Notes: Rackmount version of the 3/260. Upgradeable to a
4/280 by replacing the CPU board. Code-named
"Sirius".
3/80
Processor(s): 68030 @ 20MHz, 68882 @ 20 or 40MHz, 68030 on-chip
MMU, 3 MIPS, 0.16 MFLOPS
CPU: 501-1401/1650
Chassis type: square pizza box
Bus: P4 connector (not same as P4 on 3/60)
Memory: 16M or 40M physical, 4G virtual, 100ns cycle
Notes: Similar packaging to SparcStation 1. Parallel
port, SCSI port, AUI Ethernet, 1.44M 3.5" floppy
(720K on early units?). No onboard framebuffer.
Code-named "Hydra". Type-4 keyboard and Sun-4 mouse,
plugged together and into the machine with a small
DIN plug. Boot ROM versions 3.0.2 and later allow
using 4M SIMMs in some slots for up to 40M (see
Misc Q&A #14 and #15).
3/460
Processor(s): 68030 @ 33 MHz, 68882, 68030 on-chip MMU,
7 MIPS, 0.6 MFLOPS
CPU: 501-1299/1550
Bus: VME
Memory: 128M physical with ECC, 4G/process virtual,
64K cache, 80ns cycle
Notes: A 3/260 upgraded with a 3/4xx CPU board. Uses
original 3/2xx memory boards.
3/470
Processor(s): 68030 @ 33 MHz, 68882, 68030 on-chip MMU,
7 MIPS, 0.6 MFLOPS
CPU: 501-1299/1550
Chassis type: deskside
Bus: VME
Memory: 128M physical with ECC, 4G/process virtual,
64K cache, 80ns cycle
Notes: Rare. Code-named "Pegasus". 8M standard, uses
same memory boards as 3/2xx.
3/480
Processor(s): 68030 @ 33 MHz, 68882, 68030 on-chip MMU,
7 MIPS, 0.6 MFLOPS
CPU: 501-1299/1550
Chassis type: rackmount
Bus: VME
Memory: 128M physical with ECC, 4G/process virtual,
64K cache, 80ns cycle
Notes: Rare. Code-named "Pegasus". 8M standard, uses
same memory boards as 3/2xx.
3/E
Processor(s): 68020
CPU: 501-8028
Bus: VME
Notes: Single-board VME Sun-3, presumably for use as a
controller, not as a workstation. 6U form
factor. Serial and keyboard ports. External RAM,
framebuffer, and SCSI/ethernet boards
available.
Sun 386i
--------
OVERVIEW
The Sun 386i models, based on the Intel 80386 processor, were
introduced when 80386-based IBM PC/AT clones were starting to become
widespread. Intel had finally produced a chip sufficiently capable
(32-bit, among other things) to allow porting SunOS, and using an Intel
processor and an ISA bus offered the ability to run MS-DOS applications
without speed-draining emulation. Unfortunately, they were a dismal
failure.
Support for Sun-386i's was introduced in SunOS 4.0 (?). The 386i
SunOS releases came from Sun's East Coast division, so 386i SunOS was
not identical to the standard version with the same number. The last
released version of SunOS to support Sun-386i's was 4.0.2; there are a
few copies of 4.0.3Beta (with OpenLook 2.0) floating around.
MODELS
386i/150
Processor(s): 80386 @ 20MHz, 80387, 80386 on-chip MMU,
3 MIPS, 0.17 MFLOPS
CPU: 501-1241/1414
Chassis type: tower (20"H * 7"W * 16"D)
Bus: ISA (4 32-bit slots, 3 16-bit, 1 8-bit)
Memory: 8M physical
Notes: Shared code name "Roadrunner" with the /250. The
frame buffer was not on the ISA bus. 720K or
1.44M 3.5" floppy. A variant of the 150 had the
250's external cache.
386i/250
Processor(s): 80386 @ 25MHz, 80387, 80386 on-chip MMU,
5 MIPS, 0.2 MFLOPS
CPU: 501-1324/1413
Chassis type: tower
Bus: ISA (4 32-bit slots, 3 16-bit, 1 8-bit)
Memory: 16M physical, 32K cache
Notes: Shared code name "Roadrunner" with the /150. The
frame buffer was not on the ISA bus. 720K or
1.44M 3.5" floppy.
486i
Processor(s): 80486
Notes: Code-named "Apache". A very limited quantity of
these were supposedly built and shipped to
customers just before the Intel-based line was
cancelled.
Sun-4/SPARCstation/SPARCserver/SPARCwhatever
--------------------------------------------
OVERVIEW
These machines were initially introduced with model designations in
the same pattern as previous lines: Sun 4/xxx. However, for marketing
purposes, Sun departed from their classic naming scheme with the name
SPARCstation, and has since experimented with alphabetic designations
(e.g. "SPARCstation SLC") before returning to numbered SPARCstations.
Until the SPARCstation 10, however, every model still had a 4/xxx
designation as well, which is displayed by the ROM monitor during
power-up and used by much of Sun's documentation.
This model line marks the introduction of Sun's own RISC chip, the
SPARC. There have been a number of different implementations of the chip
from various manufacturers, with varying degrees of hardware support for
the instruction set.
Support for Sun-4's was introduced in SunOS 4.0, although there was a
special variant of SunOS 3.2 for Sun-4's which was shipped with some
very early units. Since this product line is still current, it is still
supported by SunOS, which has mutated to become Solaris.
Some of the later models have pictures silkscreened on their CPU
boards.
Note that MIP/GIP ratings for later models are even more suspicious
than usual for benchmarks.
There are several kernel architectures in the Sun-4 model line. Where
known, the architecture for each model is listed.
MODELS
4/260
Processor(s): SF9010 @ 16.67MHz, Weitek 1164/1165, Sun-4 MMU,
16 hardware contexts, 10 MIPS, 1.6 MFLOPS
CPU: 501-1129/1491/1522
Chassis type: deskside
Bus: VME, 12 slot
Memory: 128M physical with ECC, 1G/process virtual,
60ns cycle
Architecture: sun4
Notes: First SPARC machine. Code-named "Sunrise". Cache
much like Sun-3/2xx, uses same memory boards.
4/110
Processor(s): MB86900 @ 14.28MHz, Weitek 1164/1165, Sun-4 MMU,
16 hardware contexts, 7 MIPS
CPU: 501-1199/1237/1462/1463/1512/1513/1514/1515/
1464/1465/1516/1517/1656/1657/1658/1659/
1660/(many others)
Chassis type: deskside
Bus: VME, 3 slot
Memory: 32M physical with parity, 1G/process virtual,
70ns cycle
Architecture: sun4
Notes: First desktop-able SPARC. CPU doesn't support
VME busmaster cards (insufficient room on CPU
board for full VME bus interface), so DMA disk
and tape boards won't work with it. Originally
intended as single-board machine, although there
are a few slave-only VME boards (such as the
ALM-2 and second ethernet controller) which work
with it. Onboard SCSI, two serial ports,
Ethernet, keyboard/mouse. "P4" frame buffer
could be monochrome or color. Used static column
RAM rather than a conventional cache. Code-named
"Cobra".
4/280
Processor(s): SF9010 @ 16.67MHz, Weitek 1164/1165, Sun-4 MMU,
16 hardware contexts, 10 MIPS, 1.6 MFLOPS
CPU: 501-1129/1491/1522
Chassis type: rackmount
Bus: VME, 12 slot
Memory: 128M physical with ECC, 1G/process virtual,
60ns cycle
Architecture: sun4
Notes: Rackmount version of 4/260.
4/150
Notes: 4/110 CPU in a 3/150 chassis.
SPARCstation 1 (4/60)
Processor(s): MB86901A or LSI L64801 @ 20MHz, Weitek 3170,
Sun-4c MMU, 8 hardware contexts, 12.5 MIPS, 1.4
MFLOPS, 10 SPECmark89
CPU: 501-1382-12/1382-13/1382-14/1629/1629-14
Chassis type: square pizza box
Bus: SBus, 3 slots
Memory: 64M physical with synchronous parity,
512M/process virtual; 64K write-through cache,
direct-mapped, virtually indexed, virtually
tagged, 16-byte lines; 50ns cycle
Architecture: sun4c
Notes: Code name "Campus". 1M x 9 30-pin 100ns SIMMs,
possibly higher capacities as well, in four
banks. 720K or 1.44M (?) 3.5" floppy.
SPARCserver 1
Notes: SPARCstation 1 without a monitor/framebuffer.
4/330 (SPARCstation 330, SPARCserver 330)
Processor(s): CY7C601 @ 25MHz, TI8847, Sun-4 MMU, 16 hardware
contexts, 16 MIPS, 2.6 MFLOPS, 11.3 SPECmark89
CPU: 501-1316/1742
Bus: VME
Memory: 56M/72M physical with synchronous parity, 1G/process
virtual, 128K cache, 40ns cycle
Architecture: sun4
Notes: Onboard SCSI, serial ports. Uses SIMMs. Cache
similar to 4/2xx but write-through. Code-named
"Stingray". 56M limit only for early versions of
ROM. 1M or 4M 9-chip SIMMs, 100ns.
4/310
Notes: 4/3xx CPU in a 4/110 chassis.
4/350
Notes: 4/3xx CPU in a 3/150 chassis.
4/360
Processor(s): CY7C601 @ 25MHz, TI8847, Sun-4 MMU, 16 hardware
contexts, 16 MIPS, 2.6 MFLOPS, 11.3 SPECmark89
CPU: 501-1316/1742
Chassis type: deskside
Bus: VME, 12 slots
Memory: 56M+ physical with synchronous parity, 1G/process
virtual, 128K cache, 40ns cycle
Architecture: sun4
Notes: 4/260 upgraded with a 4/3xx CPU. Onboard SCSI,
serial ports. Uses SIMMs. Cache similar to 4/2xx
but write-through. Code-named "Stingray". Room
for SCSI disk in top of chassis. 56M limit only
for early versions of ROM.
4/370 (SPARCstation 370, SPARCserver 370)
Processor(s): CY7C601 @ 25MHz, TI8847, Sun-4 MMU, 16 hardware
contexts, 16 MIPS, 2.6 MFLOPS, 11.3 SPECmark89
CPU: 501-1316/1742
Bus: VME, 12 slots
Memory: 56M+ physical with synchronous parity, 1G/process
virtual, 128K cache, 40ns cycle
Architecture: sun4
Notes: Onboard SCSI, serial ports. Uses SIMMs. Cache
similar to 4/2xx but write-through. Code-named
"Stingray". Room for up to four SCSI disks in
top of chassis. 56M limit only for early
versions of ROM.
4/380
Notes: 4/280 upgraded with 4/3xx CPU.
4/390 (SPARCserver 390)
Processor(s): CY7C601 @ 25MHz, TI8847, Sun-4 MMU, 16 hardware
contexts, 16 MIPS, 2.6 MFLOPS, 11.3 SPECmark89
CPU: 501-1316/1742
Bus: VME
Memory: 56M+ physical with synchronous parity, 1G/process
virtual, 128K cache, 40ns cycle
Architecture: sun4
Notes: Onboard SCSI, serial ports. Uses SIMMs. Cache
similar to 4/2xx but write-through. Code-named
"Stingray". 56M limit only for early versions of
ROM.
4/470 (SPARCstation 470, SPARCserver 470)
Processor(s): CY7C601 @ 33MHz, TI8847 (?), 64 hardware
contexts, 22 MIPS, 3.8 MFLOPS, 17.6 SPECmark89
CPU: 501-1381/1899
Bus: VME
Memory: 96M physical, 128K cache
Architecture: sun4
Notes: Write-back rather than write-through cache,
3-level rather than 2-level Sun-style MMU.
Code-name "Sunray" (which was also the code name
for the 7C601 CPU).
4/490 (SPARCserver 490)
Processor(s): CY7C601 @ 33MHz, TI8847 (?), 64 hardware
contexts, 22 MIPS, 3.8 MFLOPS, 17.6 SPECmark89
CPU: 501-1381/1899
Bus: VME
Memory: 96M physical, 128K cache
Architecture: sun4
Notes: Write-back rather than write-through cache,
3-level rather than 2-level Sun-style MMU.
Code-name "Sunray" (which was also the code name
for the 7C601 CPU).
SPARCstation SLC (4/20)
Processor(s): MB86901A or LSI L64801 @ 20MHz, 12.5 MIPS, 1.2
MFLOPS, 8.6 SPECmark89
CPU: 501-1627/1680/1720/1748/1776/1777
Chassis type: monitor
Bus: none
Memory: 16M physical; 64K write-through cache,
direct-mapped, virtually indexed, virtually
tagged, 16-byte lines
Architecture: sun4c
Notes: Code name "Off-Campus". 4M SIMMs. No fan.
17" mono monitor built in.
SPARCstation IPC (4/40)
Processor(s): MB86901A or LSI L64801 @ 25MHz, 13.8 SPECint92,
11.1 SPECfp92, 327 SPECintRate92, 263
SPECfpRate92
CPU: 501-1689/1690/1835
Chassis type: lunchbox
Bus: SBus, 2 slots
Memory: 48M physical; 64K write-through cache,
direct-mapped, virtually indexed, virtually
tagged, 16-byte lines
Architecture: sun4c
Notes: Code name "Phoenix". 1M or 4M x 9 30-pin 100ns
SIMMs, three banks. Onboard mono frame buffer.
1.44M 3.5" floppy.
SPARCstation 1+ (4/65)
Processor(s): LSI L64801 @ 25MHz, Weitek 3172, Sun-4c MMU,
8 hardware contexts, 15.8 MIPS, 1.7 MFLOPS, 12
SPECmark89
CPU: 501-1632
Chassis type: square pizza box
Bus: SBus, 3 slots
Memory: 64M (40M?) physical with synchronous parity,
512M/process virtual; 64K write-through cache,
direct-mapped, virtually indexed, virtually
tagged, 16-byte lines; 50ns cycle
Architecture: sun4c
Notes: Code name "Campus B". 1M x 9 30-pin 100ns SIMMs,
possibly higher capacities as well, in four
banks. 1.44M 3.5" floppy. Essential same as
SPARCstation 1, just faster clock and improved
SCSI controller.
SPARCserver 1+
Notes: SPARCstation 1+ without a monitor/framebuffer.
SPARCstation 2 (4/75)
Processor(s): CY7C601 @ 40MHz, TI TMS390C601A (602A ?), Sun-4c
MMU, 16 hardware contexts, 28.5 MIPS, 4.2
MFLOPS, 21.8 SPECint92, 22.8 SPECfp92, 517
SPECintRate92, 541 SPECfpRate92
CPU: 501-1638/1744
Chassis type: square pizza box
Bus: SBus @ 20MHz, 3 slots
Memory: 64M physical on motherboard/128M total, 64K
write-through cache, direct-mapped, virtually
indexed, virtually tagged, 32-byte lines
Architecture: sun4c
Notes: Code name "Calvin". 1M or 4M x 9 30-pin 80ns
SIMMs, in four banks. Case slightly larger and
has more ventilation. (Some models apparently
have LSI L64811 @ 40MHz?) Expansion beyond 64M
is possible with a 32M card which can take a 32M
daughterboard (card blocks SBus slot).
SPARCserver 2
Notes: SPARCstation 2 without a monitor/framebuffer.
SPARCstation ELC (4/25)
Processor(s): Fujitsu MB86903 or Weitek W8701 @ 33MHz, FPU on
CPU chip, Sun-4c MMU, 8 hardware contexts,
21 MIPS, 3 MFLOPS, 18.2 SPECint92, 17.9
SPECfp92, 432 SPECintRate92, 425 SPECfpRate92
CPU: 501-1730/1861
Chassis type: monitor
Bus: none
Memory: 64M physical; 64K write-through cache,
direct-mapped, virtually indexed, virtually
tagged, 32-byte lines
Architecture: sun4c
Notes: Code name "Node Warrior". 4M or 16M x 33 SIMMs.
No fan. 17" mono monitor built in.
SPARCstation IPX (4/50)
Processor(s): Fujitsu MB86903 or Weitek W8701 @ 40MHz, FPU on
CPU chip, Sun-4c MMU, 8 hardware contexts,
28.5 MIPS, 4.2 MFLOPS, 21.8 SPECint92,
21.5 SPECfp92, 517 SPECintRate92, 510
SPECfpRate92
Chassis type: lunchbox
Bus: SBus, 2 slots
Memory: 64M physical; 64K write-through cache,
direct-mapped, virtually indexed, virtually
tagged, 32-byte lines
Architecture: sun4c
Notes: Code name "Hobbes". 4M or 16M x 33 72-pin SIMMs.
Onboard GX-accelerated cg6 color framebuffer
(not usable with ECL mono monitors, unlike SBus
version). Picture of Hobbes (from Watterson's
"Calvin and Hobbes" comic strip) silkscreened on
motherboard. 1.44M 3.5" floppy.
SPARCengine 1E (4/E)
CPU: 501-8058/8035
Bus: SBus, 1 slot
Notes: Basically a SPARCstation 1 (or 1+?) with a VME
interface and 8K rather than 4K pages. Sold as a
6U VME board. Code name "Polaris".
SPARCsystem 6xxMP/xx
Processor(s): ROSS CY7C601 @ 40MHz or SuperSPARC @ 45 or
50MHz, CY7C602 FPU or on TI chip, CY7C605 MMU or
on TI chip (Reference); 4096 or 65536 hardware
contexts; ROSS: 114 MIPS
Chassis type: rackmount
Bus: VME, SBus, and Mbus
Memory: ROSS: Off-chip 64K write-back, direct-mapped,
virtually indexed, virtually and physically
tagged, 32-byte lines
Architecture: sun4m
Notes: First Mbus-based machine. Cypress/ROSS Mbus
modules later upgraded to TI SuperSPARC modules
(/xx models). Code name "Galaxy". ROSS cache can
be run write-through but OS puts it in
write-back; physically tagged for MP cache
coherency. Up to four CPUs. 630MP/600MP: 128M
physical. 670MP/690MP: 640M physical.
SPARCclassic (SPARCclassic Server)(SPARCstation LC) (4/15)
Processor(s): microSPARC @ 50MHz, 59.1 MIPS, 4.6 MFLOPS,
26.4 SPECint92, 21.0 SPECfp92,
626 SPECintRate92, 498 SPECfpRate92
Chassis type: lunchbox
Bus: SBus @ 25MHz (?), 2 slots
Memory: 96M physical
Architecture: sun4m
Notes: Sun4m architecture, but no Mbus. Shares code name
"Sunergy" with LX. Uniprocessor only. 1.44M 3.5"
floppy. Soldered CPU chip. Onboard cgthree
framebuffer, AMD79C30 8-bit audio chip. Takes
pairs of 4M or 16M 60ns SIMMs. First supported
by special SunOS release 4.1.3c, then general
release 4.1.3_U1.
SPARCstation LX (4/30)
Processor(s): microSPARC @ 50MHz, 59.1 MIPS, 4.6 MFLOPS,
26.4 SPECint92, 21.0 SPECfp92,
626 SPECintRate92, 498 SPECfpRate92
Chassis type: lunchbox
Bus: SBus @ 25MHz (?), 2 slots
Memory: 96M physical
Architecture: sun4m
Notes: Sun4m architecture, but no Mbus. Shares code
name "Sunergy" with SPARCclassic. Uniprocessor
only. Takes pairs of 4M or 16M 60ns SIMMs.
Soldered CPU chip. Onboard cgsix framebuffer, 1M
VRAM standard, expandable to 2M. DBRI 16-bit
audio/ISDN chip. First supported by special
SunOS release 4.1.3c, then general release
4.1.3_U1.
SPARCstation Voyager
Processors(s): microSPARC II @ 60MHz, 47.5 SPECint92,
40.3 SPECfp92, 1025 SPECintRate92, 859
SPECfpRate92
Bus: SBus; PCMCIA type II, 2 slots
Memory: 80M physical
Architecture: sun4m
Notes: Portable (laptop?). 16M standard, two memory
expansion slots for Voyager-specific SIMMs (16M
or 32M). Code-named "Gypsy". 14" 1152x900 mono
or 12" 1024x768 color flat panel displays. DBRI
16-bit audio/ISDN chip.
SPARCserver 10/xx
Notes: SPARCstation 10/xx without monitor/framebuffer.
SPARCstation 3
Notes: Although this model appeared in a few Sun price
lists, it was renamed the SPARCstation 10 before
release.
SPARCstation 10/xx
Processor(s): SuperSPARC @ 33, 36, 40, 45, and 50MHz;
86.1-96.2 MIPS (?), see below for SPEC
Motherboard: 501-1733/2259/2274
Chassis type: square pizza box
Bus: SBus, 4 slots and Mbus, 2 slots
Memory: 512M physical; 32K off-chip cache for model 30,
1M off-chip direct-mapped cache physically
indexed and tagged for model 41; 1M off-chip
cache for models 30LC (?), 412MP, 51, 512MP,
514MP, 52, and 54.
Architecture: sun4m
Notes: Code name for 10/41 "Campus-2". 1.44M 3.5"
floppy. Up to four CPUs, some models with
multiple CPUs stock. 16M or 64M 70ns SIMMs.
Some models (514, others?) use double-width CPU
modules which block SBus slots.
model MHz SPECint92 SPECfp92 SPECint SPECfp
----- --- --------- -------- -Rate92--Rate92-
10/20 33 39.8 46.6 943 1104
10/30 36 45.2 54.0 1072 1282
10/40 40 50.2 60.2 1191 1427
10/402 40x2 2112 2378
10/41 40 53.2 67.8 1264 1607
10/412 40x2 2411 2854
10/51 50 65.2 83.0 1580 2008
10/512 50x2 2950 3744
10/514 50x4 5155 5809
10/52 45x2 announced but never shipped
10/54 45x4 announced but never shipped
10/61
10/612
10/71
10/712
SPARCcenter 2000
Processor(s): SuperSPARC @ 40MHz, 50MHz, or 60MHz
Motherboard: 501-1866/2334
Bus: XDBus, SBus
Memory: 5G physical, 1M or 2M off-chip cache
Architecture: sun4d
Notes: Dual XDBus backplane with 20 slots. One board
type that carries dual Mbus SPARC modules with
2M cache (1M for each XDBus), 512M memory and
4 SBus modules. Any combination can be used;
memory is *not* tied to the CPU modules but to
the XDBus. Current CPU modules clock at 50 MHz,
initially they were at 40 MHz. Solaris 2.x
releases support an increasing number of CPUs
(up to full twenty at last info); this is due to
tuning efforts in the kernel. The initial
release supporting this machine is Solaris 2.2.
Code name "Dragon". 2.19 GIPS, 269 MFLOPS.
model MHz SPECint92 SPECfp92 SPECint SPECfp
----- --- --------- -------- -Rate92--Rate92-
2108 40x8 8047 10600
2216 50x16 21196 28064
SPARCclassic M
Processor(s); microSPARC @ 50MHz
Memory: 96M physical
Notes: 16M standard.
SPARCstation 10M
Processor(s): SuperSPARC @ 36MHz, 86.1 MIPS
Bus: SBus, Mbus
Memory: 512M physical, 32K cache
Notes: 32M standard. 1.44M 3.5" floppy.
SPARCserver 1000
Processor(s): SuperSPARC @ 50MHz or 60MHz
Motherboard: 501-2247/2248/2336/2338
Bus: XDBus, SBus
Memory: 2G physical, 1M off-chip cache
Architecture: sun4d
Notes: Single XDBus design with curious L-shaped
motherboards. Three SBus slots, onboard FSBE,
512M, two CPU modules per motherboard. Four
motherboards total, or a disk tray with four
535M 1" high 3.5" disks (1G disks supported
recently). Code name "Scorpion". 135 MIPS.
model MHz SPECint92 SPECfp92 SPECint SPECfp
----- --- --------- -------- -Rate92--Rate92-
1102 50x2 2730 3681
1104 50x4 5318 7076
1108 50x8 10113 12710
SPARCcluster 1
Processor(s): SuperSPARC @ 45MHz, 86.1 MIPS
Bus: SBus
Memory: 1M off-chip cache
Notes: 512M standard. A bunch of SPARCstation 10's
glued together with an switch (Alantec?
Kalpana?).
SPARCstation 5
Processor(s): microSPARC II @ 70MHz or 85MHz, 57.0/64.0
SPECint92, 47.3/54.6 SPECfp92, 1352/1518
SPECintRate92, 1122/1295 SPECfpRate92
Bus: SBus
Memory: 256M physical
Architecture: sun4m
Notes: 16M standard in 70MHz model, 32M standard in
85MHz model. 8 SIMM slots, 8M or 32M SIMMs,
mixable except that any 32M SIMMs must be in
slots before any 8M SIMMs. Code name "Aurora".
Uses SCA connectors (see Misc Q&A #29) for
internal SCSI drives. Socketed CPU chip.
SPARCserver 5
Notes: SPARCstation 5 without monitor/framebuffer.
SPARCserver 20
Notes: SPARCstation 20 without monitor/framebuffer.
SPARCstation 20M
Processor(s): SuperSPARC @ 50MHz, 86.1 MIPS
Bus: SBus, MBus
Memory: 512M physical, 32K off-chip cache
Notes: 32M standard. 1.44M 3.5" floppy.
SPARCstation 20/xx
Processor(s): SuperSPARC @ 50 or 60MHz, see below for SPEC
Bus: SBus and Mbus; SBus for models 50 and 61 (and
possibly others?) @ 25MHz/64bits
Memory: 512M physical; 1M off-chip cache for model 61,
2M off-chip cache for model 612, 4M off-chip
cache for model 514, other models unknown
Architecture: sun4m
Notes: 1.44M 3.5" floppy. 32M standard all models. Two
CPUs in models 502 and 612; four CPUs in model
514. 50MHz for models 50, 502, 51, and 514;
60MHz for models 61 and 612. Code name "Kodiak".
Uses SCA connectors (see Misc Q&A #29) for
internal SCSI drives. 16, 32, or 64M 60ns SIMMs.
Some models (514, others?) use double-width CPU
modules that block SBus slots.
model MHz SPECint92 SPECfp92 SPECint SPECfp
----- --- --------- -------- -Rate92--Rate92-
20/50 50 69.2 78.3 1628 1842
20/502 50x2 2833 2995
20/51 50 73.6 84.8 1731 1995
20/514 50x4 6034 6752
20/61 60 88.9 102.8 2092 2418
20/612 60x2 3903 4645
20/71
20/712
SPARCstation 4
Processor(s): MicroSPARC II @ 70MHz
Bus: SBus, 1 slot
Architecture: sun4m
Notes: Optional 16-bit audio, onboard framebuffer.
Processor Data
--------------
SuperSPARC
Texas Instruments TMX390Z50. On-chip 20K 5-way set-associative
I-cache, physically indexed and tagged. On-chip 16K 4-way
set-associative D-cache, write-back, physically indexed and tagged.
65536 hardware contexts. FPU and SPARC Reference MMU on chip. SPARC
Reference MMU has in-memory 3-level page tables, similar to a
"de-baroqued subset" of the 68030 MMU, but with Sun-MMU-style contexts.
Code name "Viking".
"When the SuperSPARC Multi-Cache Controller is used in the Mbus
configuration, it supports either no E-cache or 1MB of E-cache. When the
MCC is used in the X[D]Bus configuration, it supports a variety of
E-cache sizes: none, 512Kb, 1Mb, or 2Mb." -- Texas Instruments
SuperSPARC User's Guide, Alpha release.
microSPARC
Texas Instruments TMX390S10. On-chip 4K I-cache. On-chip 2K D-cache.
64 hardware contexts. FPU and SPARC Reference MMU on chip. SPARC
Reference MMU has in-memory 3-level page tables, similar to a
"de-baroqued subset" of the 68030 MMU, but with Sun-MMU-style contexts.
Code name "Tsunami".
microSPARC II
Fujitsu MB86904. On-chip 16K I-cache. On-chip 8K D-cache.FPU and
SPARC Reference MMU on chip.
SF9010/MB86900
These two are the same chip; Fujitsu simply renamed it. The FPC
portion was later given the separate designation MB86910 (?).
ROSS RT601/Cypress CY7C601
These two are the same chip, renamed when Cypress sold ROSS
Technology to Fujitsu. No on-chip cache.
ROSS RT602/Cypress CY7C602
These two are the same chip, renamed when Cypress sold ROSS
Technology to Fujitsu.
ROSS RT605/Cypress CY7C605
These two are the same chip, renamed when Cypress sold ROSS
Technology to Fujitsu. 64K unified cache which can run in either
write-through or write-back mode; SunOS/Solaris uses write-back. SPARC
Reference MMU with 4096 contexts.
hyperSPARC
ROSS RT620 IU/FPU and ROSS RT625 MMU/cache controller. On-chip 8K
direct-mapped I-cache, 128K or 256K external (?) unified cache which can
run in write-through or write-back mode; SunOS/Solaris uses write-back.
SPARC Reference MMU with 4096 contexts. Code name "Pinnacle".
END OF PART I OF THE SUN HARDWARE REFERENCE
Archive-name: sun-hdwr-ref/part2
Posting-Frequency: as revised
Version: $Id: part2,v 1.5 1995/05/29 22:00:44 jwbirdsa Exp $
THE SUN HARDWARE REFERENCE
compiled by James W. Birdsall
(jwbirdsa@picarefy.com)
PART II
=======
FAQ
FAQ
===
ROM Monitors
------------
Sun-2's sported a rather primitive monitor; with each succeeding
model line, it has become more powerful. In all models, the machine
enters the ROM monitor upon power up. The monitor tries to boot from a
default device, which may be determined by a simple priority-ordered
search for boot devices (Sun-2) or by EEPROM settings (Sun-3 and later).
If it cannot find a boot device or the boot device is offline, it enters
command-line mode. Command-line mode may be manually invoked at any
time, including while the OS is running, by holding down L1 and then
pressing A on a Sun console, or sending BREAK if you are using a
terminal as the console. On all models, the "c" (continue) command
resumes execution at the point where the monitor was entered, so you can
recover from accidentally halting the OS. Note that if you are using a
terminal as the console, turning it off or disconnecting it is usually
interpreted as BREAK and halts the machine.
Note that the ROM monitor in a machine may or may not know about any
particular color framebuffer, depending on the revision of the ROM and
the age of the framebuffer standard. If the ROM does not know how to
detect and display on the particular color framebuffer you have
installed, it will be unable to display the normal ROM boot messages.
This does not affect OS support for the framebuffer; if you are willing
to boot blind, SunOS should find the framebuffer and start displaying on
it normally. The alternative is to get a more recent ROM or a different
framebuffer.
SUN-1
No information. The 100U used a Sun-2 CPU (the same one used in early
2/120 units), so it had a Sun-2 ROM monitor.
SUN-2
The ROM monitor in at least the 2/120 and 2/170 (and probably all
other Sun-2 models) is capable of booting and performing some memory and
register operations, but not much more. There is no online help or
diagnostics.
The boot command is of the form "b dd(x,y,z) args" where "dd" is a
device string, "x" is the controller number, "y" is the unit number (?),
"z" is the partition number, and "args" are optional arguments to the
kernel. "dd" may be sd (SCSI disk), st (SCSI tape), xy (Xylogics SMD
controller), ie (Sun Ethernet board), or ec (3Com Ethernet board), and
probably others (mt?). For example, to boot from the first partition on
the first SCSI disk on the first SCSI controller (a common
configuration), the command would be "b sd(0,0,0)". To boot from the
first partition on the second SMD disk on the first SMD controller (a
configuration I have), the command would be "b xy(0,1,0)". To boot from
the fourth file on the first SCSI tape drive on the first SCSI
controller (booting from the n'th file may be required during OS
installation), the command would be "b st(0,0,3)".
Note that the ROM monitor makes certain assumptions about SCSI IDs --
the tape drive is actually at SCSI ID 4, but is referred to as tape unit
0. By default ("b"), the ROM monitor tries to boot from (0,0,0) on the
highest-priority bootable device that it can find in the machine's
slots; the priority order is xy, sd, and ie/ec (don't know which has
priority over the other). It never boots from tape by default. There may
be other bootable devices, but I have never seen them.
Also note that for at least some versions of SunOS, "args" is not
actually passed to the kernel. The "b" command reads a tiny bootstrap
from the indicated device. The bootstrap then automatically continues
the boot from the same device, ignoring "args". The only way I have
found to actually pass arguments such as the single-user flag (-s) to
the kernel is to use the bootstrap program on the OS tapes, which gives
a prompt rather than continuing automatically. At that prompt, entering
the device information followed by the arguments (e.g. "xy(0,1,0) -s")
will actually get the arguments passed to the kernel.
SUN-3
The Sun-3 ROM monitor is much more sophisticated. Entering "?" will
produce a list of commands with brief explanations and syntax. The ROM
contains diagnostics sufficient for a preliminary checkout of a machine
for which you do not have a boot device. Syntax of the boot command is
largely the same as for Sun-2's, with a few differences: the default
boot device is determined by the EEPROM settings rather than a hardware
search; on machines with a Lance Ethernet chip rather than Intel, the
Ethernet device is le rather than ie; and "args" is passed to the kernel
correctly.
SUN-386i
No information.
SUN-4
The Sun-4 ROM monitor is vastly more sophisticated than even the
Sun-3 version. It has two different command-line modes. The old mode, in
the style of earlier monitors, can do exactly three things: boot (using
the old-style syntax), continue execution, or switch to new command-line
mode.
New mode uses "ok" for a prompt. Help may be obtained by typing
"help". It has a built-in command-line editor, and (at least in newer
versions) a Forth interpreter (I haven't seen any sign of one on my SLC
but I wouldn't know how to look, either). You can boot either using
the old-style syntax or by specifying a type of device ("boot disk",
"boot tape", etc.). EEPROM configuration is through "printenv" and
"setenv", which use names rather than addresses. Good help is available
for most commands, and there are a lot of commands, encompassing all the
functionality available in earlier monitors and adding helpful new
features, such as "probe-scsi", which searches the SCSI bus and prints
out the ID, LUN, device type, and identification string for anything it
finds.
Using a Terminal as Console
---------------------------
Every Sun model has the ability to use a serial terminal as a
console, instead of a Sun framebuffer and keyboard. In general, machines
which have a removeable framebuffer (on a separate board rather than
built into the CPU board/motherboard) require that the framebuffer be
removed; the ROM monitor notes the absence of a framebuffer and sends
output to the first serial port on the CPU board (usually labelled
ttya), and the OS does the same when booted. Machines which do not have
a removeable framebuffer may switch to terminal mode when the keyboard
is not connected, or may require that the console designator in the
EEPROM be changed.
The Sun 2/120 and 2/170 have an unusual configuration: the keyboard
and mouse connect to the framebuffer board rather than the CPU. If the
framebuffer board is removed, all input and output goes to ttya, as
might be expected. If a framebuffer is present but no keyboard is
connected, output goes to the framebuffer, but input comes from ttya.
Terminals should be set for 9600 bps, 8 data bits, one stop bit, and
no parity. The Sun 3/260 and 3/280 support the usual connection on ttya,
but can also support a console terminal at 1200 bps on the second serial
port on the CPU board, ttyb.
The equivalent of L1-A (halt machine, drop to ROM monitor) from a
terminal console is BREAK. Unfortunately, turning off the terminal or
disconnecting it is usually interpreted as a BREAK and halts the
machine. Thus, it is not easily possible to use one terminal with many
machines via a switchbox.
Memory Display On Startup
-------------------------
One of the points which causes much confusion is the startup display
of how much memory is installed versus how much is being tested.
As with most subjects, little is known about what the Sun-1's
displayed, except the 100U which used a Sun-2 CPU.
The Sun 2/120, 2/170, and probably all other Sun-2 models simply
display the amount of memory installed. If the ROM monitor sees the
memory, SunOS should see it as well, and if the ROM monitor does not see
it, SunOS is most unlikely to see it either. All memory is tested, but
there are no displays to that effect unless an error is found. (Note
that installing memory boards set to overlapping address ranges causes
errors.)
With the Sun-3's, the ability to set how much memory would be tested
on startup was added; it is stored in the EEPROM along with a variety of
other settings. The total amount of memory installed is displayed, on
one of the first lines printed (in the same area as ROM revision, serial
number, etc.), but the line stating how much memory is being tested is
much more conspicuous. The amount of memory tested is not automatically
increased when more memory is installed, which frequently leads to dismay
by the installer when the machine apparently does not recognize the
memory just installed. Sun-4's behave the same way.
SunOS does not care how much memory was tested. It will use however
much is installed. As with the Sun-2's, if the ROM monitor sees the
memory, SunOS should see it as well, and if the ROM monitor does not see
it, SunOS is most unlikely to see it either.
Miscellaneous Questions and Answers
-----------------------------------
1) I can't get anything out of the onboard SX video port on my
SPARCstation 20.
2) Why doesn't my old SBus card fit the slot in my newer machine, or
vice versa?
3) My IDPROM just died. What can I do?
4) Where can I get information about the IDPROM/NVRAM?
5) Why doesn't my new monochrome monitor work with older monochrome
framebuffers (especially the GX), or vice versa?
5a) My machine won't boot with the monochrome monitor connected. What?
6) There is a battery on my VME SCSI host adapter board. What's it for?
7) Can I run my old, slow SCSI drives on a new machine with fast SCSI?
8) Can I use a type-4 keyboard on a Sun-3 that normally takes a type-3
keyboard?
9) I have a VME-based CPU but not the matching chassis. Can I put it in
some other Sun VME chassis?
10) What's the situation with the 4/6xx and Solaris 1.x/2.x?
11) Can I use a non-Sun CD-ROM drive? Will I be able to boot from it?
12) Can I use a Sun CD-ROM drive on some other computer?
13) What's the maximum DVMA burst size for various SBus machines?
14) How do I put SIMMs into a 3/80? SPARCstation 1/1+/2? IPX? 4/110? SLC?
15) Can I put 4M SIMMs in my 3/80?
16) Can I put two 36MHz MBus modules in my SPARCstation 10/30?
16a)What are the limitations on mixing MBus modules in a single machine?
17) My Sun doesn't like 3-chip SIMMs.
18) How do I switch between the built-in thin Ethernet (BNC) transceiver
and the AUI port on a 4/110?
19) My SPARCstation 1+ says "The SCSI bus is hung. Perhaps an external
device is turned off." when I try to boot, or it locks up completely
after displaying the banner. What do I do?
20) My SPARCstation IPC chokes with "panic: mmp_getpmg" when booting.
What do I do?
21) I have some old SMD drives and controllers and/or a 9-track tape
drive. Can I still use them with newer machines and OS versions?
22) My Sun-3 won't boot from a SCSI disk, but when I hook the disk up
to another machine or boot from another disk, it works fine. What?
22a)My Sun-4 won't boot from a SCSI disk, but...
23) I'm getting "timeout" and "disk not responding to selection" errors
with a brand-new SCSI disk.
24) I have a SunOS CD-ROM with sun3 and/or sun3x versions of the OS on
it. Can I boot my Sun-3 from this CD-ROM?
25) Can I move a HOSTID ROM between machines?
26) I have a SunPC Accelerator card with an Intel 486DX on it. Can I use
one of the DX2/DX4 replacement chips?
27) Can I set the stock serial ports to rates higher than 38400?
28) Can I get an ergonomic keyboard for my Sun? A trackball?
29) What's this 80-pin SCSI connector?
1) I can't get anything out of the onboard SX video port on my
SPARCstation 20.
To use the onboard SX video, you need a VSIMM. This is an
extra-long SIMM that sits in one of the two dual-ported memory
slots. If you do not have a VSIMM, the onboard SX video will not
work. If you did not buy the machine in an SX configuration, it
did not come with a VSIMM. You can order one separately to
enable the onboard SX video.
2) Why doesn't my old SBus card fit the slot in my newer machine, or
vice versa?
From Chuck Narad:
In SBus rev A, the cards were designed to snap into place in the
SS1 enclosure. Later, before the spec went big time (before the
IEEE standard), we decided to make SBus fit into other
environments such as VME card spacing (as was done on the
600MP). For reasons of card pitch and RFI compliance the
backplate needed to be shorter, since the originators of the
spec hadn't thought about how to do this; for SS1/SS2
compatibility the snap-in 'ears' needed to be maintained. We
ended up with a 2-piece backplate where the 'ears' were a
removable part, and the screw-holes could be used to mount the
card in systems that did not use the ears.
This decision took over a year and cost thousands of lives :-)
This two-piece backplate was finalized quite a while ago, and
made it into SBus rev B.0. Unfortunately many third-party
vendors continued to make older, rev-A backplates for a couple
years after the change was announced and broadcast in such
places as the SBus spec, the SBus bulletin, newsgroups, etc.
Also unfortunately, there was a significant number of old-style
cards shipped by Sun by that time; the hope was that few
customers actually moved cards from one system to another, and
the volumes of new cards swamped the volumes of old cards
quickly. The theory was that all bus standards go through a
'shake-down cruise' in their first incarnations, and repairs to
early decisions sometimes leave incompatibilities with older
parts (examples include VME, SCSI, Multibus... you get the
picture). SBus ended up being used in a much wider range of
machines than it was originally intended for.
Later, the mechanical team on the SS10 decided to take advantage
of the removable ears for various reasons, so in that enclosure
also the older cards won't fit.
Now the good news; as long as you don't care about minor RFI
leakeage, you can just cut off the ears on the old card with a
pair of diagonal cutters, and the card will fit into the slot
fine, you just can't use screws to secure it.
3) My IDPROM just died. What can I do?
4) Where can I get information about the IDPROM/NVRAM?
Get eeprom-nvram.faq and nvram.faq from
ftp.netcom.com:/pub/he/henderso.
5) Why doesn't my new monochrome monitor work with older monochrome
framebuffers (especially the GX), or vice versa?
5a) My machine won't boot with the monochrome monitor connected. What?
Older monochrome framebuffers and monitors used a 66Hz vertical
refresh rate. Newer units use a 76Hz vertical refresh rate. The
GX framebuffers straddle the two: the dual-slot version does not
support 76Hz vertical refresh, but the single-slot version does
(except possibly for very early versions). The most common
problem is that the machine won't boot with the monitor
connected, but boots and displays properly if the monitor is
connected about sixty seconds after power-up.
An additional gotcha is that older monochrome monitors (up
through about the SPARCstation 1) used a digital signal with ECL
levels and a DB9 connector. Since then, monochrome
configurations have usually been grayscale monitors connected to
a monochrome framebuffer with analog outputs and a 13W3
connector.
6) There is a battery on my VME SCSI host adapter board. What's it for?
It powers a time-of-day clock chip which is not used by Suns.
7) Can I run my old, slow SCSI drives on a new machine with fast SCSI?
Yes. You may get a lot of SCSI errors. While the SCSI controller
is compatible with the older drives, the cables and termination
are frequently a problem. Cables should be short and of high
quality, and the termination active. Olders Sun external
enclosures don't have suitable cabling and termination.
8) Can I use a type-4 or type-5 keyboard on a Sun-3 that normally takes
a type-3 keyboard?
Yes. The 4-to-3 adapter is sold by Sun refurbisher Apex and
possibly others; Sun-3's manufactured toward the end came new
with type-4 keyboards and the appropriate adapter. It is also
reported that a type-5 can be connected to a machine expecting a
type-3 with an appropriate adapter (possibly the same one?).
9) I have a VME-based CPU but not the matching chassis. Can I put it in
some other Sun VME chassis?
In general, yes. CPU boards which have onboard memory can be put
in just about any chassis, including the 3/50 and 3/60 chassis,
which don't have a full set of VME connectors -- they only have
the power connector! CPU boards which require external memory
boards (such as the 3/2xx) obviously require a chassis with at
least two slots and a full set of VME connectors.
With some chassis, there may be problems with lacking voltages.
One individual reports that a 4/3xx CPU works in a 3/60 chassis,
except the lack of -12VDC means "we can't use a console on it."
It is also possible to make multiple CPUs share a VME chassis.
This is trickier. It requires isolating sections of the bus, and
being sure not to stomp on specialized slots used for memory or
SCSI boards.
Since 3/50 and 3/60 motherboards only use the VME bus for power
they can share a VME chassis with anything, in any slot.
10) What's the situation with the 4/6xx and Solaris 1.x/2.x?
From Greg Elkinbard:
SuperSPARC Rev 3.1, 3.2, 3.3 require patches:
Solaris 1.1 - 101508, 101509
Solaris 1.1.1_U1 - 101726, 101408
Solaris 2.3 - 101318, 101406
If you have Rev 3.5 or Rev 5.x then you should disable 101509,
101408, 101406
Rev 3.5 is compatible with Solaris 1.1, 1.1.1B, 2.3 do not use
it with 1.1.1A (4.1.3_U1)
Rev 5.x is compatible with Solaris 1.1, 1.1.1A, 1.1.1B, 2.3
Galaxy (4/6xx) compatible processors and rev:
SM41 - 501-2258, 501-2270, 501-2359 - Rev 2.x
SM51 - 501-2352, 501-2360, 501-2361, 501-2387 - rev 3.x
SM51 - 501-2607, 501-2562-01, 501-2562-02, - rev 3.5
SM51 - 501-2617, 501-2707 - rev 5.x
SM520 - 501-2444 - rev 3.x
SM521 - 501-2445 - rev 3.x
Field service manual states that minimum OS for SM520 and SM521
is 2.3, this leads me to believe that 1.x will not support
Viking MP reliably (i.e use it at your own risk)
Boot prom 2.8v2 or greater is required for SM41.
Boot prom 2.10 or greater is required for SM51.
11) Can I use a non-Sun CD-ROM drive? Will I be able to boot from it?
12) Can I use a Sun CD-ROM drive on some other computer?
The "CD-ROMs on Sun Hardware FAQ" is posted periodically to
comp.sys.sun.hardware and alt.cdrom by Kyle Downey
(96kfd@williams.edu). It may also be archived at rtfm.mit.edu.
In general, the answer is "maybe, and possibly only after
modifying the drive or the kernel."
13) What's the maximum DVMA burst size for various SBus machines?
This is a very complicated question. The SBus controller is
probably capable of handling any burst size; the limiting factor is
usually the slave interface to main memory. The SPARCstation 2
and microSPARC-based machines were supposedly limited to 16-byte
bursts (one individual reports that, using an SBus card with
programmable burst sizes, he was able to successfully use
64-byte bursts to main memory). MicroSPARC II-based machines and
MBus machines supposedly could do 32-byte bursts, and the
SPARCserver 1000 and SPARCcenter 2000 supposedly can do full
64-byte bursts. The SPARCstation 20 models with 64-bit SBuses
can do 128-byte bursts, although there are not many 64-bit SBus
cards to take advantage of it yet.
14) How do I put SIMMs into a 3/80? SPARCstation 1/1+/2? IPX? 4/110?
SPARCstation 1/1+:
Nearest disk connectors
_______ _______
| | | |
| 0 | | 1 |
| | | |
|_______| |_______|
_______ _______
| | | |
| 2 | | 3 |
| | | |
|_______| |_______|
Nearest SBus connectors
3/80, SPARCstation 2:
The sixteen SIMM slots are arranged in four groups of four.
Electrically, there are four "banks," each of which is composed
of one slot from each group:
Back of machine (nearest SBus connectors)
------------------ 0 0 --------------------
------------------ 1 1 --------------------
------------------ 2 2 --------------------
------------------ 3 3 --------------------
----------------- 0 0 --------------------
----------------- 1 1 --------------------
----------------- 2 2 --------------------
----------------- 3 3 --------------------
Front of machine (nearest disk connectors)
Banks must be filled in order (0 through 3), and SIMM sizes (1M
or 4M) must not be mixed with in a bank.
IPX:
------------------ 0
------------------ 1
------------------ 2
------------------ 3
Nearest SBus connectors
SLC:
The SIMM slots are labelled 1 through 4, and must be filled in
the order 1, 3, 2, 4.
4/110:
From the original pseudo-FAQ:
Nearest VME connectors
_______ _______
| | | |
| 3 | | 4 | Banks have eight SIMM slots
| | | | each.
|_______| |_______| J400
_______ _______ Note: when using mixed SIMMs
| | | | J1300 to get 20M, the 1M SIMMs must
| 1 | | 2 | go in banks 2 and 4 or the
| | | | J1400 machine won't boot.
|_______| |_______|
J101 1-2
J100 1-2
3-4
Total memory: 8M 16M 20M 32M
SIMM size: 256K 1M 256K/1M 1M
J100
1-2 JU UN JU UN
3-4 UN JU UN JU
J400
1-2 UN JU UN JU
3-4 JU UN UN JU
5-6 JU JU JU Un
J1300
same JU UN UN JU
different UN JU JU UN
256K JU UN JU UN
1M UN JU UN JU
2M UN UN UN UN
<32M JU JU JU UN
32M UN UN UN JU
unused UN UN UN UN
J1400
same JU UN UN JU
different UN JU JU UN
256K JU UN UN UN
1M UN JU JU JU
2M UN UN UN UN
<32M JU JU JU UN
32M UN UN UN JU
unused UN UN UN UN
NOTE THAT SIMMs MUST BE STATIC COLUMN TYPES, 120ns or faster.
15) Can I put 4M SIMMs in my 3/80?
If you have version 3.0.2 or better of the boot ROMs, yes. The
version is displayed in the startup messages immediately after
powering the machine on. You can install up to 40M of memory by
putting 4M 80ns SIMMs in banks 0 and 1 or 2 (sorry, not clear
which it should be), and filling the remaining two banks with 1M
80ns SIMMs.
Note that ROM version 3.0.2 has known problems with booting from
QIC-150 tape drives.
16) Can I put two 36MHz MBus modules in my SPARCstation 10/30?
16a)What are the limitations on mixing MBus modules in a single machine?
From John DiMarco:
There is no intrinsic technical reason why a 36MHz Mbus can't
support two modules. While it is true that you cannot normally
configure a system to support two M30 modules, the reason for
this is that early revisions of the SuperSPARC processor
contained bugs that prevented MP configurations from working
properly without the 1M external cache. Most if not all M20
(33MHz) and M30 (36MHz) modules, and many M40 (40MHz) modules
had this problem.
In general, if you want to mix and match modules (which is
unsupported but probably works for a number of configurations),
you'll need to make sure that the interface speeds of all
modules are matched.
The modules without SuperCACHE run at the MBus speed (or the
MBus runs at their speed?), so modules without SuperCACHE cannot
be mixed. Nor can they be mixed with modules with SuperCACHE.
Modules with SuperCACHE can be mixed, but may not be advisable.
The 41 and 51 modules both require a 40MHz MBus (SS10 or SS20
switched to slow board speed), but the 61 can use a 50MHz MBus
as well. Mixing a 61 with slower modules may slow down the 61 as
well.
Another consideration is that slower modules are usually older
SuperSPARC steppings that may require more drastic workarounds
and hence slow down newer, faster processors -- assuming it
works at all.
17) My Sun doesn't like 3-chip SIMMs.
From John O'Connor:
3-chip SIMMs have two 4Mbit chips (organised as 1M * 4bits) plus
one 1Mbit chip as opposed to the nine 1Mbit chips on the 9-chip
SIMMS. The difference arises from the fact that the 4Mbit chips
require more addresses to be read in the refresh cycles, so you
get unreliable operation of 3-chip SIMMs in systems that don't
provide enough refresh cycles.
18) How do I switch between the built-in thin Ethernet (BNC) transceiver
and the AUI port on a 4/110?
Jumper J1800 on the motherboard controls this. Jump it to use
the AUI port.
19) My SPARCstation 1+ says "The SCSI bus is hung. Perhaps an external
device is turned off." when I try to boot, or it locks up completely
after displaying the banner. What do I do?
Check the SCSI termination fuse, located on the motherboard near
the external SCSI connector. The fuse looks like a small
cylinder that is usually clear or totally black with a black top
and white writing. It is in a socket and is easy to remove. If
adding an external device that powers its own terminator makes
the machine work, the problem is definitely the termination
fuse.
It may also be necessary to change the settings on the disk
drive, to spin up on command only and not by default.
20) My SPARCstation IPC chokes with "panic: mmp_getpmg" when booting.
What do I do?
This may have to do with mixed 1M and 4M SIMMs. Make sure the 4M
SIMMs are in the first memory bank. This problem was supposed to
be solved after SunOS 4.1.1.
Alain Brossard reports that a few very old IPC's experience the
this failure when booting over the network, and the following
incantation at the ROM monitor prompt fixed the problem:
ok 7f fff0.0000 smap!
ok boot net
21) I have some old SMD drives and controllers and/or a 9-track tape
drive. Can I still use them with newer machines and OS versions?
SMD support is limited to VME-based machines, of which the 4/6xx
is the most recent. Stock SunOS and Solaris support these
devices on the sun4 architecture (all VME-based sun-4's except
the 4/6xx) but not on the sun4m architecture (the 4/6xx). It is
available for the 4/6xx as a special package, however.
22) My Sun-3 won't boot from a SCSI disk, but when I hook the disk up
to another machine or boot from another disk, it works fine. What?
22a)My Sun-4 won't boot from a SCSI disk, but...
SunOS can use SCSI disks with SCSI parity turned on. The boot
ROMs can't boot from them, however -- SCSI parity must be turned
off to boot. Check the jumpers on the drive or the SCSI
converter card (Emulex MD-21, Adaptec ACB4000, etc.).
For a Sun-4, the problem may be that the drive is initiating
synchronous negotiation. The boot ROMs can't cope with this;
they expect the kernel to initiate synchronous negotiation after
booting. Check the jumpers on the drive.
23) I'm getting "timeout" and "disk not responding to selection" errors
with a brand-new SCSI disk.
Check the temperature in the disk enclosure! Many newer SCSI
drives (especially Seagate, apparently) have the ability to spin
down and otherwise quiesce when the drive gets too hot. When the
drive it accessed, it will spin up again, but this takes some
time and the Sun usually complains before the disk can respond.
24) I have a SunOS CD-ROM with sun3 and/or sun3x versions of the OS on
it. Can I boot my Sun-3 from this CD-ROM?
Supposedly ROM versions 3.0.1 and above can boot from a CD-ROM.
Make sure that you're trying to boot from the correct partition
(these CD-ROMs usually have bootable partitions for a variety of
architectures). Try booting from "sd(0,30,x)" where 'x' is a
partition number.
25) Can I move a HOSTID ROM between machines?
Only if the machines are the same model, since part of the
hostid identifies the machine type. Also note that installing
one backwards will generally destroy it.
26) I have a SunPC Accelerator card with an Intel 486DX on it. Can I use
one of the DX2/DX4 replacement chips?
Only 5V chips can be used. The SBus provides sufficient power,
but cooling may be a problem. Adding a heat sink and microfan to
the new chip will probably solve that problem, but may interfere
with the next SBus slot.
27) Can I set the stock serial ports to rates higher than 38400?
Yes, but you have to hack the kernel in order to do it.
Furthermore, the standard ZS hardware is not capable of
supporting the normal bit rates (57600 and 115200) unless you
can supply an external clock and run them in synchronous mode.
The only higher internally-generated rates are 51200 (pretty
useless) and 76800, which a few modems can be set to handle.
Also, the 76800 rate will result in frequent overruns unless it
is being used for pure output, such as to a printer.
28) Can I get an ergonomic keyboard for my Sun? A trackball?
Ashok Desai (ashokd@Eng.Sun.COM) maintains an ergonomic keyboard
FAQ. Ren Tescher (ren@rap.ucar.EDU) maintains an unofficial
trackball FAQ. See also the "Alternatives" section under MICE in
this reference.
29) What's this 80-pin SCSI connector?
It is an SCA connector, as defined by the Small Form Factor
Committee, which provides a wide single-ended SCSI connection
and power (+12V, +5V). The standard number is SFF8015 23A.
Facts in Search of a Home
-------------------------
+ Sun 3/50's and 3/60's often used the Matsushita ETX-593C101M power
supply, capable of supplying 100W (15A @ 5V, 2A @ -5V, and 1.3A @
12V). The 3/75 had a 150W power supply. See pinouts below.
+ Sun 4/1xx CPU boards require 69.5W (13.8A @ 5V, and 0.1A @ -5V).
+ Mbus modules for the SPARCstation 10/514 (two 50MHz CPUs and
corresponding 1M caches) are physically so large that they each cover
two SBus slots. The SBus slots are not actually used, just
inaccessible.
+ The Adaptec 5500 card was "similar in function to the 4000", which was
a SCSI-MFM converter used for disks, mostly in Sun-2's. It had a
number of jumpers:
A-B hard reset
SCSI bus reset initiates hard reset of card when jumped.
C-D reserved
E-F hard-sectored drive on LUN0
G-H hard-sectored drive on LUN1
J-K reserved
DIAG diagnostics
Continuously repeat selftest when jumped.
Par SCSI parity
Enable SCSI bus parity checking when jumped. Parity is always
generated.
A4 SCSI ID MSB
A2 SCSI ID
A1 SCSI ID LSB
+ The internal SCSI hard drive in any SPARCstation should NOT be
terminated.
+ The Sun HSI/S interface board (501-1725) has four high-speed
synchronous serial ports with an aggregate bandwidth of 4-5Mbits per
second. If only two ports are used, full T1 speeds can be used on
both. SunExpress says it supports X.25, SNA, Frame Relay, PPP, T1, and
CEPT.
+ The Adaptec ACB4000 MFM-SCSI adapter board and the Emulex MD21
ESDI-SCSI adapter board may not coexist well on the same SCSI bus. One
individual reports getting SCSI disconnect errors from the MD21 when
attempting to run both on the SCSI bus of a 3/60 running SunOS 3.5.
+ Shorting the J900 jumper on a 4/110 motherboard erases the EEPROM.
+ The last version of the boot ROM for the 3/60 was 3.0.1. It supports
cg6 color framebuffers, and is supposed to support cg8 color
framebuffers as well.
Miscellaneous Pinouts
---------------------
+ DB9 serial ports on 3/80, 4/3xx, others?
1 DCD 4 DTR 7 RTS
2 RxD 5 GND 8 CTS
3 TxD 6 DSR 9 unused
+ parallel port on 3/80
1 STBN 9 D7 17 SLCN
2 D0 (data 0) 10 ACK 18 GND
3 D1 11 BUSY 19 GND
4 D2 12 PAPE 20 GND
5 D3 13 SLCT 21 GND
6 D4 14 AFXN 22 GND
7 D5 15 ERRN 23 GND
8 D6 16 ININ 24 GND
25 GND
+ DIN-8 serial port on SPARCstation IPC, others?
-------
/ === \
/ \
/ 6 7 8 \
| |
| 3 4 5 |
\ /
\ 1 2 /
\_______/
1 DTR 4 GND 7 DCD
2 CTS 5 RxD 8 RxC (receive clock)
3 TxD 6 RTS
+ DB25 A/B serial ports on SPARCstation SLC, ELC, others?
1 unused 9 unused 17 A-RxC (receive clock)
2 A-TxD 10 unused 18 unused
3 A-RxD 11 unused 19 B-RTS
4 A-RTS 12 B-DCD 20 A-DTR
5 A-CTS 13 B-CTS 21 unused
6 A-DSR 14 B-TxD 22 unused
7 A&B-GND 15 A-TxC in (?) 23 unused
8 A-DCD 16 B-RxD 24 A-TxC out (transmit clock out)
25 unused
Note that only port A has full modem control.
+ DB25 A/B serial ports on SPARCstation LX, SPARCclassic, and
SPARCstation 10, others?
As for the SLC/ELC, but with additional signals for the B port:
11 B-DTR 18 B-TxC in 25 B-TxC out
+ 50-pin motherboard card-edge test connector on sun4c's
1 eject 18 direction 35 unused
2 unused 19 GND 36 VCC (+5V)
3 GND 20 step 37 ledout-
4 unused 21 GND 38 VCC (+5V)
5 GND 22 wrdata 39 unused
6 unused 23 GND 40 VCC (+5V)
7 GND 24 wrgate 41 por-
8 index 25 GND 42 VCC (+5V)
9 GND 26 trk00 43 VDD (+12V)
10 ds0 27 GND 44 VCC (+5V)
11 GND 28 wrprot 45 VBB (-12V)
12 unused 29 GND 46 VCC (+5V)
13 GND 30 rddata 47 unused
14 unused 31 GND 48 VCC (+5V)
15 GND 32 hdsel 49 VCC (+5V)
16 motor_on 33 GND 50 VCC (+5V)
17 GND 34 unused
Pins 36, 38, 40, 42, 44, 46, and 48-50 (VCC, +5V) are the same as
pins 1, 2, 7, and 8 on the power connector.
Pin 37 (ledout-) is the same as pin 2 on the speaker connector.
Pin 41 (por-) is Power-On Reset, like the Power Good signal on PC
power supplies, and the same as pin 6 on the power connector.
Pin 43 (VDD, +12V) is the same as pins 5 and 11 on the power
connector.
Pin 45 (VBB, -12V) is the same as pin 12 on the power connector.
+ Power supply connector on (PS?) chassis for 3/50, 3/60, 3/75
1 -5V white 7 GND black
2 Pwr OK brown 8 GND black
3 +12V blue 9 +5V red
4 GND black 10 +5V red
5 GND black 11 +5V red
6 GND black 12 +5V red
SIMM Compatibility Chart
------------------------
+ SPARCstation 1, 1+, 2, and IPC
1M x 9 30-pin 9-chip IBM-compatible SIMMs. 100ns or faster for the 1,
1+, and IPC; 80ns or faster for the 2. The 2 and IPC can also take 4M
SIMMs.
+ SPARCstation IPX, ELC (and SLC?)
4M or 16M x 33 72-pin 80ns SIMMs.
+ SPARCstation SLC
4M 72-pin SIMMs, compatible with the HP IIIsi printer. Will NOT take
16M SIMMs.
+ SPARCclassic; SPARCstation LX
4M or 16M 72-pin 60ns SIMMS, installed in pairs only.
+ SPARCstation 10, 20
SS10: 16M or 64M 70ns SIMMs. Can also use SIMMs of appropriate sizes
from SS20.
SS20: 16M, 32M, or 64M 60ns SIMMs. The 16M and 64M SIMMs can also be
used in SS10s, but not the 32M SIMMs.
+ SPARCstation 5
8M or 32M SIMMs.
+ SPARCserver 1000, SPARCcenter 2000
END OF PART II OF THE SUN HARDWARE REFERENCE
Archive-name: sun-hdwr-ref/part3
Posting-Frequency: as revised
Version: $Id: part3,v 1.8 1995/05/29 22:17:28 jwbirdsa Exp $
THE SUN HARDWARE REFERENCE
compiled by James W. Birdsall
(jwbirdsa@picarefy.com)
PART III
========
BOARDS
BOARDS
======
This section covers the various circuit boards which make up or are
used with Sun systems. This includes: CPU boards/motherboards; memory
boards; video boards and video accelerator boards; SCSI controller
boards; non-SCSI disk controller boards such as SMD and IPI controllers
and boards used to connect non-SCSI disks to SCSI busses; non-SCSI tape
controller boards such as those used with 9-track tapes; Ethernet boards
(boards for systems where Ethernet is not integrated into the
CPU/motherboard and boards providing second, third, etc. network
connections for systems with integrated Ethernet) and boards for other
networks such as Token-Ring and FDDI; communication boards, including
serial, parallel, synchronous, and X.25 boards; floating-point and other
system accelerator boards; cardcage backplanes; and boards not covered
by the categories above. The first subsection is a brief listing of
boards described in the rest of this section, sorted by bus type
(Multibus, VME, P4, ISA, SBus, MBus, XDBus, SCSI, None).
Crossreference by bus
---------------------
MULTIBUS
370-0502 ? 0167 Computer Products Corporation TAPEMASTER
370-1012 Xylogics 450 SMD controller
370-1021 Sky Floating Point Processor
501-0288 3COM 3C400 Ethernet
501-0289 color video
501-1003 monochrome video/keyboard/mouse TTL only
501-1004 Sun-2 Ethernet
501-1006 Sun-2 SCSI/serial
501-1007 100U, 2/120, 2/170 CPU
501-1013 1M RAM
501-1048 1M RAM
501-1051 2/120, 2/170 CPU
501-1052 monochrome video/keyboard/mouse ECL/TTL
501-1232 4M RAM
xxx-xxxx Systech MTI-800A/1600A Multiple Terminal Interface
xxx-xxxx Systech VPC-2200 Versatec Printer/Plotter controller
VME
501-1014 Sun-2 color framebuffer
501-1045 "Sun-2" SCSI host adapter, 6U
501-1055 GP graphics processor (accelerator)
501-1058 GB graphics buffer (used with GP)
501-1089 cg3 color framebuffer
501-1100 3/2xx CPU
501-1102 3/2xx 8M memory
501-1116 cg3 color framebuffer
501-1131 3/1xx 2M memory
501-1132 3/1xx 4M memory
501-1138 "Sun-2" SCSI host adapter, external
501-1139 GP+ graphics processor (accelerator)
501-1149 "Sun-2" SCSI host adapter, internal
501-1167 "Sun-2" SCSI host adapter, internal/external
501-1170 "Sun-3" SCSI host adapter, internal
501-1206 3/2xx CPU
501-1217 "Sun-3" SCSI host adapter, external
501-1236 "Sun-3" SCSI host adapter, 6U
501-1267 cg5 color framebuffer
501-1268 GP2 graphics processor (accelerator)
501-1319 cg3 color framebuffer
501-1383 TAAC-1 system accelerator, POP board
501-1434 cg9 color framebuffer
501-1447 TAAC-1 system accelerator, DFB board
P4
ISA
SBUS
MBUS
XDBUS
SCSI
370-1010 Adaptec ACB4000 SCSI-MFM controller
370-1011 Sysgen SC4000 SCSI/QIC-II controller
xxx-xxxx Emulex MT-02 SCSI/QIC-02 controller
xxx-xxxx Emulex MD21 SCSI-ESDI controller
NONE
501-1075 3/50 motherboard
501-1133 3/50 motherboard
501-1162 3/50 motherboard
501-1205 3/60 motherboard
501-1207 3/50 motherboard
501-1322 3/60 motherboard
501-1334 3/60 motherboard
501-1345 3/60 motherboard
501-1689 4/40 (SPARCstation IPC) motherboard
501-1690 4/40 (SPARCstation IPC) motherboard
501-1835 4/40 (SPARCstation IPC) motherboard
CPU boards/motherboards
-----------------------
501-1007(-04 to -08) 100U,2/120,2/170 CPU Multibus
10MHz 68010, no floating point chip, MMU, no on-board memory.
Multibus interface.
The CPU board is entirely concealed within the chassis. On one
long edge, it has Multibus card-edge connectors. On the other
long edge, from top to bottom, it has: a header connector for the
Sun-1 parallel keyboard and mouse, eight LEDs, and a 50-pin header
connector (J1) for two serial ports.
Jumper information:
J200 Crystal shunt JUMPED by default
Located by crystal at D1.
Removed for A.T.E. testing, installed for normal operation.
J400 EPROM select JUMPED by default
Located by EPROMs at D10.
1-2 selects 27128 EPROMs (default)
3-4 selects 27256 EPROMs
J700 Bus priority on serial arbitration UNJUMPED by default
Located by bus connectors.
J701 Common bus request arbiter UNJUMPED by default
Located by bus connectors.
If the CPU board is used in conjunction with a Multibus DMA
board (such as a disk or tape controller) that does NOT
support the Common Bus Request (CBRQ), the CPU board must be
configured such that it gives up the Multibus after every
Multibus cycle, by jumping J701. This also causes three
additional wait states for each Multibus access. When this
jumper is unjumped, the CPU board retains bus mastership until
a lower priority master requests it by asserting CBRQ.
Following a CBRQ, the CPU board yields mastership for at least
one cycle. Certain machine configurations (especially those
with color) will be much slower if this jumper is jumped.
J702 Enables the CCLK on P1 JUMPED by default
Located by bus connectors.
J703 Enables the BCLK on P1 JUMPED by default
Located by bus connectors.
J801 Selects +5V for the parallel mouse UNJUMPED by default
Located by J2 header connector.
Used only in 100U configurations (?).
The two serial ports on J1 are usually labelled SIO-A and SIO-B
on the back of the machine and appear as /dev/ttya and /dev/ttyb
under SunOS. The documented maximum output speed is 19200 bps.
All ports are wired DTE and are compatible with both RS-232C and
RS-423, using Zilog Z8530A dual UART chips. The pinout of J1 is:
3 TxD-A 14 DTR-A 33 DD-B
4 DB-A 15 DCD-A 34 CTS-B
5 RxD-A 22 DA-A 36 DSR-B
7 RTS-A 24 BSY-A 38 GND-B
8 DD-A 28 TxD-B 39 DTR-B
9 CTS-A 29 DB-B 40 DCD-B
11 DSR-A 30 RxD-B 47 DA-B
13 GND-A 32 RTS-B 49 BSY-B
Power requirements are +5V @ 6A.
501-1051 2/120,2/170 CPU Multibus
10MHz 68010, no floating point chip, MMU, no on-board memory.
Multibus interface.
The CPU board is entirely concealed within the chassis. On one
long edge, it has Multibus card-edge connectors. On the other
long edge, from top to bottom, it has: a header connector for the
Sun-1 parallel keyboard and mouse, eight LEDs, and a 50-pin header
connector (J1) for two serial ports.
Jumper information:
J100
Sixteen pins, hardwired. All unjumped by default.
J102
1-2 Connects -5V to P1 -5V (default)
3-4 Connects -5V to regulator
J200 Crystal shunt JUMPED by default
Removed for A.T.E. testing, installed for normal operation.
J400
1-2 selects 27128 EPROMs (default)
3-4 selects 27256 EPROMs
J700
1-2 CPU drives P1 reset (jumped by default)
3-4 P1 INT drives CPU reset (unjumped by default)
5-6 serial arbiter enable (unjumped by default)
7-8 arbiter bus config select (unjumped by default)
If the CPU board is used in conjunction with a
Multibus DMA board (such as a disk or tape controller)
that does NOT support the Common Bus Request (CBRQ),
the CPU board must be configured such that it gives up
the Multibus after every Multibus cycle, by jumping
this jumper. This also causes three additional wait
states for each Multibus access. When this jumper is
unjumped, the CPU board retains bus mastership until a
lower priority master requests it by asserting CBRQ.
Following a CBRQ, the CPU board yields mastership for
at least one cycle. Certain machine configurations
(especially those with color) will be much slower if
this jumper is jumped.
J701
1-2 CPU drives P1 BCLK (jumped by default)
3-4 CPU drives P1 CCLK (jumped by default)
J801
Not used, unjumped by default.
The two serial ports on J1 are usually labelled SIO-A and SIO-B
on the back of the machine and appear as /dev/ttya and /dev/ttyb
under SunOS. The documented maximum output speed is 19200 bps.
All ports are wired DTE and are compatible with both RS-232C and
RS-423, using Zilog Z8530A dual UART chips. The pinout of J1 is:
3 TxD-A 14 DTR-A 33 DD-B
4 DB-A 15 DCD-A 34 CTS-B
5 RxD-A 22 DA-A 36 DSR-B
7 RTS-A 24 BSY-A 38 GND-B
8 DD-A 28 TxD-B 39 DTR-B
9 CTS-A 29 DB-B 40 DCD-B
11 DSR-A 30 RxD-B 47 DA-B
13 GND-A 32 RTS-B 49 BSY-B
Power requirements are +5V @ 6A, and -5V @ 0.1A or -12V @ 0.1A.
The last two are mutually exclusive.
501-1075 3/50 motherboard
15.7MHz 68020, a socket for a 68881 floating point chip (at
15.7MHz?), Sun-3 MMU with eight hardware contexts, up to 4M of
onboard memory. No bus interfaces.
From left to right, the back edge of the board has: a female
DB15 keyboard/mouse connector; eight LEDs (bit 0 to the left); a
switch to toggle between Normal and Diagnostics modes; a BNC
thin Ethernet connector; a female DB15 AUI Ethernet connector;
two female DB25 serial port connectors (ports B and A from left
to right); a female D50 SCSI port connector; and a female DB9
monochrome video connector.
Pin 1 is usually in the upper right corner of all connectors.
Unconnected pins are not listed.
The pinout of the keyboard/mouse connector is:
1 RxD0 (keyboard) 8 GND
2 GND 9 GND
3 TxD0 (keyboard) 10 VCC
4 GND 11 VCC
5 RxD1 (mouse) 12 VCC
6 GND 14 VCC
7 TxD1 (mouse) 15 VCC
The eight LEDs are used for diagnostic purposes. In the chart
below, a "1" indicates a lit LED, and a "0" indicates an unlit
LED. The pattern is shown left to right, as it appears on the
LEDs.
Pattern Status Error
-------- ------ -----
11111111 Resetting CPU or PROMs bad
00000000 Test 0: CPU to SCC path CPU board (SCC) bad
10000000 Test 1: boot PROM Boot PROM bad
11000000 Test 3: context register CPU board (MMU) bad
00100000 Test 4: segment map RAM rd/wr CPU board (MMU) bad
10100000 Test 5: segment map RAM CPU board (MMU) bad
01100000 Test 6: page map RAM CPU board (MMU) bad
11100000 Test 7: memory data path CPU board bad
00010000 Test 8: bus error detection CPU board bad
10010000 Test 9: interrupt capability CPU board bad
01010000 Test 10: MMU read access CPU board bad
11010000 Test 11: MMU write access CPU board bad
00110000 Test 12: write to invalid page CPU board bad
10110000 Test 13: write to protected pg CPU board bad
01110000 Test 14: parity error check CPU board bad
11110000 Test 15: parity error check CPU board bad
00001000 Test 16: memory tests CPU board bad
00000001 Self-tests have found an error See below
00000010 An exception class error found See below
"Marching ones" (cycling through 10000000, 01000000, 00100000,
etc.) indicates that Unix is running OK. On power up, it cycles
through the tests in the chart above, then boots Unix. Pattern
11111111 may also mean that a SCSI device was powered up prior
to the CPU being powered up. If LED 7 (00000001) lights up while
the tests are being performed, it indicates that the test
failed. If LED 6 (00000010) lights up while the tests are being
performed, it indicates that an unexpected error (bus error,
address error, unexpected interrupt, etc.) occurred during the
test. When all tests are finished, LED 5 (00000100) starts
blinking to indicate that the ROM monitor is running and/or Unix
is booting.
If you want the machine to boot normally, set the diagnostics
switch to "NORM" (labelled "BOOT" on some early versions). If
you want extended diagnostics when you power up the system, set
the switch to the "DIAG" position. If the switch is set to
"DIAG", power-on self-test messages are sent to serial port A.
To switch between thin and AUI Ethernet, there is an
eight-position DIP switch (0618) on the motherboard just behind
the BNC and AUI connectors. To use thin Ethernet, all eight
switches must be ON. To use AUI Ethernet, all eight switches
must be OFF. Jumper J0642, which is next to DIP switch 0618,
determines the type of the transceiver, type 1 (capacitive
coupled) or type 2 (transformer coupled). To use a type 1
transceiver, jump the two pins; to use a type 2 transceiver,
unjump the pins. The pinout of the AUI Ethernet connector is:
2 E.COL+ 9 E.COL-
3 E.TxD+ 10 E.TxD-
5 E.RxD+ 12 E.RxD-
6 GND 13 +12V
The serial ports conform to both RS-232-C and RS-423 and are
wired DTE. The documented maximum speeds are 19200 bps for
output and 9600 bps for input. The pinout of the serial ports
is:
2 TxD (transmit data) 8 DCD (Data Carrier Detect)
3 RxD (receive data) 15 DB (transmit clock from DCE)
4 RTS (Request To Send) 17 DD (receive clock from DCE)
5 CTS (Clear To Send) 20 DTR (Data Terminal Ready)
6 DSR (Data Set Ready) 24 DA (transmit clock from DTE)
7 GND 25 VERR (-5V)
The DB, DD, and DA signals are not used with ordinary
asynchronous equipment such as most modems and terminals,
printers, etc.).
The pinout of the SCSI connector is:
1 GND 17 GND 34 GND
2 data bus 0 18 data parity 35 GND
3 GND 19 GND 36 busy
4 data bus 1 20 GND 37 GND
5 GND 21 GND 38 acknowledge
6 data bus 2 22 GND 39 GND
7 GND 23 GND 40 reset
8 data bus 3 24 GND 41 GND
9 GND 25 GND??? 42 message
10 data bus 4 26 ??? 43 GND
11 GND 27 GND 44 select
12 data bus 5 28 GND 45 GND
13 GND 29 GND 46 command/data
14 data bus 6 30 GND 47 GND
15 GND 31 GND 48 request
16 data bus 7 32 attention 49 GND
33 GND 50 input/output
and the pattern of the pins is:
49 46 43 .... 19 16 13 10 7 4 1
48 45 42 .... 18 15 12 9 6 3
50 47 44 41 .... 17 14 11 8 5 2
The monochrome video output levels are ECL/TTL. The pinout of
the monochrome video connector is:
1 VIDEO+ 6 VIDEO-
3 HSYNC 7 GND
4 VSYNC 8 GND
9 GND
A variety of parameters may be set in the EEPROM. Only settings
meaningful to the hardware are listed here; information used by
SunOS may be stored at other addresses.
0x18 Choose polling or selected boot device
0x00 poll -- search for SCSI disks, then
try to boot from network if none
found
0x12 boot from the selected device only
0x19-0x1D Selected boot device
first two bytes are 'sd' (0x73 0x64) to boot
from SCSI disk or 'le' (0x6C 0x65) to boot
from Ethernet
byte at 0x1B is controller number, usually 0
byte at 0x1C is unit number, usually 0
byte at 0x1D is partition number, usually 0
0x1F Set console I/O
0x00 monochrome framebuffer/keyboard
0x10 serial port A
0x11 serial port B
0x20 Choose boot display banner
0x00 Sun logo display
0x12 Display banner stored in 0x68-0xB7
0x21 Turn keyboard "click" on or off
0x00 no click
0x12 click
0x22-0x26 Specify diagnostic boot device (when NORM/DIAG
switch in DIAG position)
as 0x19-0x1D, or all zeroes to invoke ROM
monitor
0x28-0x4F Specify diagnostic boot path (when NORM/DIAG
switch in DIAG position)
ASCII codes for path and filename (?) to boot,
or all zeroes to invoke ROM monitor
0x68-0xB7 Custom banner
ASCII codes for desired banner, padded with
spaces and ending with 0x0D, 0x0A in
locations 0xB6 and 0xB7
Power requirements are +5V @ 13.5A max, -5.2V @ 0.8A max, and
+12V @ 0.5A max.
501-1100 3/2xx CPU VME
25MHz 68020, 20MHz 68881 floating point chip, Sun-3 MMU with
eight hardware contexts, no on-board memory but 64K write-back
cache, direct-mapped, virtually-indexed and virtually-tagged,
with 16-byte lines. VME interface. 256K of dual-ported video RAM
for the onboard high-resolution monochrome framebuffer.
From top to bottom, the back edge of the board has: two female
DB25 serial ports (A and B, respectively); a female DB15 AUI
Ethernet connector; a reset button; a switch to toggle between
Normal and Diagnostics modes; a female DB15 keyboard/mouse
connector; eight LEDs; and at the bottom, a female DB9 high-res
monochrome video connector.
The serial ports conform to both RS-232-C and RS-423 and are
wired DTE. The pinout of the serial ports is:
2 TxD (transmit data) 8 DCD (Data Carrier Detect)
3 RxD (receive data) 15 DB (transmit clock from DCE)
4 RTS (Request To Send) 17 DD (receive clock from DCE)
5 CTS (Clear To Send) 20 DTR (Data Terminal Ready)
6 DSR (Data Set Ready) 24 DA (transmit clock from DTE)
7 GND 25 -5V
The pinout of the AUI Ethernet connector is:
1 chassis ground 7 VCC
2 E.COL+ 9 E.COL-
3 E.TxD+ 10 E.TxD-
4 chassis ground 12 E.RxD-
5 E.RxD+ 13 +12V
6 GND
Note that VCC on pin 7 will be present only when pins 3-4 of
jumper J2401 are jumped.
The user reset button invokes a watchdog reset. The result
depends on the value at address 0x17 of the EEPROM (see table
below).
If you want the machine to boot normally, set the diagnostics
switch to "NORM". If you want extended diagnostics when you
power up the system, set the switch to the "DIAG" position. If
the switch is set to "DIAG", power-on self-test messages are
sent to serial port A at 9600 bps or serial port B at 1200 bps.
The pinout of the keyboard/mouse connector is:
1 RxD0 (keyboard) 8 GND
2 GND 9 GND
3 TxD0 (keyboard) 10 VCC
4 GND 11 VCC
5 RxD1 (mouse) 12 VCC
6 GND 14 VCC
7 TxD1 (mouse) 15 VCC
The eight LEDs are used for diagnostic purposes. In the chart
below, a "1" indicates a lit LED, and a "0" indicates an unlit
LED. Bit 0 is at the top and bit 7 is at the bottom; the
patterns below are shown with bit 0 on the left.
Pattern Status
-------- ------
11111111 Resetting
10000000 PROM checksum test
01000000 DVMA register test
11000000 Context register test
00100000 Segment map read/write test
10100000 Segment map address test
01100000 Page map test
11100000 Memory path data test
00010000 Nonexistent memory bus error test
10010000 Interrupt test
01010000 Time-Of-Day clock interrupt test
11010000 MMU protection/status tests
00110000 ECC error test
10110000 Cache data 3-pattern test
01110000 Cache tag 3-pattern test
11110000 Memory tests
01001111 Initializing MMU
00000001 Self-tests have found an error
00000010 An exception class error occurred
"Marching ones" (cycling through 10000000, 01000000, 00100000,
etc.) indicates that Unix is running OK. On power up, it cycles
through the tests in the chart above, then boots Unix. If LED 7
(00000001) lights up while the tests are being performed, it
indicates that the test failed. If LED 6 (00000010) lights up
while the tests are being performed, it indicates that an
unexpected error (bus error, address error, unexpected
interrupt, etc.) occurred during the test. When all tests are
finished, LED 5 (00000100) starts blinking to indicate that the
ROM monitor is running and/or Unix is booting.
The monochrome video output levels are TTL (HSYNC and VSYNC)/
ECL (Video+ and Video-). The output is high resolution (1600 x
1100) only and a high-resolution monochrome monitor must be
used. The pinout of the monochrome video connector is:
1 VIDEO+ 6 VIDEO-
3 HSYNC 7 GND
4 VSYNC 8 GND
9 GND
The ID PROM is at location E4.
There is a lithium battery (BBCV2) on this board. It is
Matsushita Electric/Panasonic part number BR2325. It is
documented as not being a customer-replacable part.
Ethernet operation is governed by jumper J2401 in grid location
A-16. Factory configurations are marked with "*".
pins IN OUT
---- -- ---
1-2 *enable Ethernet clock disable Ethernet clock
3-4 +5V to Ethernet tap *no voltage (?)
5-6 type 1 transceiver (capacitive) *type 2 transceiver (xformer)
7-8 *UART clock enable UART clock disable
Operation of the VME bus is governed by jumpers J300, J500,
J2500, and J2600. J300 is found only on 501-1100 boards.
J300 at H-2 (only on 501-1100 boards)
1-2 P2 bus enable P2 bus disable
J500 at H-3/H-4
1-2 *VME interrupt level 1 (enable?)
3-4 *VME interrupt level 2 (enable?)
5-6 *VME interrupt level 3 (enable?)
7-8 *VME interrupt level 4 (enable?)
9-10 *VME interrupt level 5 (enable?)
11-12 *VME interrupt level 6 (enable?)
13-14 *VME interrupt level 7 (enable?)
15-16 nothing *nothing
J2500 at L-11
1-2 *CPU is VME arbiter & requester
3-4 CPU is VME requester only *
5-6 CPU is VME reset slave *
7-8 *CPU is VME reset master
J2600 at L-9
1-2 *enable VME clock disable VME clock
Operation of the CPU is governed by jumpers J100, J200, and
J2000.
J100 at H-5
1-2 68020 cache disable *68020 cache enable
J200 at J-6
1-2 nothing *nothing
3-4 *25MHz CPU enable
5-6 select 25MHz 68881 clock *
7-8 *select 20MHz 68881 clock
J2000 at H-1
1-2 *select 27512 boot PROM
3-4 select 27256 boot PROM
A variety of parameters may be set in the EEPROM. Only settings
meaningful to the hardware are listed here; information used by
SunOS may be stored at other addresses. There are probably other
settings which are not listed.
0x16 Should contain 0x13 for a 1600x1280 screen
0x17 Reset switch action
0x00 invoke ROM monitor
0x12 imitate power-on reset
0x1F Display device
0x00 monochrome monitor
0x10 terminal on serial port A
0x11 terminal on serial port B
0x12 color framebuffer/monitor
0x50 Number of columns
0x51 Number of rows
501-1133 3/50 motherboard
See 501-1075.
501-1162 3/50 motherboard
See 501-1075.
501-1205 3/60 motherboard
20MHz 68020, 20MHz 68881 floating point chip, Sun-3 MMU with
eight hardware contexts, up to 24M on-board SIMM memory. No bus
interface, but a P4 connector for a color video board or other
option -- not the same as the P4 in the 3/80 or any SPARC model.
From left to right, the back edge of the board has: a female
DB15 keyboard/mouse connector; eight LEDs (bit 0 to the right); a
switch to toggle between Normal and Diagnostics modes; a BNC
thin Ethernet connector; a female DB15 AUI Ethernet connector;
two female DB25 serial port connectors (ports B and A from left
to right); a female D50 SCSI port connector; and a female DB9
monochrome video connector. Above these are an upper row of
cutouts or connectors for color video and other options.
Pin 1 is usually in the upper right corner of all connectors.
Unconnected pins are not listed.
The pinout of the keyboard/mouse connector is:
1 RxD0 (keyboard) 8 GND
2 GND 9 GND
3 TxD0 (keyboard) 10 VCC
4 GND 11 VCC
5 RxD1 (mouse) 12 VCC
6 GND 14 VCC
7 TxD1 (mouse) 15 VCC
The eight LEDs are used for diagnostic purposes. In the chart
below, a "1" indicates a lit LED, and a "0" indicates an unlit
LED. The pattern is shown right to left, as it appears on the
LEDs.
Pattern Status
-------- ------
11111111 Resetting
00000001 PROM checksum test
00000011 Context register test
00000100 Segment map read/write test
00000101 Segment map address test
00000110 Page map test
00000111 Memory path data test
00001000 Nonexistent memory bus error test
00001001 Interrupt test
00001010 Time-Of-Day clock interrupt test
00001011 MMU protection/status tests
00001110 Parity error test #1
00001111 Parity error test #2
00010000 Memory test
10000000 Self-tests have found an error
01000000 An exception class error occurred
"Marching ones" (cycling through 10000000, 01000000, 00100000,
etc.) indicates that Unix is running OK. On power up, it cycles
through the tests in the chart above, then boots Unix. If LED 7
(10000000) lights up while the tests are being performed, it
indicates that the test failed. If LED 6 (01000000) lights up
with the tests are being performed, it indicates that an
unexpected error (bus error, address error, unexpected
interrupt, etc.) occurred during the test. When all tests are
finished, LED 5 (00100000) starts blinking to indicate that the
ROM monitor is running and/or Unix is booting.
If you want the machine to boot normally, set the diagnostics
switch to "NORM". If you want extended diagnostics when you
power up the system, set the switch to the "DIAG" position. If
the switch is set to "DIAG", power-on self-test messages are
sent to serial port A at 9600 bps, 8 data bits, one stop bit, no
parity, and XON/XOFF flow control.
To switch between thin and AUI Ethernet, there is a jumper block
in the forward left corner of the motherboard. The jumper
labelled "EXTXVR" (the second in from the right) should be
jumped for AUI Ethernet and unjumped for thin Ethernet. The
pinout of the AUI Ethernet connector is:
1 chassis ground 7 VCC
2 E.COL+ 9 E.COL-
3 E.TxD+ 10 E.TxD-
4 chassis ground 12 E.RxD-
5 E.RxD+ 13 +12V
6 GND
The serial ports conform to both RS-232-C and RS-423 and are
wired DTE. The pinout of the serial ports is:
2 TxD (transmit data) 8 DCD (Data Carrier Detect)
3 RxD (receive data) 15 DB (transmit clock from DCE)
4 RTS (Request To Send) 17 DD (receive clock from DCE)
5 CTS (Clear To Send) 20 DTR (Data Terminal Ready)
6 DSR (Data Set Ready) 24 DA (transmit clock from DTE)
7 GND 25 VERR (-5V)
The DB, DD, and DA signals are not used with ordinary
asynchronous equipment such as most modems and terminals,
printers, etc.).
The pinout of the SCSI connector is:
1 GND 17 GND 34 GND
2 data bus 0 18 data parity 35 GND
3 GND 19 GND 36 busy
4 data bus 1 20 GND 37 GND
5 GND 21 GND 38 acknowledge
6 data bus 2 22 GND 39 GND
7 GND 23 GND 40 reset
8 data bus 3 24 GND 41 GND
9 GND 25 GND??? 42 message
10 data bus 4 26 ??? 43 GND
11 GND 27 GND 44 select
12 data bus 5 28 GND 45 GND
13 GND 29 GND 46 command/data
14 data bus 6 30 GND 47 GND
15 GND 31 GND 48 request
16 data bus 7 32 attention 49 GND
33 GND 50 input/output
and the pattern of the pins is:
49 46 43 .... 19 16 13 10 7 4 1
48 45 42 .... 18 15 12 9 6 3
50 47 44 41 .... 17 14 11 8 5 2
The monochrome video output levels are ECL/TTL. The output can be
switched between low resolution (1152 x 900) and high resolution
(1600 x 1100) via a jumper in the front left corner of the
motherboard. The jumper labelled "HIGHRES" (the rightmost
jumper) should be jumped for high resolution operation and
unjumped for low resolution operation. The pinout of the
monochrome video connector is:
1 VIDEO+ 6 VIDEO-
3 HSYNC 7 GND
4 VSYNC 8 GND
9 GND
Memory is in the form of up to 24 1Mx9 SIMMs, rated 100ns or
faster, installed in groups of four starting with the SIMM slots
nearest the back of the motherboard and moving forward. These
SIMMs are the same kind used in IBM PC clones. Note that some
users have experienced problems with three-chip SIMMs (as
opposed to nine-chip SIMMs) -- see Misc Q&A #17. The amount of
memory present is set via a jumper block in the front left
corner of the motherboard. The leftmost six jumpers (labelled
"4MB", "8MB", "12MB", "16MB", "20MB", and "24MB") must be set so
that the jumpers up to the amount of memory installed are
jumped, and all higher jumpers are unjumped. For example, a
motherboard with 8M of memory should have the "4MB" and "8MB"
jumpers jumped and the rest unjumped.
Power requirements are +5V @ 11/13.5A typical/max, -5.2V @
0.3/0.5A typical/max, and +12V @ 0.3/0.5A typical/max.
501-1206 3/2xx CPU VME
See 501-1100.
501-1207 3/50 motherboard
See 501-1075.
501-1322 3/60 motherboard
See 501-1205.
501-1334 3/60 motherboard
See 501-1205.
501-1345 3/60 motherboard
See 501-1205.
501-1689 4/40 (SPARCstation IPC) motherboard
There are three replaceable fuses on the motherboard:
F071 Keyboard/mouse
2A fuse, PN 150-1162, loated above the serial ports
F0801 SCSI terminator power
1.5A fuse, PN 150-1162, located next to F0802
F0802 Ethernet transceiver power
2A fuse, PN 150-1974, located on the corner of the motherboard
by the SCSI connector
These fuses look like little plastic light bulbs about half an
inch long.
Memory is in the form of 1M or 4M x 9 30-pin 80ns SIMMs in three
banks:
Nearest disk connectors
_______ _______
| | | |
| 0 | | 1 |
| | | |
|_______| |_______|
_______
| |
| 2 |
| |
|_______|
Nearest SBus connectors
501-1690 4/40 (SPARCstation IPC) motherboard
See 501-1689.
501-1835 4/40 (SPARCstation IPC) motherboard
See 501-1689.
Memory boards
-------------
501-1013 1M Multibus
One megabyte of zero-wait-state memory with parity, consisting
of 144 64K x 1-bit chips. Connected to the processor by the
Multibus P2 connector only; the Multibus P1 connector is used
only for +5V and ground connections.
Eight-position DIP switch U506 controls the address at which the
board appears. The switches are all mutually exclusive. To make
the board the first megabyte (starting at address 0), turn
switch 1 ON and all others OFF. To make the board the second
megabyte (starting at address 0x100000), turn switch 2 ON and
all others OFF, etc. Via this method, the board may be set for
any megabyte from the first to the eighth; the eighth is only
available for memory when a monochrome display board is not
present in the system.
Power requirements are +5V @ 3A.
501-1048 1M Multibus
Laid out differently than 501-1013, but functionally the same.
The address DIP switch is in a different location but is set in
the same manner. See 501-1013.
501-1102 8M VME 3/2xx
Eight megabytes of ECC memory consisting of 256K x 1-bit chips,
with onboard refresh control.
The first memory board in a Sun 3/2xx must always be in VME slot
6 and must have a 220/270-ohm terminator pack at location 34F.
Up to four boards are supported, with the other three boards
being in slots 2-4, and not having the terminator pack installed
at location 34F.
The jumper on the upper rear edge of the board (accessible
through the back panel) determines the memory location of the
board, in 8M increments. The first board should have the jumper
set to 0 (at the bottom); additional boards should be set to 1
through 3 (moving toward the top of the board) in order.
There are five LEDs on the upper rear edge of the board. In
normal operation, only the two green LEDs should be lit.
UE Uncorrectable error (when lit) RED
CE Correctable error (when lit) YELLOW
DIS CPU access disabled (when lit) YELLOW
CPU CPU accessing memory GREEN
This LED flickers because it is only lit when the CPU is
actually accessing the memory on the board. If the LED is not
flickering, that simply means you have more memory than you
need at the moment -- the board is not being accessed
significantly.
REF Refresh OK (when lit) GREEN
If this LED is not lit, refresh has failed and the board
should be repaired or replaced.
501-1131 2M VME 3/1xx
Two megabytes of memory, similar in construction to the 501-1132
4M memory board.
There are two jumpers near one of the VME connectors. The one
nearest the connector should be jumped, and the other unjumped.
There are two DIP switches (U3118 and U3119) near the jumpers.
These set the base address of the board. The switch positions
are mutually exclusive; within each bank, only one should be ON
at a time. U3119 is apparently not used for this board.
U3118
1 unknown
2 base address 0x200000 (starts at 2M)
3 base address 0x400000 (starts at 4M)
4 base address 0x600000 (starts at 6M)
5-8 unknown
501-1132 4M VME 3/1xx
Four megabytes of memory, similar in construction to the
501-1131 2M memory board.
There are two jumpers near one of the VME connectors. The one
farther away from the connector should be jumped, and the other
unjumped.
There are two DIP switches (U3118 and U3119) near the jumpers.
These set the base address of the board. The switch positions
are mutually exclusive; within each bank, only one should be ON
at a time.
base address U3118 U3119
------------ ----- -----
0x200000 (2M) 2 3
0x400000 (4M) 3 4
0x600000 (6M) 4 5
0x800000 (8M) 5 6
0xA00000 (10M) 6 7
0xC00000 (12M) 7 8
501-1232 4M Multibus
Four megabytes of memory, with parity, consisting of 144 256K x 1
chips, 120ns. 14-pin jumper at U1115, may control address. My board
is the first 4M of RAM and pins 1-2, 3-4, 5-6, and 7-8 are jumped.
Video boards
------------
VIDEO STANDARDS
MONO
bwone
Sun-1 monochrome framebuffer.
bwtwo
The standard monochrome framebuffer, found in everything
from the first Sun-2 to desktop SPARCs, and the 386i as
well. Standard resolution is 1152 x 900 and high
resolution is 1280 x 1024; other resolutions may exist.
MG
MG standards are apparently monochrome framebuffers with analog
outputs connected to grayscale monitors. Still researching this one.
COLOR
Note that the ROM monitor in a machine may or may not know about any
particular color framebuffer, depending on the revision of the ROM and
the age of the framebuffer standard. If the ROM does not know how to
detect/display on the particular color framebuffer you have installed,
it will be unable to display the normal ROM boot messages. This does not
affect OS support for the framebuffer; if you are willing to boot blind,
SunOS should find the framebuffer and start displaying on it normally.
The alternative is to get a more recent ROM or a different framebuffer.
cgone
Sun-1 color framebuffer. Can run SunWindows. The
hardware occupies 16K of Multibus address space, by
default starting at addresses 0xE8000 or 0xEC000 and
using interrupt level 3.
cgtwo
VME-based color framebuffer found in Sun-2's and up. The
hardware occupies 4M of VMEbus address space, by default
starting at address 0x400000 and using interrupt level
4.
cgthree
8-bit color framebuffer found in Sun-4's and Sun-386i's.
cgfour
8-bit color framebuffer, found in Sun-3's and Sun-4's,
with a monochrome overlay plane and an overlay enable
plane on the 3/110 and some 3/60 models. It is the
onboard framebuffer for the 3/110. The SunOS driver
implements ioctls to get and put colormaps; the 3/60
models have an overlay plane colormap as well.
cgfive
No information.
cgsix
8-bit accelerated (GX) color framebuffer, found in
Sun-3's and Sun-4's. The GX accelerator is a low-end
accelerator designed to enhance vector and polygon
drawing performance.
cgeight
24-bit color framebuffer, found in Sun-3's and Sun-4's,
with a monochrome overlay plane and in some cases an
overlay enable plane as well. Despite being 24-bit, the
SunOS driver is documented as implementing ioctls to get
and put colormaps.
cgnine
24-bit double-buffered VME-based color framebuffer, with
two overlay planes and the ability to work with the GP2
graphics accelerator board. In double-buffer mode, color
resolution is reduced to 12 bits.
cgtwelve
24-bit double-buffered SBus-based color framebuffer,
with graphics accelerator, an overlay plane and an
overlay enable plane. Apparently can run in an 8-bit
colormapped mode as well. In double-buffer mode, color
resolution is reduced to 12 bits.
cgfourteen
From the manpage: "The cgfourteen device driver controls
the video SIMM (VSIMM) component of the video and graphics
subsystem of the SPARCstation 10SX. The VSIMM provides
24-bit truecolor visuals in a variety of screen
resolutions and pixel depths."
ACCELERATORS
gpone
Generic name for Graphics Processor (GP), Graphics
Processor Plus (GP+), and Graphics Processor 2 (GP2)
boards. The hardware occupies 64K of VMEbus address space,
starting at address 0x210000 by default and using interrupt
level 4.
VIDEO BOARDS
MONO
501-1003 monochrome video/keyboard/mouse TTL only Multibus
From top to bottom on the rear edge of the board are a female
DB-9 video connector, a header connector for the serial type 2
keyboard, and a header connector for the serial Sun-2 mouse.
This board must be placed in a slot in the Multibus P2
section shared by the CPU. For backplane P/N 501-1090, it must
be placed in slot 6 to terminate the P2 bus; for newer
backplanes, it is usually placed in slot 6 anyway.
DIP switch and jumper information for revisions -03 through -07:
U100 DIP switch video board address
Eight-position DIP switch. All switches are mutually exclusive
and they correspond to megabyte sections of the address space
in the same way as the 501-1013 memory board. The first video
board must be set to the eighth megabyte, which means switch
eight must be ON and all others must be OFF.
J1903 jumper serial interrupt level select
pins 13-14 jumped by default, all others unjumped
J1904 jumper video interrupt level select
pins 9-10 jumped by default, all others unjumped
Power requirements are +5V @ 4A.
501-1052 monochrome video/keyboard/mouse ECL/TTL Multibus
From top to bottom on the rear edge of the board are a female
DB-9 video connector, a header connector for the serial type 2
keyboard, and a header connector for the serial Sun-2 mouse.
This board must be placed in a slot in the Multibus P2
section shared by the CPU. For backplane P/N 501-1090, it must
be placed in slot 6 to terminate the P2 bus; for newer
backplanes, it is usually placed in slot 6 anyway.
Jumper information (note that pin 1 is to the right if you
hold the board with the printing right-side up -- the same
orientation as the ICs):
J1600
Bits read on startup to determine size of screen, either
standard (1152 x 900) or 1000 x 1000. Pins 9 through 16 are
not used and unjumped. Pins 3-4, 5-6, and 7-8 are always
jumped. Pins 1-2 are jumped for the standard screen and
unjumped for the 1000 x 1000 screen.
J1801 Crystal Shunt JUMPED by default
When jumped, the crystal signal is active; when unjumped, the
crystal is disabled for A.T.E. testing.
J1803 video levels
To select TTL (very early Sun-2 monitors), jump pins 1-2 and
5-6, unjump 3-4 and 7-8. To select TTL/ECL (all monochrome
monitors since then, including any that can work with
Sun-3's), jump 3-4 and 7-8 and unjump 1-2 and 5-6.
J1804 Ground test point UNJUMPED by default
Used during troubleshooting only.
J1903 Serial interrupt level select
Located at N3, farther away from the bus connectors.
pins 13-14 jumped by default, all others unjumped
J1904 Video interrupt level select
Located at N3, nearer the bus connectors.
pins 9-10 jumped by default, all others unjumped
Power requirements are +5V @ 4A.
COLOR
501-0289 color video Multibus
Jumper information:
J1
1-2 VODD JUMPED by default
3-4 VRESET JUMPED by default
5-6 SYSCP1 JUMPED by default
7-8 HRESET JUMPED by default
9-10 STATE 11 JUMPED by default
J2
1-2 M0 JUMPED by default
3-4 M1 JUMPED by default
5-6 M2 JUMPED by default
7-8 M3 JUMPED by default
9-10 M4 JUMPED by default
11-12 M5 JUMPED by default
J3 Color board interrupt level
pins 5-6 jumped by default, all others unjumped
J4 Invert BBUS.A0
1-2 JUMPED by default
3-4 UNJUMPED by default
J5 Ground the P2 bus
All pins (1-2, 3-4, 5-6, 7-8, 9-10, 11-12) jumped by default.
Power requirements are +5V @ 6A and -5V @ 1.2A.
501-1014 Sun-2 color framebuffer VME
Output resolution 1152 x 900, 66Hz vertical refresh, 62KHz
horizontal sync. Known to work in 2/160, 3/160, 3/180, 3/260,
3/280, 3/460, 3/470, 3/480.
501-1058 GB graphics buffer VME
Used with GP graphics accelerator. Known to work in 2/160,
3/160, 3/180, 3/260, 3/280, 3/460, 3/480, 4/150, 4/260, 4/280,
4/330, 4/350, 4/360, 4/370, 4/380.
501-1089 cg3 color framebuffer VME
Output resolution 1152 x 900, 66Hz vertical refresh, 62KHz
horizontal sync. Known to work in 3/160, 3/180, 3/260, 3/280,
3/460, 3/480, 4/150, 4/260, 4/280, 4/330, 4/350, 4/360, 4/370,
4/380.
501-1116 cg3 color framebuffer VME
See 501-1089.
501-1267 cg5 color framebuffer VME
Output resolution 1152 x 900, 66Hz vertical refresh, 62KHz
horizontal sync. Known to work in 3/160, 3/180, 3/260, 3/280,
3/460, 3/480, 4/150, 4/260, 4/280, 4/330, 4/350, 4/360, 4/370,
4/380, 4/470, 4/490.
501-1319 cg3 color framebuffer VME
See 501-1089.
501-1434 cg9 color framebuffer VME
Output resolution 1152 x 900, 66Hz vertical refresh, 62KHz
horizontal sync. Known to work in 3/160, 3/180, 3/260, 3/280,
3/460, 3/480, 4/150, 4/260, 4/280, 4/330, 4/350, 4/360, 4/370,
4/380, 4/470, 4/490.
ACCELERATORS
501-1055 GP graphics processor VME
Known to work in 2/160, 3/160, 3/180, 3/260, 3/280, 3/460,
3/480, 4/150, 4/260, 4/280, 4/330, 4/350, 4/360, 4/370, 4/380.
501-1139 GP+ graphics processor VME
Known to work in 2/160, 3/160, 3/180, 3/260, 3/280, 3/460,
3/480, 4/150, 4/260, 4/280, 4/330, 4/350, 4/360, 4/370, 4/380.
501-1268 GP2 graphics processor VME
Known to work in 3/160, 3/180, 3/260, 3/280, 3/460, 3/480,
4/150, 4/260, 4/280, 4/330, 4/350, 4/360, 4/370, 4/380, 4/470,
4/490.
END OF PART III OF THE SUN HARDWARE REFERENCE
Archive-name: sun-hdwr-ref/part4
Posting-Frequency: as revised
Version: $Id: part4,v 1.7 1995/05/29 22:05:47 jwbirdsa Exp $
THE SUN HARDWARE REFERENCE
compiled by James W. Birdsall
(jwbirdsa@picarefy.com)
PART IV
=======
BOARDS
DISKS
KEYBOARDS
MICE
MONITORS
BOARDS (cont'd)
===============
SCSI controller boards
----------------------
501-1006 Sun-2 SCSI/serial Multibus
SCSI interface and four serial lines with full modem control.
Identifiable by its three 50-pin header connectors, one of which
(J3, the bottommost) is the SCSI interface and the other two of
which (J1 and J2) are the serial lines.
There are three DIP switches: U305, U312, and U315. Holding the
board with the 50-pin header connectors down and component side
toward you, U312 is lowest, U315 in the middle, and U305 at the
top. All three are eight-position.
U305 SCSI board base address/bus priority in (BPRN)
Switches one through six correspond to address bits A14
through A19 respectively. The default setting is switch six
on, switches one through five off. Switch eight grounds the
bus priority in (BPRN) line and must be OFF; it should be ON
only if you are configuring the board as the highest-priority
DMA master in a serial card cage (i.e. a non-Sun
configuration).
U312 SCSI interrupt priority
Switches eight through one correspond to interrupt priorities
0 through 7 in that (reverse) order. The default is for switch
six to be ON and all others OFF, which yields an interrupt
priority of 2.
U315 Serial interrupt priority
Switches eight through one correspond to interrupt priorities
0 through 7 in that (reverse) order. The default is for switch
two to be ON and all others OFF, which yields an interrupt
priority of 6.
Serial ports C and D appear on connector J2, E and F on
connector J1. These are usually labelled SIO-S0 through SIO-S3
on the back of the machine (SIO-C through SIO-F on older
machines) and appear as /dev/ttys0 through /dev/ttys3 under
SunOS. If you have a second SCSI/serial board, the serial ports
appear as /dev/ttyt0 through /dev/ttyt3 under SunOS. The
documented maximum output speed is 19200 bps. All ports are
wired DTE and are compatible with both RS-232C and RS-423, using
Zilog Z8530A dual UART chips. The pinout of J2 is:
3 TxD-C 14 DTR-C 33 DD-D
4 DB-C 15 DCD-C 34 CTS-D
5 RxD-C 22 DA-C 36 DSR-D
7 RTS-C 24 BSY-C 38 GND-D
8 DD-C 28 TxD-D 39 DTR-D
9 CTS-C 29 DB-D 40 DCD-D
11 DSR-C 30 RxD-D 47 DA-D
13 GND-C 32 RTS-D 49 BSY-D
The pinout of J1 is exactly similar; substitute "E" for "C" and
"F" for "D".
Power requirements are +5V @ 5A.
501-1045 "Sun-2" SCSI host adapter, 6U VME
Used with various 6U/9U VME adapters to produce the 501-1138,
501-1149, and 501-1167. Uses PALs and logic sequencers to
implement SCSI protocols. Frequently found in Sun-3's despite
name.
There are DIP switches at U702 and U704. The bits are inverted,
so the default settings correspond to an address of 0x200000.
U702 VMEbus address, low bits
1-4 not connected
5-8 A12-A15 ON by default
U704 VMEbus address, high bits
1-5 A16-A20 ON by default
6 A21 OFF by default
7-8 A22-A23 ON by default
501-1138 "Sun-2" SCSI host adapter, external, VME
A 501-1045 6U VME SCSI host adapter in a 270-1138 6U/9U VME
adapter, which provides only an external D50 connection. See
501-1045. See 3/50 motherboard listing for pinout.
501-1149 "Sun-2" SCSI host adapter, internal, VME
A 501-1045 6U VME SCSI host adapter in a 270-1059 6U/9U VME
adapter, which provides only an internal connection to VME slot
7 in 12-slot chassis. See 501-1045.
501-1167 "Sun-2" SCSI host adapter, external/internal, VME
A 50