| Title: | CSGUK_SYSTEMS |
| Notice: | No restrictions on keyword creation |
| Moderator: | KERNEL::ADAMS |
| Created: | Wed Mar 01 1989 |
| Last Modified: | Thu Nov 28 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 242 |
| Total number of notes: | 1855 |
This topic is reserved for notes about the CIXCD
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 114.1 | fix to CIXCD problems | KERNEL::WRIGHTON | odd numbered release = bug insert | Tue Oct 23 1990 18:11 | 121 |
<<< KERNEL::DISK$APD1:[NOTES$LIBRARY]CSGUK_SYSTEMS.NOTE;1 >>>
-< CSGUK_SYSTEMS >-
================================================================================
Note 78.29 VAX 9000 topic. 29 of 78
KERNEL::WRIGHTON "odd numbered release = bug inser" 113 lines 10-AUG-1990 07:19
-< fix to the CIXCD problems >-
--------------------------------------------------------------------------------
+---------------------------+ TM
| | | | | | | |
| d | i | g | i | t | a | l | INTEROFFICE MEMORANDUM
| | | | | | | |
+---------------------------+
DATE: August 9, 1990
TO: 9K_TECH FROM: Charlie Kretz
CC: VAX 9000 CSSE Group DEPT: HPS CSSE
Bob Aston EXT: 297-4948
Dave Riehl LOC: MRO2-3/5E
ENET: MRCSSE::KRETZ
SUBJECT: VAX 9000 XJA and CIXCD Selftest Interaction Problems
There have been some interaction problems between the XJA and the CIXCD
selftest. These problems caused the XJA to fail self test and depending
on what slot the CIXCD was in would prohibit VMS from booting. All these
problems have been resolved, the CIXCD requires a microcode update to
correct these problems. The latest version of the CIXCD functional
microcode is version V0.22 with selftest microcode version V0.38 corrects
these problems.
The latest version of the CIXCD microcode is accessible on our cluster,
the file name is MRCSSE::NONAME:[PUBLIC]CIXCD.BIN. Some people have
gotten an early release copy of the CIXCD functional microcode version
0.22 that still had the older selftest version V0.37 microcode. While
this provided the latest functional features it did not have the selftest
interaction problems corrected. Unfortunately the diagnostic firmware
revision is not displayed in the XMI XDEV register, only the functional
revision is displayed. You can identify the new microcode file by dumping
or typing the file and looking for the version information. The version
is stored in a human readable format in the first block of the file, see
the example on page 2 (two) of this memo.
In case you do not have the CIXCD Users Guide, I have put a softcopy of
this manual in our cluster. This manual contains information about the
CIXCD on the VAX 6000, which is an unannounced product. Therefore, it can
not to be given or viewed by any Non-Digital personnel. The file name is
MRCSSE::NONAME:[PUBLIC]CIXCD_UG.PS.
The proper procedures for loading the CIXCD Microcode ON A VAX 9000 are:
Copy the latest version of the CIXCD microcode file in the [SYSMAINT]
directory on the console disk.
>>> I/K
>>> SET XMI_UPDATE/XMI:0 ON
>>> B VDS
DS> ATTACH XJA HUB XJA0 0
DS> ATTACH CIXCD XJA0 PAA0 'xmi_node_number 'ci_node_number
DS> SEL PAA0
DS> R EVGEA/SECTION=UPDATE
The diagnostic will ask for the filename of the CIXCD microcode file, the
default file name is CIXCD.BIN.
Page 2 of 2
The have been a couple of systems that had trouble updating the microcode
due to problem with a cable. This cable (17-02324-01) brings the signal
XMI EEPROM UPDATE ENABLE from the IORIC to the XMI card cage. Check this
cable for the correct revision (C01) and that it is plugged in securely.
The following is pin out for this cable:
1o o2 IORIC(J6) Name (IORIC) XMI A (J1)
o o --------------------------------------------
o o pin 1 PRM A RESET L pin 17
o o pin 2 GND pin 1
o o pin 3 XMI A DC LO L pin 19
notch o o pin 4 GND pin 11
o o pin 5 XMI LAT AC LO L pin 20
o o pin 6 GND pin 15
o o pin 7 XUE A H pin 5
19o o20 pin 8 XMI A PRESENT L pin 18
pin 9 NC
cable connector for pin 10 NC
IORIC and XMIA viewed
from the wire side
$ DUMP MRCSSE::NONAME:[PUBLIC]CIXCD.BIN
Dump of file NONAME:[PUBLIC]CIXCD.BIN;1 on 9-AUG-1990 10:20:11.00
File ID (6610,5,0) End of file block 353 / Allocated 354
Virtual block number 1 (00000001), 512 (0200) bytes
28207468 67697279 706F4320 0A0A0D99 .... Copyright ( 000000
70697571 45206C61 74696769 44202963 c) Digital Equip 000010
6E6F6974 61726F70 726F4320 746E656D ment Corporation 000020
74686769 72206C6C 41202E30 39393120 1990. All right 000030
0A0A0D20 202E6465 76726573 65722073 s reserved. ... 000040
6D726946 20636974 736F6E67 61694420 Diagnostic Firm 000050 <-- Diag.
2E30206E 6F697369 76655220 65726177 ware Revision 0. 000060 V0.38
206C616E 6F697463 6E754620 2C203833 38 , Functional 000070 <-- Func.
6F697369 76655220 65726177 6D726946 Firmware Revisio 000080 V0.22
20202020 20200A0A 0D203232 2E30206E n 0.22 ... 000090
20202020 20362E38 56205043 55444358 XCDUCP V8.6 0000A0
20202020 20202020 20202020 20202020 0000B0
$ TYPE MRCSSE::NONAME:[PUBLIC]CIXCD.BIN
Copyright (c) Digital Equipment Corporation 1990. All rights reserved.
Diagnostic Firmware Revision 0.38 , Functional Firmware Revision 0.22
XCDUCP V8.6
The rest of the file is unreadable by a human.
| |||||
| 114.2 | CIXCD update procedure | KERNEL::WRIGHTON | odd numbered release = bug insert | Tue Oct 23 1990 18:12 | 148 |
<<< KERNEL::DISK$APD1:[NOTES$LIBRARY]CSGUK_SYSTEMS.NOTE;1 >>>
-< CSGUK_SYSTEMS >-
================================================================================
Note 78.36 VAX 9000 topic. 36 of 78
KERNEL::LOANE "Once upon a time in a TU45!" 140 lines 30-AUG-1990 11:15
-< CIXCD Update procedure (+hints/kinks) >-
--------------------------------------------------------------------------------
___ ___ ___ ___ ___ ___ ___
| | | | | | | |
| d | i | g | i | t | a | l | I N T E R O F F I C E M E M O
|___|___|___|___|___|___|___|
To: Distribution Date : August 20, 1990
From : Joe Mellone
Dept : ISB
Ext : 297-4682
Loc/MS : MR01-2 S10/KL18.6
Enet : IOENG::MELLONE
SUBJECT: CIXCD Software Release Area Update Notification
A software release area is available which contains all of
the required CIXCD software components, needed for diagnostic
and functional operations. The below listed files can be
retrieved by using the following procedure call:
$ @IOENG::XMVDSK:[CIXCD.DIAG]RETRIEVE
The 'retrieve' procedure will prompt you for the destination
directory and whether you want diagnostic or operational
files. If the destination directory is not specified, the
procedure will use your default directory. If diagnostic
or operational is not specified, all files will be retrieved.
A new feature was added to the retrieve procedure, which allows
the copy of just a single file. Use the 's' option when prompted
for diagnostic, operational or single files.
COMPONENT CREATION DATE VERSION NUMBER
--------- ------------- -----------------------------
>CIXCD.BIN 16-AUG-1990 V1.00
ELSAA.EXE 16-JUL-1990 X13.2-2008
ERSAA.EXE 06-JUL-1990 13.1-893
EWSAA.EXE 17-AUG-1990 13.2-1221
>DIAGBOOT.EXE 17-AUG-1990 n/a
EVGEA.BIN 04-APR-1990 V0.01
>EVGEA.EXE 14-AUG-1990 V2.1
>EVGEA.HLP 14-AUG-1990 n/a
EVGEB.EXE 16-JUL-1990 V2.0
EVGEB.HLP 16-JUL-1989 n/a
EVGAA.EXE 18-JUL-1990 V6.1
EVGAB.EXE 18-JUL-1990 V6.1
EVGAC.EXE 18-JUL-1990 V1.1
VMS T5.4-4HW 11-JUL-1990 Available from VMS
HYPERION.EEROM 10-MAY-1990 V4.E
CALYPSO.EEROM 10-MAY-1990 V3.D
RIGEL.EEROM 07-MAY-1990 V1.FE
---------------------------------------------------------
>=New version
COMPONENT DESCRIPTIONS :
CIXCD.BIN = Microcode file
ELSAA.EXE = Calypso/Hyperion Diagnostic Supervisor
ERSAA.EXE = Rigel Diagnostic Supervisor
EWSAA.EXE = Aridus Diagnostic Supervisor
DIAGBOOT.EXE = Diagnostic bootstrap file
EVGEA.BIN = CIXCD Repair Level Diagnostic Test Microcode
EVGEA.EXE = CIXCD Repair Level Diagnostic / Loader Program
EVGEA.HLP = CIXCD Repair Level Diagnostic VDS Help File
EVGEB.EXE = CIXCD Microcode Load Utility
EVGEB.HLP = CIXCD Microcode Load Utility VDS Help File
EVGAA.EXE = CI Functional Diagnostic (part 1)
EVGAB.EXE = CI Functional Diagnostic (part 2)
EVGAC.EXE = CI Multi-Node Diagnostic
HYPERION.EEROM = Hyperion CPU eeprom microcode patch file
CALYPSO.EEROM = Calypso CPU eeprom microcode patch file
RIGEL.EEROM = Rigel CPU eeprom microcode patch file
COMPONENT CHANGES SINCE LAST RELEASE :
CIXCD.BIN :
On 9000 series machines, the CIXCD could not be used as the boot
device in XMI slots 4 and C. This problem was fixed with a new
version of the CIXCD self-test microcode. A couple of bug fixes
were also made to the functional microcode.
EVGEA.EXE :
A correction to the BAR_DCB init section to support extended module
revisions was done. A correction to properly decode default file
name after executing START/SECT=MFG was done. Changing the definition
of EVENT FLAG 1 from INHIBIT external loopback tests to ENABLE
external loopback tests was chnaged as requested.
EWSAA.EXE :
The previous version would not boot VDS via the CIXCD. The problem
was found a fixed in this version. A new DIAGBOOT.EXE image is
also needed in conjuction with this new supervisor.
COMPATABLE HSC MICROCODE REVISIONS :
HSC70 Version (Y50D)
HSC50 Version (YB02)
CURRENT KNOWN PROBLEMS :
VDS will not boot correctly through the CIXCD when the
NODE specification in the boot string contains a failover
CI address. It will boot, only when the correct HSC node is
in bits 15:8, not when the correct HSC node is in bits 7:0.
INSTALLATION/USAGE NOTES:
All CIXCDs currently in use must be updated with the latest
microcode version. QARs posted against previous versions
will be answered "microcode out-of-rev" and closed.
On 6000 series machines, the CIXCD will only operate in slots
1-4 and B-E.
When installing the header assembly, needed for Rev E modules,
make sure that all pins are plugged into the connector. The
connectors are not keyed, and it is possible to plug the header
card in one position to high or one position to low.
Take note of the hardware revision held in XDEV<24:16>. The
format of this field has changed and must be reprogrammed with
section init_dcb of EVGEA. The old format displayed an E02 module
as "A2", the new format will display an E02 module as "52".
HYPERION/CALYPSO/RIGEL.EEROM CPU MICROCODE FILES :
Three files have been added to the directory. These files can be
used to patch the cpu microcode on the respective processor. This
updated cpu microcode will enable the cpu to recognize the CIXCD
as a valid I/O device, thus allowing the CIXCD to function as the
primary boot device.
A command procedure "CREATE_EEROM_TAPE.COM" can be used to create
a patch tape for the respective processor. This procedure is located
in the release area for general use.
| |||||
| 114.3 | CIXCD ucode | KERNEL::WRIGHTON | odd numbered release = bug insert | Tue Oct 23 1990 18:12 | 36 |
<<< KERNEL::DISK$APD1:[NOTES$LIBRARY]CSGUK_SYSTEMS.NOTE;1 >>>
-< CSGUK_SYSTEMS >-
================================================================================
Note 78.70 VAX 9000 topic. 70 of 78
KERNEL::WRIGHTON "odd numbered release = bug insert" 28 lines 11-OCT-1990 14:55
-< CIXCD uCode >-
--------------------------------------------------------------------------------
SUBJECT: CIXCD MICROCODE
There are still some CIXCDs running with the incorrect
version of Microcode. The current released and supported
version is 1.04.
Please ensure that all CIXCDs are now running with V1.04.
This version can copied from:
IOENG::XMVDSK:[CIXCD.DIAG]CIXCD.BIN
A quick check of the XDEV register will decode the current
CIXCD code. Bits <31:24> of the XDEV contain the current
Microcode version and should contain a 24, which represents
V1.04. If 24 is not present, then a Microcode upgrade is
needed.
Also copy the most current version of CIXCD diagnostics from
that same area. These diagnostics are: EVGAA, EVGAB, EVGAC
and EVGEA.
Please do not mix different releases of Microcode and
diagnostics, the symptoms and problems they could produce are
many and varied.
| |||||
| 114.4 | CIXCD diagnostic failures | KERNEL::WRIGHTON | odd numbered release = bug insert | Tue Oct 23 1990 18:13 | 81 |
<<< KERNEL::DISK$APD1:[NOTES$LIBRARY]CSGUK_SYSTEMS.NOTE;1 >>>
-< CSGUK_SYSTEMS >-
================================================================================
Note 78.72 VAX 9000 topic. 72 of 78
KERNEL::WRIGHTON "odd numbered release = bug insert" 73 lines 19-OCT-1990 09:18
-< CIXCD diagnostic failures >-
--------------------------------------------------------------------------------
Current problems exist with CIXCD Diagnostics EVGAA, EVGAB and EVGAC.
EVGAA - Revision 6.1
EVGAB - Revision 6.1
EVGAC - Revision 1.1
PROBLEM:
There seems to be 3 "intermittent" diagnostic failures related
to the CIXCD. These diagnostics will run in some cases, and
fail in others. In some cases, it was the order of sequence
of previously run diagnostics.
Below are listed the 3 known CIXCD related faults:
Failure 1:
An ASB block unaligned failure was experienced when other
diagnostics were run previous to EVGAA and EVGAB. The allocated memory
area contained junk data and needed to be initialized (CIXCD only).
The failure is exhibited with the banner in EVGAA test 1 being
displayed with no ports being displayed and an error message
indicating an unexpected interrupt;
EVGAB test 1 failure with an unexpected interrupt.
If the register dump is analyzed there is an ASB block unaligned
failure code in the pertinent adapter register.
Failure 2:
When run using multiple CIs, only the last specified unit
was reset in the cleanup code.
If EVGEA is run after the EVGAA and EVGAB functional diagnostics,
EVGEA will fail with an unexpected interrupt.
Failure 3:
EVGAA SETCKT test failures, received contents of the VCD does not match
expected.
Workaround:
****************************************************************
NEW DIAGNOSTICS ARE AVAILABLE AS OF 12:00 EST. OCTOBER 12, 1990.
****************************************************************
EVGAA.EXE V6.3
EVGAB.EXE V6.3
EVGAC.EXE V1.2
ARE AVAILABLE ON:
IOENG::XMVDSK:[CIXCD.DIAG]
Long Term fix:
Final Microcode and Diagnostics will be distributed through the
normal release process.
*** DIGITAL INTERNAL USE ONLY***
| |||||
| 114.5 | CIXCD revision matrix | KERNEL::WRIGHTON | odd numbered release = bug insert | Tue Oct 23 1990 18:13 | 297 |
<<< KERNEL::DISK$APD1:[NOTES$LIBRARY]CSGUK_SYSTEMS.NOTE;1 >>>
-< CSGUK_SYSTEMS >-
================================================================================
Note 78.76 VAX 9000 topic. 76 of 78
KERNEL::WRIGHTON "odd numbered release = bug inser" 289 lines 22-OCT-1990 09:07
-< CIXCD revision matrix >-
--------------------------------------------------------------------------------
CIXCD Diagnostic/Microcode/Software Revision Matrix
------------+--------------------+--------------------+--------------------+--------------------+
Component | Creation Date/ | Creation Date/ | Creation Date/ | Creation Date/ |
Name | Notes | Notes | Notes | Notes |
------------+--------------------+--------------------+--------------------+--------------------+
| RELEASE DATE | RELEASE DATE | RELEASE DATE | RELEASE DATE |
| APRIL 3, 1990 | APRIL 13, 1990 | MAY 2, 1990 | MAY 11, 1990 |
------------+--------------------+--------------------+--------------------+--------------------+
CIXCD.BIN | APRIL 3, 1990 | APRIL 10, 1990 | MAY 1, 1990 | MAY 11, 1990 |
| SELFTEST = 0.36 | EXPERIMENTAL VER. | V0.04 | V0.05 |
| FUNCTIONAL = 0.01 | V0.02 | | |
------------+--------------------+--------------------+--------------------+--------------------+
ELSAA.EXE | FEB. 5, 1990 | FEB. 5, 1990 | | MAY 3, 1990 |
| X12.6-1584 | X12.6-1584 | | | 12.6-1847 |
------------+--------------------+--------------------+ | +--------------------+
ERSAA.EXE | FEB. 2, 1990 | FEB. 2, 1990 | | | FEB. 2, 1990 |
| X12.6-696 | X12.6-696 | | | X12.6-696 |
------------+--------------------+--------------------+ | +--------------------+
EWSAA.EXE | N/A | APRIL 2, 1990 | | | APRIL 2, 1990 |
| | X12.7-1032 | | | X12.7-1032 |
------------+--------------------+--------------------+ | +--------------------+
EVGEA.BIN | FEB. 27, 1990 | APRIL 4, 1990 | | APRIL 4, 1990 |
| V0.01 | V0.01 | N | V0.01 |
------------+--------------------+--------------------+ O +--------------------+
EVGEA.EXE | APRIL 3, 1990 | APRIL 9, 1990 | | APRIL 9, 1990 |
| V0.14 | V1.0 | C | V1.0 |
------------+--------------------+--------------------+ H +--------------------+
EVGEA.HLP | APRIL 3, 1990 | APRIL 6, 1990 | A | APRIL 6, 1990 |
| N/A | N/A | N | N/A |
------------+--------------------+--------------------+ G +--------------------+
EVGEB.EXE | N/A | APRIL 9, 1990 | E | APRIL 9, 1990 |
| | V1.0 | S | V1.0 |
------------+--------------------+--------------------+ +--------------------+
EVGEB.HLP | N/A | APRIL 6, 1990 | | | APRIL 6, 1990 |
| | N/A | | | N/A |
------------+--------------------+--------------------+ | +--------------------+
EVGAA.EXE | MARCH 19, 1990 | APRIL 11, 1990 | | | APRIL 11, 1990 |
| V0.8 | V0.9 | | V0.9 |
------------+--------------------+--------------------+ N +--------------------+
EVGAB.EXE | MARCH 19, 1990 | APRIL 11, 1990 | O | APRIL 11, 1990 |
| V0.8 | V0.9 | | V0.9 |
------------+--------------------+--------------------+ C +--------------------+
EVGAC.EXE | MARCH 2, 1990 | APRIL 12, 1990 | H | MAY 4, 1990 |
| V0.7 | V0.9 | A | V1.0 |
------------+--------------------+--------------------+ N +--------------------+
VMB.EXE | MARCH 16, 1990 | MARCH 16, 1990 | G | MARCH 16, 1990 |
| AETNA 4F4 REQUIRED | AETNA 4F4 REQUIRED | E | AETNA 4F4 REQUIRED |
------------+--------------------+--------------------+ S +--------------------+
PADRIVER.EXE| MARCH 30, 1990 | MARCH 30, 1990 | | MARCH 30, 1990 |
| AETNA 4F4 REQUIRED | AETNA 4F4 REQUIRED | | | AETNA 4F4 REQUIRED |
------------+--------------------+--------------------+ | +--------------------+
SYSLOA9CC. | MARCH 28, 1990 | MARCH 28, 1990 | | | MARCH 28, 1990 |
EXE | AETNA 4F4 REQUIRED | AETNA 4F4 REQUIRED | | | AETNA 4F4 REQUIRED |
------------+--------------------+--------------------+ | +--------------------+
SYSLOA9RR. | MARCH 28, 1990 | MARCH 28, 1990 | | | MARCH 28, 1990 |
EXE | AETNA 4F4 REQUIRED | AETNA 4F4 REQUIRED | | | AETNA 4F4 REQUIRED |
------------+--------------------+--------------------+ | +--------------------+
HSC CODE | N/A | HSC50 - V39A | | | HSC50 - V39B |
| | HSC70 - Y50A | | HSC70 - Y50D |
------------+--------------------+--------------------+--------------------+--------------------+
HYPERION. | N/A | N/A | N/A | MAY 10, 1990 |
EEPROM | | | | V4.3E |
------------+--------------------+--------------------+--------------------+--------------------+
CALYPSO. | N/A | N/A | N/A | MAY 10, 1990 |
EEPROM | | | | V3.D |
------------+--------------------+--------------------+--------------------+--------------------+
RIGEL. | N/A | N/A | N/A | MAY 7, 1990 |
EEPROM | | | | V1.FE |
------------+--------------------+--------------------+--------------------+--------------------+
CIXCD Diagnostic/Microcode/Software Revision Matrix - Continued
------------+--------------------+--------------------+--------------------+--------------------+
Component | Creation Date/ | Creation Date/ | Creation Date/ | Creation Date/ |
Name | Notes | Notes | Notes | Notes |
------------+--------------------+--------------------+--------------------+--------------------+
| RELEASE DATE | RELEASE DATE | RELEASE DATE | RELEASE DATE |
| MAY 23, 1990 | JUNE 6, 1990 | JULY 19, 1990 | JULY 27, 1990 |
------------+--------------------+--------------------+--------------------+--------------------+
CIXCD.BIN | MAY 22, 1990 | MAY 22, 1990 | JULY 17, 1990 | JULY 17, 1990 |
| V0.06 | V0.06 | V0.22 | V0.22 |
| | | | |
------------+--------------------+--------------------+--------------------+--------------------+
ELSAA.EXE | MAY 3, 1990 | MAY 30, 1990 | MAY 30, 1990 | JULY 16, 1990 |
| X12.6-1847 | X13.1-1887 | X13.1-1887 | X13.2-2008 |
------------+--------------------+--------------------+--------------------+--------------------+
ERSAA.EXE | FEB. 2, 1990 | JUNE 1, 1990 | JUNE 1, 1990 | JULY 6, 1990 |
| X12.6-696 | X13.1-861 | X13.1-861 | X13.1-893 |
------------+--------------------+--------------------+--------------------+--------------------+
EWSAA.EXE | APRIL 2, 1990 | MAY 29, 1990 | JUNE 13, 1990 | JUNE 13, 1990 |
| X12.7-1032 | X13.0-1118 | X13.0-1144 | X13.0-1144 |
------------+--------------------+--------------------+--------------------+--------------------+
EVGEA.BIN | APRIL 4, 1990 | APRIL 4, 1990 | | APRIL 4, 1990 |
| V0.01 | V0.01 | | V0.01 |
------------+--------------------+--------------------+ N +--------------------+
EVGEA.EXE | APRIL 9, 1990 | MAY 30, 1990 | O | JULY 10, 1990 |
| V1.0 | V1.4 | | V2.0 |
------------+--------------------+--------------------+ C +--------------------+
EVGEA.HLP | APRIL 6, 1990 | APRIL 6, 1990 | H | JULY 16, 1990 |
| N/A | N/A | A | N/A |
------------+--------------------+--------------------+ N +--------------------+
EVGEB.EXE | APRIL 9, 1990 | APRIL 9, 1990 | G | JULY 16, 1990 |
| N/A | V1.0 | E | V2.0 |
------------+--------------------+--------------------+ S +--------------------+
EVGEB.HLP | APRIL 6, 1990 | APRIL 6, 1990 | | JULY 16, 1990 |
| N/A | N/A | | N/A |
------------+--------------------+--------------------+--------------------+--------------------+
EVGAA.EXE | APRIL 11, 1990 | MAY 23, 1990 | JULY 18, 1990 | JULY 18, 1990 |
| V0.9 | PRE-RELEASE 6.1 | V6.1 | V6.1 |
------------+--------------------+--------------------+--------------------+--------------------+
EVGAB.EXE | APRIL 11, 1990 | APRIL 11, 1990 | JULY 18, 1990 | JULY 18, 1990 |
| V0.9 | V0.9 | V6.1 | V6.1 |
------------+--------------------+--------------------+--------------------+--------------------+
EVGAC.EXE | MAY 4, 1990 | MAY 4, 1990 | JULY 18, 1990 | JULY 18, 1990 |
| V1.0 | V1.0 | V1.1 | V1.1 |
------------+--------------------+--------------------+--------------------+--------------------+
VMB.EXE | MARCH 16, 1990 | | | |
| AETNA 4F4 REQUIRED | | | |
------------+--------------------+ | | |
PADRIVER.EXE| MARCH 30, 1990 | VMS VERSION | VMS VERSION | VMS VERSION |
| AETNA 4F4 REQUIRED | | | |
------------+--------------------+ T5.4-4GD | T5.4-4HW | T5.4-4HW |
SYSLOA9CC. | MARCH 28, 1990 | | | |
EXE | AETNA 4F4 REQUIRED | MAY 24, 1990 | JULY 11, 1990 | JULY 11, 1990 |
------------+--------------------+ | | |
SYSLOA9RR. | MARCH 28, 1990 | AVAILABLE FROM VMS | AVAILABLE FROM VMS | AVAILABLE FROM VMS |
EXE | AETNA 4F4 REQUIRED | | | |
------------+--------------------+--------------------+--------------------+--------------------+
HSC CODE | HSC50 - V39B | HSC50 - V39B | HSC50 - V39B | HSC50 - V39B |
| HSC70 - Y50D | HSC70 - Y50D | HSC70 - Y50D | HSC70 - Y50D |
------------+--------------------+--------------------+--------------------+--------------------+
HYPERION. | MAY 10, 1990 | MAY 10, 1990 | MAY 10, 1990 | MAY 10, 1990 |
EEPROM | V4.E | V4.E | V4.E | V4.E |
------------+--------------------+--------------------+--------------------+--------------------+
CALYPSO. | MAY 10, 1990 | MAY 10, 1990 | MAY 10, 1990 | MAY 10, 1990 |
EEPROM | V3.D | V3.D | V3.D | V3.D |
------------+--------------------+--------------------+--------------------+--------------------+
RIGEL. | MAY 7, 1990 | MAY 7, 1990 | MAY 7, 1990 | MAY 7, 1990 |
EEPROM | V1.FE | V1.FE | V1.FE | V1.FE |
------------+--------------------+--------------------+--------------------+--------------------+
CIXCD Diagnostic/Microcode/Software Revision Matrix - Continued
------------+--------------------+--------------------+--------------------+--------------------+
Component | Creation Date/ | Creation Date/ | Creation Date/ | Creation Date/ |
Name | Notes | Notes | Notes | Notes |
------------+--------------------+--------------------+--------------------+--------------------+
| RELEASE DATE | RELEASE DATE | RELEASE DATE | RELEASE DATE |
| AUGUST 9, 1990 | AUGUST 20, 1990 | SEPTEMBER 4, 1990 | OCTOBER 12, 1990 |
------------+--------------------+--------------------+--------------------+--------------------+
CIXCD.BIN | AUGUST 9, 1990 | AUGUST 16, 1990 | SEPTEMBER 4, 1990 | SEPTEMBER 4, 1990 |
| FUNCTIONAL V0.22 | V1.0 | V1.04 | V1.04 |
| SELF TEST V0.38 | | | |
------------+--------------------+--------------------+--------------------+--------------------+
ELSAA.EXE | JULY 17, 1990 | JULY 17, 1990 | JULY 17, 1990 | JULY 17, 1990 |
| X13.2-2008 | X13.2-2008 | X13.2-2008 | X13.2-2008 |
------------+--------------------+--------------------+--------------------+--------------------+
ERSAA.EXE | JULY 6, 1990 | JULY 6, 1990 | JULY 6, 1990 | JULY 6, 1990 |
| X13.1-893 | X13.1-893 | 13.1-893 | 13.1-893 |
------------+--------------------+--------------------+--------------------+--------------------+
EWSAA.EXE | JUNE 13, 1990 | AUGUST 17, 1990 | AUGUST 17, 1990 | AUGUST 17, 1990 |
| X13.0-1144 | 13.2-1221 | 13.2-1221 | 13.2-1221 |
------------+--------------------+--------------------+--------------------+--------------------+
EVGEA.BIN | APRIL 4, 1990 | APRIL 4, 1990 | APRIL 4, 1990 | APRIL 4, 1990 |
| V0.01 | V0.01 | V0.01 | V0.01 |
------------+--------------------+--------------------+--------------------+--------------------+
EVGEA.EXE | JULY 10, 1990 | AUGUST 14, 1990 | AUGUST 14, 1990 | AUGUST 14, 1990 |
| V2.0 | V2.1 | V2.1 | V2.1 |
------------+--------------------+--------------------+--------------------+--------------------+
EVGEA.HLP | JULY 16, 1990 | AUGUST 14, 1990 | AUGUST 14, 1990 | AUGUST 14, 1990 |
| N/A | N/A | N/A | N/A |
------------+--------------------+--------------------+--------------------+--------------------+
EVGEB.EXE | JULY 16, 1990 | JULY 16, 1990 | JULY 16, 1990 | JULY 16,1990 |
| V2.0 | V2.0 | V2.0 | V2.0 |
------------+--------------------+--------------------+--------------------+--------------------+
EVGEB.HLP | JULY 16, 1990 | JULY 16, 1990 | JULY 16, 1990 | JULY 16, 1990 |
| N/A | N/A | N/A | N/A |
------------+--------------------+--------------------+--------------------+--------------------+
EVGAA.EXE | JULY 18, 1990 | JULY 18, 1990 | JULY 18, 1990 | OCTOBER 12, 1990 |
| V6.1 | V6.1 | V6.1 | V6.3 |
------------+--------------------+--------------------+--------------------+--------------------+
EVGAB.EXE | JULY 18, 1990 | JULY 18, 1990 | JULY 18, 1990 | OCTOBER 12, 1990 |
| V6.1 | V6.1 | V6.1 | V6.3 |
------------+--------------------+--------------------+--------------------+--------------------+
EVGAC.EXE | JULY 18, 1990 | JULY 18, 1990 | JULY 18, 1990 | OCTOBER 12, 1990 |
| V1.1 | V1.1 | V1.1 | V1.2 |
------------+--------------------+--------------------+--------------------+--------------------+
VMB.EXE | | | | |
| | | | |
------------+ | | | |
PADRIVER.EXE| VMS VERSION | VMS VERSION | VMS VERSION | VMS VERSION |
| | | | |
------------+ T5.4-4HW | T5.4-4HW | V5.4 | V5.4 |
SYSLOA9CC. | | | | |
EXE | JULY 11, 1990 | JULY 11, 1990 | AVAILABLE | AVAILABLE |
------------+ | | | |
SYSLOA9RR. | AVAILABLE FROM VMS | AVAILABLE FROM VMS | FROM VMS | FROM VMS |
EXE | | | | |
------------+--------------------+--------------------+--------------------+--------------------+
HSC CODE | HSC50 - V39B | HSC50 - YB02 | HSC50 - V400 | HSC50 - V400 |
| HSC70 - Y50D | HSC70 - Y50D | HSC70 - Y50A | HCS70 - Y50A |
------------+--------------------+--------------------+--------------------+--------------------+
HYPERION. | MAY 10, 1990 | MAY 10, 1990 | MAY 10, 1990 | MAY 10, 1990 |
EEPROM | V4.E | V4.E | V4.E | V4.E |
------------+--------------------+--------------------+--------------------+--------------------+
CALYPSO. | MAY 10, 1990 | MAY 10, 1990 | MAY 10, 1990 | MAY 10, 1990 |
EEPROM | V3.D | V3.D | V3.D | V3.D |
------------+--------------------+--------------------+--------------------+--------------------+
RIGEL. | MAY 7, 1990 | MAY 7, 1990 | MAY 7, 1990 | MAY 7, 1990 |
EEPROM | V1.FE | V1.FE | V1.FE | V1.FE |
------------+--------------------+--------------------+--------------------+--------------------+
DIAGBOOT. | | AUGUST 17, 1990 | AUGUST 17, 1990 | AUGUST 17, 1990 |
EXE | | N/A | N/A | N/A |
------------+--------------------+--------------------+--------------------+--------------------+
CHANGES AS OF OCTOBER 12, 1990
EVGAA, EVGAB, EVGAC - SOME PROBLEMS WERE FOUND WHILE RUNNING THESE DIAGNOSTICS
ON THE VAX 9000.
CURRENT KNOWN PROBLEMS:
VDS WILL NOT BOOT CORRECTLY THROUGH THE CIXCD WHEN THE NODE SPECIFICATION IN THE
BOOT STRING CONTAINS A FAILOVER CI ADDRESS. IT WILL BOOT, ONLY WHEN THE CORRECT
HSC NODE IS IN BITS <15:8>, NOT WHEN THE HSC NODE IS IN BITS <7:0>.
ALL CIXCDS CURRENTLY IN USE MUST BE UPDATED WITH THE LATEST MICROCODE VERSION.
QARs POSTED AGAINST PREVIOUS VERSIONS WILL BE ANSWERED "MICROCODE OUT OF REV"
AND CLOSED.
ON 6000 SERIES MACHINES, THE CIXCD WILL ONLY OPERATE IN SLOTS 1-4, AND B-E
WHEN INSTALLING THE HEADER ASSEMBLY, MAKE SURE ALL THE PINS ARE PLUGGED
INTO THE CONNECTOR. THE CONNECTORS ARE NOT KEYED, IT IS POSSIBLE TO PLUG
THE HEADER CARD IN ONE POSITION TO HIGH OR LOW.
IN THE XDEV REG. <24:16>, THE FORMAT OF THIS FIELD HAS CHANGED AND MUST BE
REPORGRAMMED WITH THE SECTION OF INIT_DCB OF EVGEA. THE OLD FORMAT DISPLAYED AN
E02 MODULE AS "A2", THE NEW FORMAT WILL DISPLAY AN E02 MODULE AS "52".
DEFINITIONS
-----------------------------
CIXCD.BIN = MICROCODE FILE
ELSAA.EXE = CALYPSO DIAGNOSTIC SUPERVISOR
ERSAA.EXE = RIGEL DIAGNOSTIC SUPERVISOR
EWSAA.EXE = ARIDUS DIAGNOSTIC SUPERVISOR
EVGEA.BIN = CIXCD REPAIR LEVEL DIAGNOSTIC TEST MICROCODE
EVGEA.EXE = CIXCD REPAIR LEVEL DIAGNOSTIC / LOADER PROGRAM
EVGEA.HLP = CIXCD REPAIR LEVEL DIAGNOSTIC VDS HELP FILE
EVGEB.EXE = CIXCD MICROCODE LOAD UTILITY
EVGEB.HLP = CIXCD MICROCODE LOAD UTILITY VDS HELP FILE
EVGAA.EXE = CI FUNCTIONAL DIAGNOSTIC, PART 1
EVGAB.EXE = CI FUNCTIONAL DIAGNOSTIC, PART 2
EVGAC.EXE = CI MULTI-NODE DIAGNOSTIC
VMB.EXE = BOOT PRIMITIVE
PADRIVER.EXE = CIXCD PORT DRIVER
SYSLOA9CC.EXE = CALYPSO SPECIFIC LOAD/INIT/HANDLER ROUTINES
SYSLOA9RR.EXE = RIGEL SPECIFIC LOAD/INIT/HANDLER ROUTINES
HYPERION.EEPROM= HYPERION CPU EEPROM MICROCODE PATCH FILE
CALYPSO.EEPROM = CALYPSO CPU EEPROM MICROCODE PATCH FILE
RIGEL.EEPROM = RIGEL CPU EEPROM MICROCODE PATCH FILE
DIAGBOOT.EXE = DIAGNOSTIC BOOTSTRAP FILE
| |||||
| 114.6 | KERNEL::WRIGHTON | odd numbered release = bug insert | Thu Nov 29 1990 19:42 | 362 | |
___ ___ ___ ___ ___ ___ ___
| | | | | | | |
| d | i | g | i | t | a | l | I N T E R O F F I C E M E M O
|___|___|___|___|___|___|___|
To: Distribution Date : November 28, 1990
From : Joe Mellone
Dept : ISB
Ext : 297-4682
Loc/MS : MR01-2 S10/KL18.6
Enet : IOENG::MELLONE
SUBJECT: CIXCD Software Release Area Update Notification
COMPONENT CHANGES SINCE LAST RELEASE :
EVGAA.EXE, EVGAB.EXE, EVGAC.EXE :
Some problems were found while running these diagnostics on the
9000. Please note that the revision information displayed when
running the diagnostics does not include the 'Pre-Release '
message. For instance, the official version of EVGAA is now
version 6.2 whereas the previous version of EVGAA was
'Pre-Release Version 6.3'. A less confusing scheme will be
employed in subsequent releases.
EVGEA.EXE, EVGEA.HLP, EVGEB.EXE, EVGEB.HLP :
** WARNING **
These versions of the diagnostics impact (Pre-Rev E) modules.
Please read the appended EVGEA/EVGEB Functional Notes section
that I have appended to the end of this notice. Read it
completely so that you will know how to run the new diagnostics
on the Previous Rev E modules and know what new functionality
is present.
CIXCD.BIN :
Some microcode problems were found during CVG testing. This
version of microcode has been submitted to SDC for Release 42,
available January 14, 1991.
COMPONENT CREATION DATE VERSION NUMBER
--------- ------------- -----------------------------
>CIXCD.BIN 01-NOV-1990 V1.09
ELSAA.EXE 16-JUL-1990 X13.2-2008
ERSAA.EXE 06-JUL-1990 13.1-893
EWSAA.EXE 17-AUG-1990 13.2-1221
DIAGBOOT.EXE 17-AUG-1990 n/a
EVGEA.BIN 04-APR-1990 V0.01
>EVGEA.EXE 26-OCT-1990 V3.0
>EVGEA.HLP 26-OCT-1990 n/a
>EVGEB.EXE 29-OCT-1990 V3.0
>EVGEB.HLP 30-OCT-1990 n/a
>EVGAA.EXE 03-NOV-1990 V6.2
>EVGAB.EXE 04-NOV-1990 V6.2
>EVGAC.EXE 04-NOV-1990 V1.2
VMS V5.4 24-AUG-1990 Available from VMS
HYPERION.EEROM 10-MAY-1990 V4.E
CALYPSO.EEROM 10-MAY-1990 V3.D
RIGEL.EEROM 07-MAY-1990 V1.FE
---------------------------------------------------------
>=New version
AREA ACCESS PROCEDURE :
A software release area is available which contains all of
the required CIXCD software components, needed for diagnostic
and functional operations. The below listed files can be
retrieved by using the following procedure call:
$ @IOENG::XMVDSK:[CIXCD.DIAG]RETRIEVE
The 'retrieve' procedure will prompt you for the destination
directory and whether you want diagnostic or operational
files. If the destination directory is not specified, the
procedure will use your default directory. If diagnostic
or operational is not specified, all files will be retrieved.
A new feature was added to the retrieve procedure, which allows
the copy of just a single file. Use the 's' option when prompted
for diagnostic, operational or single files.
COMPONENT DESCRIPTIONS :
CIXCD.BIN = Microcode file
ELSAA.EXE = Calypso/Hyperion Diagnostic Supervisor
ERSAA.EXE = Rigel Diagnostic Supervisor
EWSAA.EXE = Aridus Diagnostic Supervisor
DIAGBOOT.EXE = Diagnostic bootstrap file
EVGEA.BIN = CIXCD Repair Level Diagnostic Test Microcode
EVGEA.EXE = CIXCD Repair Level Diagnostic / Loader Program
EVGEA.HLP = CIXCD Repair Level Diagnostic VDS Help File
EVGEB.EXE = CIXCD Microcode Load Utility
EVGEB.HLP = CIXCD Microcode Load Utility VDS Help File
EVGAA.EXE = CI Functional Diagnostic (part 1)
EVGAB.EXE = CI Functional Diagnostic (part 2)
EVGAC.EXE = CI Multi-Node Diagnostic
HYPERION.EEROM = Hyperion CPU eeprom microcode patch file
CALYPSO.EEROM = Calypso CPU eeprom microcode patch file
RIGEL.EEROM = Rigel CPU eeprom microcode patch file
CURRENT KNOWN PROBLEMS :
VDS will not boot correctly through the CIXCD when the
NODE specification in the boot string contains a failover
CI address. It will boot, only when the correct HSC node is
in bits 15:8, not when the correct HSC node is in bits 7:0.
INSTALLATION/USAGE NOTES:
All CIXCDs currently in use must be updated with the latest
microcode version. QARs posted against previous versions
will be answered "microcode out-of-rev" and closed.
On 6000 series machines, the CIXCD will only operate in slots
1-4 and B-E.
When installing the header assembly, needed for Rev E modules,
make sure that all pins are plugged into the connector. The
connectors are not keyed, and it is possible to plug the header
card in one position to high or one position to low.
Take note of the hardware revision held in XDEV<24:16>. The
format of this field has changed and must be reprogrammed with
section init_dcb of EVGEA. The old format displayed an E02 module
as "A2", the new format will display an E02 module as "52".
HYPERION/CALYPSO/RIGEL.EEROM CPU MICROCODE FILES :
Three files have been added to the directory. These files can be
used to patch the cpu microcode on the respective processor. This
updated cpu microcode will enable the cpu to recognize the CIXCD
as a valid I/O device, thus allowing the CIXCD to function as the
primary boot device.
A command procedure "CREATE_EEROM_TAPE.COM" can be used to create
a patch tape for the respective processor. This procedure is located
in the release area for general use.
EVGEA/EVGEB Functional Notes
The latest version of EVGEA/B has hardware EEPROM data protection
ENABLED as the default. This was done to provide an additional
level of EEPROM data protection. While that sounds like "APPLE_PIE",
it may have an impact on you.
With rev "E" hardware functionality, all the EEPROM's will support
hardware EEPROM data protection. On these boards, the new program
versions will work correctly. The problem comes if the microcode
in the modules are loaded with V3 and then someone attempts to use
V2.0/V2.1 UPDATE the microcode. The V2.0/V2.1 will fail to update
the microcode and will report errors.
With prior to "E" hardware functionality, not all the EEPROM's support
hardware EEPROM data protection. On these boards, the new program
versions will not work correctly. The problem comes when the microcode
is updated with EVGEA/B V3 and EVENT FLAG 3 is cleared, the program will
default to issuing a 'write-thru' data protection sequence to update
the EEPROM's. This will cause EEPROM data corruption of some addresses.
I have added support for 'EVENT FLAG 3' in V3 to allow the bypass of
the 'write-thru' feature of V3 to support these earlier boards. With
EVENT FLAG 3 set, the software EEPROM data protection will be disabled.
This is more a workaround than a fix to support these older modules.
There have been two new sections added to both EVGEA/B to support
the hardware EEPROM data protection. These sections are LOCK and
UNLOCK and are only to be used with rev "E" hardware functionality.
The UNLOCK section will be the way to DISABLE the hardware EEPROM
data protection feature. Once this section is executed, the operator
is required to removed the power from the CIXCD to complete the
UNLOCKing function.
Below is a copy of the "EVGEB.HLP" file (Sorry for the strange
looking file format but that is the VDS formatting).
EVGEB.HLP :
1 ATTACH
The CPU (KA0) and/or SBIA 0 (SI0) and/or SBIA 1 (SI1) must be
attached:
DS> ATTACH CIXCD HUB PAA0 (1) (2)
(1) CIXCD node address, Hex
(2) CI node number, Hex
1 HELP
Help information for EVGEB, revision 3.0
EVGEB is a Level 3 Repair Level utility designed to provide
Update and Verification functions for the CIXCD EEPROM.
1 SECTIONS
Sections have been allocated to provide certain functions.
2 UPDATE
This section is used to load the contents of the EEPROM from a
MICROCODE binary file on the load media.
2 VERIFY
This section is used to verify the contents of the EEPROM
against a MICROCODE binary file on the load media.
2 RVERIFY
This section is used to verify the contents of the Primary
EEPROM region against the Backup EEPROM region. No load media
file is used.
2 REPLACE
This section is used to replace the contents of the BACKUP
EEPROM regions by copying the PRIMARY regions into the BACKUP
regions of the EEPROM. No load media file is used.
2 RESTORE
This section is used to restore the contents of the PRIMARY
EEPROM regions by copying the BACKUP regions into the PRIMARY
regions of the EEPROM. No load media file is used.
2 DEFAULT
Same as UPDATE section
2 RBD
This section is used to enable the operator to enter RBD mode
to test the CIXCD.
2 ERRORLOG
This section is used to examine the ERRORLOG header information
stored in the EEPROM.
2 EXAM
This section is used to examine the ERRORLOG data entry stored
in the EEPROM.
2 UNLOCK
This section is used to disable or UNLOCK the hardware data
protection of the data stored in the EEPROM.
***WARNING*** ***WARNING*** ***WARNING***
DO NOT EXECUTE THIS SECTION ON CIXCD MODULES BEFORE HARDWARE REVISION "E"
***WARNING*** ***WARNING*** ***WARNING***
2 LOCK
This section is used to enable or LOCK the hardware data
protection of the data stored in the EEPROM.
***WARNING*** ***WARNING*** ***WARNING***
DO NOT EXECUTE THIS SECTION ON CIXCD MODULES BEFORE HARDWARE REVISION "E"
***WARNING*** ***WARNING*** ***WARNING***
1 EVENT
Event flag 1
Not used in EVGEB
Event flag 2
INHIBITS failing test information to be loaded into
the on-board CIXCD EEPROM.
Event flag 3
INHIBITS executing the hardware write-thru feature of
loading into the on-board CIXCD EEPROM. This flag should
be set BEFORE ANY attempt to load microcode into a
CIXCD BEFORE HARDWARE REVISION "E".
WARNING: You may have already 'SHOT-YOUR-SELF-IN-THE-FOOT'
and corrupted the EEPROM data.
Event flags 4 through 5 are not active with this program.
1 SUMMARY
The summary gives a report of the program and supervisor
detected errors.
1 V3
1. Two additional sections have been added (LOCK and UNLOCK) to support
hardware data protection of the EEPROM data.
***WARNING*** ***WARNING*** ***WARNING***
DO NOT EXECUTE THESE SECTIONS ON CIXCD MODULE BEFORE HARDWARE REVISION "E"
***WARNING*** ***WARNING*** ***WARNING***
2. Default is to enable hardware data protection of the EEPROM data.
(See EVENT flag 3 description for a workaround)
If version 3.0 is executed on CIXCD BEFORE HARDWARE REVISION "E"
without EVENT flag 3 set, the EEPROM data will be corrupted since
hardware support of EEPROM data protection logic is not complete
on previous hardware revisions.
HINT: a. If after you update the CIXCD microcode and then attempt to
run EVGEA logic tests, Test 1 will pass but Test 2 (EEPROM
region Checksum) Subtest 1 and/or Test 5, Subtest 1 fails.
or
b. The VERIFY section fails (the 'give-away' is that the high
order bits of the Xored CS EEPROM bad pattern will be the
ones in error).
DS> START/SECTION=VERIFY
******** EVGEB CIXCD EEPROM update - Level 3 Diag - 3.0 ********
Pass 1, test 2, subtest 0, error 6, 17-OCT-1990 09:16:19.26
Hard error while testing PAZ0: EEPROM region data did not
VERIFY correctly
Xored CS EEPROM = 00200000 00000000 00000000
Reading CS EEPROM = 0020D057 00400000 0000FF00
Verify ucode file = 0000D057 00400000 0000FF00, Loc 1FD5
******** End of Hard error number 6 ********
DS>
WORKAROUND FIX for corrupted EEPROM data prior to rev "E"
1. Clear EVENT flag 3
2. Start section UNLOCK to disable hardware data protection
3. Power down the CIXCD ***MUST****
4. Power up the CIXCD
5. Boot VDS, LOAD EVGEA or EVGEB, SET EVENT FLAG 3
6. START/SECTION=UPDATE and re-load the microcode file
1 XMI_UPDATE
On VAX 6000 based machines, the front panel switch should
be placed in the "UPDATE" postion during this program
execution.
On VAX 9000 based machines, the operator must issue a console
command to set hardware XMI_UPDATE enable signal. ie:
DS>^P !Exit VDS and enter 9000 console mode
>>>SHOW XMI_UPDATE !Display XMI_UPDATE off/on status
>>>SET XMI_UPDATE ON !Set XMI_UPDATE status to ON
>>>SHOW XMI_UPDATE !Display XMI_UPDATE off/on status
>>>CONT !Exit 9000 console mode and enter VDS
DS> !Now back at VDS awaiting a command
| |||||
| 114.7 | CIXCD microcode 1.09 now available | KERNEL::BLAND | toward 2000 ... | Mon Feb 04 1991 20:57 | 7 |
All CIXCD's should now be running microcode version 2.09; this will
show up as 29 in bits 24:31 of the XDEV register. The CICXD.BIN
with this revision is available on VAXPAX 42, tape #1. There is
a STARS article "CIXCD microcode 1.09 is now available" that is
worth looking at.
Norman
| |||||
| 114.8 | new ucode available | KERNEL::WRIGHTON | A +L-14005 is all you need ! | Tue Feb 05 1991 03:55 | 7 |
The latest version of ucode (mentioned by Norman in the previous
note) can be found in ...
RSDS$DISK:[BASINGSTOKE.9000.UCODE]CIXCD_109.BIN
Dave
| |||||
| 114.9 | KERNEL::MOUNTFORD | Thu Mar 28 1991 12:50 | 21 | ||
Moved by moderator.
<<< KERNEL::DISK$APD1:[NOTES$LIBRARY]CSGUK_SYSTEMS.NOTE;1 >>>
-< CSGUK_SYSTEMS >-
================================================================================
Note 134.0 CIXCD's with different DEV TYPE register contents 1 reply
KERNEL::BLAND "toward 2000 ..." 13 lines 26-MAR-1991 16:02
--------------------------------------------------------------------------------
Can someone explain what the difference is between 2 CICXD modules with
the following device type reister contents.
29FF0C05
==
29530C05
==
There appears to be some incompatability between modules with the
different device register contents on systems with dual CI's.
Norman.
| |||||
| 114.10 | KERNEL::MOUNTFORD | Thu Mar 28 1991 12:50 | 47 | ||
Moved by moderator.
<<< KERNEL::DISK$APD1:[NOTES$LIBRARY]CSGUK_SYSTEMS.NOTE;1 >>>
-< CSGUK_SYSTEMS >-
================================================================================
Note 134.1 CIXCD's with different DEV TYPE register contents 1 of 1
KERNEL::BLAND "toward 2000 ..." 38 lines 27-MAR-1991 20:43
-< CIXCD DEV TYPE REG explained >-
--------------------------------------------------------------------------------
OK, I can partially answer my own question.
CIXCD Device Type Register.
3 2 2 2 2 2 1 1 1 1 1 0 0 0 0 0
1 8 7 4 3 0 9 6 5 2 1 8 7 4 3 0
+----+----+----+----+----+----+----+----+
| | | | | | | | |
+----+----+----+----+----+----+----+----+
|Firmware |Hardware | Class | ID |
| REV | REV | | |
| DEVICE | DEVICE |
| REV | TYPE |
31:24 Firmware revision (RO)
Identifies firmware revision of CIXCD (currently 29 hex) rev
1.09
23:16 Hardware revision (RO)
Indicates hardware revision of CIXCD (currently 53) rev E3
15:08 Class
Indicates category in which node falls (0C)
<15> CPU device
<14> Memory device
<13> Bus window (I/O)
<12> Bus window (memory)
<11> I/O device
<10> XCOMM register present
07:00 ID
Uniquely identifies particular device within a specified
class (05)
| |||||
| 114.11 | KERNEL::SCOTT | you can trust a teddy bear | Fri May 17 1991 01:46 | 2 | |
Latest rev of firmware is 2.02. If you do SHO CLUS/CON and
ADD RP_REV it will be 42 with this firmware installed
| |||||
| 114.12 | KERNEL::WRIGHTON | A +L-14005 is all you need ! | Fri May 17 1991 12:20 | 7 | |
The latest version is in
RSDS$DISK:[BASINGSTOKE.9000.UCODE]CICXD_V202.BIN
Dave
| |||||
| 114.13 | latest version, V203 | KERNEL::WRIGHTON | A +L-14005 is all you need ! | Tue Jun 25 1991 18:24 | 32 |
The latest version of CIXCD microcode is available in
RSDS$DISK:[BASINGSTOKE.9000.UCODE]. It is called CIXCD_V203.BIN.
V203 has changes to accomodate a timing problem identified with the
introduction of the XJA rev D05. It has been determined that XJA rev
D05 and CIXCD ucode rev 202 and below are incompatible. Vax9000's with
XJA's at D05 and CIXCD's should be updated to 203
A dump of the header is shown below.
Dave W
Dump of file $44$DUS21:[BASINGSTOKE.9000.UCODE]CIXCD_V203.BIN;1 on 25-JUN-1991 15:08:23.14
File ID (7317,20,0) End of file block 353 / Allocated 354
Virtual block number 1 (00000001), 512 (0200) bytes
70697571 45206C61 74696769 44202963
28207468 67697279 706F4320 0A0A0D99 .... Copyright (c) Digital Equip 000000
74686769 72206C6C 41202E30 39393120
6E6F6974 61726F70 726F4320 746E656D ment Corporation 1990. All right 000020
6D726946 20636974 736F6E67 61694420
0A0A0D20 202E6465 76726573 65722073 s reserved. ... Diagnostic Firm 000040
206C616E 6F697463 6E754620 2C203933
2E30206E 6F697369 76655220 65726177 ware Revision 0.39 , Functional 000060
20202020 20200A0A 0D203330 2E32206E
6F697369 76655220 65726177 6D726946 Firmware Revision 2.03 ... 000080
20202020 20202020 20202020 20202020
20202020 20362E38 56205043 55444358 XCDUCP V8.6 0000A0
| |||||
| 114.14 | VMS V5.4-3 ROLLING UPGRADE PROBLEM | KERNEL::BLAND | I wanna be a slug | Mon Oct 07 1991 10:55 | 137 |
Author : RODNEY BOYLE
User type : PFE
Location : CSSE
Vaxmail address : CSSE::BOYLE
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT CASE
| | | | | | | |
+---------------------------+
Title/Problem Summary: Restriction for VMS V5.4-3 in
VAXcluster Configurations
Containing CIXCD Adapters
DATE: October 3, 1991
AUTHOR: Paul Lacombe TD #: 000835
DTN: 381-1697
ENET: VMSSPT::Lacombe CROSS REFERENCE #'s:
DEPARTMENT: VMS/CSSE Engineering (SPR's, CLD's, TD's)
INTENDED AUDIENCE: U.S./EUROPE/GIA PRIORITY LEVEL: 1
(1 = Time Critical,
2 = NON-Time Critical)
See attachment below
for additional info.
---------------------------------------------------------------------
Author Identification:
----------------------
Name : Jason Gallant
DTN : 381-2358
Mail Stop : ZKO1-1/F22
E-net: CSSE32::GALLANT
Department : CSSE/VMS
Article Identification:
-----------------------
Title/Problem Summary: Restriction for VMS V5.4-3 in VAXcluster
Configurations Containing CIXCD Adapters
Operating System/Layered Product: VMS
Component/Utility: VMS Version 5.4-3
Version Information: VMS Version 5.4-3
Is the problem reproducible at will?: Yes
DETAILED Problem Information:
-----------------------------
A problem exists in a mixed version cluster environment after
performing a rolling Update to VMS V5.4-3. The problem occurs with
VAXClusters that have more than one node containing CIXCDs and
at least two nodes that contain CIXCD adapters that boot from
different system disks. After updating one of the CIXCD nodes to
V5.4-3 and rebooting the node back into the cluster; the remaining
nodes with CIXCDs running V5.4-2 or earlier will crash.
In VMS V5.4-3, RDP (Resequencing Dual Path) functionality has been
turned on. In V5.4-2 and earlier versions, RDP functionality is
turned off. When running together in a mixed cluster with CIXCDs,
the system crashes with a VAXPORT BUGCHECK on all non-RDP CIXCD
nodes.
Hardware configuration specifics :
VAXcluster containing more than one node with a CIXCD Adapter.
CIXCD Adapters are currently supported on VAX 6000 and VAX 9000
hardware platforms.
Potential Impact on System Operation :
CI packets are delivered out of sequence, typically resulting
in a VAXPORT bugcheck on all non RDP-speaking CIXCD nodes.
Frequency of Occurrence : All the time.
DETAILED Resolution Information:
--------------------------------
Problem Resolution/Work-around Description :
Digital recommends that, for systems in this configuration,
you update all systems to VMS V5.4-3 at the same time.
When is the final fix expected (Version/Timeframe)? :
More information will follow in a future memo.
Can the fix be engineered/applied to any previous
versions? If so - when? : N/A
Installation Instructions :
Additional Comments :
A customer letter was included only in the Customer Update (CU)
V5.4-3 kits. The letter states the following:
"Digital does not support performing a rolling update to
VMS V5.4-3 in a VAXcluster configuration that includes at least
two systems with CIXCD adapters if the systems with CIXCD adapters
boot from seperate system disks ( that is, do not boot from a
common disk).
Digital recommends that, for systems in this configuration, you
update all systems to VMS V5.4-3 at the same time."
*** DIGITAL INTERNAL USE ONLY ***
---------------------------------------------------------------------
| |||||
| 114.15 | CIXCD EEPROM LOADER EVGEA | KERNEL::BLAND | I wanna be a slug | Mon Oct 14 1991 12:01 | 136 |
Author : RODNEY BOYLE
User type : PFE
Location : CSSE
Vaxmail address : CSSE::BOYLE
+---------------------------+
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT CASE
| | | | | | | |
+---------------------------+
TITLE: CIXCD EEPROM LOADER EVGEA
DATE: October 10, 1991
AUTHOR: Bob Aston TD #: 000847
DTN: 297-4851
ENET: MRCSSE::ASTON CROSS REFERENCE #'s:
DEPARTMENT: HIGH-END SYSTEMS CSSE (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: ALL PRIORITY LEVEL: 1
(U.S./EUROPE/GIA) (1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
OVERVIEW:
This BLITZ will address the new CIXCD MICROCODE loader/Diagnostics
EVGEA and EVGEB.
PROBLEM:
CIXCD Revision E04 and below contained XICOR EEPROMS for Microcode
retention during power down. This Microcode was then down line loaded
into the faster RAMS after power up and test for faster execution.
A problem was found with the EEPROMS used on the CIXCD. The problem
was seen as a single cell charge loss at random times and in random
EEPROMS and locations.
These EEPROMS have been replaced with FLASHPROMS which have a much
higher reliability then the EEPROMS. These FLASHPROM CIXCDs will
be released of CIXCD HARDWARE REVISION E06. The Flashproms builds
have superceded the EEprom builds on the CIXCD module. Both
versions of CIXCD will be supported.
With the release of CIXCD E06, there will be 2 types of CIXCDs in
use, the FLASHPROM and EEPROM. It is for this reason that a NEW
versions of EVGEA and EVGEB were created to handle both types of
Proms that will be in use without assistance from the operator.
Chracteristics of both are quite different and will not be
addressed in this BLITZ.
********************************************************************
* DANGER: *
* EVGEA AND EVGEB VERSION 2.1, 3.1 AND A SECTION IN 4.0 CAN CAUSE *
* PHYSICAL DAMAGE TO CIXCD MODULES WITH FLASHPROMS. *
* *
* DO NOT USE VERSION 2.1 OF EVGEA OR EVGEB WITH CIXCD REV E06 OR *
* HIGHER. *
* *
* DO NOT USE EVENT FLAG 3 WITH VERSIONS 3.1 OR 4.0 OF EVGEA OR *
* EVGEB. SETTING EVENT FLAG 3 IN VERSION 4.0 WILL CAUSE DAMAGE *
* TO THE MODULE. *
* *
* DETAILS OF THE REASON AND RESULT ARE LISTED BELOW. *
* *
********************************************************************
EVGEA 2.1
This revision of EVGEA and EVGEB does not know about FLASHPROM
memory. When either the loader or the errorlogger tries to write
data into FLASHPROM memory it is very likely that permanent damage
will result. Some data patterns will cause parts to erase. The retry
logic of the diagnostic erases the part until it is destroyed,
in short, an excess charge is built up during this retry function. Use
the UPDATE switch to prevent any writes. Update to the latest
revision ASAP.
EVGEA 3.1
Event flag 3 makes this version behave like revision 2.1. There is
no reason to set Event Flag 3 any more. This will destroy FRASHPROM
parts. This revision will not write FLASHPROM memory. Update to the
latest revision ASAP.
EVGEA 4.0
Event flag 3 makes this version behave like revision 2.1. There is
no reason to set Event Flag 3 any more. This will destroy FRASHPROM
parts. This revision was designed to program EEPROM and FLASHPROM
memories. Update to the latest revision ASAP.
QUICK CHECK:
CIXCD revisions prior to E06 contain EEPROMs.
The CIXCD XDEV Register will contain a value of 53 or below in the
hardware revision. Example: 43530C05 where 43 is the code revision,
53 is the module (E03) hardware revision and 0C05 is the module
type.
CIXCD revision E06 contains FLASHPROM.
The CIXCD XDEV Register will contain a value of 56 in the
hardware revision signifying it is revision E06.
Workaround:
Use EVGEA 4.0 and EVGEB 4.0 to test and load all CIXCD modules. DO NOT
SET EVENT FLAG 3 in rev 3.1 and 4.0. If you must use an older
version of EVGEA OR EVGEB to test a flash board, make sure the
UPDATE switch is OFF. This will prevent errorlogs from being written
to the prom destroying parts.
**PLEASE NOTE, THE OLD VERSION OF THE LOADERS WILL NOT WORK WITH THE
FLASHPROM VERSION OF THE CIXCD. THE CODE MUST BE LOADED INTO THE
MODULE USING THE NEW VERSIONS OF THE LOADERS.**
Long Term fix:
EVGEA 4.1 and EVGEB 4.1 diagnostics will be distributed through the
normal SSB release process and prevent this type of damage.
Version 4.1 will be available in Jan. of 1991. At present, version
4.0 will work today, PROVIDED event flag 3 is NOT SET.
*** DIGITAL INTERNAL USE ONLY ***
| |||||
| 114.16 | CIXCD-AC Ucode version 46 | KERNEL::BLAND | Norman Bland 833 3797 CSC, Basingstoke | Fri Nov 13 1992 06:07 | 7 |
CIXCD microcode version 46 (required for CIXCD-AC) has been released
with VAXPAX RELEASE 49 DIAGNOSTICS.
NOTE: You will see in some documemtation for LASER version 70 referred
to; (70 DECIMAL = 46 HEX).
Norman B
| |||||