Patch-ID# 119235-01 Keywords: desktop standalone flash prom update Synopsis: Hardware/PROM: Sun Blade 100/150 Flash PROM Update Date: Apr/29/2005 Install Requirements: Additional instructions may be listed below Solaris Release: 8 9 10 SunOS Release: 5.8 5.9 5.10 Unbundled Product: Hardware/PROM Unbundled Release: OBP 4.17.1,OBDIAG 4.17.1,POST_2.0.1 Xref: Topic: Relevant Architectures: sun blade 100 and sun blade 150 BugId's fixed with this patch: 5059929 5062018 5071186 5076244 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: 5062018 5071186 5076244 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 Patches accumulated and obsoleted by this patch: 111179-10 119238-01 Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: flash-update-Blade100-Blade150-latest, flash-update-Blade100-Blade150-old, flash-update-Blade100-Blade150-older, flashprom-jumper-diagram.ps, copyright README.119235-01, 802-3233-20.ps, Problem Description: 5062018 panic or fatal reset during resume 5071186 Serial console doesn't work after reset-all. 5076244 Misleading response msg to asr-enable cmd when a device is disabled by FWDIAGS 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 Patch Installation Instructions: ============================= Intro ----- This README is intended for users who wish to upgrade the firmware in their Sun Blade 100 or Sun Blade 150 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/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-Blade100-Blade150-latest" line Available Firmware Revisions ---------------------------- flash-update-Blade100-Blade150-latest: OBP 4.17.1 2005/04/11 14:31 Sun (Grover) POST 2.0.1 05:13 PM on 08/23/01 OBDIAG 4.17.1 2005/04/11 14:36 flash-update-Blade100-Blade150-old: OBP 4.16.2 2004/10/04 18:21 Sun (Grover) POST 2.0.1 05:13 PM on 08/23/01 OBDIAG 4.16.2 2004/10/04 18:23 flash-update-Blade100-Blade150-older: OBP 4.15.7 2005/03/24 12:29 Sun (Grover) POST 2.0.1 05:13 PM on 08/23/01 OBDIAG 4.15.7 2005/03/24 12:32 3) Is the UPGRADE NECESSARY? If the current Flash PROM revision matches the version numbers given under the flash-update-Blade100-Blade150-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) Power off the system. ** CAUTION ** Do not attempt to access any part of the system hardware with the system power still on! d) Remove the system top cover. (If you are unsure how to do this then consult your system "Installation Guide" or "Service Manual".) Note: consult the enclosed flashprom-jumper-diagram.ps e) Set JP2 to write enable at 2+3. Default is write protect at 1+2 Jumper JP2 provides a write enable/disable mechanism for the Flash PROM. JP2 normally connects pins 1+2, which causes the Flash PROM to be write protected. To enable patch installation, write enable the Flash PROM by MOVING the JP2 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. (If you have any difficulties consult the flashprom-jumper-diagram.ps file). f) Replace the system top cover. 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-Blade100-Blade150-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.6 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) 150 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 3.1.5 1996/08/27 16:13 no POST 3.1.4 1996/04/09 03:23 POST 3.1.5 1996/06/28 11:54 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 3.1.5 1996/08/27 16:13 YES POST 3.1.4 1996/04/09 03:23 POST 3.1.5 1996/06/28 11:54 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-Blade100-Blade150-latest entry in Step 2. 7) Restoring the system The system should be restored to the original set-up as follows: a) Turn the power to the system off. b) Remove the top cover and move jumper JP2 to pins 1+2. c) Replace the top cover. 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) Turn on the system power 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: ----------------------------- Note 1: 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. Failure to install the frame buffer patch (110126-03) will cause a "FATAL" reset after the firmware update. Note 2: 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. Note 3: 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 THIS PATCH REQUIRES A HARDWARE JUMPER 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". Note, however, that The Flash PROM 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. Reference the flashprom-jumper-diagram.ps file, which provides; (i) A board-level diagram that gives the approximate location of the hardware jumpers (that will need to be changed). (ii) Emergency instructions in the unlikely event that the Flash update should fail. ** WARNING ** WARNING ** WARNING ** WARNING ** WARNING ** WARNING ** README -- Last modified date: Thursday, June 16, 2005