OBSOLETE Patch-ID# 106122-06
Keywords: Workgroup Server Flash PROM Update
Synopsis: Obsoleted by: 106122-07 Hardware/PROM: Enterprise 450/Ultra 450 Standalone Flash PROM Update
Date: Feb/02/2000

Solaris Release: 2.5.1 2.6 7 8

SunOS Release: 5.5.1 5.6 5.7 5.8

Unbundled Product: Hardware/PROM

Unbundled Release: OBP 3.16.2, POST 6.0.9, OBDIAG 4.4.1

Xref: 

Topic: 

Relevant Architectures: sparc

BugId's fixed with this patch: 1220439 4039363 4043692 4051366 4055327 4059967 4059974 4059979 4059990 4064073 4064076 4066649 4068500 4072259 4072262 4073523 4075527 4098422 4098469 4098487 4099122 4099630 4106390 4108001 4118996 4119402 4127836 4138125 4155410 4156139 4160035 4160480 4161092 4161167 4161734 4161758 4162129 4163234 4163238 4163240 4163247 4163250 4163255 4169493 4169494 4173531 4173536 4173712 4181081 4182015 4186860 4193590 4194137 4195116 4195750 4196157 4198002 4200617 4204816 4205887 4207524

Changes incorporated in this version: 4217666 4199860 4219826 4145789 4161167 4207760 4207822 4036853 4223043 4276772 4298883 4206681 4302752 4255125

Patches accumulated and obsoleted by this patch: 

Patches which conflict with this patch: 
	  NOTE: This utility is *not* OS-dependent.  The list of releases shown
          under the "Solaris Release" and "SunOS Release" sections may not
          be complete: The absence of a valid Solaris Release or SunOS
          Release from the lists above does not preclude the installation
          of this patch against the hardware.
    NOTE: sun4u Enterprise 450 / Ultra 450 only
	  NOTE: Due to differences in motherboard and flashprom part numbers
	  on the E450, once the -03 or greater patch is installed, you
	  cannot return to the -01 or -02 patch.


Patches required with this patch: 

Obsoleted by: 

Files included with this patch: 

802-3233-19.ps,
README.106122-06,
flash-update-450-01
flash-update-450-02,
flash-update-450-03,
flash-update-450-04,
flash-update-450-05,
flash-update-450-06
flash-update-450-latest,

Problem Description:

