Patch-ID# 118323-01
Keywords: update sun blade 1000 sun fire 280r netra[tm] t20 sun blade 2000
Synopsis: Sun Blade 1000, Sun Fire 280R,  Netra[tm] T20, Sun Blade 2000
Date: Jan/10/2005


Install Requirements: Additional instructions may be listed below                      
                      
Solaris Release: 8 9

SunOS Release: 5.8 5.9

Unbundled Product: Hardware/PROM

Unbundled Release: OBP 4.16.4,POST 4.16.3,OBDIAG 4.16.4

Xref: 

Topic: 

Relevant Architectures: sun blade 1000, sun fire 280r and netra[tm] t20 sun blade 2000

BugId's fixed with this patch: 4375477 4690966 4740629 4777088 4777088 4791537 4824460 4824460 4827590 4827977 4828299 4828367 4829098 4829331 4838922 4841495 4857933 4860081 4860811 4861512 4862646 4864985 4890305 4903517 4909053 4910442 4911947 4919811 4920572 4921913 4921913 4935436 4935436 4946175 4953893 4968020 4976395 4981433 4986210 4992487 4995353 5007053 5009197 5011156 5011167 5016091 5016727 5017013 5018979 5018984 5018986 5019775 5019809 5026180 5027126 5027131 5028307 5034744 5039430 5042760 5046320 5047613 5050594 5052615 5053315 5055623 5058325 5062746 5066168 5066468 5066798 5072976 5074097 5076244 5080134 5080139 5080212 5080225 5080601 5084901 5084905 5094513 5099420 5102715 5103544 5104494 5105537 5110143 6185010 6189110 6201932 6207902 BugIds fixed in patches: previous

Changes incorporated in this version: 

Patches accumulated and obsoleted by this patch: 111292-17

Patches which conflict with this patch: 

Patches required with this patch: 

Obsoleted by: 

Files included with this patch: 

                                flash-update-Blade1000-latest
                                flash-update-Blade1000-old,
                                unix.flash-update.README,
                                unix.flash-update.SunBlade1000.sh,
README.118323-01, copyright, 802-3233-25.ps,

Problem Description:

4375477 Add scan dump information to fatal-reset output
4740629 obp should output an understandable warning when it resets it's cfg to defaults
4827590 OBDiag not called if sync or boot called after XIR and prior to reset.
4828299 Server diagnostic-mode? behaviour contravenes IEEE1275.
4828367 error-reset-recovery should default to 'sync' on servers
4838922 POST called a second time after OBDiag run when obdiag-trigger, post-trigger set
4903517 XIR sometimes gets ROMTrap error
4911947 .version output needs a carriage return
4919811 diag-out-console doesn't work for system fatal reset
4946175 RED State Exception if dimm banks do not match.
4976395 mismatched cpu modules error message is printing incorrect information
4981433 Running obdiag/normal WARNs temperature-sensor@0,9c not found in device tree
4986210 allow Chalupa to support future faster DIMMs
4992487 reduce  BUSY poll duration  for IDE disk in PIO mode data xfer
4995353 "post x min" runs with verbosity of none instead of min
5007053 Incorrect message displayed in OBP during cpu overtemp
5009197 Incorrect printenv results in safe NVRAM mode
5011156 cpu overtemp at obp doesn't get a warning or a shutdown
5011167 diagnostics mode does not override diag-script to normal
5016091 Wrong comment in lomlite.fth, change error message
5016727 boot net fails with AFT CPU 3 UUTS mode
5017013 SeSi asr-disable cpu fails for UltraSPARC-III
5018979 Corrected ECC Error during boot
5018984 The WIH bit in the lsucr should be set
5018986 Add correct MCU settings for 1350 and 1500MHz modules
5019775 FATAL: CPU: mp-get -- MSMP Incongruity ***
5019809 OpenBoot PROM download/jump request failed
5026180 extend catch throw implementation
5027126 Add obp support for Dimm Duct Fan Interposer card for EnWS
5027131 Add obdiag support for Dimm Duct Fan Interposer card for EnWS
5028307 Incorrect supply margin on slot C
5034744 Implement service-mode? configuration variable
5039430 Mask off GPIO3 pin for Taco/Taco+
5042760 Replace lsi1010 fcode with lsi1030 fcode
5046320 Chalupa-19 specific programming of MAX1617 device
5047613 unable to shutdown system when in CDE using front power button with obp 4.10.6
5050594 Booting Solaris after interrupting POST causes panic
5052615 Flash support required for a new centerplane P/N 501-6911
5053315 SunBlade 2500 heading is being truncated
5055623 Implement OBP Diag-on service-mode? and verbosity features into fiesta platforms
5058325 Change Chalupa respose to SC reset to match other Fiesta products
5062746 OBP fails at startup
5066168 Chalupa asr-enable and asr-disable fail from 4.x.build_51 on
5066468 4.x build 59 and build 60 crashes on starcat
5066798 Chalupa has possible race condition when more than 2 CPUs return from POST
5072976 Console printf's skipped in common messaging because of unexpected trap
5074097 "Fast Data Access MMU Miss" after a halt to ok promt and with any keyboarb input
5076244 Misleading response msg to asr-enable cmd when a device is disabled by FWDIAGS
5080134 Dak/Cstone Normal mode messages not printing
5080139 Change dak/Cstone post command to use common CLI and hooks
5080212 In Service Mode, post does not get executed after every second reset
5080225 remove spurrious message *Setting NVRAM parameters to default values* diag mode
5080601 POST does not get triggered every other reset when diag-trigger is all-resets
5084901 Diagon on workstations runs diagnostics by default
5084905 Diagon probing output missing when diag-switch? set true, verbosity < max
5094513 Change EnWS+/Taco+ Banner Names to "Sun Java Workstation Wx500s"
5099420 Add new JP3.x EnXS MB Part Numbers to Unix flash-update utility
5102715 USB keyboard FCode uses endpoint max packet incorrectly
5103544 Remove "diag-out-console" openboot variable name in Taco/Taco+
5104494 Add new Chalupa+ Mb part numbers to Unix flash-update utility
5105537 Performance degradation in V440 jp3.x with SPECcpu2000
5110143 Nvram var diag-script cannot be set to sys-ext for Taco+/EnWS+
6185010 depend files need to be updated
6189110 Change Taco+/EnWS+ obp banner and root names
6201932 FATAL: no exception frames available, forcing misaligned trap on reboot/power-cycles
6207902 stand-init interact breaks boot

