Hardware/PROM: Sun Fire V880 / V890 Flash PROM Update |
Status: RELEASED
Patch Id: 119231-01
Summary: Hardware/PROM: Sun Fire V880 / V890 Flash PROM Update
Date: Apr/29/2005
Installation Requirements:
Additional instructions may be listed below
Solaris Release: 8 9 10
Sun OS Release: 5.8 5.9 5.10
Unbundled Product: Hardware/PROM
Unbundled Release: OBP 4.17.1,POST 4.17.1,OBDIAG 4.17.1
Xref:
Topic:
Relevant Architecture: sun fire v880 / v890
BugId's fixed with this patch:
4740629 4827590 4828299 4828367 4838922 4911947 5026180 5042760 5046320 5055623 5058325 5059929 5062018 5062746 5066168 5066468 5066798 5071186 5072976 5074097 5076244 5080134 5080139 5080212 5080225 5080601 5084901 5084905 5094513 5099420 5102714 5102715 5103544 5103833 5104494 5105537 5106365 5110143 6180585 6185010 6189110 6191222 6198247 6201932 6206112 6207902 6216781 6217930 6220285 6220303 6231224 6235884 6246407 6246421 6247508 6247511
Changes incorporated in this version:
6216781 6217930 6220285 6220303
6231224 6235884 6246407 6246421
6247508 6247511
Patches accumulated and obsoleted by this patch:
112186-19
Patches which conflict with this patch:
Required Patches:
Obsoleted by:
Files Included in this Patch:
817-6957-10.pdf, unix.flash-update.README,
flash-update-SunFire880-latest
flash-update-SunFire880-old,
unix.flash-update.SunFire880.sh,
README.119231-01, copyright, 802-3233-25.ps,Problem Description:
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
4911947 .version output needs a carriage return
5026180 extend catch throw implementation
5042760 Replace lsi1010 fcode with lsi1030 fcode
5046320 Chalupa-19 specific programming of MAX1617 device
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
5062018 panic or fatal reset during resume
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
5071186 Serial console doesn't work after reset-all.
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
5102714 OBP .version command leaves 2 items on stack
5102715 USB keyboard FCode uses endpoint max packet incorrectly
5103544 Remove "diag-out-console" openboot variable name in Taco/Taco+
5103833 OBDiag revisions are reported incorrectly by .version command
5104494 Add new Chalupa+ Mb part numbers to Unix flash-update utility
5105537 Performance degradation in V440 jp3.x with SPECcpu2000
5106365 network download performance on ce is slow
5110143 Nvram var diag-script cannot be set to sys-ext for Taco+/EnWS+
6180585 .SILENT in makefile is messed up
6185010 depend files need to be updated
6189110 Change Taco+/EnWS+ obp banner and root names
6191222 Change Taco+/EnWS+ obp root and banner names
6198247 Add retrofit JP2.x EnXS MB Part Numbers to Unix flash-update tool
6201932 FATAL: no exception frames available, forcing misaligned trap on reboot/power-cycles
6206112 obp 4.16.1 fails DVD test without DVD is installed
6207902 stand-init interact breaks boot
6216781 Failed boot with Missing cmn-xxx[ error and Out of memory then FATAL: no exception frames available
6217930 V240 - FATAL: no exception frames available, forcing misaligned trap
6220285 Enws Enws_plus Taco Taco_Plus Banner Copyright need to be updated to year 2005 on 4.17.0_b6
6220303 ENWS banner included "Sun Fire V250" that need to be removed.
6231224 system hang up when enter ":c" to leave kadb prompt and get back into UNIX mode.
6235884 "NESTED ERRORs, going interactive forcing misaligned trap" seen after probing devices
6246407 TFTP boot on WANboot capable proms hangs if duplicate TFTP data blocks are received
6246421 Limit number of TFTP timeout messages during boot
6247508 system-tick-speed and the alarm interval need to be updated to correct value
6247511 support reentrancy in the memory list management
Revision History:
Patch Installation Instructions:
===============================
Intro
-----
This README is intended for users who wish to upgrade the firmware
in their Sun Fire V880 / V890.
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-SunFire880-latest" line
Available Firmware Revisions
----------------------------
flash-update-SunFire880-latest:
OBP 4.17.1 2005/04/11 14:28 Sun Fire 8XX
Sun Fire[TM] V880/V890 POST 4.17.1 2005/04/11 14:36
OBDIAG 4.17.1 2005/04/11 14:35
flash-update-SunFire880-old:
OBP 4.15.6 2005/01/06 04:25 Sun Fire 8XX
Sun Fire[TM] V880/V890 POST 4.15.6 2005/01/06 10:46
OBDIAG 4.15.6 2005/01/06 04:30
3) Is the UPGRADE NECESSARY?
If the current Flash PROM revision matches the version numbers given under
the flash-update-SunFire880-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
c) Jumper J3003 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) Power on 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 interrupted 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-SunFire880-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) T4
Sun Fire (tm) V880
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 4.5.6 2002/01/04 12:30 OBP 4.6.3 2002/05/28 09:09 no
POST 4.5.6 2002/01/04 15:54 POST 4.6.2 2002/05/21 10:41 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 4.5.6 2002/01/04 12:30 OBP 4.6.3 2002/05/28 09:09 YES
POST 4.5.6 2002/01/04 15:54 POST 4.6.2 2002/05/21 10:41 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-SunFire880-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.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-Special Install Instructions:
-----------------------------
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.
NOTE 3: If you are upgrading your system from 4.2.X you will need to
modify the NVRAM variable, diag-script. OBP version 4.4.7
introduced a change in the underlying keyvalue assigned to
the script keywords which will result in the value of
diag-script being changed. After the firmware upgrade, but
prior to booting, please execute the following at the "ok"
prompt:
ok setenv diag-script normal
ok reset-all
This ensures that the system will run the "normal" set of
diagnostic scripts on all subsequent system resets.
NOTE 4: Modifications to Diagnostic Operation
This released version of OpenBoot enables diagnostic execution for all
power-on and error reset events, **as the new system default.
**To implement this new policy, behavioral changes to diagnostic
controls were made to simplify the enabling of diagnostics and
controlling the level and verbosity of diagnostics.
A new feature includes a Sun-prescribed mode of diagnostic execution,
which overrides user-defined settings. This mode provides service
personnel with an easy method by which to invoke a predictable
execution of diagnostics.
The new standard (default) configuration will increase system boot
time ( measured from power-on to the 'ok>' prompt ) and messaging
( varies by system configuration ) for all 'power-on-reset' and OBP
detected 'error-reset' events. Increased boot time and messaging is
largely due to the execution of diagnostics.
Automated System Recovery (ASR), a form of restoration, is implemented
at the firmware layer and increases overall system availability when
diagnostics are enabled.
For more specific details regarding these OBP changes, reference the
pdf document; "OpenBoot[tm] PROM Enhancements for Diagnostic
Operation", included within this patch ( part 817-6957, July 2004 ).
NOTE 5: WANboot Documentation
Instructions for installing systems over a WAN is provided in
Chapters 41-46 of the "Solaris 9 9/04 Installation Guide" from the
"Solaris 9 9/04 Release and Installation Collection". This document
is accessible at:
http://docs.sun.com/db/doc/817-5768
The quick link to the WANboot specific documentation is:
http://docs.sun.com/db/doc/817-5768/6ml70g5vj?a=view
The list of arguments processed by the WAN boot capable network boot
support package is provided in the boot(1M) man page in the "man
pages section 1M: System Administration Commands" section of the
"Solaris 9 9/04 Reference Manual Collection".
A quick link to this man page is:
http://docs.sun.com/db/doc/817-3937/6mjgeafkc?a=view
Security keys used for WANboot can be installed using the
"set-security-key" command at the OBP's command prompt. Description
of usage is provided in the monitor(1M) man page in the "man pages
Section 1M: System Administration Commands" section of the (Solaris 9
09/04 Reference Manual Collection)
A quick link to the monitor(1M) man page is:
http://docs.sun.com/db/doc/817-3937/6mjgeafu2?a=view
** 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.
* 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 **
README -- Last modified date: Thursday, June 16, 2005
Sun Contracted Content
Sun Contracted Feature
