Technical data

SunOS 5.5 Devices stc(7D)
stc_attach: board revision 0x%x not supported by driver.
FATAL. This revision of the board is not supported by the driver.
stc_attach: oscillator revision undeterminable
FATAL. The driver did not get an oscillator revision level from the board’s
onboard FCode PROM.
stc_attach: wierd oscillator revision (0x%x), assuming 10Mhz
ADVISORY. The board’s onboard FCode PROM returned an unanticipated
baud-rate oscillator value, so the driver assumes that a 10Mhz oscillator is
installed.
stc_attach: error initializing stc%d
FATAL. An error occured while trying to initializethe board; perhaps a
memory access failed.
stc_attach: bad number of interrupts: %d
FATAL. An incorrect number of interrupts was read from the board’s
onboard FCode PROM.
stc_attach: bad number of register sets: %d
FATAL. An incorrect number of register sets was read from the board’s
onboard FCode PROM.
stc_init: stc%d GIVR was not 0x0ff, was: 0x%x
FATAL. The cd-180 8-channel UART failed to initializeproperly, or a memory
fault occured while trying to access the chip.
cd180_init: stc%d GIVR was not 0x0ff, was: 0x%x
FATAL. The cd-180 8-channel UART failed to initializeproperly, or a memory
fault occured while trying to access the chip.
stc%d: board revision: 0x%x should be updated
ADVISORY. Two versions of the FCode PROM on the SPC/S card have been
released; V1.0 (0x4) and V1.1 (0x5). The V1.1 PROM fixes some incompatabili-
ties between the V1.0 FCode PROM (on the SPC/S) and the V2.0 OpenBOOT
PROM (on your system) and is required on an SPC/S card to be used in a sys-
tem running Solaris 2.X.
stc%d: system boot PROM revision V%d.%d should be updated
ADVISORY. Your system’s BOOT PROM should be updated to at least V1.3
because prior versions of the BOOT PROM did not map the SBus interrupt
levels that the SPC/S uses correctly.
Messages Related To
The Serial Port:
SET_CCR: CCR timeout
ERROR. the cd-180’sCCR register did not return to zero within the specified
timeout period after it was issued a command
PUTSILO: unit %d line %d soft silo overflow
ERROR. The driver’s internal receive data silo for the enunciated line has
overflowed because the system has not gotten around to pulling data out of
the silo; check that you are using the correct flow control; all data in the silo is
modified 2 Aug 1993 7D-321