4217666  Add typeout of system timing mode to diagnostics power-on output of OBP
4199860  Cheerio Ebus-based plug-in cards cause E450/E250 OBPs to fault during probe
4219826  Remove "-a" from ''printenv'' word, not 1275-compliant
4145789  New features and abilities for interactive Forth debugger
4161167  New ability to repeat/step "n" times in Forth debugger
4207760  "Backtrace" capability for the Forth debugger
4207822  Forth debugger: step-range commands  <  and  >  don''t work quite right.
4036853  Bringover Desktop 3.15 OBP bugs/rfes into WGS src base
4223043  Wyse terminal on ttya of E250 with OBP 3.12.11 does not display at ok prompt
4276772  Memory Probing fails on Tazmo motherboards with revised memory components
4298883  Adjust PLL N Ranges in accordance with new info from Motorola
4206681  System reports "EnvMon: I2C read failure for Ambient temperature at: 9a"
4302752  UE/CE Error checking not enabled on slave processors
4255125  After L1-A and typing go, qfe driver hangs on E450 + Solaris 7
4181081 OBP needs to establish "compatible" property under /pci/ebus/flashprom
4194137 IP addresses specified as arguments to "boot net" not read correctly
4119402 .properties doesn''t display "compatible" property as a list of names
4195750 Pending breaks should be cleared before console is installed.
4169493 Change TEST-ALL (and test-all script) SelfTests selection algorithm
4200617 "compatible" and "name" are incorrectly generated
4207524 Provide updating timing for motherboard
4186860 Obdiag UART test port B fails from mfg-x script
4198002 The menutool output gets messed up in TERMINAL (xterminal) window.
4182015  help on diag variables from obdiag menu doesn''t work
4162129  OBDiag TESTREG method doesn''t handle some types of masked bits correctly
4169494  Change current SelfTest selection algorithm in OBDIAG menu tool.
4106390  scsi selftest uses CREATE ALLOT, shall use BUFFER: instead
4204816 Add WARNING( and )WARNING to obdiag library of FCodes
4196157 Need support to be able to add more INSTANCE FCode to the created device nodes
4193590 Add support for INSTANCE objects in obdiag selftests
4205887 OBP ALARM handler can be broken by consecutive events
4195116 CPU2 timeout
4138125 Fixed 400 MHz psycho error test problem. 
4108001 Heading on second OBDIAG help screen scrolls off screen.
4156139 Redesign HELP command of obdiag, call OBP HELP for diag config. variables
4043692 Should use the standard tokenizer for OBDiag library
4068500 DIAG-THROW is a critical missing word from obdiag library set
4073523 OBDiag use of version numbers should be clarified
4072259 There is a dependency in both obdiag menu and the library on SELFTEST-ERRORS
4059974 obdiag )error fcode depends on non-fcode no-P1275 DATE word
4059979 obdiag )error fcode depends on number of no-fcode no-P1275 words for CALLER:
4072262 There is a dependency on DIAG-PASSES, DIAG-VERBOSITY, DIAG-CONTINUE? in OBDiag
4059967 obdiag )error fcode depends on non-fcode word PWD interfacing it from OBP
4059990 obdiag menu tool depends on non-fcode non-P1275 PWD$ forth word from OBP
4099630 The current obdiag source tree doesn''t support compression of drop-in images
4160480 ihandle>devname and phandle>devname consume dictionary space
4039363 obdiag tool coomands doesn''t allow spaces between arguments
4055327 Add PARSE-SUBTESTS fcode to the obdiag library
4160035 Remove MASK, MASK-AND, MASK-OR, add SET-MASKS and GET-MASKS to obdiag library
4064073 Keyboard/Mouse Selftest will not run if Keyboard is attached and used as console
4064076 The SAB82532 selftest method heavily depends on the OBP serial driver
4075527 Merge kbd and mouse selftests into one. Use one source file, one dropin.
4161758 SERIAL selftest sometimes fails with Timeout Error, need to read CMD reg twice
4161734 SERIAL selftest missing DROP in flush-fifo code
4118996 Remove AFB fan dependency.
4155410 Ensure that help screen in OBDIAG and OBP are "in sync"
4051366 Need obp mechanisum for user to get list of valid values for setenv variables
4163240 Need to dynamically probe DTAG SRAM
4163234 Need to update table in freq.fth to accomodate 400MHz
4163250 Motherboard part numbers reported incorrectly
4163255 Need to be able to support multiple fan speed tables
4163247 at-speed does not work across PLL boundries
4163238 Change cpu name type out to UltraSparc I and UltraSparc II
1220439 "switch-cpu"  shows "Interrupt Vector" message
4098422 test and test-all obp commands should support dynamic loading of drop-ins
4099122 Fixed test-all from breaking if a selftest returns more than one argument onthe stack
4098487 Fixed test-all command crashes with Fast Instruction Access MMU Miss if selftest throw
4098469 Fixed test command from reporting "No selftest method" if selftest incorrectly executes throw
4161167 New ability to repeat/step "n" times in Forth debugger
4161092 probe-scsi-all ignores nvramrc setting of scsi-initiator-id on E450/OBP 3.7
4127836 Openboot PROM 3.7 on Javalin and Tazmo does not support fddi client boots
4066649 Fixed shutdown user interface to provide suffient time to abort shutdown
4173531 SCIQ field in the UPA Config register incorrect
4173536 Change in N=2 PLL range on MC12430
4173712 Added ''flash-verify'' command; ''flash-update'' and ''flash-verify'' will report the first 16 "fails"

Patch Installation Instructions:
================================
Intro
-----
    This README is intended for users who wish to upgrade the firmware
    in their Enterprise 450 system Flash PROM.
Summary of the Patch Installation Process:
------------------------------------------
The installation shall comprise of the following steps
1)  Determine the system''s current Flash Prom firmware revision.
2)  Compare the current Flash Prom firmware revision with the available or 
    latest Flash Prom firmware revisions.
3)  If the current Flash Prom firmware revision is lower than the latest
    available firmware revision in this patch, then proceed to the next step. 
    If NOT, STOP: DO NOT CONTINUE.
4)  Prepare the system for the Flash Prom update
5)  Running the Flash Prom Utility
6)  Verifying successful Flash Prom Update
7)  Restoring the system
8)  Resume operations
Patch Installation instructions (in detail):
============================================
The required steps are explained in greater detail below.
1)  Determine the System''s Current Firmware Revisions
    -------------------------------------------------
    While the OS is running the following command may be used to
    determine the current system firmware revisions;
	/usr/platform/sun4u/sbin/prtdiag -v | grep OBP
	or
	/usr/sbin/prtconf -V
    The firmware revisions may also be determined from the PROM monitor''s
    "ok" prompt with the following command;
	.version
2)  Compare the current Flash Prom firmware revision with the available or 
    latest Flash Prom firmware revisions.
    Compare the output of the OBP line in the "prtdiag -v" or "prtconf -V"   	
    output. Find the revision number and compare with the revision on the 
    entries below that of the "flash-update-450-latest" line
      Available Firmware Revisions
      ----------------------------
-01     flash-update-450-01
        OBP  3.5.105 1997/07/25 15:20
        POST 4.0.6   1997/07/22 10:20