Patch Installation Instructions:
===============================
 
Intro
-----
 
    This README is intended for users who wish to upgrade the firmware
    in their Sun Blade 1000, Sun Blade 2000, Sun Fire 280R or Netra[tm] T20 system 
    Flash PROM.  
 
Note:
----
The Solaris System Firmware update utility provides the ability to update the
system firmware from Solaris. This utility is provided as an alternate means of
flash update and may be used in place of the standard utility described in this
README file. In general this utility is a bit faster than the standard update
utility, and because it is a Solaris script, it may be used at the end of an
installation script for users who may be updating the firmware on multiple
systems as part of a large installation.
 
If you choose to update your system firmware using the traditional method,
please follow the instructions in this README file. If you would like to update
your system using the Solaris System Firmware update utility please follow the
instructions detailed in the unix.flash-update.README file.
 
 
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/sbin/prtconf -V
        or
	/usr/platform/sun4u/sbin/prtdiag -v | grep OBP
 
    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-Blade1000-latest" line
 
      Available Firmware Revisions
      ----------------------------
flash-update-Blade1000-latest:
	OBP 4.16.4 2004/12/18 05:18 Sun Fire 280R
	 Sun Fire[TM] V280, Sun Blade[TM] 1000 POST 4.16.3 2004/11/05 20:02 
	OBDIAG 4.16.4 2004/12/18 05:21  
 
flash-update-Blade1000-old:
	OBP 4.13.0 2004/01/19 18:27 Sun Fire 280R
	 Sun Fire[TM] V280, Sun Blade[TM] 1000 POST 4.13.0 2004/03/15 19:13 
	OBDIAG 4.13.0 2004/01/19 18:30  
 
3)  Is the UPGRADE NECESSARY?
 
    If the current Flash PROM revision matches the version numbers given under
    the flash-update-Blade1000-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 latest "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
 
5)  Running the Flash Update Utility
    --------------------------------
 
  a) 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-Blade1000-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.7
                        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
			Sun Blade[tm] 100
			Sun Blade[tm] 1000
			Sun Fire [tm] 280R
			Netra[tm] T20 
 
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.1.2 1996/03/28 17:08         OBP 4.6.7 2002/07/24 15:43            no
POST 3.1.4 1996/04/09 03:23        POST 4.6.2 2002/06/20 12:50           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.1.2 1996/03/28 17:08         OBP 4.6.7 2002/07/24 15:43            YES
POST 3.1.4 1996/04/09 03:23        POST 4.6.2 2002/06/20 12:50           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 ...
 
 
+++++++++++++++++++++ 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-Blade1000-latest entry in Step 2.
 
7)  Resume operations
 
    a) Allow the system to auto-boot, or issue the boot command for your
       environment as necessary.
 
    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.
 
 
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
 
 
Appendix A    Power Interruption During Updating
------------------------------------------------
 
Power Interruption Recovery Scenarios
-------------------------------------
 
If your system has a front panel switch:
 
1. Turn the power switch to the standby position to prevent power surge to
   the system when power is restored.
2. After power is restored to the system location, return the power switch
   to the on position.
 
After power is restored, one of the following two recovery scenarios should
happen on your system. Follow the instructions described for the 
appropriate scenario.
 
Scenario 1 - System Recovers After Power Restoration
----------------------------------------------------
 
If your system attempts to autoboot after power is restored, or if it 
returns to the flash PROM's ok prompt, you must complete the programming
process by rebooting the flash PROM utility.
 
