ALPHA Firmware Update Seminar By Wes Gulden Diagnose Before Dispatch Colorado Springs CSC Wesley.Gulden@Compaq.Com Version 6.
ii
iii
iv
Revision History / Change List for Alpha Firmware Update Seminar. With every change to the document the title page will be modified to reflect current version and date. Page numbers listed on a specific revision may not be accurate on later versions of the document. 03-Mar-1999 - Version 5.3 Rev 1 28-Feb-1999 the printed doc and the 03-Mar-1999 electronic document are the same. 06-Mar-1999 - Version 5.3 Rev 2 Added V4.4 (vax7000_s0f) firmware version to VAX 7000 model 800 (page 10) 12-Mar-1999 - Version 5.
07-May-1999 – Version V5.4 Rev 1 Added Compaq AlphaServer DS20 section (pages 109-116) Added Compaq AlphaServer ES40 section (pages 117-122) 12-May-1999 – Version V5.4 Rev 1 Final revision. Printed copy of V5.4 Rev 1. 14-May-1999 – Version V5.4 Rev 2 Removed "on each CPU" from Build -e line on AlphaServer 1200 and 4100 (pages 61 and 85) Changed SRM version from 5.4-1 to 5.4-2 on the AlphaServer 1200 and 4x00 (pages 5 and 6) 15-May-1999 – Version V5.
17-Sep-1999 - Version V5.5 Rev 1 Completed section on environmental variables. Moved sections concerning environmental variable. 19-Sep-1999 - Version V5.5 Rev 1 Add wwidmgr sections 24-Sep-1999 - Version V5.5 Rev 1 Add ES40 and DS20 failsafe loader sections 26-Sep-1999 - Version V5.5 Rev 1 Added section on Galaxy environmental variables. 03-Oct-1999 - Version V5.5 Rev 1 Updated ES40 failsafe loader section 05-Oct-1999 - Version V5.
22-Feb-2000 - Version V5.6 Rev 1 Modify DS20 failsafe loader page 24-Feb-2000 - Version V5.6 Rev 1 Modify the Galaxy firmware update procedure page Add more to the Galaxy environmental variable definition page Modify the DS10 update using LFU 04-Mar-2000 - Version V5.6 Rev 1 Added ES40/RMC firmware page 10-Mar-2000 - Version V5.6 Rev 1 Modified ES40/RMC firmware page 14-Mar-2000 - Version V5.6 Rev 1 Added GS60/GS60E/GS140 Blitz TD 2766 17-Mar-2000 - Version V5.
Started GS80/GS160/GS320 section 16-Jul-2000 - Version V5.7 Rev 3 Added lp_error_target variable to the Galaxy variable page. Continued modifying the GS80/GS160/GS320 section 01-Aug-2000 – Version V5.8 Rev 1 Added V5.8 versions to firmware tables 15-Aug-2000 – Version V5.8 Rev 2 Restored missing images and tables throughout the document 29-Aug-2000 – Version V5.8 Rev 2 Modified top and bottom margins from .7" to .5" 29-Aug-2000 – Version V5.8 Rev 2 Updated filenames and versions to reflect newer V5.
24-May-2001 – Version V5.9 Rev 3 Modified Turbolaser build –e command. Added DS10 blitz 31-May-2001 – Version V6.0 Rev 1 Updated document to include the V6.0 filenames and versions 01-Jun-2001 – Version V6.0 Rev 1 Added ES45 to jumpers page Modified DEC3000-400 article concerning SROM V1.0 01-Jul-2001 – Version V6.0 Rev 1 Added Wildfire V6.0 update example Added ES45 Jumper pictures and definitions Changed all ProSIC references to prosic.inet.cpqcorp.
LIST OF ROM UPDATE JUMPERS, FSL UPDATE JUMPERS AND FSL SELECT JUMPERS ..............................1 LIST OF ROM UPDATE JUMPERS, FSL UPDATE JUMPERS AND FSL SELECT JUMPERS - CONT. ..............2 MINIMUM ACCEPTABLE FIRMWARE CD VERSIONS FOR RECENT OS VERSIONS .......................................3 WHAT VERSION FIRMWARE IS ON WHICH CD.........................................................................................................4 ALPHASERVER 300 THRU ALPHASERVER 800 SYSTEMS ........................
Non-System Disk .......................................................................................................................................................... 37 System Disk .................................................................................................................................................................. 38 METHOD 5 - BOOT OFF OF A BOOTABLE FLOPPY - V5.6 FIRMWARE OR EARLIER .............................................................. 38 OpenVMS AXP ..............
METHOD 7 – BOOT OFF OF A BOOTABLE FLOPPY - V5.3 FIRMWARE OR LATER ................................................................ 68 Windows NT ................................................................................................................................................................. 68 METHOD 8 - BOOTP NETWORK UPGRADE - TRU64 UNIX ............................................................................................... 68 ALPHASERVER 2000/2100/2100A .............................
Floppy - NT................................................................................................................................................................. 103 Floppy - OpenVMS..................................................................................................................................................... 104 Network..............................................................................................................................................................
System Disk ................................................................................................................................................................ 151 METHOD 7 - BOOTP NETWORK UPGRADE – TRU64 UNIX............................................................................................. 151 ALPHASERVER DS10 JUMPERS .................................................................................................................................. 153 MOTHERBOARD ....................
ARC Console .............................................................................................................................................................. 191 METHOD 2 - BOOT THE CONSOLE CD OFF OF AN INFOSERVER ........................................................................................ 192 METHOD 3 - BOOTING OFF THE NETWORK - OPENVMS ..................................................................................................
ALPHASTATION 500/600 ................................................................................................................................................ 226 METHOD 1 - LOAD THE CONSOLE FIRMWARE OFF A LOCAL CDROM............................................................................. 227 SRM Console .............................................................................................................................................................. 227 ARC Console ...................
METHOD 5 - BOOT OFF OF A BOOTABLE FLOPPY ............................................................................................................. 256 Windows NT ............................................................................................................................................................... 256 TRU64 UNIX..............................................................................................................................................................
METHOD 2 - BOOT THE CONSOLE CD OFF OF AN INFOSERVER ........................................................................................ 285 METHOD 3 - BOOTING OFF THE NETWORK ....................................................................................................................... 285 METHOD 4 - BOOT OFF OF A DISK - NON-SYSTEM DISK AND SYSTEM DISK USING OPENVMS....................................... 285 Non-System Disk .......................................................................
RUNNING RCU FIRMWARE UPDATE ON AN ALPHASERVER 8200 / 8400........................................................ 339 OVERVIEW ........................................................................................................................................................................ 339 UTILITY FILENAME DEFINITIONS ...................................................................................................................................... 339 Filenames used up to the V3.8 CD............
CDROM ...................................................................................................................................................................... 366 Floppy ......................................................................................................................................................................... 366 ERRORS ...................................................................................................................................................
ALPHASERVER 1000/1000A EV5 FIRMWARE FROM V5.2 CD WON’T FIT ON FLOPPY................................ 403 ALPHASERVER 1000/1000A 5/300 CPU REQUIRES V5.23 ALPHABIOS ............................................................... 405 ALPHASERVER 1000/1000A LED CODE CB DUE TO WRONG FIRMWARE ON MOTHERBOARD .............. 407 HARDWARE METHOD .......................................................................................................................................................
HOW TO BUILD THE FLOPPY USING ES45FSL.EXE FILE WITH MKBOOT.EXE OR MAKEBOOT.EXE ......................................... 441 WNT/W2k - PC........................................................................................................................................................... 441 WNT - Alpha .............................................................................................................................................................. 441 UNIX – Alpha ...........................
CERTAIN ALPHASERVERS WITH V5.7-4 GETS CONSOLE DAC960 SIZING ERRORS .................................. 475 UPDATING CONSOLE FIRMWARE ON A SYSTEM CONFIGURED AS A GALAXY ........................................ 477 ALPHASERVER 8X00 IMPORTANT CAUTIONS BEFORE UPDATING FIRMWARE !!! .................................. 479 OPERATION WITH MIXED FIRMWARE REVISIONS IS NOT SUPPORTED.............................................................................
UTILITIES/ADAPTERS........................................................................................................................................................ 528 FIRMWARE LOCATIONS ON THE INTERNET ........................................................................................................ 529 FIRMWARE LOCATIONS ONLINE..............................................................................................................................
xxvi
No Jumpers J18 - PCI Backplane No Jumpers No Jumpers J12/J13 pins 1-2 on CSB J24 2-3 on CSB (RMC) J19 pins 1-2 - CSB (SROM) J20 pins 1-2 - CSB (TIG) J7 2–3 - CSB (RMC) SW3 #8 off Motherboard PCI Backplane CPU CPU CSB Motherboard AlphaServer 1200 AlphaServer 4100 AlphaServer 8200/8400 AlphaServer GS60/GS140 AlphaServer ES40 (1) HPM J3 on PBM J60 on PSM J9 on STDIO J17 on or NVR variable SCM_FORCE_FSL SW3 #8 on SW2 #1 on No FSL Available Requests floppy when checksum fails Requests floppy whe
Top SW Right Left SW Down Backplane I/O Backplane AlphaServer 2100A AlphaServer 2100A RM J6 Off J6 Off Jumper W1 Pins 2-3 Rom Update Jumper (Labeled) Flash Enable Jumper IN on system and IO Update Jumper on IO Update Jumper on IO J20 enable (sys) / IO jumper (See #5 on page 7-5 of EK-FLSPC-SV) J20 enable (sys) / IO jumper (See #5 on page 7-5 of EK-FLSPC-SV) No Jumpers No Jumpers No Jumpers No Jumpers System I/O System I/O I/O System System I/O I/O CPU CPU DEC 3000-300 DEC 3000-400 DEC 3000-500 DEC 3
Minimum Acceptable Firmware CD Versions for Recent OS Versions Operating System Digital UNIX Tru64 UNIX OpenVMS Windows NT OS Version Minimum Acceptable Firmware CD Version V3.0 V3.0B V3.2 V3.2A V3.2B V3.2C V3.2D V3.2E V4.0 V3.2F V3.2G V4.0 V4.0A V4.0B V4.0C V4.0D V4.0E FW FW FW FW FW FW FW FW FW FW FW FW FW FW FW FW FW CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD V2.9 V3.0 V3.1 V3.1 V3.2 V3.3 V3.4 V3.5 V3.5 V3.6 V3.6 V3.5 V3.7 V3.8 V3.9 V5.0 V5.3 V4.0F V4.0G V5.0 V5.0A V5.1 V5.1A V5.
What Version Firmware is on Which CD AlphaServer 300 thru AlphaServer 800 Systems System Type AlphaServer 300 AlphaServer 400 AlphaServer 800 or Digital Server 3000 Model 3300/3305 (NT only) Filename SRM Fw Rev NT Fw Rev CD Ver as300_v7_0 as300_v7_0 as300_v7_0 as300_v7_0 as300_v7_0 as300_v7_0 as300_v7_0 as300_v7_0 as300_v6_9 as300_v6_8 as300_v6_7 as300_v6_6 as300_v6_5 as300_x6_2 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 6.9 6.8 6.7 6.6 6.5 6.2-165-1 4.58 4.58 4.58 4.58 4.58 4.58 4.58 4.58 4.57 4.56 4.
AlphaServer 1000 EV4 thru AlphaServer 1000A EV4 Systems System Type AlphaServer 1000 EV4 AlphaServer 1000 EV5 AlphaServer 1000A EV4 Filename SRM Fw Rev NT Fw Rev CD Ver as1000_e4_v5_4 as1000_e4_v5_4 as1000_e4_v5_4 as1000_e4_v5_4 as1000_e4_v5_4 as1000_e4_v5_4 as1000_e4_v5_4 as1000_e4_v5_4 as1000_e4_v5_3 as1000_e4_v5_2 as1000_e4_v5_1 as1000_e4_v5_0 as1000_e4_v4_9 as1000_e4_v4_8 as1000_e4_v4_7 as1000_e4_v4_6 as1000_e4_v4_5 as1000_v5_5 as1000_v5_3 as1000_v5_1 as1000_v5_0 as1000_v4_0 5.4-101 5.4-101 5.
AlphaServer 1000A EV5 thru AlphaServer 2x00 EV4 Systems System Type AlphaServer 1000A EV5 AlphaServer 1200 or Digital Server 5000 Model 5300/5305 (NT only) AlphaServer 2x00 EV4 Filename SRM Fw Rev NT Fw Rev CD Ver as1000a_e5_v5_7 as1000a_e5_v5_7 as1000a_e5_v5_7 as1000a_e5_v5_7 as1000a_e5_v5_7 as1000a_e5_v5_6 as1000a_e5_v5_5 as1000a_e5_v5_4 as1000a_e5_v5_3 as1000a_e5_v5_2 as1000a_e5_v5_1 as1000a_e5_v5_0 as1000a_e5_v4_9 as1000a_e5_v4_8 as1000a_e5_v4_7 as1000a_e5_v4_6 as1000a_e5_v4_5 5.7-80 5.7-80 5.
AlphaServer 2x00 EV5 thru AlphaServer 2100A EV5 Systems System Type Filename AlphaServer 2x00 EV5 AlphaServer 2100A AlphaServer 2100A EV4 EV5 SRM Fw Rev NT Fw Rev CD Ver as2100_e5_v5_3 as2100_e5_v5_3 as2100_e5_v5_3 as2100_e5_v5_3 as2100_e5_v5_3 as2100_e5_v5_3 as2100_e5_v5_3 as2100_e5_v5_3 as2100_e5_v5_3 as2100_e5_v5_2 as2100_e5_v5_1 as2100_e5_v5_0 as2100_e5_v4_9 as2100_e5_v4_7 as2100_e5_v4_7 as2100_e5_v4_6 as2100_e5_v4_5 as2100_e5_v4_4 as2100_e5_v4_3 as2100_e5_v4_1 as2100_e5_v4_0 5.3-6 5.3-6 5.
AlphaServer 4x00 thru 8x00 Systems System Type AlphaServer 4000 / 4100 or Digital Server 7000 Model 7300/7305 (NT only) AlphaServer 8200 / 8400 * Filename SRM Fw Rev NT Fw Rev CD Ver as4x00_v6_0 as4x00_v6_0 as4x00_v5_9 as4x00_v5_8 as4x00_v5_7 as4x00_v5_6 as4x00_v5_5 as4x00_v5_4 as4x00_v5_3 as4x00_v5_2 as4x00_v5_1 as4x00_v5_0 as4x00_v4_9 as4x00_v4_8 as4x00_v3_0 as4x00_v2_0 as4x00_v1_2 6.0-4 6.0-4 5.9-5 5.8-2 5.7-4 5.6-4 5.5-5 5.4-2 5.3-1 5.2-1 5.1-3 5.0-2 4.9-1 4.8-5 3.0-6 2.0-0 1.2-3 5.70-0 5.
Compaq AlphaServer DS10, DS20/DS20E and Compaq AlphaServer GS60/GS60E/GS140 System Type DS10 DS20/DS20E GS60 GS60E GS140 * ** *** Filename SRM Fw Rev NT Fw Rev CD Ver ds10_v6_1 ds10_v6_0 ds10_v5_9 ds10_v5_8 ds10_v5_7 ds10_v5_6 ds10_v5_5 6.1-2 6.0-8 5.9-4 5.8-10 5.7-8 5.6-3 5.5-1 5.71 5.71 5.70 * 5.70 * 5.70 5.70 5.69 6.1 6.0 5.9 5.8 5.7 5.6 5.5 ds20_v6_1 ds20_v6_0 ds20_v5_9 ds20_v5_8 ds20_v5_7 ds20_v5_6 ds20_v5_5 ds20_v5_4 or pc264srm.rom / pc264nt.rom 6.1-2 6.0-8 5.9-4 5.8-10 5.7-8 5.6-3 5.
Compaq AlphaServer GS80/GS160/GS320 System GS80 GS160 GS320 Type Filename gs320_v61 gs320_v60 gs320_v59b gs320_v59 gs320_v58 gs320_v57p4 v57_wfupdate T57_wfupdate.sys V56_wfupdate.sys SRM Fw Rev 6.1-1011 6.0-514 5.9-331 5.9-111 5.8-251 5.8-124 5.8-121 5.8-21 5.8-1 Micro Fw Rev 6.1 6.0 5.9 5.9 5.8 5.7 5.7 5.7 5.6 CD Ver 6.1 6.0 Network 5.
AlphaServer ES40 System Type es40_v6_1 es40_v6_0 es40_v5_9 es40_v5_8 es40_v5_7 es40_v5_6 es40_v5_5 ES40 * There • • • • Filename SRM Fw Rev NT Fw Rev 6.1-3 6.0-31 5.9-24 5.8-43 5.7-84 5.6-102 5.5-68 T5.4-4 5.71*** 5.71*** 5.70** 5.70 5.70 5.70 5.70 5.68 SROM 2.12F 2.12F 2.12F 2.11F 2.10F 2.5F 2.2F RMC 2.7/2.8* 2.7 2.6 2.5 2.4 2.2 2.1 TIG 10 10 10 10 10 10 10 CD Ver 6.1 6.0 **** 5.9 5.8 5.7 5.6 5.5 Network are 4 versions of the RMC firmware on the V6.1 CD. V2.7 for the ES40. I2.
Digital Personal WorkStation a/au Series System Type Digital Personal WorkStation a/au Series Filename digitalpw_v72_1 digitalpw_v72_1 digitalpw_v72_1 digitalpw_v72_1 digitalpw_v72_1 digitalpw_v71_3 digitalpw_v7_0 digitalpw_v7_0 digitalpw_v6_9 digitalpw_v6_8 digitalpw_v6_7 digitalpw_v6_6 digitalpw_v6_5 SRM Fw Rev 7.2-1 7.2-1 7.2-1 7.2-1 7.2-1 7.1-3 7.0-10 7.0-10 6.9-7 6.8-41 6.7-196 6.6-29 6.5-72 NT Fw Rev 5.70 5.70 5.70 5.70 5.70 5.70 5.68 5.68 5.67 5.65 5.64 5.33 5.31 SROM (POST) Rev CD Ver 5.90 5.
AlphaStation 200 thru AlphaStation 255 Systems System AlphaStation 200 AlphaStation 250 AlphaStation 255 Type Filename SRM Fw Rev NT Fw Rev CD Ver as200_v7_0 as200_v7_0 as200_v7_0 as200_v7_0 as200_v7_0 as200_v7_0 as200_v7_0 as200_v7_0 as200_v6_9 as200_v6_8 as200_v6_7 as200_v6_6 as200_v6_5 as200_v5_9 as200_v5_8 as200_v5_7 as200_v5_6 as200_v5_5 as200_v5_1 as200_v5_0 as200_v4_2 as200_v2_9 as200_v2_8 7.0-9 7.0-9 7.0-9 7.0-9 7.0-9 7.0-9 7.0-9 7.0-9 6.9-4 6.8-2 6.7-2 6.6-1 6.5-2 6.4-1 6.3-4 6.2-2 6.
AlphaStation 400 thru AlphaStation 600 Systems System AlphaStation 400 AlphaStation 500 AlphaStation 600 Type Filename SRM Fw Rev NT Fw Rev CD Ver as400_v72_1 as400_v72_1 as400_v72_1 as400_v72_1 as400_v72_1 as400_v7_1 as400_v7_0 as400_v7_0 as400_v6_9 as400_v6_8 as400_v6_7 as400_v6_6 as400_v6_5 as400_v5_9 as400_v5_8 as400_v5_7 as400_v5_6 as400_v5_5 as400_v5_1 as400_v5_0 as400_v4_2 as400_v2_9 as400_v2_8 7.2-1 7.2-1 7.2-1 7.2-1 7.2-1 7.1-2 7.0-9 7.0-9 6.9-4 6.8-2 6.7-2 6.6-1 6.5-2 6.4-1 6.3-4 6.
AlphaStation 600A Systems System Type AlphaStation 600A Filename SRM Fw Rev as600a_e5_v5_6 as600a_e5_v5_6 as600a_e5_v5_6 as600a_e5_v5_6 as600a_e5_v5_6 as600a_e5_v5_6 as600a_e5_v5_5 as600a_e5_v5_4 as600a_e5_v5_3 as600a_e5_v5_2 as600a_e5_v5_1 as600a_e5_v5_0 as600a_e5_v4_9 as600a_e5_v4_8 5.6-114 5.6-114 5.6-114 5.6-114 5.6-114 5.6-114 5.5-80 5.4-115 5.3-103 5.2-114 5.1-204 5.0-106 4.9-169 4.8-79 NT Fw Rev CD Ver 5.70 5.70 5.70 5.70 5.70 5.70 5.69 5.68 5.66 5.64 5.64 5.30 5.30 5.28 6.1 6.0 5.9 5.8 5.
DEC 3000 Systems System Type DEC 3000 Model 300 DEC 3000 Models 400,600 and 700 Filename System FW Ver I/O FW Ver CD Ver m300_v7_0 m300_v7_0 m300_v7_0 m300_v7_0 m300_v7_0 m300_v7_0 m300_v7_0 m300_v7_0 m300_v7_0 m300_v7_0 m300_v7_0 m300_v7_0 m300_v7_0 m300_v7_0 m300_v6_9 m300_v6_8 m300_v6_7 m300_v6_5 m300_v6_4 m300_v6_2 m300_v6_1 m300_v6_0 m300_v5_2 m300_v5_1 m300_v3_3 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 6.9 6.8 6.7 6.5 6.4 6.2 6.1 6.0 5.2 5.1 3.3 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.
DEC 3000 Systems cont System Type DEC 3000 Models 500, 800 and 900 Filename m500_v7_0 m500_v7_0 m500_v7_0 m500_v7_0 m500_v7_0 m500_v7_0 m500_v7_0 m500_v7_0 m500_v7_0 m500_v7_0 m500_v7_0 m500_v7_0 m500_v7_0 m500_v7_0 m500_v6_9 m500_v6_8 m500_v6_7 m500_v6_5 m500_v6_4 m500_v6_2 m500_v6_1 m500_v6_0 m500_v5_2 m500_v5_1 m500_v3_3 System FW Ver 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 6.9 6.8 6.7 6.5 6.4 6.2 6.1 6.0 5.2 5.1 3.3 I/O FW Ver 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.0 7.
DEC 4000 Systems System Type DEC 4000 Models 600 and 700 Filename DecChip Ver Firmware Ver CD Ver cfw_v40_updp3 cfw_v40_updp3 cfw_v40_updp3 cfw_v40_updp3 cfw_v40_updp3 cfw_v40_updp3 cfw_v40_updp3 cfw_v40_updp3 cfw_v40_updp3 cfw_v40_updp3 cfw_v39_updp3 cfw_v39_updp3 cfw_v39_updp3 cfw_v39_updp3 cfw_v39_updp3 cfw_v38_updp3 cfw_v38_updp3 cfw_v37_updp3 cfw_v36_updp3 cfw_v35_updp3 cfw_v35_updp3 cfw_v35_updp3 cfw_v34_updp3 ? ? cfw_v33_updp3 cfw_v33_updp2 cfw_v28_ev4p3 cfw_v28_ev4p2 cfw_v23_e43 cfw_v25_ev4p
DEC 7000/10000 Systems System Type DEC 7000/10000 Models 600 and 700 Filename axp7000_v18 axp7000_v18 axp7000_v18 axp7000_v18 axp7000_v18 axp7000_v18 axp7000_v18 axp7000_v18 axp7000_v17 axp7000_v17 axp7000_v17 axp7000_v17 axp7000_v17 axp7000_v16 axp7000_v15 axp7000_v14 axp7000_v13 axp7000_v12 axp7000_v11 axp7000_v10 axp7000_v0f axp7000_v0e axp7000_v0d axp7000_v0c axp7000_v0b axp7000_v0a axp7000_v09 axp7000_v08 Version 5.4-4819 5.4-4819 5.4-4819 5.4-4819 5.4-4819 5.4-4819 5.4-4819 5.4-4819 5.0-4814 5.
20
Alpha Windows NT Matrix AXP 150 DEC 2000 AlphaXL 4/2xx 5/xxx PWS 433a 500a 600a AlphaStation 200 250 255 400 500 600 600a 1200 AlphaServer 300 400 800 1000 4/2xx 5/xxx 1000a 4/2xx 5/xxx 1200 2000 4/2xx 5/3xx 2100 4/2xx 5/3xx 2100a 4/2xx 5/3xx 4000 4100 8x00 1. 2. 3. 4. HAL 1,3 1,3 Firmware ARC AlphaBIOS 4.31 X 4.31 X SWXCR boot N N HSZ boot N N 3.51 Y Y 4.
22
Alpha System Firmware Update Procedures In order to perform a firmware upgrade successfully you need to follow these steps. • • • • • • • • • • • • • • Determine current firmware versions of the system (SRM, ARC/AlphaBIOS and SROM where pertinent) and options. Determine what firmware version you are updating to. Print and read the release notes for that version. Write down the environmental variable settings. Determine method to be used to do the update.
24
AlphaServer 300 The AlphaServer 300 system contains 4 flash roms on the CPU module. Two contain ARC console firmware for Windows NT and two contain SRM console firmware for Digital UNIX and OpenVMS. The ability to write to these roms is controlled by jumper J4 on the CPU motherboard. When ever the CPU motherboard is replaced the firmware will need to be updated. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available.
MEMORY 32 Meg Bank 0 Bank 1 Bank 2 PCI Bus Bus 00 of System Memory = 16 Mbytes(8 MB Per Simm) Starting at 0x0 = 16 Mbytes(8 MB Per Simm) Starting at 0x1000000 = No Memory Detected 810 Scsi Controller pka0.7.0.6.0 SCSI Bus ID 7 dka0.0.0.6.0 RZ26L dka400.4.0.6.0 RRD43 Bus 00 Slot 07: Intel SIO 82378 Bus 00 Slot 11: Digital ZLXp Graphics Controller Bus 00 Slot 12: Digital DE435 Network Controller ewa0.0.0.12.
Method 2 - Boot the Console CD Off of an Infoserver a. Insert CD in the Infoserver b. >>> boot ewa0 -file filename (leave off the .sys extension) Method 3 - Booting off the Network - OpenVMS a. Copy firmware.sys file to MOM$LOAD of an existing node in the cluster b. Set the attributes on the file with the following commands: $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) firmware.sys c.
System Disk a. Only steps a and b above are used. Do NOT execute writeboot step c. b. Specify the flags of 0,a0 and use "system_disk":[sys0.sysexe]filename for bootfile. >>> boot -fl 0,a0 dua0 bootfile: dua0:[sys0.sysexe]as300_v7_0.exe Method 5 - Boot Off of a Bootable Floppy OpenVMS AXP a. Init and mount floppy. Create a directory and copy the firmware to the floppy with the following commands.
Windows NT a. Copy the firmware file to a FAT formatted floppy with the update image filename a:\fwupdate.exe. b. Shut down NT and from the ARC menu, select "Install new firmware". Caution If you are running the V4.49 ARC console you will not be able to use the "Install new Firmware" utility. The SRM firmware will need to be updated from the >>>. Method 6 - BOOTP Network Upgrade - Tru64 UNIX a. Mount the Firmware Update CD using the following command: # mount -rt cdfs -o noversion /dev/rz4c /mnt b.
5.
UPD> list Device fwa0 pka0 Current Revision 2.46 A06 Filename Update Revision dfxaa_fw kzpsa_fw 3.20 A12 UPD> update * or update Will update all LFU supported devices found in this system UPD> update pka0 - will update device PKA0 Confirm update on: pka0 [Y/(N)]Y WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! pka0 Updating to A12... Verifying A12... PASSED.
32
AlphaServer 300 Jumpers Motherboard Jumper J1 J2 J3 J4 J7 J21 J25 J26 J27 J32 Pins (1 to 2) (2 to 3) (D) (1 to 2) (2 to 3) (D) Function Mini-console Jump to main console Boot floppy Normal (flashROM load) (1 to 2) (D) (2 to 3) (1 to 2) (D) (2 to 3) (1 to 2) (D) (2 to 3) (1 to 2) (3 to 4) (5 to 6) Reset Halt Interrupt Request Enables flashROM writes Disables writes 267 MHz CPU Not used Not used Hang off 1 (D) Hang off 3 (D) Hang off 5 (D) (1 to 2) (D) Removed (1 to 2) (D) Removed (1 to 2) 87332 Sup
34
AlphaServer 800 or Digital Server 3000 Models 3300/3305 The AlphaServer 800 system contains one flash rom on the motherboard that contains ARC console firmware for Windows NT and SRM console firmware for Tru64 UNIX and OpenVMS. When ever the motherboard is replaced the firmware may need to be updated. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available. Rom updates are enabled by jumper J50 on the motherboard.
>>> show config Firmware SRM Console: V4.7-3046 ARC Console: 4.49 PALcode: VMS PALcode V1.19-2, OSF PALcode V1.21-4 Serial ROM: 0.4 Processor DECchip - 21164A-2 400MHZ System Motherboard Revision: 0 MEMORY 64 Meg of System Memory Bank 0 = 64 Mbytes(16 MB Per Simm) Starting at 0x00000000 Bank 1 = No Memory Detected Slot Option 5 Qlogic ISP1020 a. 7 11 Slot 1 Slot 2 3 S3 Trio64/Trio32 Intel 82375eB DECchip 20140-AA Option DE425 Option Qlogic ISP1020 Qlogic ISP1020 Hose 0, Bus 0, pka0.7.0.5.0 dka0.0.0.5.
Method 2 – Boot the Console CD Off of an Infoserver a. Insert CD in the Infoserver b. >>> boot ewa0 –file filename (leave off the .sys extension) Method 3 – Booting Off the Network – OpenVMS a. Copy the firmware.sys file and the option firmware files to MOM$LOAD of an existing node in the cluster. (These versions are from the V5.9 CD) as800_v5_8.sys - System firmware as800fw.sys - This file tells the update utility which option files to load. ccmab022.
Note: Updating options via this method is only supported if the system disk is on the NCR810 SCSI bus (the on-board SCSI). e. To update the option firmware, first create an options directory. $ set def dua5:[000000] $ create/dir [.options] f. Copy the option firmware files to the options directory. as800fw.txt ccmab022.sys dfeaa130.sys dfeab320.sys dfxaa320.sys kzpsaa12.sys g. When booting the update utility enter the device name where the option firmware is located. System Disk a.
f. Enter the following commands to create the options floppy: $ init/dens=HD/index=begin dva0: optionfw $ mount dva0: optionfw $ create/dir dva0:[options] - Note:The directory name must be [options] $ copy as800fw.txt dva0:[options] $ copy ccmab022.sys dva0:[options] $ copy dfeaa130.sys dva0:[options] $ copy dfeab320.sys dva0:[options] $ copy dfxaa320.sys dva0:[options] $ copy kzpsaa12.sys dva0:[options] $ dismount dva0: g. Insert the floppy when it asks for the options firmware and enter the location.
Windows NT a. Copy the firmware file to a FAT formatted floppy with the update image filename a:\fwupdate.exe. b. Shut down NT and from the NT Console menu, select "Install new firmware". c. If you wish to update the options firmware, you must create a second floppy. Download the following files from the options directory at the firmware website. as800fw.txt ccmab022.sys dfeaa130.sys dfeab320.sys dfxaa320.sys kzpsaa12.sys d. FAT format a floppy and copy the files to the floppy. e.
Windows NT - Alpha or PC a. Locate and save the following files to your Alpha or PC. Save them on the top level directory of any disk. makeboot.exe can be found on Cybrary at http://cybrary.inet.cpqcorp.net/DOWNLOAD/UTILITIES/SYSTEM/makeboot.zip • • • • makeboot.exe mkboot.exe cru.exe crarcrom.exe Alpha image to make a bootable disk PC/ALPHA NT image to make a bootable disk LFU and SRM firmware AlphaBIOS firmware b. Fat format two floppies c.
e. Format the floppy. # fddisk -fmt /dev/rfd0a or With Tru64 UNIX V5.0 you can do one of the following # fddisk -fmt /dev/rdisk/floppy0a or # cd /dev # ./MAKEDEV fd0 # fddisk -fmt /dev/rfd0a f. From directory where files are located execute the following # ./mkbootfirm clu.exe |dd of=/dev/rfd0c bs=64k g. Insert floppy diskette 2. h. Create a soft link to /dev/fddrive with the following command # ln -s /dev/rfd0c /dev/fddrive i. Format the floppy. See step 5 for commands. j.
c. Modify the /etc/inetd.conf file. Uncommon the tftp and bootps process. It should look like the following example: tftp dgram udp wait root /usr/sbin/tftpd tftpd /mnt bootps dgram upd wait root /usr/sbin/bootpd bootpd d. Find the process /usr/sbin/inetd daemon: This step will stop network traffic # ps aux | grep ine # kill process# e. Restart the inetd daemon: # /usr/sbin/inetd Note The bootpd and tftp daemon will be removed if the system is rebooted.
8. Verify that update was successful and exit UPD> verify ARC SRM pkc0 Verifying v5.70... PASSED. Verifying v5.8-16... PASSED. Verifying A12... PASSED. UPD> exit Initializing.... 9. Power cycle the machine to load console firmware. Reboot firmware CD and execute a RESTORE_NVRAM if you saved it in step 5. If you are updating device firmware, proceed to step 10. If you are done reset any environmental variables that changed, init and reboot. 10. Update the option firmware. The V5.
AlphaServer 800 Jumpers Motherboard Jumper J16 Name Fan fail override J22 Remote Management Console (RMC) VGA Enable J27 J50 J51 Flash ROM VPP Enable SCSI Termination Description Allows the fan failure detection logic to be disabled to accommodate alternative enclosures Sets default values to the RMV NVRAM Default Setting This jumper is not installed on AlphaServer 800 systems Disabled When enabled the on-board VGA logic is activated Enabled for onboard VGA; Disabled if an EISA- or PCI-based VGA
CPU Daughter Card J1 and J3 Settings The figure above shows the settings for the J3 jumper depending on CPU speed. This jumper affects the clock speed and other critical system settings.
AlphaServer 1000/1000A The AlphaServer 1000/1000A systems have flash roms on the motherboard that contain ARC console firmware for Windows NT and SRM console firmware for Tru64 UNIX and OpenVMS. When ever the motherboard is replaced or the CPU’s are upgraded or downgraded between EV4 and EV5 CPU’s the firmware will need to be updated. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available.
>>> show config Firmware SRM Console: X4.6-218 ARC Console: 4.49 PALcode: VMS PALcode X5.65-4, OSF PALcode X1.45-9 Serial ROM: V1.2 Processor DECchip (tm) 21064-2 MEMORY 64 Meg Bank 0 Bank 1 Bank 2 Bank 3 of System Memory = 64 Mbytes(16 MB Per Simm) Starting at 0x00000000 = No Memory Detected = No Memory Detected = No Memory Detected PCI Bus Bus 00 Slot 06: NCR 810 Scsi Controller pka0.7.0.6.0 dka0.0.0.6.0 dka400.4.0.6.
Method 2 - Boot the Console CD Off of an Infoserver a. Insert CD in the Infoserver b. >>> boot ewa0 -file filename (leave off the .sys extension) Method 3 - Booting Off the Network - OpenVMS a. Copy the firmware.sys file and the option firmware files to MOM$LOAD of an existing node in the cluster. (These versions are from the 5.9 CD and may change) as1000fw.sys ccmab022.sys dfeaa130.sys dfeab320.sys dfxaa320.sys kzpsaa12.sys – - This file is read first. It tells utility which files to load.
Note: Updating options via this method is only supported if the system disk is on the NCR810 SCSI bus (the on-board SCSI). e. To update the option firmware, first create an options directory. $ set def dua5:[000000] $ create/dir [.options] f. Copy the option firmware files to the options directory. as1000fw.txt ccmab022.sys dfeaa130.sys dfeab320.sys dfxaa320.sys kzpsaa12.sys g. When booting the update utility enter the device name where the option firmware is located. System Disk a.
f. Enter the following commands to create the options floppy: $ init/dens=HD/index=begin dva0: optionfw $ mount dva0: optionfw $ create/dir dva0:[options] - Note:The directory name must be [options] $ copy as1000fw.txt dva0:[options] $ copy ccmab022.sys dva0:[options] $ copy dfeaa130.sys dva0:[options] $ copy dfeab320.sys dva0:[options] $ copy dfxaa320.sys dva0:[options] $ copy kzpsaa12.sys dva0:[options] $ dismount dva0: g. Insert the floppy when it asks for the options firmware and enter the location.
Windows NT a. Copy the firmware file to a FAT formatted floppy with the update image filename a:\fwupdate.exe. b. Shut down NT and from the NT Console menu, select "Install new firmware". c. If you wish to update the options firmware, you must create a second floppy. Download the following files from the options directory at the firmware website. as1000fw.txt ccmab022.sys dfeaa130.sys dfeab320.sys dfxaa320.sys kzpsaa12.sys d. FAT format a floppy and copy the files to the floppy. e.
f. Enter the following command to boot from the BOOTP server: >>> boot -p bootp ewa0 Should a boot file "pathname" need to be specified in must be in quotes >>> boot -p bootp ewa0 -file “/dir1/dir2/filename” g. Currently there is no BOOTP support for updating option firmware. 5. From the UPD> prompt save contents of NVRAM to floppy using SAVE_NVRAM. 6. List the current firmware version. UPD> list Device ARC SRM Current Revision v4.56 v5.
UPD> update option-name or update pka0 - will update device PKA0 Confirm update on: pka0 [Y/(N)]Y WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! pka0 Updating to A12... Verifying A12... UPD> verify fwb0 pka0 Verifying 3.20... PASSED. Verifying A12... PASSED. PASSED. 11. Power cycle the machine to load console firmware then reset any environmental variables that changed, init and reboot.
AlphaServer 1000/1000A Jumpers Motherboard Jumper Name Description Default Setting J27 VGA Enable When Enabled (as shown in above diagram), the on-board VGA logic is activated Enabled for on-board VGA; Disabled if an EISA- or PCI- based VGA is installed. J49 SCSI Termination Allows the internal SCSI Terminator to be disabled Enabled ( as shown in diagram ) J50 Flah ROM VPP Enable Permits the 12V voltage needed to update the Flash ROMs.
EV4 CPU J4, J3 and J1 Settings Jumper J4 J3 J1 0 1 2 3 4 5 6 7 4/200 4/233 4/266 OFF OFF OFF ON ON OFF ON OFF ON OFF OFF OFF ON ON ON This jumper is never installed on any EV4 CPU Setting Standard Boot Setting (default) Mini-Console (Internal Use Only) SROM Cache Test: BCache test SROM BCache Test: BCache and MEM Test SROM Memtest: Mem test with BCache and DCache Disabled SROM Memtest Cache On: Mem test with BCache and DCache Enabled SROM BCache Tag Test: Backup Cache Tag Test Fail-Safe Loader setting:
EV5/300 CPU J3 and J4 Settings J4 0 1 2 3 4 5 6 7 Setting Standard Boot Setting (AlphaServer 1000/1000A systems) Jumper can be in either 0 or 1. Default is in 0.
EV5/333 CPU J1 and J3 Settings J1 0 1 2 3 4 5 6 7 J3 setting Setting Standard Boot Setting (AlphaServer 1000/1000A systems) Jumper can be in either 0 or 1. Default is in 0.
EV5/400 CPU J1 and J3 Settings J1 0 1 2 3 4 5 6 7 J3 setting Setting Standard Boot Setting (AlphaServer 1000/1000A systems) Jumper can be in either 0 or 1. Default is in 0.
60
AlphaServer 1200 or Digital Server 5000 Models 5300/5305 or Digital Ultimate WorkStation The console firmware on the AlphaServer 1200 system is located on the system motherboard in two FEPROMs. Whenever the motherboard is replaced, the firmware will most likely need to be upgraded. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available. This system also contains a failsafe loader.
starting console on CPU 1 probing IOD1 hose 1 bus 0 slot 1 - NCR 53C810 bus 0 slot 4 - PCI-PCI Bridge probing PCI-PCI Bridge, bus 2 bus 2 slot 0 - QLogic ISP1020 probing IOD0 hose 0 bus 0 slot 1 - PCEB probing EISA Bridge, bus 1 bus 0 slot 2 - S3 Trio64/Trio32 bus 0 slot 3 - DECchip 21140-AA configuring I/O adapters... ncr0, hose 1, bus 0, slot 1 isp0, hose 1, bus 2, slot 0 floppy0, hose 0, bus 1, slot 0 tulip0, hose 0, bus 0, slot 3 System temperature is 27 degrees C AlphaServer 1200 Console V5.
Method 1 - Load the Console Firmware Off a Local CDROM SRM Console a. Insert the CD in the local CDROM. b. P00>>> boot DKA500 - You can also use the procedure c. BOOTFILE: [as1200]as1200_v6_0.exe - for the AlphaServer 1200 Note: These filenames will change with different console versions. Apu-> See step 5 below for update procedure. c.
Floppy a. Create a system and/or I/O firmware floppies using the following procedure. You will need up three floppies. Two for system firmware and one for I/O firmware. This is as of V5.4 . With V5.3 or earlier two floppies would work. b. Execute the following command file to create both floppies $! $! make_tcods2cp_1and2.
d. Execute LFU command and select device dva0 for the floppy device and the filenames as1200cp or as1200io depending if you want to update console or I/O firmware. If running console version V1.2 or greater you can specify as1200fw and it will load files off the console firmware floppy and then request you load the I/O firmware floppy.
c. Enable service on that node from NCP $ MC NCP MC NCP> Show Known Circuit Characteristic Known Circuit Volatile Characteristics as of 12-FEB-1997 19:27:41 Circuit = BNA-0 State Service Counter timer Designated router Cost Maximum routers allowed Router priority Hello timer Type Adjacent node Listen timer = = = = = = = = = = = on disabled (if enabled skip to boot command) 65534 28.1023 (CXO28A) 4 33 64 15 Ethernet 28.
Method 6 – Boot Off of a Bootable Floppy - V5.2 Firmware or Earlier OpenVMS AXP a. Init and mount to floppy. Create a directory and copy the firmware to the Floppy with the following commands. $ init/dens=HD/index=begin dva0: fwupdate $ mount dva0: fwupdate $ create/dir dva0:[as1200] $ copy/contiguous as1200_v5_2.exe dva0:[as1200]fwupdate.exe b. MCR Writeboot Update VAX portion of boot block (default is Y): No Update Alpha portion of boot block (default is Y):Yes [enter AXP bootfile:] dva0:[as1200]fwupdate.
Method 7 – Boot Off of a Bootable Floppy - V5.3 Firmware or Later Windows NT a. Fat format up to three floppies. To update system firmware you will need two floppies. However if you want to update IO firmware, you will need three floppies. A disk1.zip, disk2.zip and disk3.zip file are available on the firmware website. b. Locate and copy the following files to disk #1. • • • • as1200cp.sys as1200fw.sys tcreadme.sys tcarcrom.
c. Modify the /etc/inetd.conf file. Uncommon the tftp and bootps process. It should look like the following example: tftp dgram udp wait root /usr/sbin/tftpd tftpd /mnt bootps dgram upd wait root /usr/sbin/bootpd bootpd d. Find the process /usr/sbin/inetd daemon: This step will stop network traffic # ps aux | grep ine # kill process# e. Restart the inetd daemon: # /usr/sbin/inetd Note The bootpd and tftp daemon will be removed if the system is rebooted.
b. UPD> list Device AlphaBIOS srmflash Current Revision V5.70-0 V5.8-2 Filename arcrom srmrom cipca_fw dfxaa_fw kzpsa_fw ccmab_fw Update Revision V5.70-0 V5.9-5 A420 3.20 A12 22.0 NOTE: If upgrading to V5.3 or later for the first time, or downgrading from V5.3 or 5.4 to a lower version, make sure you read the release notes. The correct update procedure is as follows. 1. 2. 3. 4. 5. Boot firmware CD Update SRM Exit and reboot firmware CD Update AlphaBIOS Exit c. UPD> update srm* - See NOTE above.
updating firmware. i. From the >>> restore the NVRAM contents with RESTORE_NVRAM or reboot the firmware CD and RESTORE_NVRAM if you did the SAVE_NVRAM in step b. Otherwise check and set the following environmental variables. P00>>> set Bootdef_dev set Boot_osflags set Auto_action j. P00>>> init 5. If ECU is required to be run you must use the AlphaBIOS. a. P00>>> AlphaBIOS b. Select Run ECU from Floppy. 6. If RCU is required to be run you must use the AlphaBIOS. a. P00>>> AlphaBIOS b.
• • PKA0_SOFT_TERM Enables or disables SCSI terminators. This environment variable applies to systems using the QLogic ISP1020 SCSI controller. The QLogic ISP1020 SCSI controller implements the 16-bit wide SCSI bus. The QLogic module has two terminators, one for the 8 low bits and one for the high 8 bits. There are five possible values: • off — Turns off both low 8 bits and high 8 bits. • low — Turns on low 8 bits and turns off high 8 bits. • high — Turns on high 8 bits and turns of low 8 bits.
AlphaServer 2000/2100/2100A The AlphaServer 2100 systems contain flash roms on the standard I/O that contain ARC console firmware for Windows NT and SRM console firmware for Tru64 UNIX and OpenVMS. The 2000 flash roms are on the I/O backplane and the 2100A flash roms are on the backplane module. When ever these modules are replaced or the CPU’s are upgraded or downgraded between EV4 and EV5 CPU’s the firmware will need to be updated.
1. Get the current firmware revision at power on or with Show commands >>> show version Version X3.6-83 May 23 1994 09:30:16 >>> show pal PAL VMS PALcode X5.48-33, OSF PALcode X1.35-23 >>> show config Console V3.6-83 VMS PALcode X5.48-33, OSF PALcode X1.35-23 Component CPU 0 CPU 1 Memory 0 Memory 1 Memory 2 Memory 3 IO Hose 0, PCI slot 0 slot 1 slot 2 Status P P P P P Module ID B2020-AA DECchip (tm) 21064-3 B2020-AA DECchip (tm) 21064-3 B2021-BA 64 MB B2021-BA 64 MB B2110-AA dva0.0.0.0.
Method 2 - Boot the Console CD Off of an Infoserver a. Insert CD in the Infoserver b. >>> boot ewa0 -file filename (leave off the .sys extension) Method 3 - Booting Off the Network - OpenVMS a. Copy the firmware.sys file and the option firmware files to MOM$LOAD of an existing node in the cluster. (These versions are from the V5.9 CD and may change) as2x00fw.sys ccmab022.sys cipca420.sys dfeaa130.sys dfeab320.sys dfxaa320.sys kzpsaa12.sys - This file is read first. It tells utility which files to load.
Target system device (and boot file if not VMB.EXE):$1$dua5:[TEMP]filename.exe d. >>> b -fl 0,0 dua5 Note: Updating options via this method is only supported if the system disk is on the NCR810 SCSI bus (the on-board SCSI). e. To update the option firmware using Method 4 first create an options directory. $ set def dua5:[000000] $ create/dir [.options] f. Copy the option firmware files to the options directory. as2x00fw.txt ccmab022.sys cipca420.sys dfeaa130.sys dfeab320.sys dfxaa320.sys kzpsaa12.sys g.
e. If you wish to update option firmware you must create a second floppy with option firmware on it. Downline load the following files from the Website. as2x00fw.txt ccmab022.sys cipca420.sys dfeaa130.sys dfeab320.sys dfxaa320.sys kzpsaa12.sys f. Enter the following commands to create the options floppy: $ init/dens=HD/index=begin dva0: optionfw $ mount dva0: optionfw $ create/dir dva0:[options] – The directory name must be [options] $ copy as2x00fw.txt dva0:[options] $ copy ccmab022.
dd if=v39_options.dd of=/dev/rfd0c bs=64k NOTE: This assumes the v39_options.dd image file is in the current directory and that the floppy is in drive 0. l. After booting the firmware floppy created with mkbootfirm, the update utility will complain that it cannot find the options files on either CD or floppy, and will prompt for a device to look for the options files. Simply insert the options floppy you created above, type the device name of the floppy (e.g.
d. Find the process /usr/sbin/inetd daemon: This step will stop network traffic # ps aux | grep ine # kill process# e. Restart the inetd daemon: # /usr/sbin/inetd Note The bootpd and tftp daemon will be removed if the system is rebooted. Refer to the manual pages: bootpd(8) or tftpd(8) for more information. Use Man bootpd and man tftpd f.
UPD> update srm* - To only update the SRM console Confirm update on: srmflash [Y/(N)] Y WARNING: updates may take several minutes to complete for each device. srmflash DO NOT ABORT! Updating to 5.3-2... Verifying 5.3-2... PASSED. UPD> update arc* - To only update the ARC console Confirm update on: arcflash [Y/(N)] Y WARNING: updates may take several minutes to complete for each device. arcflash DO NOT ABORT! Updating to 4.57-0... Verifying 4.57-0... PASSED. UPD> 8. Verify that update was successful.
13. Run ECU and do a SAVE and EXIT. Also reset any console variables. If you executed the SAVE_NVRAM step 8 above you can also use RESTORE_NVRAM command from the UPD> prompt to restore the contents on NVRAM to floppy. See pages 199 and 200 for a description. This will write console variables, NT settings and ECU data to the floppy. Execute this command from LFU before doing the CLEAR_ARC_NVRAM and CLEAR_SRM_NVRAM commands.
82
AlphaServer 2000/2100/2100A Jumpers AlphaServer 2000 BA720 Enclosure • • • J3 – Power supply mode: When installed, dual power supplies operate in redundant mode J5 – Program voltage: Internal use only.
AlphaServer 2100 and 2100 RM BA740/BA741 Enclosures • • • J3 – Power supply mode: When installed, dual power supplies operate in redundant mode J5 – Program voltage: Internal use only.
AlphaServer 2100A • • Top switch to RIGHT – Enable FSL Use Bottom switch to RIGHT – Enable writes to FSL ROM AlphaServer 2100A RM • • Left switch DOWN – Enable writes to FSL ROM Right switch DOWN – Enable FSL Use 85
AlphaServer 2100A LP Caution: Do not perform console upgrades with the W6 jumper installed or the system firmware will be corrupted.
AlphaServer 4000/4100 or Digital Server 7000 Models 7300/7305 The console firmware on the AlphaServer 4000/4100 systems is located on the PCI backplane. The ability to write to the ROM is controlled by jumper J18 on the motherboard. Whenever the PCI backplane is replaced, the firmware will most likely need to be upgraded. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available. This system also contains a failsafe loader.
bus 0 slot 1 - PCEB probing EISA Bridge, bus 1 bus 0 slot 2 - DEC PCI MC bus 0 slot 3 - S3 Trio64/Trio32 bus 0 slot 5 - Mylex DAC960 configuring I/O adapters... ncr0, hose 1, bus 0, slot 1 isp0, hose 1, bus 2, slot 0 tulip0, hose 1, bus 0, slot 3 tulip1, hose 1, bus 0, slot 4 kzpsa0, hose 1, bus 0, slot 5 floppy0, hose 0, bus 1, slot 0 dac0, hose 0, bus 0, slot 5 mc0, hose 0, bus 0, slot 2 System temperature is 33 degrees C AlphaServer 4100 Console V5.
AlphaBIOS Console a. Insert the CD in the local CDROM. b. Enter the AlphaBIOS menu by typing ARC or AlphaBIOS or initializing the system when os_type = nt c. AlphaBIOS -Select F2 to go into Setup then select Upgrade AlphaBIOS Method 2 - Boot Console CD, Firmware Floppy or Network Device CD a. Insert the CD in the local CDROM. b. Execute LFU command and select device cda0 for the CDROM and specify as4x00fw.
If creating a diskette for updating your I/O option firmware only: $! $! make_rhods2io.com $! $ inquire ignore "Insert blank HD floppy in DVA0, then continue" $ set verify $ set proc/priv=all $ init/density=hd/index=begin dva0: rhods2io $ mount dva0: rhods2io $ create/directory dva0:[as4x00] $ create/directory dva0:[options] $ copy as4x00fw.sys dva0:[as4x00]as4x00fw.sys $ copy as4x00io.sys dva0:[as4x00]as4x00io.sys $ copy rhreadme.sys dva0:[as4x00]rhreadme.sys $ copy ccmab022.sys dva0:[options]ccmab022.
c. Execute LFU command and select device EWA0 fir Digital PCI Ethernet or FWA0 for Digital PCI FDDI (DEFPA). Specify the files as4x00fw, as4x00cp or as4x00io depending on what you want to update.
Method 5 - Boot Off of a Disk - Non-System Disk and System Disk Using OpenVMS Non-System Disk a. Locate the as4x00_v6_0.exe file b. Set the attributes on the file and copy it contiguous to the target disk (non-system) and directory with the following commands: $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) as4x00_v6_0.exe $ copy/contiguous as4x00_v6_0.exe "non_system_disk":[directory] c. Use writeboot to make the disk bootable. Specify the disk, directory and filename of the firmware.
Tru64 UNIX a. Go to the Digital Internet firmware site at http://ftp.digital.com/pub/Digital/Alpha/firmware/ b. Copy the firmware.exe file from the AS4x00 directory to your system and rename it fwupdate.exe c. Download the file mkbootfirm.tar from the firmware website. ftp://ftp.digital.com/pub/Digital/Alpha/firmware/utilities/mkbootfirm.tar You can untar mkbootfirm on your target Tru64 UNIX system with the command: # tar xvf mkbootfirm.tar d. Make sure you have a floppy that has been low-level formatted.
d. Locate and copy the following files to disk #3 to update I/O firmware. • • • • • • as4x00.sys rhreadme.sys cipca315.sys dfxaa320.sys kzpsaa12.sys ccmab022.sys IO LFU update file LFU text file CIPCA firmware DFXAA firmware KZPSA firmware CCMAB firmware e. At the >>> type LFU and enter when it asks for the filename enter as1200cp (cpu firmware), as1200io (IO firmware) or as1200fw (system and IO firmware). f. I will prompt you to load the floppies in one at a time.
f. Enter the following command to boot from the BOOTP server: >>> boot -p bootp ewa0 Should a boot file "pathname" need to be specified in must be in quotes >>> boot -p bootp ewa0 -file “/dir1/dir2/filename” 5. List the current version then Update the firmware at the UPD> prompt. Use update * or update *SRM*, or update al* or update KZPSA0 etc. Then verify the update before exiting.
AlphaBIOS Updating to V5.70-0... ....... Verifying V5.70-0... Confirm update on: kzpsa0 kzpsa0 srmflash d. UPD> verify AlphaBIOS kzpsa0 srmflash [Y/(N)] y DO NOT ABORT! Updating to A12 ... Confirm update on: srmflash PASSED. Verifying A12... PASSED. [Y/(N)] y DO NOT ABORT! Updating to V5.9-5............... Verifying V5.9-5...PASSED. Verifying V5.70-0... PASSED. Verifying A12... PASSED. Verifying V5.9-5... PASSED. e. UPD> exit Initializing... f.
9. You can also set up some controller parameters at the console using the PK*0 variables. There are different parameters depending on the controller type. Some you may see are • PKA0_DISCONNECT • PKA0_FAST Specifies mode of controller 0 = Normal 1 = Fast • PKA0_HOST_ID Specifies SCSI Host ID Range is 0-7. 7 is the Default. • PKA0_SOFT_TERM Enables or disables SCSI terminators. This environment variable applies to systems using the QLogic ISP1020 SCSI controller.
98
AlphaServer 4000/4100 Jumpers PCI/EISA Motherboard J18 Installed = Flash ROM writes enabled AlphaServer 4000/4100 LP Jumpers PCI/EISA Motherboard J18 Installed = Flash ROM writes enabled 99
100
AlphaServer 8200/8400 The console firmware on the AlphaServer 8200/8400 is located on the CPU module. All Cpu’s must run the same version of firmware. You can NOT have mixed versions and expect it to work. Any time a CPU module is added or replaced, the firmware will most likely need to be upgraded. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available. The firmware files used for the 8200/8400 and GS60/GS140 are different.
a. Set Auto_action to HALT P02>>> set Auto_action halt 3. Boot the firmware using one of the following methods. Method 1 - Boot the Console CD Off a Local CDROM SRM Console a. Insert the CD in the local CDROM. b. P02>>> boot -fl 0,a0 DKA600 Bootfile: [AS8x00]as8000_v16.exe UPD> See below for update steps - AlphaServer 8200/8400 AlphaBIOS Console Do NOT use this procedure with the V5.3 firmware on the AlphaServer 8200/8400 a. Insert the CD in the local CDROM. b.
Floppy - NT a. Fat format 3 floppies. b. Copy the following files to floppy 1 • as8x00fw.sys • as8x00cp.sys • as8x00ab.sys • tlreadme.sys • tlsrmrom.sys c. Copy the following files to floppy 2 • tl56ab.sys d. Copy the following files to floppy • as8x00fw.sys • as8x00io.sys • tlreadme.sys • cipca420.sys • cixcd007.sys • defaa110.sys • demfa021.sys • demna094.sys • dfxaa320.sys • kcm44cfg.sys • kcm44031.sys • kdm70044.sys • kfmsb024.sys • kfmsb001.sys • kzmsa056.sys • kzpsaa12.sys • ccmab022.sys e.
Floppy - OpenVMS a. Create a system and/or I/O firmware floppies using the following procedure. You will need up three floppies. Two for system firmware and one for I/O firmware. b. Execute the following command file to create both floppies $! $! make_tlodscp_1and2.com $! $ inquire ignore "Insert first blank HD floppy in DVA0, then continue" $ set verify $ set proc/priv=all $ init/density=hd/index=begin dva0: tlods2cp1 $ mount dva0: tlodscp1 $ create/directory dva0:[as8x00] $ copy as8x00fw.
d. Execute LFU command and select device dva0 for the floppy device and the filenames as8x00cp or as8x00io depending if you want to update console or I/O firmware. You can also specify as8x00ab to load AlphaBIOS firmware only or as8x00fw and it will load system and I/O firmware.
Method 3 - Boot the Console CD Off of an Infoserver a. Insert CD in the Infoserver b. P02>>> boot exa0 -file as8000_v16 (leave off the .sys extension) Method 4 - Booting Off the Network a. Copy firmware.sys file to MOM$LOAD of an existing node in the cluster b. Set the attributes on the file with the following commands: $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) as8000_v16.sys c.
System Disk a. Only steps a and b above are used. Do NOT execute writeboot step c. b. Specify the flags of 0,a0 a0 and use "system disk":[sys0.sysexe]filename for bootfile. >>> b -fl 0,a0 dua0 bootfile: dua0:[sys0.sysexe]as8000_v16.exe Method 6 - BOOTP Network Upgrade - Tru64 UNIX a. Mount the Firmware Update CD using the following command: # mount -rt cdfs -o noversion /dev/rz4c /mnt b.
pfi0 3.20 dfxaa_fw ccmab_fw cipca_fw cixcd_fw defaa_fw demfa_fw demna_fw kcm44_fw kdm70_fw kfmsb_fw kzmsa_fw kzpsa_fw 3.20 22 A420 7 1.10 2.1 9.4 3.1 4.4 2.4 5.6 A12 b. Update the firmware using one of the following commands UPD> Update * or Update - Update all supported devices WARNING: updates may take several minutes to complete for each device. Confirm update on: kn7cc-ab0_arc kn7cc-ab0_arc DO NOT ABORT! Updating to V5.70c... Verifying V5.70c...
d. Type Exit to leave the utility. UPD> exit Initializing... 5. After you have updated the firmware you MUST FORMAT THE EEPROMs to the new console firmware format. Note This process will require you to re-enter your default boot specifications and EWx0_mode EV settings after you have re-initialized. BE SURE TO RECORD THE CURRENT SETTINGS BY TYPING SHOW * BEFORE REFORMATTING THE EEPROMS. a. Show environmental variables using console SHOW command. P00>>> show * b.
c. The build -n command is used to format the NVR (non-volatile RAM) . This command is not documented in the release notes. It is valid and may correct problems after the update. You must do this on each cpu. P00>>> build -n Build NVR on kn7cc-ab0 ? [Y/N]> y NVR built on kn7cc-ab0 d. Set console environmental variables back to original settings as necessary. P00>>> Set bootdef_dev dka0.0.0.1.0 P00>>> Set boot_osflags 0,0 P00>>> Set ewa0_mode twisted-pair e. P02>>> init 6.
7. The RUN command has 4 options. Rcu - Run the RAID Configuration Utility swxcrfw - Update the firmware on the RAID controller eeromcfg – Run the ISP1020 EEPROM Configuration Utility (KFTIA and other ISP1020 Controllers i.e. KZPBA ) util_cli – Run the KZPSA Configuration Utility lp6ldr - KGPSA firmware update utility RCU and SWXCRFW are on floppy and require a floppy drive. RCU is also on the CD. EEROMCFG and UTIL_CLI are available on floppy or CD. a.
d. If updates to KGPSA firmware are required P02>>> set arc_enable on P02>>> set console_mode advanced P02>>> init P02>>> load –f iso9660 – load CDROM driver P02>>> run iso9660:[UTILITY]lp6ldr.exe -d dkd500 -p 0 (specify CD loaded into DKD500 on PCI bus 0 ) The utility lp6dutil will not properly function on the TurboLaser or GS series machine thru the serial port. You will see a repeating character problem. 8. You can also run KZSPA_EDIT from the console prompt to set up some KZPSA parameters.
Modify four bytes of parameters >>> kzpsa_edit -offset 0 -value 11223344 kzpsa0 Set one bit of the parameters >>> kzpsa_edit -offset 0 -bit 1 -set kzpsa0 Set all defaults >>> kzpsa_edit -sd kzpsa0 113
There is one other UNRECOMMENDED method for updating firmware from an existing CPU’s EEPROM. That is the use of the UPDATE command to copy one CPU’s EEPROM info to another CPU’s EEPROM area. The problem with this command is if the EEPROM format does not match the between the CPU’s it may render the new CPU useless. Forewarn any engineer who decides to do this. He may need another spare CPU module. NEVER Allow a customer to use this procedure! NOTE: Updating Firmware - Off existing CPU a.
Compaq AlphaServer GS60/GS140 The console firmware on the Compaq AlphaServer GS60/GS140 systems is located on the CPU module. All Cpu’s must run the same version of firmware. You can NOT have mixed versions and expect it to work. Any time a CPU module is added or replaced, the firmware will most likely need to be upgraded. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available.
2. P00>>> show * to printout all the environmental variables. Check all customer set variables. Also verify the setting of the following variables. Bootdef_dev Boot_osflags Auto_action a. Set Auto_action to HALT P00>>> set Auto_action halt 3. Boot the firmware using one of the following methods. Method 1 - Boot the Console CD Off a Local CDROM SRM Console a. Insert the CD in the local CDROM. Prior to V5.4 CD the GS60/GS140 had a separate CD that contained only GS firmware. b.
Floppy - NT a. Fat format 3 floppies. b. Copy the following files to floppy 1 • gs140fw.sys • gs140cp.sys • gs140ab.sys • t6readme.sys • t6srmrom.sys c. Copy the following files to floppy 2 • tl6ab.sys d. Copy the following files to floppy • gs140fw.sys • gs140io.sys • t6readme.sys • cipca420.sys • cixcd007.sys • demfa021.sys • demna094.sys • dfxaa320.sys • kdm70044.sys • kfmsb024.sys • kzmsa056.sys • kzpsaa12.sys • ccmab022.sys e.
Floppy - OpenVMS a. Create a system and/or I/O firmware floppies using the following procedure. You will need up three floppies. Two for system firmware and one for I/O firmware. b. Execute the following command file to create both floppies $! $! make_gsodscp_1and2.com $! $ inquire ignore "Insert first blank HD floppy in DVA0, then continue" $ set verify $ set proc/priv=all $ init/density=hd/index=begin dva0: gsods2cp1 $ mount dva0: gsodscp1 $ create/directory dva0:[gs140] $ copy gs140fw.
d. Execute LFU command and select device dva0 for the floppy device and the filenames gs140cp or gs140io depending if you want to update console or I/O firmware. If running console version V1.2 or greater you can specify gs140fw and it will load files off the console firmware floppy and then request you load the I/O firmware floppy.
Method 4 - Create a Bootable CD Using a CD Writer and the .iso Firmware File Files in the Alpha Systems Firmware web site that have a ".iso" file type are ISO9660 image files and can be used to create bootable CD-ROMs. ZIP files that have "_iso" in the file name contain a ".iso" file which, when extracted, can be used to create a bootable CD-ROM. a. Make sure you have a CD writer and software package that is capable of creating a CD from an image file. b. Obtain the .iso firmware.
Method 6 - Boot Off of a Disk - Non-System Disk and System Disk Using OpenVMS Non-System Disk a. Locate the gs140_v60.exe b. Set the attributes on the file and copy it contiguous to the target disk (non-system) and directory with the following commands: $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) gs140_v60.exe $ copy/contiguous gs140_v60.exe "non_system_disk":[directory] c. Use writeboot to make the disk bootable. Specify the disk, directory and filename of the firmware.
e. Restart the inetd daemon: # /usr/sbin/inetd Note The bootpd and tftp daemon will be removed if the system is rebooted. Refer to the manual pages: bootpd(8) or tftpd(8) for more information. Use Man bootpd and man tftpd f. Enter the following command to boot from the BOOTP server: >>> boot -p bootp ewa0 Should a boot file "pathname" need to be specified in must be in quotes >>> boot -p bootp ewa0 -file “/dir1/dir2/filename” 4. Update the firmware at the UPD> prompt. a.
devices. WARNING: updates may take several minutes to complete for each device. Confirm update on: pfi0 [Y/(N)] y DO NOT ABORT! Updating to 3.20... Verifying 3.20... pfi0 c. After you have updated the firmware type UPD> verify kn7cg-ab0_arc kn7cg-ab0 kzpsa0 pfi0 d. Type Verifying Verifying Verifying Verifying verify PASSED. to check the update V5.68... PASSED. V5.8-2... PASSED. A12... PASSED. 3.20... PASSED. Exit to leave the utility. UPD> exit Initializing... 5.
P02>>> build -e Build EEPROM on kn7cg-ab2 ? [Y/N]> y EEPROM built on kn7cg-ab2 The build -e command may prompt you for a system serial number and module part number. P00>>> build -e Build EEPROM on kn7cg-ab0 ? [Y/N]> y Please input module information for CPU module in slot 0 Module Serial Number> AY80973463 Module Unified 2-5-2.4 Part Number> 00-E2063-DA.C02 EEPROM built on kn7cg-ab0 c. The build -n command is used to format the NVR (non-volatile RAM) . This command is not documented in the release notes.
Transferring control... 7. The RUN command has 4 options. Rcu - Run the RAID Configuration Utility swxcrfw - Update the firmware on the RAID controller eeromcfg – Run the ISP1020 EEPROM Configuration Utility (KFTIA and other ISP1020 Controllers i.e. KZPBA ) util_cli – Run the KZPSA Configuration Utility lp6ldr - KGPSA firmware update utility RCU and SWXCRFW are on floppy and require a floppy drive. RCU is also on the CD. EEROMCFG and UTIL_CLI are available on floppy or CD. a.
On CDs V3.5 and earlier use P02>>> run iso9660:[CDROM.UTILITY]UTIL_CLI.EXE -d dkd500 -p 0 d. If updates to KGPSA firmware are required P02>>> set arc_enable on P02>>> set console_mode advanced P02>>> init P02>>> load –f iso9660 – load CDROM driver P02>>> run iso9660:[UTILITY]lp6ldr.exe -d dkd500 -p 0 (specify CD loaded into DKD500 on PCI bus 0 ) The utility lp6dutil will not properly function on the TurboLaser or GS series machine thru the serial port. You will see a repeating character problem. 8.
>>> kzpsa_edit busid kzpsa0 kzpsa0 bus id = 7, new bus id ? 6 Modify four bytes of parameters >>> kzpsa_edit -offset 0 -value 11223344 kzpsa0 Set one bit of the parameters >>> kzpsa_edit -offset 0 -bit 1 -set kzpsa0 Set all defaults >>> kzpsa_edit -sd kzpsa0 127
128
Compaq AlphaServer GS80/GS160/GS320 The AlphaServer GS80/GS160/GS320 has an SRM console located on every standard I/O module in the PCI box/boxes. It also has five different micro firmwares on four different modu1es. All micros in the machine must be the same version. There are also failsafe loaders on the modules. These are only to be updated in the factory. You can NOT have mixed versions and expect it to work.
o • • • • • UPD> UPDATE Answer "Y" to update all devices including SRM and micros When the update completes you will be at the SCM> prompt. Execute a BUILD EEPROM command from each SCM console. o SCM_E0> BUILD EEPROM o SLV_E1> BUILD EEPROM o etc. Reset SCM NVR settings to original settings. Power on the system Reset SRM console variable as necessary. Init the machine and reboot. 1.
2. P00>>> show * to printout all the SRM environmental variables. Check all customer set variables. Also verify the setting of the following variables. Bootdef_dev Boot_osflags Auto_action All the “lp” variables a. Set Auto_action to HALT P00>>> set Auto_action halt 3. Print out all SCM NVRAM console variables using the show nvr command from SCM>.
Method 3 - Create a Bootable CD Using a CD Writer and the .iso Firmware File Files in the Alpha Systems Firmware web site that have a ".iso" file type are ISO9660 image files and can be used to create bootable CD-ROMs. ZIP files that have "_iso" in the file name contain a ".iso" file which, when extracted, can be used to create a bootable CD-ROM. a. Make sure you have a CD writer and software package that is capable of creating a CD from an image file. b. Obtain the .
Update VAX portion of boot block (default is Y): No Update Alpha portion of boot block (default is Y):Yes Target system device (and boot file if not VMB.EXE):$1$DUA5:[TEMP]gs320_v61.exe d. >>> b -fl 0,0 dua5 System Disk a. Only steps a and b above are used. Do NOT execute writeboot step c. b. Specify the flags of 0,a0 and use "system_disk":[sys0.sysexe]filename for bootfile. >>> boot -fl 0,a0 dua0 bootfile: dua0:[sys0.sysexe]gs320_v61.exe Method 6 - BOOTP Network Upgrade - Tru64 UNIX a.
6. At the UPD> prompt type list to see current and update versions. Then execute the update command. ***** Loadable Firmware Update Utility ***** ---------------------------------------------------------------------------Function Description ---------------------------------------------------------------------------Display Displays the system’s configuration table. Exit Done exit LFU (reset). List Lists the device, revision, firmware name, and update revision. Readme Lists important release information.
fwa0 Updating to 3.20... Verifying 3.20... pga0 Updating to SS3.03A1... Verifying SS3.03A1... PASSED. pgb0 Updating to SS3.03A1... Verifying SS3.03A1... PASSED. pgc0 Updating to SS3.03A1... Verifying SS3.03A1... PASSED. pgd0 Updating to DS3.81A4... Verifying DS3.81A4... PASSED. pge0 Updating to SS3.03A1... Verifying SS3.03A1... PASSED. pua0 Updating to A420... micro Updating to V6.1(10.11/13:32)... Verifying A420... PASSED. PASSED.
MEM0 added to QBB1 MEM1 added to QBB1 MEM2 added to QBB1 MEM3 added to QBB1 IOR01 added in QBB1 CPU0 added to QBB1 CPU1 added to QBB1 CPU2 added to QBB1 CPU3 added to QBB1 SCM_E0> QBB2 Directory Module Added Power Supply-1 present in Subrack-2 Power Supply-2 present in Subrack-2 Power Supply-3 present in Subrack-2 QBB2 3.3V Main Power Converter present QBB2 3.
Update Cmd processed Transferring hex file.................. ~I~ Flashing node 30 (please wait) ~I~ Flashing node 31 (please wait) ~I~ Flashing node 32 (please wait) ~I~ Flashing node 33 (please wait) CSB download of .Hex file complete Updating HPM node 40 Update Cmd processed Transferring hex file.................. CSB download of .Hex file complete Updating PSM nodes 30,31,32,33 Update Cmd processed Transferring hex file.......................... CSB download of .
Firmware Update is now complete. If you require a partitioned system, please set your HP_COUNT and ’POWER ON -ALL’. For non-partitioned systems enter ’POWER ON’ 7. At the SCM prompt show the NVR variables and then execute the build eeprom command.
Errors • If a firmware update is attempted with hp_count set to a value other than 0 (system hard partitioned), it will not load micros and you will get an error message. LFU micro updates are not supported when the system is hard partitioned. Please power down and unpartition first.
Method 6 - SCM Update Laptop system setup When the SCM update command is used, firmware update files are downloaded from some source to the master SCM module. To perform the update from a laptop, the COM1 port of the laptop must be set appropriately. the following table shows the settings for four versions of the Windows operating system. These Setting must be exact to function properly.
Powerterm 525 setup 1. 2. 3. 4. 5. Start Power Term. At the Connect dialog box, set: Session type COM Terminal type VT420-8 Baud Rate 57600 Stop Bits 1 Port Number 1 Parity 8/none Flow Control Xon/Xoff Click Connect. From the Communications menu, select File Transfer Setup, and set: Host Data Type 8-Bit (DOS – Ascii) PC Data Type 8-Bit (DOS – Ascii) Click OK. SCM Update Files Below is a table of the files that can be flashed using the update command.
SCM update – Conditions of Note When Using This Update Method CAUTION! These allowable states may be risky. Engineering prefers that all firmware upgrades be done with the operating system down and the entire system powered off. • • • • • • A master and slave SCM may be updated using this method but a master SCM cannot update a slave. To update either a master or slave the device downloading the SCMROM.HEX file must be run connected physically to the target standard I/O local port.
• • • • • • • • • • • • • • • POWER OFF the system or specific partition in preparation for the firmware upgrade. o POWER OFF or o POWER OFF –part # Excute the SHOW CSB command to obtain the necessary CSB addresses o SHOW CSB Locate the ID of the SCM master and update it. o UPDATE –CSB E0 (if ID is E0) o Select the SCMROM.HEX file to load. This will load file, power on and init. Execute a BUILD EEPROM command.
SCM Update Example ( PSM only) SCM_E0> power off – part 0 SCM_E0> sho csb CSB Type Firmware Revision FSL Revision Power State 10 11 12 30 PBM PBM PBM PSM T05.5 T05.5 T05.5 T05.5 (05.04/02:07) (05.04/02:07) (05.04/02:07) (05.04/02:04) X4.3 X4.3 X4.3 T4.0 ON ON ON OFF 30 C0 C1 C2 C0 C1 C2 C3 31 31 C4 C5 C6 C7 C4 C5 40 E0 E1 E2 E6 XSROM CPU0/SROM CPU1/SROM CPU3/SROM IOR0 IOR1 IOR2 IOR3 PSM XSROM CPU0/SROM CPU1/SROM CPU0/SROM CPU1/SROM IOR0 IOR1 HPM SCM MASTER SCM SLAVE SCM SLAVE SCM SLAVE T05.
. AlphaServer DS10 and Professional WorkStation XP900 The AlphaServer DS10 and the Professional WorkStation XP900 systems contains one flash rom. It contains ARC console firmware for Windows NT and SRM console firmware for Tru64 UNIX and OpenVMS. When ever the motherboard is replaced the firmware may need to be updated. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available. The console firmware is NOT present on the V5.
AlphaServer DS10 466 MHz SRM Console: V54-2 PALcode: OpenVMS PALcode V1.56-45, Tru64 UNIX PALcode V1.50-48 Processors CPU 0 Alpha 21264-4 466 MHz SROM Revision: V1.8.208 Bcache size: 2 MB Core Logic Cchip DECchip 21272-CA Rev 2 Dchip DECchip 21272-DA Rev 2 Pchip 0 DECchip 21272-EA Rev 2 TIG Rev 2.1 Arbiter Rev 3.
2. >>> show or show * to printout all the environmental variables. Check all customer set variables. Also verify the setting of the following variables. Bootdef_dev Boot_osflags Auto_action 3. Verify the motherboard switches are in the default position. The default position enables writes to the flash. 4. Boot the firmware using one of the following methods. Method 1 – Load the Console Firmware Off a Local CDROM SRM Console a. Insert the CD in the local CDROM. b.
will now be executed. ENTER = Execute ESC = Continue g. ESC takes you back to AlphaBIOS setup menu h. ENTER will reset the system and reload the new AlphaBIOS/SRM image. Method 4 - Using the Console LFU Command Note: You may also have problems with files saved from Netscape. Either use Internet Explorer to download files or if using Netscape, get the files from the website at ftp://ftp.digital.com/pub/Digital/Alpha/firmware/. Floppy - CPU Firmware Only a. Copy the files ds10fw.txt, pc264nt.
Example of the file PC264NT.ROM nt_fw DS10SRM.ROM srm_fw CCMAB022 ccmab_fw DFXAA320 NOTE: dfxaa_fw The bolded area are filenames that were added to the KZPSAA12 standard ds10fw.txt file to allow options firmware to load. kzpsa_fw CIPCA420 cipca_fw ! This file is a list of all the firmware for the system. The exclamation point above is the file terminator, so anything below it will not be seen by the update utility. Anything above the exclamation point must adhere to the existing format.
Network a. Copy the following files to MOM$LOAD of you local MOP server. ds10fw.txt ds10srm.rom pc264nt.rom b. Set the attributes for the file using the following OpenVMS command on each file. $ set file/attr=rfm:fix,lrl:512,mrs:512,rat:none filename.sys c. Execute LFU command and select device EWA0 for Digital PCI Ethernet or FWA0 for Digital PCI FDDI (DEFPA). Specify ds10fw.txt P00>>> lfu Checking dqa0.0.0.13.0 for the option firmware files. . . Checking dva0 for the option firmware files. . .
Method 6 - Boot Off of a Disk - Non-System Disk and System Disk Using OpenVMS Non-System Disk a. Locate the firmware file ds10_v6_1.exe at the firmware website and copy to your system b. Set the VMS attributes on the file and copy it contiguous to the target disk (non-system) and directory with the following commands: $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) ds10_v6_1.exe $ copy/contiguous ds10_v6_1.exe "non_system_disk":[directory] c. Use writeboot to make the disk bootable.
Note The bootpd and tftp daemon will be removed if the system is rebooted. Refer to the manual pages: bootpd(8) or tftpd(8) for more information. Use Man bootpd and man tftpd f. Enter the following command to boot from the BOOTP server: >>> boot -p bootp ewa0 Should a boot file "pathname" need to be specified in must be in quotes >>> boot -p bootp ewa0 -file “/dir1/dir2/filename” 5. At the UPD> prompt type list to verify current and update versions.
AlphaServer DS10 Jumpers Motherboard Set SW3-8 ON to enable the FailSafe Loader 153
154
AlphaServer DS20/DS20E The AlphaServer DS20 system contains one flash rom. It contains ARC console firmware for Windows NT and SRM console firmware for Tru64 UNIX and OpenVMS. The ability to write to this rom is controlled by switch SW3 #8 on the motherboard. When ever the motherboard is replaced the firmware may need to be updated. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available. The console firmware is NOT present on the V5.
P00>>> sho version version P00>>> show pal pal T5.4-3 Dec 9 1998 11:49:01 OpenVMS PALcode V1.48-37, Digital UNIX PALcode V1.44-40 P00>>> sho config AlphaServer DS20 500 MHz SRM Console: T5.4-3 PALcode: OpenVMS PALcode V1.48-37, Digital UNIX PALcode V1.44-40 Processors CPU 0 CPU 1 Alpha 21264-3 500 MHz Bcache size: 0 MB SROM Revision: X1.72 Alpha 21264-3 500 MHz Bcache size: 4 MB SROM Revision: X1.
ewa0.0.0.2002.1 ISA Slot 0 Device 0 1 2 3 4 Name Type MOUSE Embedded Yes KBD Embedded Yes COM1 Embedded Yes COM2 Embedded Yes LPT1 Embedded Yes 5 FLOPPY Embedded Enabled 60 60 3f8 2f8 3bc Yes 00-06-2B-00-0A-43 BaseAddr 12 1 4 3 7 3f0 6 IRQ DMA 2 2. >>> show or show * to printout all the environmental variables. Check all customer set variables. Also verify the setting of the following variables. Bootdef_dev Boot_osflags Auto_action 3. Verify the motherboard switches are in the default position.
has completed. You will be prompted to type F10 to continue or ESC to abort. Pressing F10 will display a window with writing progress and verifying progress bars. e. Next pc264srm.rom will load and you will receive a window that lists Old and New Versions of SRM and display the same warning listed above. You will be prompted to type F10 to continue or ESC to abort. Pressing F10 will display a window with writing progress and verifying progress bars. f.
Copying Copying Copying Copying Copying Copying Copying Copying pc264fw.txt from dva0. . . PC264NT.SYS from dva0. . . PC264SRM.SYS from dva0. . . PC264FSB.SYS from dva0. . . ccmab022.sys from dva0. . . cipca420.sys from dva0. . . dfxaa320.sys from dva0. . . kzpsaa12.sys from dva0. . . UPD> CD a. Insert the CD in the local CDROM. b. Execute LFU command and if the firmware CD is loaded it will not ask any questions and will load the files.
160
Method 5 - Booting Off the Network - OpenVMS a. Copy firmware.sys file to MOM$LOAD of an existing node in the cluster b. Set VMS attributes on the file with the following command. $ Set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) ds20_v6_1.sys c.
Method 7 - BOOTP Network Upgrade – Tru64 UNIX a. Mount the Firmware Update CD using the following command: # mount -rt cdf– -o noversion /dev/rz4c /mnt b. Modify or Create the Client Database in the /etc/bootptab File :ht::ha=:bf=:ip= where: host is the system name in /etc/hosts hw_type is the hardware type. Proteon is ht = 4. Ethernet is ht = 1. Regular token-ring (IEEE 802) is ht = 6. hw_addr is the hardware address: use the console command show device.
***** Loadable Firmware Update Utility ***** -----------------------------------------------------------------------------Function Description -----------------------------------------------------------------------------Display Displays the system’s configuration table. Exit Done exit LFU (reset). List Lists the device, revision, firmware name, and update revision. Readme Lists important release information. Update Replaces current firmware with loadable data image.
164
AlphaServer DS20 Jumpers Motherboard SW2 Label Function Default 1 FSB - FailSafe Booter Tells the SROM to jump either to SRM or the FSB (currently the debug monitor) off * 2 CACHE_OFF_A off 3 CACHE_OFF_ B These two bits are currently assigned to different (faster/slower) memory timings 4 MINI_DEB The SROM jumps to the SROM Mini debugger off 5 TS_SPD0 Tsunami speed[0] on 6 TS_SPD1 Tsunami speed[1] on 7 TS_SPD2 Tsunami speed[2] off 8 PASS_BY Selects the debug monitor to output
** SW3-4 default is listed as OFF but it needs to be ON in our lab 166
167
Compaq AlphaServer ES40/TS40 The Compaq AlphaServer ES40 clipper system backplane module (CSB) has 2 1MB flash roms that contain an Abios console firmware for AlphaBIOS and a SRM console firmware for Tru64 UNIX and OpenVMS. The system also has TIG, RMC and SROM code that gets loaded. The ability to write to these roms is controlled by setting jumpers J12 and J13 on the CSB to pins 1-2. When ever the system board is replaced the firmware will need to be updated.
Memory size 512 MB testing memory … probe I/O subsystem probing hose 1, PCI bus 0, slot 6 -- ewa -- DE500-BA Network Controller probing hose 0, PCI probing PCI-to-ISA bridge, bus 1 bus 0, slot 2 -- vga -- DEC PowerStorm bus 0, slot 4 -- pka -- NCR 53C895 bus 0, slot 15 -- dqa -- Acer Labs M1543C IDE bus 0, slot 15 -- dqb -- Acer Labs M1543C IDE starting drivers entering idle loop initializing keyboard starting console on CPU 1 initialized idle PCB initializing idle process PID lowering IPL CPU 1 speed is 2.
Slot 2 4 512 MB of System Memory Option DEC PowerStorm NCR 53C895 7 15 Acer Labs M1543C Acer Labs M1543C IDE 19 Acer Labs M1543C USB Slot 6 P00>>> Hose 0, Bus 0, PCI pka0.7.0.4.0 dka0.0.0.4.0 dqa.0.0.15.0 dqb.0.1.15.0 dqa0.0.0.15.0 Option Floppy Hose 0, Bus 1, ISA dva0.0.0.1000.0 Option DE500-BA Network Con Hose 1, Bus 0, PCI ewa0.0.0.6.1 SCSI Bus ID 7 RZ2CA-LA Bridge to Bus 1, ISA TOSHIBA CD-ROM XM-* 00-00-F8-1B-2B-EE 2. >>> show or show* to printout all the environmental variables.
$ Set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) es40_v6_1.sys d. Enable service on that node from NCP $ MC NCP MC NCP> Show Known Circuit Characteristic Known Circuit Volatile Characteristics as of 12-FEB-1997 19:27:41 Circuit = BNA-0 - Circuit State = Service = Counter timer = Designated router = Cost = Maximum routers allowed = Router priority = Hello timer = Type = Adjacent node = Listen timer = name will change from system to system on disabled (if enabled skip to boot command) 65534 28.
e. Insert the first floppy in the ES40 DVA0 and boot it. At the UPD prompt type exit and answer Y for manual update >>> Boot DVA0 Checking dqa0.0.0.15.0 for the option firmware files. . . dqa0.0.0.15.0 has no media present or is disabled via the RUN/STOP switch dqa0.0.0.15.0 has no media present or is disabled via the RUN/STOP switch Checking dva0 for the option firmware files. . . If you have a floppy containing option firmware, Please insert it now and hit when ready.
Tru64 UNIX This method requires two floppies. One with the LFU utility and the other with the system firmware. There are 4 different LFU utilities depending on the system type. a. Locate the following files and unzip them on a PC. They can be found on the firmware website at http://ftp.digital.com/pub/Digital/Alpha/firmware/ • clu.exe ilu.exe flu.exe glu.exe ES40.zip ES40lp.zip ES40cv.zip TS20-TS40.zip These file contain the SRM, AlphaBIOS, LFU image and mkbootfirm.exe files. b.
o. Insert the first floppy in the ES40 DVA0 and boot it. At the UPD prompt type exit and answer Y for manual update >>> Boot DVA0 Checking dqa0.0.0.15.0 for the option firmware files. . . dqa0.0.0.15.0 has no media present or is disabled via the RUN/STOP switch dqa0.0.0.15.0 has no media present or is disabled via the RUN/STOP switch Checking dva0 for the option firmware files. . . If you have a floppy containing option firmware, Please insert it now and hit when ready.
Method 5 - OpenVMS - Boot Off of a Disk - Non-System Disk and System Disk Non-System Disk a. Locate the firmware file es40_v6_1.exe at the firmware website and copy it to your system b. Set the VMS attributes on the file and copy it contiguous to the target disk (non-system) and directory with the following commands: $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) es40_v6_1.exe $ copy/contiguous es40_v6_1.exe "non_system_disk":[directory] c. Use writeboot to make the disk bootable.
Note The bootpd and tftp daemon will be removed if the system is rebooted. Refer to the manual pages: bootpd(8) or tftpd(8) for more information. Use Man bootpd and man tftpd f. Enter the following command to boot from the BOOTP server: >>> boot -p bootp ewa0 Should a boot file "pathname" need to be specified in must be in quotes >>> boot -p bootp ewa0 -file “/dir1/dir2/filename” 5.
177
Compaq AlphaServer ES40 Jumpers CSB - System Backplane CSB Jumper Position Function J21 1-2 2-3 1-2 2-3 Disable RMC Flash Update Enable RMC Flash Update Load TIG from Flash RAM Load TIG from Serial ROM J20 1-2 = “0” 2-3 = “1” FIR_FUNC2 FIR_FUNC Table J22 1-2 = “0” 2-3 = “1” FIR_FUNC1 J23 1-2 = “0” 2-3 = “1” FIR_FUNC0 000 = Normal 001 = Prevent FLASH Loads/Load from SROM 010 = Load from Floppy 111 = Lock Console 1-2 2-3 Enable Flash ROM Update Disable Flash ROM Update J24 J12 / J13 178
179
Compaq AlphaServer ES45 The Compaq AlphaServer ES45 privateer system backplane module (CSB) contains a flash ROM that holds a SRM console firmware for Tru64 UNIX and OpenVMS. The system also has TIG, RMC and SROM code that gets loaded. The ability to write to these roms is controlled by setting jumpers J7, J19 and J20 on the CSB to pins 1-2. When ever the system board is replaced the firmware will need to be updated.
Memory sizing in progress Memory configuration in progress Testing AAR1 Memory data test in progress Memory address test in progress Memory pattern test in progress Testing AAR0 Memory data test in progress Memory address test in progress Memory pattern test in progress Memory thrashing test in progress Memory initialization Loading console Code execution complete (transfer control) OpenVMS PALcode V1.93-37, Tru64 UNIX PALcode V1.
initialized idle PCB initializing idle process PID lowering IPL CPU 3 speed is 1000 MHz create powerup initializing GCT/FRU at 220000 initializing pka dqa dqb eia Memory Testing and Configuration Status Array Size Base Address --------- ---------- ---------------0 512Mb 0000000000000000 1 512Mb 0000000020000000 Intlv Mode ---------2-Way 2-Way 1024 MB of System Memory Testing the System Testing the Disks (read only) Testing the Network AlphaServer ES45 Console V6.
Option Floppy Hose 0, Bus 1, ISA dva0.0.0.1000.0 Slot 6 Option Yukon PCI Hot-Plug C Hose 1, Bus 0, PCI - 33 MHz Slot 2 6 Option QSW ELan3 Yukon PCI Hot-Plug C Hose 3, Bus 0, PCI - 66 MHz 2. >>> show or show* to printout all the environmental variables. Check all customer set variables. Also verify the setting of the following variables. Bootdef_dev Boot_osflags Auto_action 3. Check that the ROM update jumpers are enabled. Consult the service manual for their location and setting.
Router priority Hello timer Type Adjacent node Listen timer = = = = = 64 15 Ethernet 28.1023 (CXO28A) 30 NCP> Set Circ BNA-0 State OFF - This step will stop network activity NCP> Set Circ BNA-0 Service Enable NCP> Set Circ BNA-0 State ON e. >>> boot eia0 -file es45_v6_1 (Leave off .SYS or node that services request will get an error - BAD MOP FID) Method 4 – Using the Console LFU Command Floppy a. Obtain the ES45 disk1.zip file from the firmware website at http://ftp.digital.
***** Loadable Firmware Update Utility ***** ---------------------------------------------------------------------------Function Description ---------------------------------------------------------------------------Display Displays the system’s configuration table. Exit Done exit LFU (reset). List Lists the device, revision, firmware name, and update revision. Readme Lists important release information. Update Replaces current firmware with loadable data image. Verify Compares loadable and hardware images.
d. >>> boot -fl 0,0 dua5 System Disk a. Only steps a and b above are used. Do NOT execute writeboot step c. b. Specify the flags of 0,a0 and use "system disk":[sys0.sysexe]filename for the bootfile. >>> b -fl 0,a dua0 bootfile: dua0:[sys0.sysexe]es45_v6_1.exe Method 6 - BOOTP Network Upgrade – Tru64 UNIX a. Mount the Firmware Update CD using the following command: # mount -rt cdf– -o noversion /dev/rz4c /mnt b.
execute Update and Verify ***** Loadable Firmware Update Utility ***** ---------------------------------------------------------------------------Function Description ---------------------------------------------------------------------------Display Displays the system’s configuration table. Exit Done exit LFU (reset). List Lists the device, revision, firmware name, and update revision. Readme Lists important release information. Update Replaces current firmware with loadable data image.
Compaq AlphaServer ES45 Jumpers CSB - System Backplane 188
CSB Jumper Position Function J20 1-2 2-3 1-2 2-3 1-2 2-3 Disable RMC Flash Update Enable RMC Flash Update (Normal) Enable TIG Flash ROM Update (Normal) Disable TIG Flash ROM Update Enable SROM Flash ROM Update (Normal) Disable SROM Flash ROM Update J21 1-2 = “0” 2-3 = “1” FIR_FUNC2 J22 1-2 = “0” 2-3 = “1” FIR_FUNC1 J23 1-2 = “0” 2-3 = “1” FIR_FUNC0 J24 1-2 2-3 Load TIG from flash ROM (Normnal) Failsafe – Load TIG from SROM J7 J19 FIR_FUNC Table 000 = Load from flash ROM (Normal) 001 = Loa
AlphaStation 200/250 Full Flash Systems The AlphaStation 200 system comes in full and half flash configurations. Half flash systems contain only 2 roms and can not have both SRM and ARC console loaded at the same time. The AlphaStation 200 and 250 full flash systems contain 4 flash roms on the motherboard. Two contain ARC console firmware for Windows NT and two contain SRM console firmware for Tru64 UNIX and OpenVMS.
MEMORY 32 Meg Bank 0 Bank 1 Bank 2 of System Memory = 16 Mbytes(8 MB Per Simm) Starting at 0x0 = 16 Mbytes(8 MB Per Simm) Starting at 0x1000000 = No Memory Detected PCI Bus Bus 00 Slot 06: NCR 810 Scsi Controller pka0.7.0.6.0 dka0.0.0.6.0 dka400.4.0.6.0 SCSI Bus ID 7 RZ26L RRD43 Bus 00 Slot 07: Intel SIO 82378 Bus 00 Slot 11: Digital ZLXp Graphics Controller Bus 00 Slot 12: Digital DE435 Network Controller ewa0.0.0.12.
Method 2 - Boot the Console CD Off of an Infoserver a. Insert the CD in the Infoserver b. >>> boot ewa0 -file filename (leave off the .sys extension) Method 3 - Booting Off the Network - OpenVMS a. Copy firmware.sys file to MOM$LOAD of an existing node in the cluster b. Set VMS attributes on the file with the following command. $ Set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) firmware.sys c.
System Disk a. Only steps a and b above are used. Do NOT execute writeboot step c. b. Specify the flags of 0,a0 and use "system disk":[sys0.sysexe]filename for the bootfile. >>> b -fl 0,a dua0 bootfile: dua0:[sys0.sysexe]as200_v7_0.exe Method 5 - Boot Off of a Bootable Floppy OpenVMS AXP a. Init and mount to floppy. Create a directory and copy the firmware to the Floppy with the following commands. $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) as200_v7_0.
Windows NT a. Copy the firmware file to a FAT formatted floppy with the update image filename of a:\fwupdate.exe. b. Shut down NT and from the NT Console menu, select "Install“ new firmware". Method 6 – BOOTP Network Upgrade – Tru64 UNIX a. Mount the Firmware Update CD using the following command: # mount -rt cdf– -o noversion /dev/rz4c /mnt b.
5.
UPD> update * or update Will update all LFU supported devices found in this system UPD> update pka0 - will update device PKA0 Confirm update on: pka0 [Y/(N)]Y WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! pka0 Updating to A12... Verifying A12... PASSED. UPD> update fwa0 -path m–pd1:new_firm/eza0 Will update the device named fwa0 with firmware NEW_FIRM from the network. UPD>verify fwa0 pka0 Verifying 3.20... PASSED. Verifying A12... PASSED. 9.
197
AlphaStation 200 Jumpers Motherboard 198
Setting AlphaStation 200 Motherboard Jumper Function Description (1 to 2) Mini-console. (2 to 3) (D) Jump to main console. (1 to 2) Boot floppy. (2 to 3) (D) Normal (flashROM load). J3 (1 to 2) (D) (2 to 3) Reset. Halt Interrupt Request. The position of J1 determines whether the SROM code goes to the SROM mini-console (for manufacturing use) or passes control to the next stage of initialization, the DROM code.
AlphaStation 250 Jumpers Motherboard Jumper J1 J2 J3 J4 J7 J21 J25 J26 J27 J32 Pins (1 to 2) Function Mini-console (2 to 3) (D) Jump to main console (1 to 2) Boot floppy (2 to 3) (D) Normal (flashROM load) (1 to 2) (D) (2 to 3) (1 to 2) (D) Reset Halt Interrupt Request Enables flashROM writes (2 to 3) (1 to 2) (D) (2 to 3) (1 to 2) (3 to 4) (5 to 6) Disables writes 267 MHz CPU Not used Not used Hang off 1 (D) Hang off 3 (D) Hang off 5 (D) (1 to 2) (D) 87332 Super I/O chip Removed (1 to 2
201
AlphaStation 200/255 Half Flash Systems The AlphaStation 200 system comes in full and half flash configurations. The AlphaStation 255 only comes in a half flash configuration. Half flash systems contain only 2 roms on the motherboard and can not have both SRM and ARC console loaded at the same time. The ability to write to these roms is controlled on the AlphaStation 200 by jumper J6 on the motherboard/system module and by switch 3 on the AlphaStation 255.
MEMORY 128 Meg of System Memory Bank 0 = 128 Mbytes PCI Bus Bus 00 Slot 06: NCR 810 Scsi Controller pka0.7.0.6.0 dka0.0.0.6.0 dka400.4.0.6.0 SCSI Bus ID 7 RZ26L RRD43 Bus 00 Slot 07: Intel SIO 82378 Bus 00 Slot 11: Digital ZLXp Graphics Controller Bus 00 Slot 12: Digital DE435 Network Controller ewa0.0.0.12.
Method 3 - Booting off the Network - OpenVMS a. Copy firmware.sys file to MOM$LOAD of an existing node in the cluster b. Set the VMS attributes on the file with the following commands. $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) firmware.sys c.
Method 5 - Boot Off of a bootable floppy OpenVMS AXP a. Init and mount to floppy. Create a directory and copy the firmware to the floppy with the following commands. The commands shown are for the AlphaStation 255. For the AlphaStation 200 use directory [ALPHA200] and file as200_v7_0.exe. $ $ $ $ $ Set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) as255_v8_1.exe init/dens=HD/index=begin dva0: fwupdate mount dva0: fwupdate create/dir dva0:[ALPHA255] copy/contiguous as255_v8_1.exe dva0:[ALPHA255]fwupdate.
Method 6 – BOOTP Network Upgrade – Tru64 UNIX a. Mount the Firmware Update CD using the following command: # mount -rt cdf– -o noversion /dev/rz4c /mnt b. Modify or Create the Client Database in the /etc/bootptab File :ht::ha=:bf=:ip= where: host is the system name in /etc/hosts hw_type is the hardware type. Proteon is ht = 4. Ethernet is ht = 1. Regular token-ring (IEEE 802) is ht = 6. hw_addr is the hardware address: use the console command show device.
Apu-> update arc - you can not do both, Only Update ARC or Update SRM APU-I VERIFY LOADED ROM IMAGE APU-I VERIFY LOADED ROM IMAGE DONE APU-I VERIFY LOADED ROM IMAGE APU-I VERIFY LOADED ROM IMAGE DONE APU-I VERIFY LOADED ROM IMAGE APU-I VERIFY LOADED ROM IMAGE DONE APU-I *** ROMS 0,1 CONTENTS WILL BE DESTROYED *** APU-I ARE YOU READY TO PROGRAM DEVICE ? (Y/N )Y APU-I ROM SET NOT ERASED APU-I PRECHARGING DEVICE APU-I ERASING ROM DEVICE APU-I PROGRAMMING DEVICE APU-I ROM 0 VERIFYING ROM IMAGE APU-I PROGRAMMING
UPD> update pka0 - will update device PKA0 Confirm update on: pka0 [Y/(N)]Y WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! pka0 Updating to A12… Verifying A12… PASSED. UPD> update fwa0 -path m–pd1:new_firm/eza0 Will update the device named fwa0 with firmware NEW_FIRM from the network. UPD> verify fwa0 pka0 Verifying 3.20… PASSED. Verifying A12… PASSED. 9.
209
AlphaStation 200 Jumpers Motherboard 210
Setting AlphaStation 200 Motherboard Jumper Function Description (1 to 2) Mini-console. (2 to 3) (D) Jump to main console. (1 to 2) Boot floppy. (2 to 3) (D) Normal (flashROM load). J3 (1 to 2) (D) (2 to 3) Reset. Halt Interrupt Request. The position of J1 determines whether the SROM code goes to the SROM mini-console (for manufacturing use) or passes control to the next stage of initialization, the DROM code.
AlphaStation 255 Jumpers Motherboard Switch Setting Function OFF OFF Normal ON OFF Stop at SROM prompt OFF ON ON ON Boot from Floppy (including Fail-safe Loader) Reset RTC and NRAM 1-2 OFF ON OFF ON OFF 3 4 Write enabled (default) Writes disabled Halt interrupt request Reset Enable TC sound (Default) Diables TC sound 5 ON 6-8 On Off On Off On Off On Off On On Off Off On On Off Off On On On On Off Off Off Off 133 166 200 233 266 300 333 366 Description Switches 1 and 2 are the config
213
AlphaServer 400 / AlphaStation 400 The AlphaServer and AlphaStation 400 systems contain 4 flash roms on the CPU module. Two contain ARC console firmware for Windows NT and two contain SRM console firmware for Tru64 UNIX and OpenVMS. The ability to write to these roms is controlled by jumper J4 on the CPU module. When ever the CPU module is replaced the firmware will need to be updated. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available.
MEMORY 32 Meg Bank 0 Bank 1 Bank 2 of System Memory = 16 Mbytes(8 MB Per Simm) Starting at 0x0 = 16 Mbytes(8 MB Per Simm) Starting at 0x1000000 = No Memory Detected PCI Bus Bus 00 Slot 06: NCR 810 Scsi Controller pka0.7.0.6.0 dka0.0.0.6.0 dka400.4.0.6.0 SCSI Bus ID 7 RZ26L RRD43 Bus 00 Slot 07: Intel SIO 82378 Bus 00 Slot 11: Digital ZLXp Graphics Controller Bus 00 Slot 12: Digital DE435 Network Controller ewa0.0.0.12.
Method 2 - Boot the Console CD Off of an Infoserver a. Insert the CD in the Infoserver b. >>> boot ewa0 -file f–lename (leave off the .sys extension) Method 3 - Booting off the Network - OpenVMS a. Copy firmware.sys file to MOM$LOAD of an existing node in the cluster b. Set the attributes on the file with the following commands: $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) firmware.sys c.
b. Set the flags of 0,a0 and use "system disk":[sys0.sysexe]filename for the bootfile. >>> b -fl 0,a– dua0 bootfile: dua0:[sys0.sysexe]as400_v72_1.exe Method 5 - Boot Off of a Bootable Floppy OpenVMS AXP a. Init and mount to floppy. Create a directory and copy the firmware to the floppy with the following commands. The commands shown are for the AlphaServer 400. For the AlphaStation 400 use directory [ALPHA400] and file as400_v72_1.exe.
Windows NT a. Copy the firmware file to a FAT formatted floppy with the update image filename of a:\fwupdate.exe. b. Shutdown NT and from the NT Console menu, select "Install“ new firmware". Method 6 - BOOTP Network Upgrade - Tru64 UNIX a. Mount the Firmware Update CD using the following command: # mount -rt cdfs -o noversion /dev/rz4c /mnt b.
6.
WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! pka0 Updating to A12... Verifying A12... PASSED. UPD> update fwa0 -path mopd1:new_firm/eza0 Will update the device named fwa0 with firmware NEW_FIRM from the network. UPD> verify fwa0 pka0 Verifying 3.20... PASSED. Verifying A12... PASSED. 10. Power cycle the machine to load console firmware then reset any environmental variables that changed, init and reboot.
221
AlphaServer 400 Jumpers Motherboard Jumpers Jumper J29 J32 J33 J34 J35 J39 J40 Motherboard Jumpers Pins 1 to 2 Pins 2 to 3 Function Clear CMOS Normal * Clear CMOS Clear Password Normal * Clear Password ** Color Mono * Display Type ** Recovery Mode Normal * Recovery mode ** Enable Disabled * BIOS upgrade ** Alpha AXP * Unsupported CPU selection Disable * Enable Reprogram boot Block ** * = default ** = These Functions are not used in the AlphaServer 400 Series 222
CPU Jumpers AlphaServer 400 CPU Jumpers Jumper Pins 1 to 2 Pins 2 to 3 J3 SROM mini-console Pass control to DROM* J4 Enable * Disable J5 Floppy loader (FSL) Reset * DROM Loads flashROM * Unsupported J6 Function Control whether the SROM code goes to the mini console (for manufacturing) or loads the DROM code.
AlphaStation 400 Jumpers Motherboard Jumpers Motherboard Jumpers Jumper J29 J32 Pins 1 to 2 Clear CMOS Clear Password Pins 2 to 3 Normal * Normal * Function Clear CMOS Clear Password ** J33 J34 J35 J39 J40 Color Recovery Mode Enable * Alpha AXP * Disable * Mono * Normal * Normal N/A Enable Display Type ** Recovery mode ** BIOS upgrade ** CPU selection Reprogram boot Block ** * = default ** = These Functions are not used in the AlphaStation 400 Series 224
Cpu Jumpers AlphaStation 400 CPU Jumpers Jumper J3 Pins 1 to 2 S-Port Pins 2 to 3 Normal * J4 Enable * Disable J5 J6 Floppy loader (FSL) Reset * DROM Loads flashROM * HALT Function Stay at SROM Prompt (MiniConsole) in S-Port Position Enables/disables Writes to FlashROM Determines DROM Load Action Reset/Halt Selection * = default 225
AlphaStation 500/600 The AlphaStation 500/600 systems contain 4 flash roms on the System module. Two contain ARC console firmware for Windows NT and two contain SRM console firmware for Tru64 UNIX and OpenVMS. The ability to write to these roms is controlled on the AlphaStation 500 by jumper J18 on the system module and on the AlphaStation 600 by jumper W13 on the system module. When ever the system module is replaced the firmware will need to be updated.
MEMORY Memory Size = 128Mb Bank -----00 Size/Sets ---------128Mb/1 Base Addr --------000000000 Speed ----Fast BCache Size = 4Mb Tested Memory = 128Mb PCI Bus Bus 00 Slot 06: DECchip 21040 Network Controller ewa0.0.0.6.0 00-00-FB-21-32-E8 Bus 00 Slot 07: Digital PV-PCI Graphics Controller Bus 00 Slot 09: ISP1020 Scsi Controller pka0.7.0.9.0 dka0.0.0.9.0 dka400.4.0.9.0 SCSI Bus ID 7 RZ25L RRD45 2. >>> show or show * to printout all the environmental variables. Check all customer set variables.
Method 3 - Booting Off the Network - OpenVMS a. Copy the firmware.sys file to MOM$LOAD of an existing node in the cluster b. Set the attributes on the file with the following commands: $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) firmware.sys c.
Method 5 - Boot Off of a bootable floppy OpenVMS AXP a. Init and mount to floppy. Create a directory and copy the firmware to the Floppy with the following commands $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) as500_v72_2.exe $ init/dens=HD/index=begin dva0: fwupdate $ mount dva0: fwupdate $ create/dir dva0:[AS500] $ copy/contiguous as500_v72_2.exe dva0:[AS500]fwupdate.exe b.
Method 6 - BOOTP Network Upgrade - Tru64 UNIX a. Mount the Firmware Update CD using the following command: # mount -rt cdfs -o noversion /dev/rz4c /mnt b. Modify or Create the Client Database in the /etc/bootptab File :ht::ha=:bf=:ip= where: host is the system name in /etc/hosts hw_type is the hardware type. Proteon is ht = 4. Ethernet is ht = 1. Regular token-ring (IEEE 802) is ht = 6. hw_addr is the hardware address: use the console command show device.
6. Verify that update was successful and exit Apu-> verify SRM ROM verify successful ARC /AlphaBIOS ROM verify successful Apu-> exit …Please Cycle System Power … 7. Power cycle the machine to load console firmware. If you are updating device firmware, proceed to step 8. 8. Update the option firmware. The options supported for update in the V5.9 CD firmware version are the DEFPA (PCI FDDI), KZPSA (PCI SCSI) and DEFEA (EISA FDDI) a. Boot the Option firmware file.
AlphaStation 500 Jumper Locations System Module Jumper J11 J12 J13 J14 J15 J16 J17 J19 System Module SROM Jumpers Position Function 0 Power Up (default) * 1 Mini Console 2 Floppy loader (Failsafe Loader) 3 MFG Memtest 4 Reserved 5 Reserved 6 MCHK Mini-Console 7 Noinit Mini-Console * Only one jumper can be used at a time.
System Board Jumpers Jumper J6 J9 J10 J18 J2, J20, J33.
AlphaStation 600 Jumper Locations System Module 234
System Board Jumpers W1-W8 Jumper Function W1 W2 W3 W4 W5 W6 W7 Normal power-up flow, SROM will default to floppy boot if Flash ROM is not loaded.
AlphaStation 600A The AlphaStation 600A systems contain flash roms on the System module. They contain ARC console firmware for Windows NT and SRM console firmware for Tru64 UNIX and OpenVMS. The ability to write to these roms is controlled on the AlphaStation 600A by jumper J50 on the system module. When ever the system module is replaced the firmware will need to be updated. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available.
Memory 64 Meg of System Memory Bank 0 = 64 Mbytes(16 MB Per Simm) Starting at 0x00000000 Bank 1 = No Memory Detected Bank 2 = No Memory Detected Bank 3 Slot Option Hose 0, Bus 0, PCI 5 Qlogic ISP1020 pka0.7.0.5.0 SCSI Bus ID 7 dka0.0.0.5.0 RZ28 dka400.4.0.5.0 RRD43 6 S3 Trio64/Trio32 7 Intel 82375eB Bridge to Bus 1, EISA 11 DECchip 20150-AA ewb0.0.0.11.0 08-00-2B-E5-CC-B1 Slot Option 1 ISA2000 Hose 0, Bus 1, EISA Slot Option 2 Qlogic ISP1020 3 Qlogic ISP1020 Hose 0, Bus 2, PCI pkb0.7.0.2002.0 pkc0.7.0.
Method 3 - Booting Off the Network - OpenVMS a. Copy the firmware.sys file and the option firmware files to MOM$LOAD of an existing node in the cluster. (These versions are from the V5.9 CD and may change) as600a_e5_v5_6.exe – This is the system firmware as1000fw.sys - This file tells update utility which option files to load. dfeaa130.sys - DEFEA firmware (EISA DEC FDDI controller. Pass 1 module only) dfeab320.sys - DEFEA firmware (EISA FDDI controller. All modules after pass 1) dfxaa320.
e. To update the option firmware, first create an option directory. $ set def dua0:[000000] $ create/dir [.options] f. Copy the option firmware files to the options directory. as1000fw.txt dfeaa130.sys dfeab320.sys dfxaa320.sys kzpsaa12.sys g. When booting the update utility enter the device name where the option firmware is located. System Disk a. Only steps a and b above are used. Do NOT execute writeboot step c. b. Specify the flags of 0,a0 and use "system disk":[sys0.sysexe]filename for the bootfile.
Tru64 UNIX a. Go to the Digital Internet firmware site at http://ftp.digital.com/pub/Digital/Alpha/firmware/ b. Copy the firmware.exe file from the Alpha600A directory to your system and rename it fwupdate.exe c. Download the file mkbootfirm.tar from the firmware website. ftp://ftp.digital.com/pub/Digital/Alpha/firmware/utilities/mkbootfirm.tar You can untar mkbootfirm on your target Tru64 UNIX system with the command: # tar xvf mkbootfirm.tar d.
c. If you wish to update the options firmware, you must create a second floppy. Download the following files from the options directory at the firmware website. as1000fw.txt dfeaa130.sys dfeab320.sys dfxaa320.sys kzpsaa12.sys d. FAT format a floppy and copy the files to the floppy. e. When the utility asks for the options floppy, insert it and tell the utility the device it is located on. Method 6 - BOOTP Network Upgrade - Tru64 UNIX a.
6. Execute list at the UPD prompt to check current versions. UPD> list Device ARC SRM Current Revision 5.64 v5.2-115 Filename arc_fw srm_fw dfxaa_fw dfeaa_fw dfeab_fw kzpsa_fw Update Revision 5.70 v5.6-114 3.20 1.3 3.20 A12 7. Update the firmware from the UPD> prompt UPD> update Confirm update on: ARC SRM [Y/(N)]y WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! ARC SRM Updating to v5.70… Verifying v5.70… PASSED. Updating to v5.6-114… Verifying v5.6-114… PASSED.
243
AlphaStation 600A Jumpers System Board Item 1 Jumper J50 2 3 J16 J53 4 J52 5 J56 6 7 J51 J25 System Module Jumpers and Locations Name Description FROM VPP enable Permits the 12 volts needed to update the Flash ROMs Fan Allows the large fan to be disabled. Fan shutdown Allows the software to shut down the system in the event of a fan failure. Temperature shutdown Allows the temperature chips to shut down the system in an orderly sequence.
Cpu Module Bank 0 1 CPU J1 Jumper Jumper Setting Function Standard boot setting Standard boot setting 2 Mini console setting (Internal use only) 3 Mini console setting (Internal use only) 4 Startup with no backup cache (Internal use only) 5 Mini console setting (Internal use only) 6 Mini console setting (Internal use only) 7 Fail-safe loader setting: selects fail-safe loader firmware Note The J1 jumper on the CPU card activates the SROM tests and the fail-safe loader.
Digital Personal WorkStation a/au Series The Digital Personal WorkStation a/au Systems contain a single 1MB flash Rom located on the motherboard. It contains ARC console firmware for Windows NT and SRM console firmware for Tru64 UNIX and OpenVMS. When ever the CPU motherboard is replaced the firmware will need to be updated. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available. There are several ways to upgrade the firmware.
MEMORY Memory Size = 192Mb Bank -----0 1 Size/Sets ---------64Mb 128Mb Base Addr --------08000000 00000000 Bcache Size = 2Mb Tested Memory = 192Mbytes PCI Bus Bus 00 Slot 03: Digital Semiconductor 21143 Network Controller ewa0.0.0.3.0 00-00-F8-75-5F-2A Bus 00 Slot 04: PCI IDE pqa0.0.0.4.0 dka0.0.0.4.
Method 1 - Load the Console Firmware Off a Local CDROM SRM Console a. Insert the CD in the local CDROM. b. >>> Boot -fl 0,a0 DKA400 BOOTFILE:[digitalpw]digitalpw_v72_1.exe Note: These filenames will change with different console versions. Apu-> See step 5 below for update procedure. ARC Console a. Insert the CD in the local CDROM. b. Enter the ARC menu by typing ARC or initializing system if os_type = NT c. Select Supplementary Menu and Install new Firmware Caution If you are running the V4.
Method 4 - Boot Off of a Disk - Non-System Disk and System Disk Using OpenVMS Non-System Disk a. Locate the firmware.exe file b. Set the attributes on the file and copy it contiguous to the target disk (non-system) and directory with the following commands: $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) firmware.exe $ copy/contiguous firmware.exe "non_system_disk":[directory] c. Use writeboot to make the disk bootable. Specify the disk, directory and filename of the firmware.
fddisk -fmt /dev/rfd0a e. Change default to directory with mkbootfirm.exe cd mkbootfirm f. Run mkbootfirm on the .exe firmware image that you downloaded. mkbootfirm uses a .exe firmware image to create a file that can be dd’d to floppy. The following will create a bootable floppy from a downloaded .exe firmware image: ./mkbootfirm fwupdate.exe | dd of=/dev/rfd0c bs=64k NOTE: Assumes mkbootfirm.exe is in current directory and floppy is in drive 0. g.
e. Restart the inetd daemon: # /usr/sbin/inetd Note The bootpd and tftp daemon will be removed if the system is rebooted. Refer to the manual pages: bootpd(8) or tftpd(8) for more information. Use Man bootpd and man tftpd f. Enter the following command to boot from the BOOTP server: >>> boot -p bootp ewa0 Should a boot file "pathname" need to be specified in must be in quotes >>> boot -p bootp ewa0 -file “/dir1/dir2/filename” 5. Enter the update utility.
Debug :Apu-> verify Version = v7.2 Vendor = DEC Product = MIATA Firmware = MIATA_SRM Length = 0x72200 1024KB ROM present Version = v7.2 Vendor = DEC Product = MIATA Firmware = MIATA_SRM Length = 0x72200 Version = v7.2 Vendor = DEC Product = MIATA Firmware = MIATA_SRM Length = 0x72200 SRM ROM verify successful Version = 5.70 Vendor = DEC Product = MIATA Firmware = MIATA_ARC Length = 0x677ac Version = 5.
>>> boot -fl 0,a0 DKA400 for the Personal WorkStation Bootfile: [digitalpw]digitalpw_pci_v7_2.exe This filename may change with each new firmware release. . . . Copying Copying Copying Copying DFEAA130 DFEAB320 DFXAA320 KZPSAA12 from from from from dqa0.0.0.107.0. dqa0.0.0.107.0. dqa0.0.0.107.0. dqa0.0.0.107.0. . . . . . . . .
Compaq Professional Workstation XP1000 The Compaq Professional WorkStation XP1000 contains a single flash Rom located on the motherboard. It contains SROM code containing Power on Self Test(POST) , ARC console firmware for Windows NT and SRM console firmware for Tru64 UNIX. When ever the motherboard is replaced the firmware may need to be updated. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available.
Method 1 - Load the Console Firmware Off a Local CDROM a. Insert the CD in the local CDROM b. >>> boot -fl 0,a0 DKA400 BOOTFILE: [xp1000]xp1000_v59_1.exe The filename will change with different console versions. APU> See below for update steps Method 2 - Boot the Console CD Off of an InfoServer a. Insert the CD in the InfoServer b. >>> boot ewa0 -file filename (leave off the .sys extension) Method 3 – Booting Off the Network – Need an OpenVMS Host on Network a. Copy the firmware.
d. >>> b –fl 0,0 dua5 System Disk a. Only steps a and b above are used. Do NOT execute writeboot step c. b. Specify the flags of 0,a0 and use "system disk":[sys0.sysexe]filename for bootfile. >>> boot -fl 0,a0 dua0 bootfile: dua0:[sys0.sysexe]xp1000_v59_1.exe Method 5 - Boot Off of a Bootable Floppy Windows NT a. Copy the firmware file to a FAT formatted floppy with the update image filename a:\fwupdate.exe. b. Shut down NT and from the NT Console menu, select " Upgrade AlphaBIOS". TRU64 UNIX a.
c. Dismount the disk and shutdown VMS. $ dismount dva0: d. Insert the floppy on the target system and boot it from the >>>. >>> boot dva0 Method 6 - BOOTP Network Upgrade – TRU64 UNIX a. Mount the Firmware Update CD using the following command: # mount -rt cdfs -o noversion /dev/rz4c /mnt b. Modify or Create the Client Database in the /etc/bootptab File :ht::ha=:bf=:ip= where: host is the system name in /etc/hosts hw_type is the hardware type. Proteon is ht = 4.
Apu-> 4. Type update SROM to update the POST code 5. After update is completed type exit. 6. Power cycle the machine to load console firmware then reset any environmental variables that changed, init and reboot. 7. Update the option firmware. The V5.9 CD supports updates on the PCI options DEFPA (FDDI), KZPSA (SCSI), CCMAB (Memory Channel) and the EISA option DEFEA (FDDI). a. Boot the Option firmware file. >>> boot -fl 0,a0 DKA400 Bootfile: [xp1000]xp1000_pci_v5_9.
259
DEC 2000 Model 300/500 AXP and DECpc AXP150 The DEC 2000 Model 300 (Jensen) / Model 500 (Culzean) and DECpc AXP 150 (Jensen) contain flash roms on the system backplane that contain ARC console firmware for Windows NT and SRM console firmware for Tru64 UNIX and OpenVMS. When ever this modules is replaced the firmware will need to be updated. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available.
2. >>> show * to list all environmental variables. Check all customer set variables. Also verify the setting of the following variables. Bootdef_dev Boot_osflags Auto_action os_type >>> set os_type flash OS_TYPE = FLASH_UPDATE 3. Power cycle machine again. 4. Boot the firmware using one of the following methods Method 1 - Boot the Console CD Off a Local CDROM a. Insert the CD in the local CDROM. b.
d. Enable service on that node from NCP $ MC NCP MC NCP> Show Known Circuit Characteristic Known Circuit Volatile Characteristics as of 12-FEB-1997 19:27:41 Circuit = BNA-0 State = on Service = disabled (if enabled skip to boot command) Counter timer = 65534 Designated router = 28.1023 (CXO28A) Cost = 4 Maximum routers allowed = 33 Router priority = 64 Hello timer = 15 Type = Ethernet Adjacent node = 28.
System Disk a. Only steps a and b above are used. Do NOT execute writeboot step c. b. Specify the flags of 0,a0 and use "system disk":[sys0.sysexe]filename for the bootfile. >>> b -fl 0,80 dua0 bootfile> dua0:[sys0.sysexe]dec2000_v2_2.exe Method 5 - Boot Off of a Bootable Floppy OpenVMS AXP a. Init and mount the floppy. Create a directory and copy the firmware to the floppy with the following commands. The commands shown are for the AlphaServer 2x00 EV4.
a. Copy the firmware file to a FAT formatted floppy with the update image filename of a:\fwupdate.exe. b. Shut down NT and from the NT Console menu, select "Install new firmware". Method 6 - BOOTP Network Upgrade - Tru64 UNIX a. Mount the Firmware Update CD using the following command: # mount -rt cdfs -o noversion /dev/rz4c /mnt b. Modify or Create the Client Database in the /etc/bootptab File :ht::ha=:bf=dec2000_v2_2.
5. Update the firmware at the UPD> prompt. UPD> update UPDATE SYSTEM ROM DEVICE UPD-I VERIFY LOADED ROM IMAGE …......................................................... …....................................... UPD-I VERIFY LOADED ROM IMAGE DONE FIRMWARE REVISION: V2.
DEC 3000 - All Models The console firmware on the DEC 3000 systems is located on the system module for the model 300, on the I/O for the models 400, 600 and 700 and on the system and I/O modules for the models 500, 800 and 900. The firmware must match between the system and I/O modules. They are each enabled with separate jumpers that allow the firmware to be updated. Anytime you replace a system or I/O module, the firmware will most likely need to be upgraded.
2. >>> show * to printout all the environmental variables. Check all customer set variables. Also verify the setting of the following variables. Bootdef_dev Boot_osflags Auto_action 3. Check to ROM update jumpers. See the release notes Chapter 2. These show the location of the SYSTEM ROM update jumper. There is also one on the I/O module. Consult the Service Manual for its location and setting. 4. Boot the firmware using one of the following methods. Method 1 - Boot the Console CD Off a Local CDROM a.
Ultrix a. Mount the Firmware Update CD using the following command: # mount -rt cdfs -o noversion /dev/rz4c /mnt b. Copy the appropriate firmware to the mop directory. # cp /mnt/DEC3000/filename /usr/lib/mop/filename The system firmware filename [DEC3000]m300_v7_0.sys - DEC [DEC3000]m400_v7_0.sys - DEC [DEC3000]m500_v7_0.
Method 5 - Boot Off of a Bootable Floppy OpenVMS AXP a. Init and mount to floppy. Create a directory and copy the firmware to the floppy with the following commands $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) m300_v7_0.btp $ init/dens=HD/index=begin dva0: fwupdate $ mount dva0: fwupdate $ create/dir dva0:[DEC3000] $ copy/contiguous M300_v7_0.btp dva0:[dec3000]fwupdate.exe b.
Method 6 - BOOTP Network Upgrade - Tru64 UNIX a. Mount the Firmware Update CD using the following command: # mount -rt cdfs -o noversion /dev/rz4c /mnt b. Modify or Create the Client Database in the /etc/bootptab File :ht::ha=:bf=:ip= where: host is the system name in /etc/hosts hw_type is the hardware type. Proteon is ht = 4. Ethernet is ht = 1. Regular token-ring (IEEE 802) is ht = 6. hw_addr is the hardware address: use the console command show device.
UPD-I ERASING ROM DEVICE …........................................................ UPD-I PROGRAMMING DEVICE …....................................................... UPD-I PROGRAMMING COMPLETED …............................. SYSTEM ROM UPDATE SUCCESSFUL UPDATE IO ROM DEVICE UPD-I VERIFY LOADED ROM IMAGE …............................ UPD-I VERIFY LOADED ROM IMAGE DONE FIRMWARE REVISION: V6.
show n Shows the checksum and ROM revision for the slot n option ROM and its corresponding loaded image. list Displays the loaded images and flash memories supported. • Use the list command to show a list of memory-loaded images, plus a list of currently supported flash ROMs: c. Type list to see the supported options TC_UPD> list Image name --------AV300-AA KZTSA PMAF-FA PMAF-FD PMAF-FS PMAF-FU PMAGB-BA PMAGC-AA PMAGC-BA PMAT-AA PMAZB-AA PMAZC-AA PMAGD PMAGD-AA DGLTA-FA Revision -------V1.1 A11 V3.
f. Use the repair command if one of the following occurs. • The system doesn’t recognize the adapter,or the adapter has an empty flash ROM. • The update command returns a failure message saying that a repair may be needed. • The information to be changed in the adapter flash ROM includes the name of the adapter (stored in the ROM header). • If a power failure occurs during the upgrade. TC_UPD> repair 5 TC_UPD-I *** REPAIR command entered *** select an image: Image name Revision ---------------AV300-AA V1.
DEC 3000 Model 300 Jumpers Rom Update Jumper DEC 3000 Model 400, 600 and 700 Jumper Location ROM Update Jumper The ROM update jumper has two positions. Disabled is position 1 and Enabled is position 2. The factory default setting is in the enabled.
275
DEC 3000 Model 500, 500S, 500X Jumper Locations System Module The following figure shows the location of jumpers and the serial ROM on the system module. The table below describes each location System Module Jumper Locations Feature 1 Description Components Default Setting Serial ROM Not used (500/500S) Reference only. Remote sense cable (500X) Must be installed All jumpers must be removed. Installed Serial ROM jumpers Not used (500/500S) Reference only. Jumper location 0 only.
The following figure shows the location of the jumpers, Enet address ROM chip, TOY/NVR chip and the flash ROM on the I/O module.
DEC 3000 Model 800 and 900 ROM Update Jumper Locations System Module Jumpers The following figure shows the location of jumpers and the serial ROM on the system module.
I/O Module Jumpers The following figure shows the location of the jumpers, Enet address ROM chip, TOY/NVR chip and the flash ROM on the I/O module. The picture shows the back of the I/O module.
DEC 4000 - Models 600 and 700 The console firmware on the DEC 4000 systems is located on the I/O modules. Anytime you replace an I/O module, the firmware will most likely need to be upgraded. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available. There are several ways to upgrade the firmware. All involve booting Loadable Firmware Utility (LFU). It can be booted one of the following ways.
Method 1 - Boot the Console CD Off a local CDROM a. Insert the CD in the local CDROM b. >>> boot -fl 0,a0 DKE0 BOOTFILE: [dec4000]cfw_v40_updp3.exe The filename will change with different console versions. UPD> See below for update steps Method 2 - Boot the Console CD Off of an Infoserver a. Insert CD in the Infoserver b. >>> boot eza0 -file filename (leave off the .sys extension) Method 3 - Booting Off the Network VMS System a. Copy the firmware.sys file to MOM$LOAD of an existing node in the cluster b.
c. Use writeboot to make the disk bootable. Specify the disk, directory and filename of the firmware. Take the defaults for the other questions. $ MCR Update Update Target Writeboot VAX portion of boot block (default is Y): No Alpha portion of boot block (default is Y):Yes system device (and boot file if not VMB.EXE):$1$dua5:[TEM]CFW_V40_UPDP3.EXE d. >>> b -fl 0,0 dua5 System Disk a. Only steps a and b above are used. Do NOT execute writeboot step c. b.
4. Update the firmware from the UPD> prompt type update * or update IO. UPD> update * Confirm update on: fbc0 io [Y/(N)] Y WARNING: updates may take several minutes to complete for each device. DO NOT ABORT! fbc0 Updating to … Verifying … io Updating to 3.8… PASSED. Verifying 3.8… PASSED. To update only the console, enter the update io command. UPD> exit 5. Power cycle the machine to load the new firmware into memory.
DEC 7000/10000 The console firmware on the DEC 7000/10000 systems is located on the CPU module. All Cpu’s must run the same version of firmware. You can NOT have mixed versions and expect it to work. Any time a CPU module is added or replaced, the firmware will most likely need to be upgraded. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available. There are several ways to upgrade the firmware.
Method 1 - Boot the Console CD Off a Local CDROM a. Insert the CD in the local CDROM b. P00>>> boot -fl 0,80 DKA600 Bootfile:[DEC7000]axp7000_v18.exe - for the DEC 7000 Bootfile:[DEC10000]axp7000_v18.exe - for the DEC 10000 Function? See below for update steps Method 2 - Boot the Console CD Off of an Infoserver a. Insert CD in the Infoserver b. P00>>> boot exa0 -file axp7000_v18 (leave off the .sys extension) Method 3 - Booting off the Network a. Copy the firmware.
and filename of the firmware. Take the defaults for the other questions. $ MCR Writeboot Update VAX portion of boot block (default is Y): No Update Alpha portion of boot block (default is Y):Yes Target system device (and boot file if not VMB.EXE):$1$dua5:[TEMP]axp7000_v18.exe d. P00>>> b -fl 0,0 dua5 System Disk a. Only steps a and b above are used. Do NOT execute writeboot step c. b. Specify the flags of 0,a0 and use "system disk":[sys0.sysexe]filename for the bootfile.
demna0 DO NOT ABORT! Updating to 9.4... Reading Device... Verifying 9.4... PASSED. WARNING: Updates may take several minutes to complete for each device. b. Function? exit System initializes now and prints configuration map. c. P00>>> build nvr d. P00>>> build eeprom Create new EEPROM image [Y/(N)]? y e. P00>>> set CPU # , where # is the other CPU numbers. Must do all CPUs. f. If you get the following message do a SET CONFIG at the >>>.
There is one other UNRECOMMENDED method for updating firmware from an existing CPU’s EEPROM. That is the use of the UPDATE command to copy one CPU’s EEPROM info to another CPU’s EEPROM area. The problem with this command is if the EEPROM format does not match the between the CPU’s it may render the new CPU useless. Forewarn any engineer who decides to do this. He may need another spare CPU module.
289
VAX 7000/10000 The console firmware on the VAX 7000/10000 systems is located on the CPU module. All Cpu’s must run the same version of firmware. You can NOT have mixed versions and expect it to work. Any time a CPU module is added or replaced, the firmware will most likely need to be upgraded. You will also need to do occasional console firmware upgrades to load the latest version of firmware that is available. There are several ways to upgrade the firmware.
Method 1 - Booting Off a Local CDROM Typically this procedure isn’t available since most VAX7000's don’t have a local CD. a. Insert the VAX 7000/10000 Console CD in the local CDROM drive. b. >>> boot -fl 0,0,0 -fi vax7000_v0c DKA600 Function? See below for update steps Method 2 - Booting Over the Network a. Copy the firmware.sys file to MOM$LOAD of an existing node in the cluster b. Set the attributes on the file with the following commands: $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) vax7000_v0c.
5 - Stop Enter a function ID value: 3 - for Choose Service OPTION ID 1 2 OPTION - Find Services Enter known Service Name Enter an Option ID value: 1 - for Find Service Working Servers found:: 1 Service Name Format: Service Number Service Name Server Name Ethernet ID #1 SMC P9_ESS 08-00-2B-24-72-6B #2 6000_DIAG_H P9_ESS 08-00-2B-24-72-6B #3 VAX7000_V0C P9_ESS 08-00-2B-24-72-6B Enter a Service Number or for more: 3 = VAX7000_V0C firmware Copyright Digital Equipment Corporation 1991, 1993, 1994, 199
System Disk a. Only steps a and b above are used. Do NOT execute writeboot step c. b. Specify the flags of 0,0,100 and use "system disk":[sys0.sysexe]filename for the bootfile. >>> b -fl 0,0,100 dua0 bootfile> dua0:[sys0.sysexe]vax7000_v0c.exe 4. Update the firmware at the Function? prompt. a. Function? update all or update KA7AA, update CIXCD0 etc. b. Function? exit c. >>> build nvr d. >>> build eeprom Create new EEPROM image [Y/(N)]? y e. >>> set CPU # - where # are the other CPU numbers. Repeat steps c.
There is one other UNRECOMMENDED method for updating firmware from an existing CPU’s EEPROM. That is the use of the UPDATE command to copy one CPU’s EEPROM info to another CPU’s EEPROM area. The problem with this command is if the EEPROM format does not match the between the CPU’s it may render the new CPU useless. Forewarn any engineer who decides to do this. He may need another spare CPU module.
295
Alpha Firmware Issues 296
297
A Description of HALcode and PALcode What is HALcode The Windows NT hardware abstraction layer (HAL) refers to a layer of software that deals directly with your computer hardware. Because the HAL operates at a level between the hardware and the Windows NT executive services, applications and device drivers need not be aware of any hardware-specific information.
299
Generic Powerup Sequence to Load Console Firmware This is a generic procedure describing the power on initialization and firmware code load on the Alpha CPU’s. The exact specifics vary from machine to machine. Check CPU specific manuals for exact sequence. However most will follow this routine. Failure during these routines will cause beep-codes, OCP error displays, console error displays, no display or hangs. Terms SROM - Serial ROM - Located on CPU . Starts initialization routine.
301
Definitions of Environmental Variables The following are some of the environmental variable you will need to be concerned with. Some will not be available on every machine. You can view variables at the console by typing • Show * (to see all variables) • Show b* (to see all variables starting with the letter b) • Show variable (must spell out variable if you do not use wildcards (*)) From VMS you can see some variable using the following DCL command.
This variable may be a boot search list. The console derives the value from the boot command if a device or string is specified, otherwise from the bootdef_dev variable. The value is preserved across warm bootstraps. boot_file The default fine name used for the primary bootstrap when no file name is specified in the boot command example: 1/boot/vmlinuz-2.2.5-16 (linux) boot_osflags Default additional parameters to be passed to the software during boot if none are specified in the boot command.
BASIC DIAG ADVANCED Normal operating mode Used when running console diagnostics Used when running utilities cpu_enabled A bitmask indicating which processors are enabled to run (leave console mode). If this variable is not defined, all available processors are considered enabled. cpu_mask A bitmask indicating which processors are enabled to run (leave console mode). cpu_primary A bitmask indicating which processors are eligible to be the next boot processor, following the next reset.
ffnext Allows booting from a disk that is in the "Not Connected" State. FFNEXT determines the console behavior of the next command issued to a “not connected” device. FFNEXT is a volatile environment variable and its value is temporary therefore does not propagate across a system reset or reboot. ON The console will change the next “not connected” device to a “connected” state for booting.
os_type Specifies the OS that will be booted on the machine NT On reset, control is passed to ARC Firmware/AlphaBios. VMS Same as "OpenVMS". OpenVMS The default for most Alpha platforms. The only setting for which the firmware CIPCA driver will be started. OSF Same as "Unix". Unix The default for Alpha evaluation board products. pal Specifies the versions of OpenVMS and Digital Unix PALcode available in the firmware.
simm_callout AlphaServer 8x00 and Compaq AlphaServer GS60/GS140 only; specifies that if any memory errors are detected during power-on self-test, the console should identify the failing SIMM. Defined values are: OFF (Default) ON identify failing SIMM. The "ON" value is pre-served across one system initialization only, then reset to "OFF". sys_model_num FIS process writes a model number to this variable. sys_serial_num FIS process writes a system serial number to this variable.
Definition of Galaxy Environmental Variables The following environmental variables are required for Galaxy setup. The values are dependent upon the system type and configuration. See the Compaq OpenVMS Alpha Galaxy Guide (AA-REZQB-TE) or STARS for further information on setup. These are used for OpenVMS. UNIX only uses these parameters on the AlphaServer 8200/8400 and AlphaServer GS60/GS140 machines. lp_count The number of Galaxy partitions or instances the console should expect. 0 - Galaxy console is OFF.
309
How to Set Customer Defined Environmental Variables Customers can define site-specific console environmental variables for specialized booting. Originally you could create non-volatile variables with CREATE –NV commands that would hold variable contents over re-inits. This procedure does not appear to work. After setting the variables they clear on init. In order to set customer defined variables that will hold after an init you must define them in a power-up script so they are redefined on each init.
311
How to Set Customer Defined Environmental Variables on a TurboLaser In order to set customer defined environmental variables on an AlphaServer 8200 or 8400 you will need to use one of the following procedures. 1. Create conv -nv and then set the value of the variable. a. P00>>> Create -nv conv b. P00>>> Set conv dkb0.0.0.0.0 -fl 0,1 (note flags is passed second) 2. Can do command on one line. a. P00>>> Create -nv conv dkb0.0.0.0.0 -fl 0,1 3. Create a powerup script a. P00>>> set mode advanced b.
313
Description of the Environmental Variable Bus_Probe_Algorithm The Environmental variable bus_probe_algorithm changes the algorithm we use to probe buses. Bus_probe_algorithm must be set to NEW for the following operating systems. • • OpenVMS V6.2 or greater Digital Unix V3.0B or greater. OpenVMS will crash with an INCONSTATE bugcheck on boot if not set correctly Digital UNIX will halt on boot.
315
Using FFNEXT and FFAUTO Environmental Variables This section describes how to use console environment variables FFAUTO and FFNEXT to force devices (e.g. disks) from a “not connected” state to a “connected” state to make them bootable. The console does not allow booting devices that are in the “not connected” state. FFAUTO and FFNEXT are used for situations and configurations where an operator needs to force the console to boot a “not connected” device.
P00>>>wwidmgr -show wwid -udid 40 –full [0] UDID:40 WWID:01000010:6000-1fe1-0000-04a0-ffff-fffe-0005-0000 (ev:wwid0) current_unit:40 current_col: 1 default_unit: 5901 via adapter via fc_nport Con DID Lun pga0.0.0.6.0 5000-1fe1-0000-04a2 Yes 210313 40 pga0.0.0.6.0 5000-1fe1-0000-04a1 Yes 210513 40 pga0.0.0.6.
Using FFNEXT on "Not Connected" Devices FFNEXT determines the console behavior of the next command issued to a “not connected” device. FFNEXT can be set to either OFF or ON. The default-state is OFF where console behavior is not affected. FFNEXT is a volatile environment variable and its value is temporary therefore does not propagate across a system reset or reboot. >>> set FFNEXT ON In the ON-state, the console will change the next “not connected” device to a “connected” state for booting.
319
LFU Scripts and Console Commands Available The following is a list of LFU scripts available on different platforms. Not every system uses these scripts. AlphaStation 600A The AlphaStation 600A uses the same motherboard as the AlphaServer 1000A. These scripts allow loading of the correct console code into the flash roms. • • 600A_to_1000A - Loads the 1000A console code into a 600A. 1000A_to_600A - Loads the 600A console code into a 1000A.
bytes onto a write-UN-locked FAT formatted floppy to a file. By default, if no script argument is specified, all NVRAM is saved to file ALLNVRAM.SAV. If the file already exists, then a copy of the original file is made to *.BAK. If that file exists, it is overwritten. Note, attempts to write to a writelocked floppy fail silently. Syntax save_nvram [{all,arc,srm,toy}] Arguments group Specifies the group of NVRAM data to be saved.
Online commands for OSF/1,Unix and OpenVMS to Get Firmware and CPU Rev Info Unix To get processor speed and EV version under Unix V4.0 $PWD> psrinfo -v Status of processor 0 as of: 03/07/97 01:30:42 Processor has been on-line since 03/06/97 19:23:09 The alpha EV5 (21164) processor operates at 291 MHz, and has an alpha internal floating point processor.
_81818000, data 406b37a8 scsi0 at psiop0 slot 0 rz0 at scsi0 target 0 lun 0 (LID=0) _(DEC RZ29B (C) DEC 0014) _(Wide16) rz1 at scsi0 target 1 lun 0 (LID=1) _(DEC RZ29B (C) DEC 0014) _(Wide16) rz2 at scsi0 target 2 lun 0 (LID=2) _(DEC RZ29B (C) DEC 0016) _(Wide16) rz6 at scsi0 target 6 lun 0 (LID=3) _(DEC RRD45 (C) DEC 1645) Initializing xcr0. Please wait....
OpenVMS To find the console version on an OpenVMS AXP system running V6.1 use the following: SDA> CLUE CONFIG to get console version For systems running V7.2 you can access the FRU tables from a crash or online SDA. SDA> CLUE FRU SDA> exit $ diagnose clue$fru.sys - Shows FRU packets. Not available on all systems For systems running V6.2 and later the following commands are available SDA> CLUE SCSI/SUM to get disk/tape firmware info. SDA> CLUE SCSI/PORT to get KZPSA SCSI ID.
WNT The following procedure allows you to determine the AlphaBIOS version when WNT is running. You need to check the Windows NT Diagnostic Menu Use one of the following methods. Go to the Start bar, Select Programs, then Administrative Tools (Common) and then select , Windows NT Diagnostics OR 1. Open an MSDOS window 2. Type winmsd to bring up the Windows NT Diagnostic Menu 3. Select SYSTEM. The BIOS information indicates the AlphaBIOS version.
326
FFFFFFFF.80D8F75C FFFFFFFF.80D8F760 FFFFFFFF.80D8F740 FFFFFFFF.80D8F744 FFFFFFFF.80D8F748 FFFFFFFF.80D8F74A FFFFFFFF.80D8F74B FFFFFFFF.80D8F74C FFFFFFFF.80D8F74E FFFFFFFF.80D8F750 FFFFFFFF.80D8F754 FFFFFFFF.80D8F758 SDA> for 80D8F740 SPDT$L_PORT_FLAGS SPDT$L_SCSI_PORT_ID SPDT$L_SCSI_BUS_ID SPDT$IS_SCSI_ID_NUM SPDT$Q_SCSI_ID_NUM SPDT$R_SCSI_ID_OVERLAY SPDT$L_FLINK SPDT$L_VERSION_CHECK SPDT$W_SIZE SPDT$B_TYPE SPDT$B_SUBTYP SPDT$W_SPDT_TYPE SPDT address 3. Format the SPDT Address data structure.
FFFFFFFF.80D8F764 FFFFFFFF.80D8F768 FFFFFFFF.80D8F76C FFFFFFFF.80D8F770 FFFFFFFF.80D8F774 FFFFFFFF.80D8F775 FFFFFFFF.80D8F778 FFFFFFFF.80D8F77C FFFFFFFF.80D8F77E FFFFFFFF.80D8F780 FFFFFFFF.80D8F784 FFFFFFFF.80D8F788 FFFFFFFF.80D8F78C FFFFFFFF.80D8F790 FFFFFFFF.80D8F794 FFFFFFFF.80D8F798 FFFFFFFF.80D8F79C FFFFFFFF.80D8F7A0 FFFFFFFF.80D8F7A4 FFFFFFFF.80D8F7A8 FFFFFFFF.80D8F7AC FFFFFFFF.80D8F7B0 FFFFFFFF.80D8F7B4 FFFFFFFF.80D8F7B8 FFFFFFFF.80D8F7BC FFFFFFFF.80D8F7C0 FFFFFFFF.80D8F7C4 FFFFFFFF.
FFFFFFFF.80D8F82C FFFFFFFF.80D8F830 FFFFFFFF.80D8F834 FFFFFFFF.80D8F838 FFFFFFFF.80D8F83C FFFFFFFF.80D8F840 FFFFFFFF.80D8F844 FFFFFFFF.80D8F848 FFFFFFFF.80D8F84C FFFFFFFF.80D8F850 FFFFFFFF.80D8F854 FFFFFFFF.80D8F858 FFFFFFFF.80D8F85C FFFFFFFF.80D8F860 FFFFFFFF.80D8F864 FFFFFFFF.80D8F868 FFFFFFFF.80D8F86C FFFFFFFF.80D8F870 FFFFFFFF.80D8F874 FFFFFFFF.80D8F878 FFFFFFFF.80D8F87C FFFFFFFF.80D8F880 FFFFFFFF.80D8F884 FFFFFFFF.80D8F888 FFFFFFFF.80D8F88C FFFFFFFF.80D8F890 FFFFFFFF.80D8F894 FFFFFFFF.
FFFFFFFF.80D8F8F8 FFFFFFFF.80D8F8FC FFFFFFFF.80D8F900 FFFFFFFF.80D8F904 FFFFFFFF.80D8F908 FFFFFFFF.80D8F90C FFFFFFFF.80D8F910 FFFFFFFF.80D8F914 FFFFFFFF.80D8F918 FFFFFFFF.80D8F91C FFFFFFFF.80D8F920 FFFFFFFF.80D8F924 FFFFFFFF.80D8F928 FFFFFFFF.80D8F92C FFFFFFFF.80D8F930 FFFFFFFF.80D8F934 FFFFFFFF.80D8F938 FFFFFFFF.80D8F93C FFFFFFFF.80D8F940 FFFFFFFF.80D8F944 FFFFFFFF.80D8F948 FFFFFFFF.80D8F94C FFFFFFFF.80D8F950 FFFFFFFF.80D8F954 FFFFFFFF.80D8F958 FFFFFFFF.80D8F95C FFFFFFFF.80D8F960 FFFFFFFF.
SPDT$L_PORT_SPECIFIC SPDT$IW_MAX_BUS_WIDTH SPDT$L_SCSI_BUS_WIDTHS SPDT$IW_CONFIG_BUS_WIDTH SPDT$L_SCSI_AUTO_ID SPDT$L_RSVD_LONG 0010 00000000 00000000 00000000 00000000 00000000 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF 0010 Decimal = 557 UCB$L_CICMD+00001 The firmware for the KZPBA would be the decimal value 557. SDA> EVAL 0000022D Hex = 00000000.0000022D 5. Evaluate the data in the last longword (0000022D) to get the firmware revision. SDA> EXAMINE 80D8F9F8+80 FFFFFFFF.
332
How to Boot RCU off of the firmware Update CD You can run the RCU utilities off of the CD. However you can not update firmware. To boot the CD, do the following. a. Determine the directory structure on the CD you are using. b. Get to the run a program selection of the ARC console. Run A Program CD:\utility\swxcrmgr\swxcrmgr - good from V3.6 to the V3.8 CD. CD:\utility\swxcrmgr\ra200rcu - good for the V3.9 CD and later. CD:\cdrom\utility\swxcrmgr\swxcrmgr - good up to the 3.
334
How to Create a RAID Standalone Configuration Utility [RCU] Floppy Procedure In order to create a standalone Raid Array Software floppy (RCU) you will need a PC or Alpha with a CD-ROM and a floppy drive. You also need an Alpha Systems Firmware CD. The RCU files are located on the Alpha Systems Firmware CD. These files are located the following directories CD version V3.5 and earlier are located at \cdrom\utility\swxcrmgr\ CD versions V3.
9. Select the directory \utility\swxcrmgr\ in cd window 10. Copy ALL files from the \utility\swxcrmgr\ directory to the floppy diskette except the Jensen directory, the .txt and the .1st files since there is not enough room on the floppy for them. e.g. \utility\swxcrmgr\*.* to A:\ If you have the 3.5 or earlier CD the directory structure is as follows \cdrom\utility\swxcrmgr\ 11. Select all the files in the directory including the following firmware files. swxcrfwa.216 (eisa) swxcrfwp.236 (PCI) (3.5 thru 3.
Error if files on floppy are set read-only This is an example of selecting firmware update with the file properties set to read-only. Run A Program> A:swxcrfw swxcrfwa.216 A:RA200FL –v249 EISA SWXCR PCI SWXCR ****************************************************************** * SWXCR Firmware Download Utility (V3.04, Mar 27, 1995) * ****************************************************************** * This utility is used to upgrade the firmware on the * * SWXCR controller.
338
Running RCU Firmware Update on an AlphaServer 8200 / 8400 WARNING! There is an issue with the firmware update utilities on the KZPSC and KZPAC SWXCR controllers when they are installed on AlphaServer 8200/8400 systems. See Blitz TD #2491 . Do NOT use RA200FL.EXE or SWXCRFW.EXE firmware update utilities from the V5.6 CD or earlier. There is a potential to corrupt the flash EEPROM and render the device unusable. You need to obtain a copy of RA200FL.EXE version 3.10A. The file will be available in .
Procedure Terminal Setup For correct operation you must use a VT320 or greater and the terminal characteristics should be set as follows: • • • • • Set to VTxxx Mode, 8 Bit Controls ( If you do not set 8-bit controls the arrow keys will not work) Set terminal ID to one of the following: VT300, VT320, VT330, VT420 Set to No Cursor mode or Text Cursor Invisible (Display setup) depending on the terminal type.
’fat:AMLX0075.CFG/dva0.0.0.1100.1’ ’fat:AMLX0077.CFG/dva0.0.0.1100.1’ ’fat:REL.TXT/dva0.0.0.1100.1’ ’fat:SRLMGR.EXE/dva0.0.0.1100.1’ ’fat:_MLX0075.CFG/dva0.0.0.1100.1’ ’fat:SWXCRFWA.216/dva0.0.0.1100.1’ ’fat:SWXCRFWP.242/dva0.0.0.1100.1’ ’fat:SWXCRMGR.EXE/dva0.0.0.1100.1’ 6. If the filename on floppy matches the environmental variables RCU or SWXCRFW you can use them. P00>>> run rcu -p 1 or you can specify a file -p 1 - specifies the PCI bus (hose) where the swxcr is installed (i.e. 0,1,2,3) 7.
CD 1. Enter the AlphaBIOS menu by typing ARC 2. Enter setup by typing function key F2 3. Select Utilities and Run Maintenance Program 4. At Program name type the program you want to run. You do not need the .exe extension but it works if you use it. Program Name: \utility\swxcrmgr\ra200rcu.exe - V3.9 CD and later \utility\swxcrmgr\swxcrmgr - V3.6 thru V3.8 CD and earlier \cdrom\utility\swxcrmgr\swxcrmgr.exe - V3.5 CD and earlier 5. At Location select from the table where files are located.
version 2.49 . 5. Press ENTER to proceed with the updates. 6. The update utility will start and allow you to update the swxcr’s. 7. Reset the system and reset system environment. See "When you are done" below. Use floppy with firmware update utility RA200FL.EXE V3.10A renamed to SWXCRFW.EXE 1. Copy the RA200FL.EXE V3.10A file to floppy and rename it SWXCRMGR.EXE. See section above for locations. See How to build an RCU floppy for entire procedure to build floppy. 2.
5. At Program name type the program you want to run Program Name: ra200fl -v249 - This will update all controllers. There is NO space between the -v and 249, To specify specific controllers to update use the following format. Program Name: ra200fl wwww xxxx yyyy zzzz wwww is filename to load on first controller i.e. swxcrfwp.
EISA Configuration Utility (ECU) Commands Using the EISA Configuration Utility Whenever you add, remove, or move an EISA or ISA module in your system, you need to run the EISA configuration utility (ECU). The ECU is a menu-based utility, run from the ARC menu interface, that provides on-line help to guide you through the configuration process. Each EISA or ISA module has a corresponding configuration file (CFG), which describes the characteristics and the system resources required for that option.
3. Invoke the ECU as follows: For systems running Windows NT: a. From the Boot menu, select the Supplementary menu. b. From the Supplementary menu, select the Setup menu. Insert the ECU diskette for Windows NT into the diskette drive. c. From the Setup menu, select "Run EISA configuration utility from floppy." This initializes the ECU program. There may be a 10- to 20-second delay in system activity while the system recognizes the ECU. For systems running Tru64 UNIX or OpenVMS: a.
Configuring ISA Options To configure ISA options, follow these steps: 1. Start up the system and run the ECU. 2. Add the ISA card configuration file to the configuration list. Use the Add or Remove Boards ECU option to add the configuration file (CFG) for the ISA option and to select an acceptable slot for the option. In some cases, the CFG file for the ISA option may reside on a configuration diskette packaged with the option. If so, insert that diskette and follow its directions.
348
Procedure to Update CIXCD with 4K Packet Firmware NOTE See Blitz 2919 if using CIXCD with 4K packet firmware. Problems have been discovered under heavy load. Overview Firmware that supports 4K CI packet transmissions for the CIXCD is qualified and available. The firmware is available on the 5.6 firmware CD but it cannot be loaded using the normal console update procedures (for either VAX or Alpha). In order to support 4K Ci packet transmission you must have the correct firmware loaded.
You can also access the files over the web at the firmware website. 2. Copy the appropriate firmware file to MOM$LOAD or MOM$SYSTEM on a node in the cluster that has service enabled with the following command $ copy $1$DKxnnn:[cixcd]cixcdg27.sys mom$load or $ copy $1$DKxnnn:[cixcd]cixcdg27.sys mom$system Note: The ’updating_firmware.txt’ file in the CIXCD directory of the firmware CD refers to the wrong file name of cixcd_v27_tl 3. Make sure service is enable on a node in the cluster. 4.
refers to the wrong file name of cixcd_v27_tl 3. Ensure circuit service is enabled for this particular circuit. Have the system manager enable this if not. 4. On the system being updated execute the following console command P00>>> boot –fl 0,0 –fi CIXCDD27 exa0 VAX7000/10000 A MOP load from another system in the network is required. The firmware must be copied to the mom$system or mom$load directory on that node. On the system containing the update CD execute the following: 1.
352
KGPSA Files Used for Firmware Updates KGPSA firmware is available in several different formats to allow for updating firmware when the adapter is installed on different platforms. These filenames are subject to change with each new version of firmware. For a list of available firmware see the Cybrary download area. Successful updates may require renaming the files to be eight characters or less. 1. Firmware loaders with • AL381a4.exe • AL303x2.exe • lp8ldr • lp7ldr • lp6ldr • 303a1ldr.exe • lp7303a1ldr.
354
Upgrading KGPSA Firmware on GS80/GS160/GS320 Machines CAUTION! The solution mentioned in Blitz TD2831 is now available in the Download directory on Cybrary. See the readme files before proceeding with an update. UNIX requires EMX driver V1.29 with firmware 381a4. UNIX requires EMX driver V1.22 with firmware 303a1or later. VMS requires patches to be installed. See Blitz TD2807-C for details Overview KGPSA firmware for the GS80/GS160/GS320 series systems is embedded within the LFU utility.
To Create a CDROM using the Firmware .ISO file 1. Copy the V5.9b .iso firmware file to your PC. 2. Use CD writer software, write this image file to a blank CD. When writing the CD, ensure that the "close disk" or equivalent option is selected. Updating KGPSA Firmware 1. Obtain the specific KGPSA firmware.sys or .awc file. It can be obtained from Cybrary or from Engineering. Create a CDROM using the method above. The .awc file can be renamed to .sys on this platform. 2.
fully qualified yet). The V5.6 firmware package has the following components Component --------SRM Console Location of Flash ROM Where Firmware Resides ---------------------SRM Flash (on STDIO) : Firmware Revision ----------------V5.8-1 Hit to scroll text, or to skip text.
CD, in the file named : \GS320\GS320_V56_FW_RELNOTE.PS \GS320\GS320_V56_FW_RELNOTE.PDF \GS320\GS320_V56_FW_RELNOTE.TXT (PS file) (PDF file) (Text file) ----------------------------------------------------------------------------Hit to scroll text, or to skip text. The default bootfile for this platform is [GS320]GS320_V56.EXE Hit at the prompt to use the default bootfile. Bootfile: OpenVMS PALcode V1.81-1, Tru64 UNIX PALcode V1.
Copying Copying Copying Copying Copying DFXAA320 KZPSAA12 CIPCA420 KG8302A1 KG7220X2 from from from from from dqa0.0.0.15.16. dqa0.0.0.15.16. dqa0.0.0.15.16. dqa0.0.0.15.16. dqa0.0.0.15.16. . . . . . . . . . . LFU micro updates are not supported when the system is hard partitioned. Please power down and unpartition first.
2. After loading newer firmware than is on the CD, the verify command will fail because it is verifying the loaded firmware off the V5.6 CD and what is in the KGPSAs NVRAM. UPD> verify pga0 pga0 Verifying SS3.03A1... FAILED. 3. There are two versions of the KGPSA. A 64 bit option and a 32 bit option. They each have different firmware. If an attempt to load the wrong firmware is made the following message appears. UPD> update pga0 -path iso9660:kg8303a1.
Upgrading KGPSA Firmware on Turbolasers or GS60/GS60E/GS140 Machines CAUTION! The solution mentioned in Blitz TD2831 is now available in the Download directory on Cybrary. See the readme files before proceeding with an update. UNIX requires EMX driver V1.29 with firmware 381a4. UNIX requires EMX driver V1.22 with firmware 303A1 or later. VMS requires patches to beinstalled.
Terminal Setup To boot the firmware executable on an Alpha Server 8000 series ARC emulator using a Digital VT420 Terminal, the following change is required to the VT420 setup. 1. 2. 3. 4. 5. 6. F3 enter setup Move to "COM" Select "XOFF at 128" Move to "Directory" Select "Save" Select "Exit" Console Setup and Running Utility To update KGPSA firmware on an AlphaServer 8200, 8400, GS60 or GS140 system, the console parameters must be set up properly and the RUN command, not ARC, is used to start the program.
Example P00>>> run iso9660:[utility]lp6ldr.exe -d dka400 -p 0 Loading image... Transferring control... WELCOME TO LP6DUTIL HOST DIAGNOSTIC UTILITY for Alpha V2.1-008 Firmware load only, Firmware revision: SS2.20X2 Copyright Digital Equipment Corporation and Emulex Corporation 1997. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.
364
Upgrading KGPSA Firmware From AlphaBIOS CAUTION! The solution mentioned in Blitz TD2831 is now available in the Download directory on Cybrary. See the readme files before proceeding with an update. UNIX requires EMX driver V1.29 with firmware 381a4. UNIX requires EMX driver V1.22 with firmware 303a1 or later. VMS requires pathes to be installed. See Blitz TD2807-C for details Overview KGPSA firmware can be upgraded on most AlphaServer Systems using AlphaBIOS.
• • • • • Move both files and options folder to be copied to CD Layout window Click on Create CD Select 4x speed Select number of copies Create CD Procedure There are several ways of performing KGPSA firmware upgrades. The methods used will depends on the version of firmware required to be loaded. 1. The Alpha Systems Firmware Update CD can be used to update KGPSA with the version that is supplied on that CD. In this case LP6LDR, LP7LDR, LP8LDR or ALPHADNLD with the firmware.awc file can be used.
7. ESC to exit to the main menu 8. Select Utilities 9. Select Run Maintenance Program 10. Now select A: for floppy and enter the filename on the floppy for the KGPSA firmware Program Name: al381a4 al303x2 alphdnld 77303ldr Location: Select A: (file includes the loader and firmware 381a4) (file includes the loader and firmware 303x2) (requires a firmware.awc file) (lp7303a1ldr.exe renamed 77303ldr) Errors When running KGPSA firmware update utilities there are several error messages that may be seen.
368
Problems Running lp6dutil.exe on a Turbolaser or GS60/60E/140 Machine Attempts to run the KGPSA utility lp6dutil.exe on a Turbolaser or a GS60/60E/140 machine on the serial console port will fail with repeating characters. You may be able to hit a character and return to get thru some of the menus but in the example of a firmware update you must type the location of the firmware file. You are not able to type CD: etc. It just echos C’s and D’s The following will show the failure.
7 - Quit Option: 55 Input value ’0x55’ out of range!!! 1 2 3 4 5 6 7 - LP6DUTIL Main Menu (not currently supported) (not currently supported) Restart Host Adapters (not supported) Maintenance Show Host Adapters Info Quit Option: 5 Maintenance 1 - Update Firmware 2 - Display Program Load List Option: 1 Enter Full Path to Firmware Image file (eg. a:\sf200.
Using the KZPSA UTIL_CLI.EXE File to Set KZPSA Parameters To change the parameters on the KZPSA installed in a PCI bus on a Turbolaser you must run a utility located on the Alpha Systems Firmware Update CD-ROM. The parameters that can be changed are: SCSI_ID FAST TERMPOWER RESET_ON_BOOT SYNC WIDE TAGGED_QUEUING DISCONNECT The utility used is located at: iso9660:[UTILITY]UTIL_CLI.EXE on CD V3.6 and up It is located at iso9660:[CDROM.UTILITY]UTIL_CLI.EXE on CD V3.5 and lower.
4+ 5+ 6+ 7+ ISP1020 ISP1020 DECchip 21040-AA PCI NVRAM 10201077 10201077 21011 71011 0001 0001 0023 0002 isp2 isp3 tulip1 pci_nvram0 C1 PCI connected to kftia0 0+ SIO 4828086 5+ KZPSA 81011 0004 0000 pci1 sio0 kzpsa0 0023 0000 0000 0000 sio0 tulip2 floppy0 kbd0 mouse0 0+ 1+ 2+ 3+ Controllers on SIO DECchip 21040-AA FLOPPY KBD MOUSE 1+ EISA connected to pci1 through sio0 EDAC960 77009835 0007 21011 2 3 4 eisa0 edac9600 P08>>> load –f iso9660 - load CDROM driver P08>>> run iso9660:[UTILITY]UTI
Example: SET SCSI ID 7 The above example sets the KZPSAs SCSI ID to 7 ENABLE / DISABLE FAST enables or disables KZPSA fast SCSI mode. ENABLE / DISABLE TERMPOWER enables or disables the supply of termpower to the SCSI bus from the KZPSA. ENABLE / DISABLE RESET_ON_BOOT enables or disables a SCSI bus reset on boot-up by the KZPSA. ENABLE / DISABLE SYNC <0-15 | ALL> enables or disables synchronous negotiation to the SCSI device having the SCSI ID specified or all of the SCSI devices.
[KZPSA #1] show kzpsa Found 1 KZPSA(s) in your system: BUS SLOT HW REV KZPSA #1 0 5 L01 KZPSA #1 is currently selected. FW REV A08 [KZPSA #1] set scsi_id 6 BUS: 0 SLOT: HW REV: L01 FW REV: TERMPOWER: Enabled FAST MODE: SCSI ID 7 5 SCSI ID: 6 TERMINATION: Absent RESET ON BOOT: Disabled A08 Enabled [KZPSA #1] exit save Initializing... F E D C B A 9 8 A o . o . + . 7 M + . + . + . 6 . . . . . . . 5 . . . . . . . 4 P ++ EB ++ EB ++ EB 3 . . . . . . . 2 . . . . . . . 1 . . . . . . . 0 . . .
4 5 6 7 8 9 10 11 12 13 14 15 Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled [KZPSA #1] test devices DEC KZPSA-BB A08 (SCSI = 6, Fast) -----------------------------------
376
KZPSA_EDIT Utility You can run KZPSA_EDIT from the console prompt to set up some KZPSA parameters. This command is available on the TurboLaser. kzpsa_edit - Edit KZPSA FLASH parameters. OVERVIEW: The kzpsa_edit command permits the modification of KZPSA Flash parameters from the console. Individual bits can be set or cleared, or bytes can be set to a specific value. Entering kzpsa_edit without an option or target device will list these parameters for all KZPSA devices in the system.
378
wwidmgr - World Wide ID Manager Description Wwidmgr command is used to configure devices connected to KGPSA/HSG80. It allows them to be seen at the console with a SHOW DEVICE command. It allows you to define alias names for fibre channel devices and associate them to the worldwide identifiers (WWIDs) for devices that will be used for booting or dumping. This command is needed to initially setup non-volatile storage with information the console will use later for booting, dumping and showing devices.
380
AlphaServer With HSJ’s May Get a Hard Error #8 On INIT An Alpha Server system, that has a Tape Loader attached to an HSJ controller, reports a Hard Error #8 after power on. PROBLEM SYMPTOM: After power on, the console may report a Hard Error #8. The error will be pointing at a disk type device. Example: *** Hard Error - Error #8 Diagnostic Name ID Device Pass Test Hard/Soft exer_kid 000002e9 duc2.12.0.4.
-------------------------------------------------------------------------TL895 loader 1 0 0 P895 Notice how the loader from the show load command (TL895) is used by the pass through device P895. ADDITIONAL COMMENTS: Engineering is investigating methods for inhibiting this error report. For the time being there is no cause for concern because the system is behaving exactly as expected. See Blitz TD 2941 for details.
Missing File Message From LFU for DEFPA firmware When booting LFU on a TurboLaser the DEFPA firmware shows as “Missing file” if you do a list from the UPD prompt. UPD> list Device kn7cc-ab0 kn7cc-ab1 kn7cc-ab2 kn7cc-ab3 kzpsa0 kzpsa1 kzpsa2 kzpsa3 kzpsa4 kzpsa5 kzpsa6 pfi0 pfi1 Current Revision V4.0-4 V4.0-4 V4.0-4 V4.0-4 A10 A10 A10 A10 A10 A10 A10 2.46 2.46 Filename kn7cc_fw kn7cc_fw kn7cc_fw kn7cc_fw kzpsa_fw kzpsa_fw kzpsa_fw kzpsa_fw kzpsa_fw kzpsa_fw kzpsa_fw dfpaa_fw dfpaa_fw Update Revision V4.
384
Option Firmware Fails to Load Off of Floppy After creating a console firmware floppy and an options floppy using the documented procedure for WNT I discovered the following problem. When attempting to create two NT firmware floppies to update an AlphaServer 2100A EV5 console and its options I could not get the option firmware to load. I used the following procedure as documented. 1. I formatted the floppies under NT and selected FAT format 2. I copied the firmware file AS2100A_e5_v4_7.
386
Firmware Upgrades with Console Secure Set With the new secure console capability ENABLED the firmware update will fail with this following message >>> console is secure - parameters are not allowed The firmware upgrade stops here and won’t continue. This is occurring because after entering bootfile name system does a reinit and loses the fact that you have already entered the password once to even start the upgrade.
388
How to Clear the SRM Console Password on an AlphaStation 500 / 600 Overview If a customer sets a console password on an AlphaStation 500 or AlphaStation 600, then forgets the password, it must be cleared before certain console commands and functions can be done. This page describes methods of creating a floppy to clear the password. There are procedures to build the floppy using OpenVMS, Tru64 UNIX and Windows. OpenVMS 1. Locate file clr_pwd.exe and copy the file to an OpenVMS system.
4. Insert writeable FAT formatted floppy (any data on this floppy will be erased). (Intel or Alpha) C:\ mkboot clr_pwd.exe (Alpha) C:\ makeboot clr_pwd.exe Procedure 1. Power down the system. 2. On the AlphaStation 500 move the jumper from J11 to J13 3. On the AlphaStation 600 move the jumper from W1 to W3. You can only select one of these jumpers at a time. Select the jumper link On Cybrary to see a picture of jumper location. 4. Insert the floppy into the AlphaStation and power it on. 5.
How to Clear the SRM Console Password on an AlphaStation 255 Overview If a customer sets a console password on an AlphaStation 255, then forgets the password, it must be cleared before certain console commands and functions can be done. This page describes methods to clear the password. If the user forgets the password, there is only one recovery mechanism. must: 1. 2. 3. 4. 5. 6. 7. 8. The user Power the system off. Open the system box.
392
How to Clear the Console Password on an AlphaStation/AlphaServer 400 Overview If a customer sets a console password on an AlphaStation or AlphaServer 400, then forgets the password, it must be cleared before certain console commands and functions can be done. This page describes methods to clear the password. The motherboard can be replaced or the toy and nvram chips can be replaced. Console environmental variables will all have to be reset.
394
How to Clear the SRM Console Password on a Miata and Miata GL Overview If a customer sets a console password on the Miata Digital Personal Workstation, then forgets the password, it must be cleared before certain console commands and functions can be done. This page describes methods of creating a floppy to clear the password. Warning Running this program will reset all the site-specific environmental variables. You must have them written down so you can restore them to original values.
396
After Firmware Update, Init Gets bad value - mopv3_boot not modified When attempting to update console firmware on an AlphaStation 500/266 to the V6.35 console off the V3.8 CD , you may get a message bad value - mopv3_boot not modified. When you boots the CD and selects the default firmware file of [ALPHA600]as600_V6_3.exe he also gets the following message Digital AlphaStation 500/600 Console V6.3-5 built on Nov 20 1996 at 16:01:42 bad value- invalid selections: ON OFF bad value - mopv3_boot not modified.
398
Running the NT ARC or AlphaBIOS Console The SRM console has the ability to run the either the NT ARC or AlphaBIOS consoles without having to re-flash the system via the firmware update utility. When following the steps below, a temporary NT ARC or AlphaBIOS runtime environment will be created. The console environment will return to the normal SRM console following a power cycle of the system.
configuration, keyboard type, and scsi host id. o Select Supplementary menu, and save changes Note: If you do not wish to boot Windows NT but only need to execute a utility program, select "Run a program" from the Boot menu and then enter the proper path and file name. At this point you may be required to set up the boot device.
Different AlphaServer’s get ‘open failure" on Update Firmware updates may fail on AlphaServer 1000/1000A EV5, AlphaServer 2100, and possibly other Alpha systems with DE500’s installed. You will see an error message similar to the example below from an AlphaServer 1000. Alphaserver 1000 ‘open failure firmware filename ’srm_fw’‘ or Alphaserver 1000 ‘open failure firmware filename ’arc_fw’‘ This is caused when an "active" network is found.
402
AlphaServer 1000/1000A EV5 Firmware From V5.2 CD Won’t Fit on Floppy The AlphaServer 1000 and 1000A EV5 firmware for the EV5 processors off of the V5.2 firmware CD is too large to fit on a 1.44 MB floppy. The files on the V5.3 CD will correct this issue. Initially files were placed I the interim directory, but since they have corrected this on later version the interim directory is no longer available for this issue.
404
AlphaServer 1000/1000A 5/300 CPU Requires V5.23 AlphaBIOS The AlphaServer 1000/1000A 5/300 CPUs required a minimum of V5.23 AlphaBIOS. This version is off the V3.8 CD. If you downgrade the console to a version prior to the V3.8 CD version you will have problems invoking the AlphaBIOS console. If you type AlphaBIOS at the >>> you will hang after the "ARC Firmware Loaded" message. This is due to a compatibility problem between AlphaBIOS V5.23 and earlier HALs. The updated HALs are on http://www.windows.
406
AlphaServer 1000/1000A Led Code CB Due to Wrong Firmware on Motherboard The AlphaServer 1000/1000A motherboard contains 1000 series machines do NOT have a dual-SRM like motherboards only come with EV4 firmware loaded. motherboard in a system with an EV5 cpu you will says SROM execution completed the console firmware. Since the the 2x00 series machines the If you install a replacement get an OCP code of CB. Led CB The system could hang here if EV4 console code is used with 5/xxx (EV5) systems.
Bootable Floppy Using OpenVMS a. Locate the console firmware from either the latest Firmware Update CD or access it over the web at one of the following locations. http://ftp.digital.com/pub/Digital/Alpha/firmware/ http://ftp.digital.com/pub/DEC/Alpha/firmware/ as1000_e5_v5_4.exe (for AlphaServer 1000 Model 5/xxx) as1000a_e5_v5_6.exe (for AlphaServer 1000A Model 5/xxx b. Make a Bootable Floppy Procedure - this example is for the 1000A.
Bootable Floppy Using a PC Running WNT a. Locate the console firmware from either the latest Firmware Update CD or access it from our Cybrary site or over the web at one of the following locations. http://Cybrary.inet.cpqcorp.net/DOWNLOAD/FIRMWARE/SYSTEMS/ALPHA/ Cybrary Online CDs http://ftp.digital.com/pub/Digital/Alpha/firmware/ Alpha Firmware Internet Readme http://ftp.digital.com/pub/DEC/Alpha/firmware/ Alpha Firmware Internet Readme b. Copy the firmware to your system. c. Locate mkboot.
Bootable Floppy Using WNT When You Already Have a Copy of Makeboot.Exe a. Locate the console firmware from either the latest Firmware Update CD or access it over the web at one of the following locations. http://ftp.digital.com/pub/Digital/Alpha/firmware/ http://ftp.digital.com/pub/DEC/Alpha/firmware/ b. Locate makeboot.exe and put on the disk (C: in this example) c. Copy the firmware to the floppy and rename fwupdate.exe. d.
Description of the Different FailSafe Loaders (FSL) Available The failsafe loader (FSL) the main console firmware would have to be replaced different implementations is a method used to reload good console firmware when image is corrupted. Without the use of a FSL, hardware if the console image is corrupted. There are several of the FailSafe Loader (FSL) available. 1. Jumper selects reading a FSL floppy on power up that has console firmware loaded on it.
412
Procedure to Make a Bootable FailSafe Loader Floppy For Most AlphaStation/AlphaServer Systems Bootable Floppy Using OpenVMS 1. Locate the console firmware from either the latest Firmware Update CD or access it from out Cybrary site or over the web at one of the following locations. http://Cybrary.inet.cpqcorp.net/DOWNLOAD/FIRMWARE/SYSTEMS/ALPHA - Cybrary http://ftp.digital.com/pub/Digital/Alpha/firmware/ -Alpha Firmware Internet Readme http://ftp.digital.
System Type Failsafe loader Jumper Setting AlphaServer 300 System Board J2 pins 1-2 AlphaServer 400 CPU J5 pins 1-2 AlphaServer 800 * CPU J1 position 7 on AlphaServer 1000/1000A EV4/xxx CPU J1 position 7 on AlphaServer 1000/1000A 5/300 CPU J4 position 7 on AlphaServer 1000/1000A 5/333 CPU J1 position 7 on AlphaServer 1000/1000A 5/400 CPU J1 position 7 on AlphaStation 200 Motherboard J2 pins 1-2 AlphaStation 250 Motherboard J2 pins 1-2 AlphaStation 255 Motherboard Switch 1 off, Switch 2
UPD> update update SRM: Yes update ARC: Yes UPD> verify UPD> exit 8. Power off the system and set the fail-safe jumper back to its original position. 9. Power on an you will now come to the >>> and the new firmware will be loaded. Bootable Floppy Using an Alpha Running WNT 1. Locate the console firmware from either the latest Firmware Update CD or access it from out Cybrary site or over the web at one of the following locations. http://Cybrary.inet.cpqcorp.
5. Pull up a MSDOS window and use these two files to create bootable FSL floppy using the following procedure: Insert writeable FAT formatted floppy C:\mkboot fwupdate.exe Bad command or file name mkboot V1.1: create a bootable floppy Please insert a formatted diskette into drive A: and press and key: Number of sectors per track for this disk is 18 Writing image to drive A:. Press ^C to abort. Track: 45 Head: 0 Sector: 16 Done. 6.
AlphaServer 800/Digital Server 3000 Model 3300/3305 New FSL Procedure Overview Starting with the V5.7 console firmware, two floppies will be needed to update console firmware. One floppy contains the LFU image and the SRM console firmware. The other floppy contains AlphaBIOS firmware. This procedure will be valid for creating a FSL floppy or a normal boot floppy. There will be methods listed to use a PC running NT or and Alpha running NT or UNIX.
Alpha - Windows NT 1. Locate and save the following files to your Alpha. Save them on the top level directory of any disk. • makeboot.exe Alpha image to make a bootable disk • mkboot.exe PC/ALPHA NT image to make a bootable disk • cru.exe LFU and SRM firmware • crarcrom.exe AlphaBIOS firmware 2. Fat format two floppies 3. From an MSDOS window execute the following command makeboot -f cru.exe or mkboot cru.exe 4. Save the crarcrom.exe file to a second fat formatted floppy. 5.
# fddisk -fmt /dev/rfd0a 6. From directory where files are located execute the following # ./mkbootfirm clu.exe |dd of=/dev/rfd0c bs=64k 7. Insert floppy diskette 2. 8. Create a soft link to /dev/fddrive with the following command # ln -s /dev/rfd0c /dev/fddrive 9. Format the floppy. See step 5 for commands. 10. Add a DOS format onto the floppy disk # /usr/bin/mtools/mformat -s 18 a: 11. Use mwrite to low level copy UNIX to DOS the SRM and ARC firmware. # /usr/bin/mtools/mwrite clsrmrom.
420
How to Build and Use a FSL Floppy on An AlphaServer 4000/4100/1200 Overview The fail-safe loader is a software routine that loads the SRM console image from floppy. Once the is running you will want to run LFU to update FEPROM 0 with a new image. FEPROM 0 contains images of the SROM, XSROM, PAL, decompression, and SRM console code. If the fail-safe loader loads, the following conditions exist on the machine: • • • The SROM has passed its tests and successfully unloaded the XSROM.
The command procedure for building the FSL floppy diskette follows: $! $! make_rawhide_floppy.com $! $! P1 = Alpha firmware EXE file to be writebooted to a floppy $! $ if P1 .eqs. "" then inquire P1 "Firmware file to writeboot" $ inquire ignore "Insert blank HD floppy in DVA0, then continue" $ set verify $ init /density=hd/index=begin dva0: rhboot $ mount dva0: rhboot $ create /directory dva0:[as4x00] $ copy /contig ’P1’ dva0:[as4x00]rhboot.exe $ mcr writeboot n y dva0:[as4x00]rhboot.
Geometry for Drive a: Media Type 3.5, 1.44 MB, 512 bytes/sector Cylinders 80 Tracks/Cylinder 2 Sectors/Track 18 Writing floppy 100 % done Note: The makeboot command defaults to drive a, to specify a different device use d b: Insert the floppy in the system with corrupt firmware and init. 4. At the LP00>>> prompt type LFU and update firmware from CD, another floppy or over ethernet. Procedure 1.
Sctr 3 CONSLE code CHKSM fail ................................................
4. A list here shows the srmflash console is corrupt UPD> list Device AlphaBIOS srmflash Current Revision Filename V5.32-0 arcrom (56377.31685-4294951srmrom cipca_fw dfxaa_fw kzpsa_fw Update Revision V5.32-0 V5.0-2 A420 3.10 A12 5. Update the firmware UPD> update WARNING: updates may take several minutes to complete for each device. Confirm update on: AlphaBIOS [Y/(N)] y DO NOT ABORT! Updating to V5.32-0... ....... Verifying V5.32-0... AlphaBIOS PASSED.
probing IOD0 hose 0 bus 0 slot 1 - PCEB probing EISA Bridge, bus 1 bus 0 slot 2 - S3 Trio64/Trio32 bus 0 slot 3 - DECchip 21140-AA configuring I/O adapters... ncr0, hose 1, bus 0, slot 1 isp0, hose 1, bus 2, slot 0 floppy0, hose 0, bus 1, slot 0 tulip0, hose 0, bus 0, slot 3 System temperature is 28 degrees C AlphaServer 1200 Console V5.
How to Build and Use a FSL Floppy on An Digital Server 7000 Model 7300 and 5000 model 5300 Overview The Digital Server 7300 is an NT ONLY version of the AlphaServer 4100 and the Digital Server is an NT ONLY version of the AlphaServer 1200. The Digital Server 7300 is essentially an AlphaServer 4100 and the Digital Server 5300 is essentially an AlphaServer 1200. The following procedures are valid on either platforms however you will need to do the OpenVMS procedure on a different system to create this floppy.
Filename Description $README.TXT V5.0 Fail Safe Loader Readme file FSL_RELNOTE.PDF AlphaServer Fail Safe Loader Release Note (PDF) AV-R1FZB-TE MAKE_FSL_FLOPPY.COM .Com file to make a FSL floppy with OpenVMS RHBOOT_V5.EXE V5.0 Digital Server 7000 Model 7300 and 5000 Model 5300 Recovery Console Image The latest rhboot.exe image (version 5 - 09/17/97) in this area will work for recovering corrupt consoles of revision v1.2-4, as well as all future versions.
How to Build a FSL floppy Using an Alpha running WNT Obtain the rhboot.exe and makeboot.exe files. This is a zip file that has rhboot.exe and makeboot.exe. 1. Format a floppy diskette 2. Go to the DOS prompt create a FSL floppy by typing the following. C:\> makeboot -f rhboot.exe makeboot utility, version 002. Executable file rhboot.exe, size 834048 1629 blocks. Warning: All data on the floppy will be overwritten. Continue? [Yes/No ]: yes Geometry for Drive a: Media Type 3.5, 1.
2. Insert the FSL floppy and reset the system. The system will load the fsl console and give you and LP00>>> prompt. SROM V1.1 on cpu0 SROM V1.1 on cpu1 XSROM V4.9 on cpu1 XSROM V4.9 on cpu0 BCache testing complete on cpu1 BCache testing complete on cpu0 mem_pair0 64 MB mem_pair1 64 MB mem_pair2 64 MB mem_pair3 64 MB 20..20..21..21..23.. please wait 6 seconds for T24 to complete 24..24.. Memory testing complete on cpu0 Memory testing complete on cpu1 Sctr 3 -CONSLE code CHKSM fail ..........................
Copying Copying Copying Copying [as1200]TCARCROM from DKA500.5.0.1.1 ............... [options]CIPCA420 from DKA500.5.0.1.1 . [options]DFXAA320 from DKA500.5.0.1.1 ... [options]KZPSAA12 from DKA500.5.0.1.1 ... ---------------------------------------------------------------------------Function Description ---------------------------------------------------------------------------Display Displays the system’s configuration table. Exit Done exit LFU (reset).
7. Exit and after re-init the console is no longer corrupt UPD> exit Initializing... SROM V1.1 on cpu0 SROM V1.1 on cpu1 XSROM V5.0 on cpu0 XSROM V5.0 on cpu1 BCache testing complete on cpu0 BCache testing complete on cpu1 mem_pair0 64 MB mem_pair1 64 MB mem_pair2 64 MB mem_pair3 64 MB 20..20..21..21..23.. please wait 6 seconds for T24 to complete 24..24..
Making a FailSafe Loader Floppy for a Compaq AlphaServer ES40 Overview The Compaq AlphaServer ES40’s failsafe loader can be invoked automatically when the console determines the firmware is corrupt or manually by putting jumpers J22 on pins 2-3. This will force the floppy to be read on power up. This procedure requires three floppies. One will contain SRM firmware to bring the system to a >>>. Floppy two will contain the LFU firmware image to bring the system to the UPD> prompt.
WNT - Alpha (clsrmrom.sys or clsrmrom.exe) a. Locate the files clsrmrom.sys and mkboot.exe or clsrmrom.exe and makeboot.exe. For EV67/EV68 CPUs use the cl67srmrom files. b. Copy the files to a disk on your Alpha. c. Fat format a floppy diskette. d. If using EV67/EV68 SRM firmware rename the files cl67srm.exe or cl67srm.sys. e. From an MSDOS window one of the following commands. makeboot -f clsrmrom.exe for EV6 CPUs makeboot -f cl67srmrom.exe for EV67/EV68 CPUs mkboot clsrmrom.
Starting secondary on CPU #1 Starting secondary on CPU #2 Starting secondary on CPU #3 Bcache data tests in progress Bcache address test in progress CPU parity and ECC detection in progress Bcache ECC data tests in progress Bcache TAG lines tests in progress Memory sizing in progress Memory configuration in progress Memory data test in progress Memory address test in progress Memory pattern test in progress Memory thrashing test in progress Memory initialization loading program from floppy .................
starting console on CPU 3 initialized idle PCB initializing idle process PID lowering IPL CPU 3 speed is 500 MHz create powerup os_type: UNIX - console CIPCA driver not started Memory Testing and Configuration Status Array Size Base Address --------- ---------- ---------------0 256Mb 0000000000000000 1 256Mb 0000000010000000 512 MB of System Memory Testing the System Testing the Disks (read only) Testing the Network Partition 0, Memory base: 000000000, size: 020000000 initializing GCT/FRU at 1a4000 AlphaSer
How to build the FSL floppy using the LFU firmware update image NT - PC or Alpha a. Go to the ES40 directory on the firmware website at http://ftp.digital.com/pub/Digital/Alpha/firmware/ b. Locate the appropriate zip file. It will include the correct LFU.exe image and firmware files for the system. All the examples are for an ES40. Other platforms will use flu.exe, glu.exe or ilu.exe Copy the file clu.exe, clsrmrom.exe for EV6 CPUs or cl67srmrom.exe for EV67 CPUs, clarcrom.exe and mkboot.
c. Change directory to where files were downloaded. # cd [to directory with files] d. You must set mkbootfirm file permissions to have execute permissions. # chmod 755 mkbootfirm e. Format the floppy. # fddisk -fmt /dev/rfd0a or With Tru64 UNIX V5.0 you can do one of the following # fddisk -fmt /dev/rdisk/floppy0a or # cd /dev # ./MAKEDEV fd0 # fddisk -fmt /dev/rfd0a f. From directory where files are located execute the following # ./mkbootfirm clu.exe |dd of=/dev/rfd0c bs=64k g. Insert floppy diskette 2.
Memory thrashing test in progress Memory initialization loading program from floppy ...................... Code execution complete (transfer control) OpenVMS PALcode V1.61-4, Tru64 UNIX PALcode V1.
Checking dqa0.0.0.15.0 for the option firmware files. . . dqa0.0.0.15.0 has no media present or is disabled via the RUN/STOP switch dqa0.0.0.15.0 has no media present or is disabled via the RUN/STOP switch Checking dva0 for the option firmware files. . . If you have a floppy containing option firmware, Please insert it now and hit when ready. Option firmware not copied.
Making a FailSafe Loader Floppy for a Compaq AlphaServer ES45 Overview The Compaq AlphaServer ES45’s failsafe loader can be invoked automatically when the console determines the firmware is corrupt or manually by putting jumpers J22 on pins 2-3. This will force the floppy to be read on power up. There is a zip file available on the firmware website that has all the necessary file. How to build the floppy using es45fsl.exe file with mkboot.exe or makeboot.exe WNT/W2k - PC a. Obtain the es45fsl.
UNIX – Alpha a. Obtain the es45fsl.zip file from the firmware website at http://ftp.digital.com/pub/DEC/Alpha/firmware/readmes/v6.1/es45/es45fsl.zip. b. Unzip the archize and copy the es45fsl.exe file to your Alpha. c. Also locate the amkeboot.exe program. Download the following files to a directory on your Tru64 UNIX system. They can be found on the firmware website interim directory at http://ftp.digital.com/pub/Digital/Alpha/firmware/interim/es40 or the ES40 directory located at http://ftp.digital.
Updating the FailSafe Booter (FSB) on a Compaq AlphaServer DS20 Overview In order for the failsafe booter code to work on the DS20/DS20E, new FSB code must first be loaded. The FSB code must be at least rev 3.2 to properly work. The FSB code is part of the V5.6 firmware update. The code can be loaded off CD or from floppy. You will need to execute a UPDATE FSB or UPDATE * command at the UPD> prompt. Procedure to update FSB code CD 1. Boot the V5.6 firmware update CD. 2.
444
Making a FailSafe Booter Floppy for a Compaq AlphaServer DS20 Overview The Compaq AlphaServer DS20’s failsafe booter can be invoked automatically when the console determines the firmware is corrupt or manually by setting switch S2-1 to on. This will cause the floppy to be read during init and the console code will be loaded into memory and executed. The system will come to a >>>. From here you should be able to boot the firmware CD and update the console firmware.
446
Making a FailSafe Booter Floppy for a Compaq AlphaServer DS10 Overview The Compaq AlphaServer DS10’s failsafe booter can be invoked automatically when the console determines the firmware is corrupt or manually by setting switch SW3 #8 to on. This will cause the floppy to be read during init and the console code will be loaded into memory and executed. The system will come to a >>>. From here you should be able to boot the firmware CD and update the console firmware. How to build the FSL floppy a.
448
Making a FailSafe Loader Floppy on a Digital Personal WorkStation Overview This document contains the procedure for repairing a Digital Personal Workstation A or AU series workstation (433a/au, 500a/au, 600a/au, etc) which is unable to function due to corrupted firmware in the MLB (main logic board) flash ROM. Flash ROMs can be corrupted by: • • • System power outage or glitch during a firmware upgrade. Cord kicked out, reset pressed, power hiccup from utility, etc).
POST (SROM) corrupted 1. If POST code is corrupted, then replace the MLB and return the bad MLB with a note saying the SROM is corrupt. Miata Main Logic Board with EV5 CPU Miata a/au Main Logic Board with EV5 CPU Chilled Miata Main Logic Board Miata GL Main Logic Board (EV56) Miata GL Main Logic Board (EV56) Miata GL Main Logic Board (EV56) 433MHz 500MHz 400MHz 500MHz 600MHz 54-24767-01 54-24767-02 54-25222-05 54-25222-01 54-25222-02 54-25222-03 2.
Make a Bootable Floppy Using Tru64 UNIX 1. 2. 3. 4. 5. 6. 7. Locate the firmware.exe file on CD or on the WEB. See Pointer at bottom of this page. Copy the firmware.exe file from the appropriate directory to your system and rename it fwupdate.exe Download the file mkbootfirm.tar from Cybrary. It is also available at the firmware website. ftp://ftp.digital.com/pub/Digital/Alpha/firmware/utilities/mkbootfirm.
Updating System Firmware 1.
5. Your same each • • target system’s firmware is now recovered. Restore your system to the configuration it was in before you began this recovery operation. Follow step below if applicable to restore your system: Remove the recovery floppy from the target system. Power machine on, and verify proper operation. Locations For Firmware on the Internet/Intranet http://cybrary.inet.cpqcorp.net/DOWNLOAD/FIRMWARE/SYSTEMS/ALPHA/default.html http://ftp.digital.com/pub/Digital/Alpha/firmware/ ftp://ftp.digital.
454
Creating a Bootable Firmware Floppy For the AlphaStation 200, 250 and 255 Overview Attempting to switch consoles on half-flash machines (all AlphaStation 255’s and some AlphaStation 200’s) can be difficult without the firmware update CD. This article will provide a .zip file that will allow you use an Intel PC to build a bootable firmware update floppy to switch from the SRM console used by OpenVMS and Tru64 UNIX to the ARC console which is used by Windows NT.
5. Place the floppy in the systems floppy drive and boot it. >>> boot dva0 6. At the APU> prompt update the ARC console firmware Apu-> update arc 7. Exit the power cycle the machine. 8. You will now come up into the ARC console to allow building or booting Windows NT.
AlphaServer 2100 "Cpu Type Not Supported" with B2041-AA 5/375 CPU Problem: After upgrading a AlphaServer 2100 to a 5/375 B2041-AA processor, you get a message "cpu type not supported" when booting Digital UNIX 3.2D-1. This occurred on SRM 5.0-80 and SRM 5.2. The install guide which comes with the cpu modules AS2x00 Series CPU Upgrade (EK-KN4xx-AA) list an nvram patch procedure, however the user guide is talking about DIGITAL UNIX 3.2C minimum or 3.2F the recommended.
458
Procedure to Update Firmware on a 2100 When an engineer replaces a B2110-AA module it doesn’t have ARC firmware loaded. They will need to load firmware and update the SRM and ARC consoles. When doing the update then can corrupt the firmware if the following procedure is not followed. What happens is they boot LFU off CD and tell it UPDATE SRM. They get a message that says the firmware on the module was greater than on the CD. Are you sure? They have been answering NO here then doing an UPDATE ARC.
Consistency checks failed, continuing anyway. FEPROM UPDATE UTILITY -----> CAUTION <----EXECUTING THIS PROGRAM WILL CHANGE YOUR CURRENT ROM Do you really want to continue [Y/N] ? : y DO NOT ATTEMPT TO INTERRUPT PROGRAM EXECUTION! DOING SO MAY RESULT IN LOSS OF OPERABLE STATE. The program will take at most several minutes. Setting to all 0s... Setting to all 1s... Programming... Verifying... Update successful P00>>> lfu P00>>> exit Do you want to do a manual update? [y/(n)] y Setting to all 1s...
AlphaServer 2100 FailSafe Loader (FSL) Overview and Functions Overview The fail-safe loader (FSL) is redundant or backup console that allows you to update or restore the SRM console if it is corrupted. The AlphaServer 2000, 2100 and 2100A systems utilize a ROM on either the standard I/O, motherboard or backplane module, depending on system type, to store the failsafe loader console.
Manual Activation If necessary, you can activate the FSL manually as follows: • • • • • • • Make sure the system power is off. Locate the FSL jumpers (AlphaServer 2000/2100) or switches (AlphaServer 2100A) Enable the FSL as follows depending on system type Install jumper J6 on the AlphaServer 2000 Backplane Install jumper J6 on the AlphaServer 2100/2100A LP Standard IO Move the FSL enable switch (top switch) on the backplane module to the right (enabled).
Method 1 1. Power off the machine. 2. Set the jumper or switch to enable failsafe ROM writes. 3. Boot the firmware CD P00>>> boot -fl 0,a0 dka600 4. Select the firmware file you desire Bootfile: [alpha2100]as2100_e4_v5_4.exe 5. At the UPD> prompt type exit UPD> exit 6. Answer Y to manual update Do you want to do a manual update? [y/(n)] y 7. Type update_fsl at the console prompt P00>>> update_fsl update_fsl is equivalent to "update -path fslrom -target fslflash -i" 8. Power off the system 9.
create powerup access NVRAM entering idle loop Starting Memory Diagnostics Memory Diagnostics completed probing hose 0, PCI probing PCI-to-EISA bridge, bus 1 bus 0, slot 0 -- ewa -- DECchip 21040-AA bus 0, slot 1 -- pka -- NCR 53C810 bus 1, slot 7 -- dra -- Mylex DAC960 bus 1, slot 8 -- vga -- Compaq Qvision bus 0, slot 8 -- ewb -- DECchip 21041-AA initializing keyboard Checking dka500.5.0.1.0 for the option firmware files. . . Copying DFEAA130 from dka500.5.0.1.0. . . Copying DFEAB320 from dka500.5.0.1.0.
Method 2 1. Power off the machine 2. Set the jumper or switch to enable failsafe ROM writes. 3. Boot the firmware CD P00>>> boot -fl 0,a0 dka600 4. Select the firmware file you desire Bootfile: [alpha2100]as2100_e4_v5_4.exe 5. At the UPD> prompt type update_fsl UPD> update_fsl update_fsl is equivalent to "update -path fslrom -target fslflash -i" 6. At the UPD> prompt type exit UPD> exit 7. Answer n to manual update Do you want to do a manual update? [y/(n)] n 8. Power off the system 9.
create timer create powerup access NVRAM entering idle loop Starting Memory Diagnostics Memory Diagnostics completed probing hose 0, PCI probing PCI-to-EISA bridge, bus 1 bus 0, slot 0 -- ewa -- DECchip 21040-AA bus 0, slot 1 -- pka -- NCR 53C810 bus 1, slot 7 -- dra -- Mylex DAC960 bus 1, slot 8 -- vga -- Compaq Qvision bus 0, slot 8 -- ewb -- DECchip 21041-AA initializing keyboard Checking dka500.5.0.1.0 for the option firmware files. . . Copying DFEAA130 from dka500.5.0.1.0. . .
Updating Firmware from the Fail-safe Loader The fail-safe loader on a 2x00 system is activated automatically when the SRM console is corrupt. You will need to follow these steps to update the firmware. Note If attempting to update firmware with the fail-safe loader manually enabled via a switch or jumper, just do the update *srm* command and exit. I have seen the second update command corrupt the first ROM that was updated.
468
AlphaServer 2x00 FSL Issues and Problems Unable to update both SRM and ARC from the FSL console With the fail-safe loader manually enabled with the jumper or switch I have noticed problems with the update corrupting one of the ROMs. I have not seen this with a system that enters the fail-safe loader automatically. The symptom you will see is after booting the CD from the ash> prompt the second ROM that is updated corrupts the 1st.
470
Unable to Set Date and Time under ARC After Replacing Module After replacing the module that houses the firmware on AlphaServer and possibly AlphaStation systems you are unable to set the Time/Date under ARC. It is set to 0/0/2000. If you attempt to enter the correct date it returns "illegal date/time entered". There appears to be a problem with ARC version 4.56 and 4.57 when the TOY clock has been set to zeroes. It appears that this is the case with new modules coming from manufacturing or repair.
472
AlphaServer 1200/4100 Issues 1. When upgrading to V5.3 or later for the first time you must follow a two step process to upgrade the firmware. Starting with the V5.3 console the AlphaBIOS image was relocated into a different area of flash ROM. In order for the new firmware to work you must update firmware as follows.
474
Certain AlphaServers With V5.7-4 Gets Console DAC960 Sizing Errors AlphaServer 4100/1200 , DigitalServer 7000/5000 and Digital Ultimate Workstation’s updated to V5.7-4 SRM console code have problems with the SWXCR controllers during initialize. You will see the following error. Configuring IO ...
476
Updating Console Firmware on a System Configured as a Galaxy Firmware on systems configured as a Galaxy node can not be updated until the system is first powered up in non-Galaxy mode (monolithic mode). You can not safely run utilities like ECU, RCU, EEROMCFG, etc. when in Galaxy mode either. The following steps are required to update the firmware successfully or run console based utilities. See page 267 for information on each variable. They are set differently depending on the system type. 1.
478
AlphaServer 8X00 IMPORTANT CAUTIONS BEFORE UPDATING FIRMWARE !!! Operation With Mixed Firmware Revisions is NOT Supported In a multiprocessor system, do NOT attempt to initialize or operate the system, with mixed-revisions of console firmware installed on the CPUs. Always insure that the CPUs all have the same revision of Console Firmware, before initializing or powering-up the system. Otherwise, the system may hang, or some CPUs may not operate.
480
AlphaServer 8X00 Single CPU Modules Fail With Console Firmware V6.0 There is a problem with single CPU Turbolaser modules (300/350 MHZ) and firmware version V6.0. If a single CPU card is upgraded to V6.0 the CPU will either hang during selftest of the selftest LED will not come on. The CPU will not show up at the console either. There is a workaround available on EV5/EV56 Turbolaser systems (not available for EV6 or EV67).
482
Compaq AlphaServer GS60/GS60E/GS140 IMPORTANT CAUTIONS BEFORE UPDATING FIRMWARE !!! Operation With Mixed Firmware Revisions is NOT Supported In a multiprocessor system, do NOT attempt to initialize or operate the system, with mixed-revisions of console firmware installed on the CPUs. Always insure that the CPUs all have the same revision of Console Firmware, before initializing or powering-up the system. Otherwise, the system may hang, or some CPUs may not operate.
484
AlphaServer GS60/GS140 Fails to Boot Firmware CD V5.4 Following the standard procedure to boot the Alpha Systems Firmware Update CD V5.4 on AlphaServer GS60 and GS140 systems may intermittently fail. PROBLEM SYMPTOM: After booting the CD and after the program reports "Starting new console, Please wait a minute...
486
DS10 With 600MHZ CPU Has No Default Bootfile Selected with V5.9 CD When an attempt is made to upgrade a DS10 system with the 6/600 MHZ CPU using the V5.9 Alpha Systems Firmware Update CD, no default bootfile will be selected. The user will need to enter the directory and filename in order to load firmware off the CD. The firmware CD uses a file called smttable.txt that defines what default bootfile that is used for each platform. The DS10 6/600 CPU was not added to the file on the V5.9 CD.
488
DS10/DS20 Invalid Image When Updating From Floppy In order to update firmware from floppy on the DS10 and DS20 platforms you need to copy platform specific firmware.sys files to a system and save them to a floppy. When attempting to update the firmware the SRM and/o AlphaBIOS images my indicate Invalid Image fom LFU when executing a list command. This nomally happens when Netscape is used to download the files. The workarounds are to either use Internet Explore to download the files of go to ftp://ftp.
490
Upgrading ES40,ES40LP or ES40CV to 667MHz or 833MHz CPUs Upgrading ES40 systems to faster processors requires loading the correct console firmware to support the faster CPUs. The 833 MHZ CPUs require SRM V5.9-24 and SROM V2.12F in order to properly function. The EV67 CPUs also require a different PALcode than the EV6 CPUs. The firmware must be updated before the CPUs are replaced. All CPUs must also be the same speed. You can not MIX different speed CPUs in the same box.
6. Remove original CPUs and install the new 667MHz or 833MHz CPUs. This will allow console control because the correct SRM and SROM code is loaded. The correct PALcode must now be loaded. There are 2 versions of PALcode. • • 7. PALcode for EV6 500MHz cpu’s is in the format of Vx.yy-z PALcode for EV67 667MHz or EV68 833MHz cpu’s is in the format of Vx.yy-zzz Boot the Alpha Systems Firmware Update V5.9 CD and select the default es40 firmware file file "ES40_V5_9.
5. When the update is complete type verify and if they all pass exit. Beware the RMC firmware mail say failed. This is because the ES40LP uses a different version than what is loaded from the default ES40 firmware file. UPD> verify UPD> exit 6. Remove original CPUs and install the new 667MHz or 833MHz CPUs. This will allow console control because the correct SRM and SROM code is loaded. The correct PALcode and RMC firmware must now be loaded. There are 2 versions of PALcode.
4. At the UPD> prompt enter the update command for all the system firmware except the RMC. This includes ABIOS, SRM, SROM and TIG. The SRM V5.9-24 and SROM V2.12F is required for the 833 MHZ CPU support. The RMC firmware F2.5 is the ES40CV version. Caution: DO NOT upgrade the RMC using the RMC firmware loaded by default. The ES40CV uses the RMC version F2.5 which is loaded from a seperate firmware file. UPD> update abios Abios Updating to 5.70... Verifying 5.70... PASSED.
10. Clear the central error repository and display status of the new CPUs. P00>>> clear_error all P00>>> show config 11.
496
ES40LP/ES40CV RMC Firmware is Different Than on the V5.6 Firmware CD Overview There are three different models of the ES40. They are the Corporate Clipper (ES40), the Flying Clipper (ES40CV), and the Ironsides (ES40LP). Each uses a different version of the RMC firmware. The V5.6 Alpha Systems Firmware CD only has RMC firmware for the Corporate Clipper. If you load the wrong RMC firmware into a system it will indicate fan failures. The Ironsides - ES40LP will complain about fan 6.
Tru64 UNIX This method requires one floppy. One with the LFU utility and the other with the system firmware. a. Download mkbootfirm.tar from Cybrary to your UNIX system. b. Extract the RMC firmware from the Cybrary. There are two files located in the Download directory. Copy it to the same directory as mkbootfirm.tar. Three methods to get the firmware are • You can copy the es40_rmc_fw.zip file to an NT system and unzip it there. Then copy the files from you PC to the UNIX box.
Network and OpenVMS a. Copy the RMC firmware.sys file to MOM$LOAD of an existing node in the cluster $ Copy es40cv_f22.sys mom$load for the Flying Clipper or $ Copy iron_i22.sys mom$load for the Ironsides b. Set the VMS attributes on the file with the following command. $ Set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) es40cv_f22.sys or $ Set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) iron_i22.sys c.
Processors CPU 0 CPU 1 CPU 2 CPU 3 Alpha Alpha Alpha Alpha Core Logic Cchip Dchip Pchip 0 Pchip 1 TIG DECchip DECchip DECchip DECchip Rev 10 Memory Array --------0 1 2 3 Size ---------512Mb 512Mb 512Mb 512Mb EV6 EV6 EV6 EV6 pass pass pass pass 2.3 2.3 2.3 2.
create timer create powerup access NVRAM Memory size 2048 MB testing memory ... probe I/O subsystem probing hose 1, PCI bus 0, slot 4 -- pka -- NCR 53C895 bus 0, slot 5 -- ewa -- DE500-BA Network Controller probing hose 0, PCI probing PCI-to-ISA bridge, bus 1 bus 0, slot 15 -- dqa -- Acer Labs M1543C IDE bus 0, slot 15 -- dqb -- Acer Labs M1543C IDE starting drivers entering idle loop Istream prefetching is being turned off (i_ctl.
-----------------------------------------------------------------------------Display Displays the system’s configuration table. Exit Done exit LFU (reset). List Lists the device, revision, firmware name, and update revision. Readme Lists important release information. Update Replaces current firmware with loadable data image. Verify Compares loadable and hardware images. ? or Help Scrolls this function table.
AlphaServer ES40’s Configured for Galaxy Should Not Use V6.0 Firmware AlphaServer ES40 systems that are configured for Galaxy, (soft partitions) must not be upgraded using the V6.0 console firmware. If this firmware is loaded partiton 1 will display an access violation. Until new firmware is released use the V5.9 console firmware on the ES40 when configured for Galaxy partitioning. See Blitz TD 2943-CR for details.
504
ES40 & GS80/GS160/GS320 Systems May Not Boot Unix V4.0G When running the wwidmgr or a non-powerup system test, the SRM on ES40 and GS80/160/320 systems may expand the console heap beyond what the operating system needs to boot. Once the heap expands, the new value continues to be used until it is changed. Due to a boundary condition in V4.0G, failure to reset the heap_expand environment variable after running the system test or wwidmgr can prevent the system from booting.
506
DEC7000/10000 and VAX 7000 - Issues With Firmware Upgrades 1. Sometimes the 7000 console will "run away" due to a problem in a powerup script (an INIT command placed in it) or due to a continuous machine check loop. You can’t get to a >>> when this happens. Use this procedure to corrupt the console EEPROM. During the init sequence when the "map" is being printed there is a pause about 2/3 of the way thru the "map".
replacing this module the KCM44 will show up as a KDM70. To correct this do the following. >>>Boot LFU Function? MODIFY KDM70# Change ID on this KDM70 to KCM44? [Y/(N)] Y Are you sure? [Y/(N)] Y Changing ID from to KCM44.... Function? exit 5. If updating from an Infoserver the file name MUST be uppercase (ISL_LVAX_V07). There is also an issue booting off of an RRD43. It will timeout and not boot. You will need to use a different CD type (i.e.RRD42). >>> boot -fl 0,0,0 exa0 -fi ISL_LVAX_V07 Initializing...
DEC3000-400 System Hangs After Upgrading Console Firmware to V6.1 SYMPTOM: After upgrading the console firmware on the DEC3000 model 400 that has a V1.0 SROM to V6.1 console from the Update CD V3.2 (PN AG_PTMWP-BE), the system hangs on boot with no VGA output. The serial console port shows a machine check message. SYSTEM MACHINE CHECK ABORT HAS OCCURRED PC=000680. NOTE: This same symptom may be seen upon upgrading the console firmware to V6.2 also.
510
DEC3000 Firmware Mismatch Between System and I/O Roms The DEC3000 has firmware ROMS on the system and I/O modules. If you replace one or both of these modules or if you do a firmware upgrade and do not have both the system and io update jumpers enabled you may get an error message at powerup complaining about a firmware mismatch. Mismatch Firmware, SYS 4.0 / I/O 6.1 The system may fail all IO tests (NI, SCSI etc) and because of this be unable to boot.
512
Contents of The System and I/O Roms on a DEC 3000 On the DEC 3000 there are System and I/O roms that contain the following.
514
Firmware/Console Related Blitz’s 515
516
Firmware/Console Related Blitz’s AlphaServers • TD 2941 Hard Error #8 on Alpha Servers with an HSJ controller AlphaServer 300 • [TD 2518-A] ASTN & ASRV w/ SRM V6.8 and the PCI ATMworks350 Errors AlphaServer 400 • [TD 2518-A] ASTN & ASRV w/ SRM V6.
AlphaServer 4000/4100 • [TD 2789] AS4x00 and AS1200 V5.7-5 firmware fails SHOW DEVICE for RAID • [TD 2781] AS4x00 and AS1200 V5.7-4 firmware fails on RAID configurations • [TD 2778] DS20E EV67 CPU Upgrade and SFM Revision • [TD 2668] V5.4 LFU Update Methods Failure on AS4x00 and AS1200 Statement • [TD 2654] OpenVMS Alpha Galaxy configuration support info for OpenVMS V7.2 • [TD 2602] AS1200 & AS4x00 DEGPA-SA System Requirements • [TD 2562] SRM Console Firmware V5.
• • • • • • • • • • • • • [TD [TD [TD [TD [TD [TD [TD [TD [TD [TD [TD [TD [TD 2252] AlphaServer 8400/8200 platforms - possible hang 2234] Recalling CIXCD V8 firmware 2192] AlphaServer 8400/8200 & V4.1-6 Console firmware 2086] AlphaServer 8200/8400 may fail 2085] AlphaServer 8200/8400 w/KZPAA & OpenVMS V6.
• • • • • • [TD [TD [TD [TD [TD [TD Compaq • [TD • [TD • [TD • [TD • [TD • [TD 2678] Firmware Upgrade for AlphaServer GS60/GS140 Systems 2651-CR] AlphaServer GS60/GS140 Console Upgrade /Firmware CD V5.4 2622-CR} UNIX Workaround for PAL Code Error 2610-CR-B] Update on Errors from Oracle 8.0.4.x w/DUNIX & EV6 2594] AlphaServer GS60/GS140 Mandatory Console Firmware Upgrade 2578] Compaq AlphaServer GS60/GS140 Problems and Solutions AlphaServer GS80/GS160/GS320 2942] UNIX V4.
• [TD 2321] AS500 w/SRM V6.4-5 hangs w/KZPSA-BB option AlphaStation 600 • [TD 1963] New Version Firmware Available for Alphastation 600 • [TD 2371] KZPBA-CA UltraSCSI Adapter • [TD 2275] AS600 with SRM V6.4-5 hangs w/ KZPSA-BB option • [TD 2054] Open APX VMS V6.
DEC 4000-600 • [TD 1585] MS430-FA (B2011-AA, 512MB)/DEC 4000 Model 6xx / 7xx Series • [TD 1338] PROBLEMS ENCOUNTERED WHEN INSTALLING DEC 4000 MODEL 610 CPU DEC 7000 / 10000 • [TD 2832] KZPCC-CE Configs, Drive Failure/Removal Causes System Crash • [TD 2015] DEC7000 Console V4.5 Problem w/ Single CI Path to HSJ40 • [TD 1947] VAX7000 & DEC7000 Memory Configuration Restrictions • [TD 1865] DEC7000/10000 Console V4.2 Has a Serious Problem • [TD 1732] DEC7000 with >2GB mem,CIXCD,run.
• [TD 1873] AlphaServer 8200/8400 Problem with KZPSA Utility 523
524
References 525
526
• • • • • • • • GS80/160/320 Bulletin Board Engineering Tools Website AlphaServer Engineering webpage AlphaServer-Inside DS20 (Goldrush) webpage DS20 (Goldrush) webpage AlphaServer 1200 (Tincup) webpage ES40 Clipper PVT page 527 Subject Moderator if Restricted AlphaStations AlphaStation500 AlphaServer 800 ( Add entry danger::notes$library:corelle ) AlphaServer 1000/1000A HS111,HS121,HS211,HS221,HS241,SWXNA (Alphaserver 1000 based) Goldrush (DS20), Clipper (ES40), and Web Brick (DS10) Wildfire (GS80, GS16
http://cybrary.inet.cpqcorp.net/ARCHIVE/PUBS/USERS/ALPHA-FIRMWARE-UPDATE-V61.pdf http://Cybrary.inet.cpqcorp.net/SYSTEMS/ALPHA/FIRMWARE/firmware_procedures.html http://Cybrary.inet.cpqcorp.net:/SYSTEMS/ALPHA/failsafe_loader.html http://Cybrary.inet.cpqcorp.net:/SYSTEMS/ALPHA/fsl_update.html http://Cybrary.inet.cpqcorp.net/SYSTEMS/ALPHA/as800_floppy.html http://Cybrary.inet.cpqcorp.net/SYSTEMS/ALPHA/ASRV2000/2x00_fsl.html http://Cybrary.inet.cpqcorp.net/SYSTEMS/ALPHA/ASRV4000/4x00_fsl_update.
http://Cybrary.inet.cpqcorp.net http://Cybrary.inet.cpqcorp.net/DOWNLOAD/FIRMWARE/SYSTEMS/ALPHA http://ftp.digital.com/pub/DEC/Alpha/firmware/ Digital’s Firmware website http://ftp.digital.com/pub/Digital/Alpha/firmware/ ftp://ftp.digital.com/pub/DEC/Alpha/firmware/ ftp://ftp.digital.com/pub/Digital/Alpha/firmware/ http://ecs2.mro.cpqcorp.net/wf/ Wildfire firmware location http://16.129.13.229/wildfire/ Wildfire firmware location http://www.compaq.com/support/files/alphant/index.
.E01) .PRE) .A01) .B01) .A01) .B01) .A01) .A01) .A01) .A01) .
531
532
Index A Alpha Windows NT Matrix .................................................................................................................................................... 21 B Blitz’s .................................................................................................................................................................................... 513 E ECU - EISA Configuration Utility ..................................................................................................
version......................................................................................................................................................................... 304 FFAUTO and FFNEXT ................................................................................................................................................... 313 Galaxy Definitions ..............................................................................................................................................
AlphaStation 500/600 ...................................................................................................................................................... 223 AlphaStation 600A........................................................................................................................................................... 233 CIXCD .........................................................................................................................................................
AlphaServer 1000/1000A, CPU EV5/300 ......................................................................................................................... 57 AlphaServer 1000/1000A, Motherboard............................................................................................................................ 55 AlphaServer 1000A, CPU EV5/333 ..................................................................................................................................
S Scripts ................................................................................................................................................................................... 317 1000A_to_600A............................................................................................................................................................... 317 600A_to_1000A................................................................................................................................
538