-02     flash-update-450-02
        OBP   3.7.107 1998/02/19 17:54
        POST  5.0.8   1998/01/26 17:52
	OBDIAG 3.9.2  1998/01/27 14:25
-03     flash-update-450-03
        OBP    3.12.2 1998/09/14 11:28
        POST   6.0.6  1998/07/16 18:40
	OBDIAG 4.3.1  1998/07/30 10:39
-04	flash-update-450-04
        OBP    3.12.3 1998/12/04 14:20
        POST   6.0.8  1998/12/04 13:51
	OBDIAG 4.3.1  1998/07/30 10:39
-05     flash-update-450-05
	OBP    3.14.1 1999/02/12 07:50
	POST   6.0.9  1999/02/12 07:52
	OBDIAG 4.4.1  1999/02/12 07:51
LATEST flash-update-450-06; flash-update-450-latest
	OBP    3.16.2 2000/01/11 15:42
	POST   6.0.9  2000/01/11 15:43
	OBDIAG 4.4.1  2000/01/11 15:43
3)  Is the UPGRADE NECESSARY?
    If the current Flash PROM revision matches the version numbers given under
    the flash-update-450-latest line, then STOP Here. This UPGRADE IS NOT
    NECESSARY.
    If the current Flash Prom firmware revision is lower than the latest
    firmware revision in this patch, then proceed to the next step.
4) Preparing the System
   ---------------------
  a) As root, copy the "flash-update" files from the directory containing the 
     patch to the root directory as follows:
     # cp flash*latest  /
     # chmod 755 /flash-update*
     In order to boot the binary, it must be located within the root
     partition.  If it is not already located within the root partition
     then move it to /.  If the binary is already located elsewhere 
     within the root partition then note the exact filepath so that the
     binary can be booted later.
  b) As root, exit the OS such that the system returns to the PROM''s "ok"
     prompt: 
     # halt
       ok
  c) Jumper J3103 is factory-set so that the flash PROM is write-enabled. 
     There is no need to switch the jumper before flash updating; however, 
     you must ensure that the keyswitch is in the Power-on or Diagnostics 
     position.  When the key switch is in the locked position the flash 
     PROM is write protected.
5)  Running the Flash Update Utility
    --------------------------------
  a) Reset the system.
     Wait for the PROM''s banner to appear, and then
  b) use the Stop-A keys (or Break key, if running from a serial line) to
     abort the auto-boot sequence.
     ** NOTE **  If the flash update completes normally then the values
     contained within the system''s Non-Volatile RAM (NVRAM) configuration
     variables will be retained.  However, if the update process is some-
     how interrrupted then it is possible that any non-default values
     contained in NVRAM will be lost.  For this reason it is recommended
     that you note down on paper the contents of any NVRAM configuration
     variable which has been customized so that they may be manually
     restored at a later time, if necessary.  (Use the PROM''s "printenv"
     command to list the variables and their values.)
  c) The system should now display the PROM monitor''s "ok" prompt.
     Now boot the Flash update utility as given below:
     CAUTION: Do not boot/run revisions lower than the latest unless you
	      are absolutely sure that that is what you want to do!
     ok boot disk /flash-update-450-latest
     NOTE: If your system''s boot device is not "disk" then you will
           have to specify the appropriate devalias (e.g. disk2).
           If the binary is located in a location other than / then
           provide the entire filepath after the boot device.
     Answer the questions as prompted by the utility. 
+++++++++++++++++++++ example Flash update follows ++++++++++++++++++++++++
++++++++ Note that this is an example only.  Much of the information ++++++
++++++++ which is displayed by your system will be different from    ++++++
++++++++ what is shown below.                                        ++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Standalone Flash PROM Update Utility, Rev. 2.4
                        Ultra(tm) 1
                        Ultra(tm) 2
                        Ultra(tm) 5/10
                        Ultra(tm) 30
                        Ultra(tm) 60 / E220R
                        Ultra(tm) 80 / E420R
                        Ultra(tm) Enterprise(tm) 250
                        Ultra(tm) Enterprise(tm) 450
This utility allows you to interactively update the firmware
revisions in specific system Flash PROM components.
Type h for help, q to quit, Return or Enter to continue: 
Every precaution should be taken to prevent the loss of system
power during the Flash PROM programming process!
Type h for help, q to quit, Return or Enter to continue: 
       Firmware Release(s)                Firmware Release(s)
 Currently Existing in the System      Available for Installation  /  Install?
---------------------------------- -------------------------------------------
OBP 3.14.1 1999/02/12 07:50        OBP 3.16.2 2000/01/11 15:42          no
POST 6.0.9 1999/02/12 07:52        POST 6.0.9 2000/01/11 15:43          no
Type sa if you wish to select all available firmware releases for
installation.  Type h for help, quit to exit, or cont to continue: sa
       Firmware Release(s)                Firmware Release(s)
 Currently Existing in the System      Available for Installation  /  Install?