Scenario 2 - System Does Not Recover After Power Restoration
------------------------------------------------------------
 
If your system does not boot or return to the ok prompt after power is
restored:
 
1. If the update was being run via a serial port and the system also has
   a frame buffer and keyboard installed, or if the system has a keyboard
   and more than one frame buffer installed:
 
   a. Connect a monitor to each frame buffer.
 
   b. Confirm that output has been redirected to one of the frame buffers.
 
     - The NVRAM configuration variables "might" have been modified
       because of the firmware update just before power was lost. If this
       happened, then the system output was possibly redirected to a 
       device other than the one originally used to display it. This
       could only have happened if a keyboard was connected to the system.
 
     - If there is no keyboard connected to the system and the NVRAM
       configuration variable are set to their default values, then
       system input and output are directed to serial port A.
 
2. If output cannot be found on any of the installed frame buffers or
   serial port A, set the boot control jumper J2104 to boot from the half
   of the PROM that is not currently selected:
 
   - If the J2104 jumper is set for "high-half booting", pins 1-2, move it
     to "normal booting", pins 2-3.
 
   - If the J2104 jumper is set for "normal booting", pins 2-3  move it to
     "half-high booting", pins 1-2.
 
 
   Reference the Sun Flash PROM Guide (802-3233-25.ps) file for the jumper
   locations.
 
3. Power on the system.
 
     - If the system recovers, complete the updating process by rebooting
       the flash PROM utility.
 
     - If the system does not recover, repeat Step 1 and Step 2 a second
       time.
 
4. If the system still does not recover after you complete Step 1 and Step
   2 a second time, contact your service provider.
 
 
Appendix B Verify/Set the System's Flash PROM Write Enable Jumper
-----------------------------------------------------------------
 
1) Power off the system.
 
** CAUTION **  Do not attempt to access any part of the system hardware
               with the system power still on!
 
2) Remove the system top cover.  (If you are unsure how to do this then
     consult your system "Installation Guide" or "Service Manual".)
 
3) Verify/change the setting of jumper J2103 on pins 2+3.
 
   Jumper J2103 provides a write enable/disable mechanism for the
   Flash PROM.  J2103 normally connects pins 2+3, which causes the
   Flash PROM to be write enabled. By default J2103 is set to pins 2+3
   to write enable the Flash PROM. If for some reason J2103 has been set
   to pins 1+2, thus disabling the Flash PROM update, then you will need
   to move the jumper from pins 1+2 to pins 2+3.
 
   **IMPORTANT NOTE**: If this jumper is NOT set to WRITE ENABLE, the
   Flash update will fail.
 
   Note: consult the enclosed Sun Flash PROM Guide (802-3233-25.ps)
 
4) Replace the system top cover.
 
Note: If you have verified that the Flash PROM jumper J2103 is set to the
      write enabled positon and you still see the message "Could not communicate
      with the Flash PROM on the system board", when the update is run then you
      will need to contact your service provider.

Special Install Instructions:
----------------------------- 
 
  Note:    This patch is NOT for Sun Blade 100.
 
  Note 1: If you have the frame buffer Raptor GFXP -04 REV 50
          (part 370-3753-04), you *must* install patch 110126-03 to upgrade the
          FCode in the card **BEFORE** you can do the firmware update. Revisions          -05 and up of the frame buffer are not affected.
 
          Failure to install the frame buffer patch (110126-03) will cause
          "FATAL" resets after the firmware update.
 
  Note 2: 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.
 
If you have a Sun Blade 2000 with 1050 cpu module(s), do not downgrade
to OBP 4.5.10 or below.
 
   Note 3: There is a known issue with this release that may result in a failed
           boot of the system. The likelihood of encountering this bug has been
           found to be very low.
 
           The error message seen will be one or both of the following:
 
           FATAL: no exception frames available, forcing misaligned trap
           FATAL: no exception frames available, NESTED ERRORs, going interactive
           ok
 
           The system should not hang. The interactive ok prompt will be
           available so that a reset-all can be issued to reset the system.
 
           ok reset-all
 
           The system should now reset and perform the boot sequen
**************************************************************************
**************************************************************************
**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 the firmware included with this patch does NOT
   require any hardware changes if the Flash update completes normally. 
 
*  Appendix A of this README is included as emergency instructions
   which are to be executed ONLY IN THE EVENT OF A POWER INTERRUPTION
   DURING THE UPDATE.
 
*  Appendix B of this README is included as emergency instructions
   which are to be executed ONLY IF THE FOLLOWING MESSAGES ARE DIPSLAYED
   WHEN THE FLASH UPDATE PATCH IS RUN:
 
   Could not communicate with the Flash PROM on the system board.
 
   It is possible that the part is defective, or that the Flash PROM
   is write protected via the hardware 'Write Protect/Enable' jumper.
   Check the setting of the CPU board jumper J2103.
 
**WARNING:****WARNING:****WARNING:****WARNING:****WARNING:****WARNING:**
**************************************************************************
**************************************************************************

README -- Last modified date:  Tuesday, January 25, 2005