---------------------------------- -------------------------------------------
OBP 3.14.1 1999/02/12 07:50        OBP 3.16.2 2000/01/11 15:42          YES
POST 6.0.9 1999/02/12 07:52        POST 6.0.9 2000/01/11 15:43          YES
Type sa if you wish to select all available firmware releases for
installation.  Type h for help, quit to exit, or cont to continue: cont
The Flash programming process is about to begin.
Type h for help, q to quit, Return or Enter to continue: 
Erasing the top half of the Flash PROM.
Programming OBP into the top half of the Flash PROM.
Verifying OBP in the top half of the Flash PROM.
Erasing the bottom half of the Flash PROM.
Programming OBP into the bottom half of Flash PROM.
Verifying OBP in the bottom half of the Flash PROM.
Erasing the top half of the Flash PROM.
Programming POST into the top half of Flash PROM.
Verifying POST in the top half of the Flash PROM.
Programming was successful.
Resetting ... 
Restoring previous NVRAM environment settings...
#power-cycles =       10
auto-boot? =          false
security-#badlogins =  0
OK
Resetting ...
+++++++++++++++++++++ example Flash update ends ++++++++++++++++++++++++++
  Once the PROM''s banner reappears then use the Stop-A keys (or Break
  key, if running from a serial line) to abort the auto-boot sequence
  if the system begins to boot.
6)  Verifying successful Flash Prom Update
    Verify from the results of the .version command that the OBP
    version matches the OBP version given above under the
    flash-update-450-latest entry in Step 2.
7)  Restoring the system
    If the keyswitch position has changed (it was in the locked position
    before flash updating) return it to its original position. 
    If any problems should be encountered during the firmware upgrade
    then consult the "Sun Flash PROM Guide for Workstations
    and Workgroup Servers - Standalone Version".
8)  Resume operations
    a) Reset the system and allow the system to boot the operating system.
    b) Once the system has rebooted you may wish to remove the Flash Update
       binaries and documents since they will no longer be needed.
       # rm /flash-update*
    c) Remember to remove the files from their original location if
       they were not extracted directly into the root directory.

Special Install Instructions:
----------------------------- 
**************************************************************************
**************************************************************************
**WARNING:****WARNING:****WARNING:****WARNING:****WARNING:****WARNING:**
*  PLEASE READ THE INSTRUCTIONS CAREFULLY AND ENTIRELY.  PLEASE FOLLOW THE
   INSTRUCTIONS EXACTLY AS THEY ARE STATED.
*  FAILURE TO FOLLOW INSTRUCTIONS COULD EITHER RESULT IN A DEFECTIVE BOARD OR
   UNSUCCESSFUL FLASH PROM UPDATE.
*  THIS IS NOT A STANDARD PATCH in that it does not use the installpatch
   and backoutpatch scripts.
*  THIS PATCH CANNOT BE INSTALLED ON AN ONLINE OPERATING SYSTEM BECAUSE
   THE INSTALL INSTRUCTIONS REQUIRES THAT THE SYSTEM BE BROUGHT DOWN.
   BE SURE TO SCHEDULE DOWN TIME TO INSTALL THIS PATCH.
*  INSTALLATION OF THIS PATCH MAY REQUIRE A KEY SWITCH CHANGE. IF YOU ARE
   UNSURE ON HOW TO OPEN THE SYSTEM BOX, PLEASE ENSURE THAT A QUALIFIED 
   PERSON, WITH THE STATIC WRIST STRAP KIT NEEDED TO SERVICE ELECTRONIC
   EQUIPMENT, IS AVAILABLE TO COMPLETE THIS ACTIVITY. FAILURE TO USE STATIC
   PROTECTION KIT OR IMPROPER HANDLING COULD RESULT IN THE DAMAGE OF THE 
   SYSTEM BOARD.
*  PLEASE REVIEW NOT ONLY THIS README BUT ALSO ADDITIONAL DOCUMENTATION
   GIVEN.
   The file "802-3233-xx.ps" (where xx stands for the latest numeric
   revision) is a PostScript copy of the "Sun Flash PROM Guide for Workstations
   and Workgroup Servers - Standalone Version", which  provides the following;
   (i) Emergency instructions in the unlikely event that the Flash
        update should fail.
   Note, however, that The Programming Guide was originally written for 
   a user who is running the Flash PROM update utility from a bootable
   CDROM, and thus it will not contain the proper boot commands for
   installation of this patch.  Also note that the instructions in
   the document for installing packages are not valid for this patch.
**WARNING:****WARNING:****WARNING:****WARNING:****WARNING:****WARNING:**
**************************************************************************
**************************************************************************

Last modified date:  Friday, December 1, 2000

