Patch-ID# 113034-15
Keywords: sun fire v480
Synopsis: Hardware/PROM: Sun Fire V480  Flash PROM Update
Date: Aug/31/2004


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

SunOS Release: 5.8 5.9

Unbundled Product: Hardware/PROM
NOTE: 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: 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.
    * * * * * * * * * * * * * * * * * * * * * * * * 
    *   NOTICE     NOTICE     NOTICE     NOTICE   * 
    *                                             * 
    *   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.
    NOTE: 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 ).

Unbundled Release: OBP_4.15.1,POST_4.15.0,OBDIAG_4.15.1

Xref: 

Topic: 

Relevant Architectures: sun fire v480

BugId's fixed with this patch: 5052771
NOTE:
BugIds fixed in previous patches: 
4.15.0
------
4375477 4903517 4992487 4995353 5007053 5009197 5011156 5011167 5016091 5016727 
5017013 5018979 5018984 5018986 5019775 5028307 5034744 5050594 5052615
4.13.6
------
4919811
4.13.2
------
5005756, 5018979
4.13.0
------
4829098, 4841495, 4857933, 4861512, 4861585, 4862582, 4862646, 4905997, 4947707, 4951700,
4864627, 4875275, 4876043, 4724733, 4829331, 4739073, 4834606, 4872447, 4885091, 4897231,
4902057, 4910442, 4912942, 4920572, 4941032, 4953893, 4954490, 4968020, 4864985, 4890305,
4791537, 4859625, 4878664, 4892741, 4903516, 4864334, 4914247, 4928813, 4929800, 4930224,
4930316, 4935825, 4942884, 4962825, 4964516, 4993156, 4855479
4.10.14
-------
4941032, 4872447, 4855479, 4864334, 4905997, 4929800
4.10.8
------
4892741
4.10.7
------
4746347, 4669869, 4712653, 4712670, 4712730, 4714724, 4875279, 4841493, 4772534
4714758, 4714777, 4714815, 4714840, 4715464, 4716236, 4723631, 4746975, 4763785,
4709109, 4739131, 4780442, 4798141, 4799710, 4802697, 4804673, 4806596, 4812128,
4841836, 4841495, 4862582, 4862646, 4875275
4.7.5
-----
4738302, 4794880, 4799710, 4797107
4.7.2
-----
4669869, 4712653, 4712670, 4712730, 4714724, 4714758, 4714777, 4714815, 4714840,
4716236, 4723631, 4738302, 4746975, 4780442, 4778877, 4739131, 4709109, 4772510,
4715464, 4708545
4.7.0
-----
4374776, 4531763, 4638478, 4627222, 4694052, 4708450, 4680238, 4717392, 4739975, 4707084,
4714617, 4753059, 4638132, 4717197, 4729996, 4769102, 4680725, 4680727, 4692532
4.6.8
-----
4739975
4.6.7
-----
4718514
4.6.4
-----
4458939, 4548849, 4510175, 4510187, 4510190, 4510193, 4510201, 4510210, 4510253, 4633110,
4633121, 4634453, 4637452, 4531763, 4640481, 4647522, 4649679, 4649681, 4651097, 4651300,
4660215, 4658179, 4673710, 4678087, 4679282, 4680725, 4680727, 4692532, 4401839, 4519545,
4618714, 4437441, 4618641, 4465159, 4465165, 4465752, 4465780, 4465817, 4465906, 4509642,
4631546, 4465736, 4616733, 4619706, 4660720, 4677356, 4458995, 4503153, 4517140, 4524793, 
4461253, 4526771, 4522404, 4528335, 4546596, 4529777, 4532261, 4466040, 4618633, 4620265,
4621997, 4533255, 4632351, 4636885, 4690089, 4523685, 4515832, 4617168, 4531883, 4621189, 
4631950, 4622592, 4510826, 4511292, 4617083, 4669037

Changes incorporated in this version: 

Patches accumulated and obsoleted by this patch: 

Patches which conflict with this patch: 

Patches required with this patch: 

Obsoleted by: 

Files included with this patch: 

				817-6957-10.pdf, flash-update-SunFire480-13,
				README.113034-15, 802-3233-25.ps,
				copyright, unix.flash-update.SunFire480.sh,
				unix.flash-update.README
flash-update-SunFire480-latest, 

Problem Description:

BugID		Synopsis
-----   	--------
4.15.1
------
5052771         SC bootmode diag does not override diag-level=off on SFV880
 
4.15.0
------
4375477         Add scan dump information to fatal-reset output
4903517         XIR sometimes gets ROMTrap error
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 ***
5028307         Incorrect supply margin on slot C
5034744         Implement service-mode? configuration variable
5050594         Booting Solaris after interrupting POST causes panic
5052615         Flash support required for a new centerplane P/N 501-6911
 
4.13.6
------
4919811         diag-out-console doesn't work for system fatal reset.
 
4.13.2
------
5005756         OBP fan monitoring: wrong printouts and LEDs
5018979         Corrected ECC Error during boot
 
4.13.0
------
4829098         corrupt nvram is not reported, crc is silently re-written
4841495         local-mac-address properties not created correctly in net devices.
4857933         checksum library Makefile missing dependency and rule for sparcv9 target dir
4861512         pcf8584 i2c probing code needs to retry.
4861585         ASR keylist should include onboard PCI devices.
4862582         Fast ECC scrubber scrubs wrong ECache line
4862646         USB keyboard FCode should not assume interface number
4864627         OPS need rmc-log node to clear rmc.
4875275         Misleading error msg on 480/880 systems w/no rsc installed
4876043         remove bogus rmc-log node
4724733         Get DPM POST status word w/out rebooting and setting OBP parameters
4829331         Running OBDiag with disg-script = 'none' causes an extra reset
4739073         fcode-debug? has no effect on earliest probed devices
4834606         make depend under obp/dev/scsi/adapters/lsi1030 fails
4872447         asr-disable cpux-banky doesn't work on a single bank
4885091         Spurious fan tray "too slow or not present" shutdown
4897231         OBP downgrade to 4.7.5 causes 20 minute hang during reset
4902057         V880 FC backplane may not set sel_id bits 4-6 to definite logic 0
4910442         POST output fails to be directed to RSC
4912942         Typo in error message.
4920572         support explicit nvram partitions
4941032         Centerplane P/N change in the works for Cstone
4953893         New Motherboard and Centerplane Partnumbers will cause Flash-update to fail.
4954490         asr-disable or asr-enable causes a fatal reset
4968020         use-nvramrc? changed to false after setting to true and reset
4864985         do faster mapping using on-demand generation of translations and forth assembler
4890305         Clean up nits in the common workspace
4791537         after hitting breakpoint obp will not proceed further with 'step' or 'go'
4859625         Implement FWARC 2003/258.
4878664         Jaguar POST code improvements: recovery/jtag scan/cleanup
4892741         POST 4.10.7 fails D-Cache TAG tests
4903516         Jaguar post aft_cpu script causes watchdog reset
4864334         POST fails if diag-level=max with 512MB DIMMs installed in CPUs other than 1st
4928813         V880 masest memory test false failures when called from menus
4929800         Need Enhanced PCI Integrity test
4930224         E$ ECC failures during se/si post report the incorrect net
4930316         Enable diagnostics as a default for VSP servers.
4935825         Dump scan chain after fatal reset
4942884         POST directory structure updates and code cleanup
4962825         New scanid required for ch++ rev 1.2 mask
4964516         Dissable CASSINI PCI INTEGRITY TEST on 5819 & 6733 Boards
4993156         POST banners pre-announce V890 and V490 platforms
4855479         The wrong LED is illuminated when POST detects a CE
4905997         Need JTAG id add to POST for Maverick.
4947707         New POST needed for IDE Daktari IOboard.
4951700		SENV init failed
4914247		After 1st fatal error jtag scan data chain not cleared masking further errors
 
4.10.14
-------
4941032         Centerplane P/N change in the works for Cstone
4872447         asr-disable cpux-banky doesn't work on a single bank
4864334         POST fails if diag-level=max with 512MB DIMMs installed in CPUs 
other than 1st
4929800         Need Enhanced PCI test
4855479         The wrong LED is illuminated when POST detects a CE
4905997         Need JTAG id add to POST for Maverick.
 
4.10.8
------
4892741 	POST 4.10.7 fails D-Cache TAG tests
 
4.10.7
------
4772534         improved Red State handling (RTI 2481) to offline a recalcitrant CPU
4841493         Change 900 MHz ECache timing to 4-3-3
4841495         local-mac-address properties not created correctly in net devices.
4862582         Fast ECC scrubber scrubs wrong ECache line
4862646         USB keyboard FCode should not assume interface number
4875275         Misleading error msg on 480/880 systems w/no rsc installed
4875279         4.10.1 hangs at POR
4746347         help command doesn't work with category-name beginning with capital
letter.
4669869         POST does not always use the same nubering scheme for memory locations
4712653         (C1_M_DATA2) POST 4.6.4 is unable to correctly identify & isolate to
failing DIM
4712670         (C1_MEMADR_EVN2) POST 4.6.4 is unable to correctly identify & isolate
to failing
4712730         (C1_MEMADR_ODD2) POST 4.6.4 is unable to correctly identify & isolate
to failing
4714724         S_PAUSEOUT_L/A_ATRANSID_L0: POST directs FATAL output to ttya, not
console-out
4714758         (C1A_CSEL0) POST identifies Dimm J79000 as failing component, instead
of CPU/Mem
4714777         (C1A_SSEL0) System unable to recover from hang during POST after failing
FRU
4714815         (S_DATA_L0) System is unable to recover as POST hangs during execution
4714840         (C1A_MSEL0) POST 4.6.4 is unable to correctly identify & isolate to FRU
4715464         (C1_P_DATA_L0) POST 4.6.4 fails to identify failing component properly
& hangs
4716236         (SCH01_ATRANSID_L0) POST 4.6.4 is unable to report, record, or recover
from fail
4723631         (SCH01_INCOMING_L) Post hangs and is unable to report, recordor
4746975         POST error messaging indicating failing component(s) is misleading
4763785         Running masest memory test cheetah+ modules fail incorrectly but
cheetah's don't
4709109         Missing space in warning message
4739131         Increase makedi's maximum dropin size
4780442         POST JTAG ID does not support Cassini+ cost-reduced.
4799710         E$ timing change for 1050/1200 MHz Ch++
4798141         memory-layout properties missing on "end" CPUs
4799710         E$ timing change for 1050/1200 MHz Ch++
4802697         POST fails when diag-level=max with a specific memory configuration.
4804673         POST fails if diag-level=max with 512MB DIMMS installed in CPUs other
than 1st
4806596         POST has wrong JTAG ID for MAVERIC DCSC replacement
4812128         OPS BFT test station failing when freq margined to 100 Mhz.
4841836         POST 4.7.5 and 4.7.6 may failsData Cache tags tests.
 
4.7.5
-----
4738302         POST FPU tests do not pick up SunVTS FPU errors of basic walking of
ones through
4794880         cpu should not have clock-divisor property.
4799710         E$ timing change for 1050/1200 MHz Ch++
4797107         see FPU BLOCK REG TEST in POST with "Address does not match in free call:" msg.
 
4.7.2
-----
4669869         POST does not always use the same nubering scheme for memory locations
4712653         (C1_M_DATA2) POST 4.6.4 is unable to correctly identify & isolate to failing DIM
4712670         (C1_MEMADR_EVN2) POST 4.6.4 is unable to correctly identify & isolate to failing
4712730         (C1_MEMADR_ODD2) POST 4.6.4 is unable to correctly identify & isolate to failing
4714724         S_PAUSEOUT_L/A_ATRANSID_L0: POST directs FATAL output to ttya, not console-out
4714758         (C1A_CSEL0) POST identifies Dimm J79000 as failing component, instead of CPU/Mem
4714777         (C1A_SSEL0) System unable to recover from hang during POST after failing FRU is
4714815         (S_DATA_L0) System is unable to recover as POST hangs during execution
4714840         (C1A_MSEL0) POST 4.6.4 is unable to correctly identify & isolate to FRU
4715464         (C1_P_DATA_L0) POST 4.6.4 fails to identify failing component properly & hangs d
4716236         (SCH01_ATRANSID_L0) POST 4.6.4 is unable to report, record, or recover from fail
4723631         (SCH01_INCOMING_L) Post hangs and is unable to report, record, or
4738302         POST FPU tests do not pick up SunVTS FPU errors of basic walking of ones through
4746975         POST error messaging indicating failing component(s) is misleading
4780442         POST JTAG ID does not support Cassini+ cost-reduced.
4778877         errors in code to fetch mac-address from bsc
4739131         Increase makedi's maximum dropin size
4709109         Missing space in warning message
4772510         Config file not included in isa.tok
4708545         Cannot drop to OBP after 64 L1-A to OBP and "go" cycles
 
4.7.0
-----
4374776         physical address range must be contiguous within a board
4531763         banner and ok prompt disappear to unresposive or removed RSC
4638478         Change tNVRAM layout for memory bank configuration
4627222         OBP hangs without producing any output.
4694052         POST does not support cheetah++
4708450         DR on CPU with bad fruproms hangs during ecache probe
4680238         Zulu environmental support
4717392         ttya interrupts broken.
4739975         Intermittent 'Data Access Error' during gigabit PHY loopback test
4707084         Watchpoint support broken for physical addresses
4714617         DPM diagnostic commands fail when executing LIPs in rapid succession
4753059         qlc device uses WWN of all zero's in LISM frames during OBDIAG selftest
4638132         Intermittent Abnormal POST reset during motherboard diag-script
4717197         New JTAG ID for DCDS (Maverick), Ele, Schizo 2.5
4729996         PCI_D_ADO:System unrecoverable and fault LED not illuminated
4769102         Incorrect OBP version field
4680725         System fails to boot after a watchdog/XIR when error-reset-recovery set to boot
4680727         System fails to boot after a watchdog/XIR when error-reset-recovery set to sync
4692532         Fatal configuration error occurs after mtst fault injector program is executed
 
4.6.8
-----
4739975		Intermittent 'Data Access Error' during gigabit PHY loopback test
 
4.6.7
-----
4718514		init interrupt state back to idle on safari platforms.
 
4.6.4
-----
4458939		Make 'diag-trigger' obsolete, replace with 'obdiag-trigger' and 'post-trigger'
4548849		Memory Referesh timming fo 512M and 1G DIMMS is wrong
4510175		(S_PAUSEOUT_L) Fatal reset from post is invoked, fails to detect failing FRU. TP
4510187		(C1_SFRI_RST_LO) Fault injected continuously resets the system
4510190		(C1_SFRI_RST_LO) Fault injected  not reported to enclosure LED
4510193		(C1A_CSEL0) Fault injected  caused to system to enter debug
4510201		(C1A_SSELO) Fault injected on the Safari bus, signal  causes to go into debug mo
4510210		(S_DATA_LO) After a fatal reset post fails to detect the failing FRU. TP S_DATA_
4510253		(C1A_MSELO) A fault injected on the Safari bus, DCDS , bails to debug
4633110		Cassini(+) OBP FCode runs into Rx Tag Errors.
4633121		Cassini(+) OBP FCode runs into a single Rx Tag Error just after link up.
4634453		GMII mode needs to be set for internal loopback test in the Cassini(+) FCode
4637452		POST reports MDR instead of CDX and centerplan instead of centerplane
4531763		banner and ok prompt disappear to unresposive or removed RSC
4640481		Cassini cannot transmit during boot net at 1000 HDX.
4647522		Cassini(+) FCode's error message at 1000Mbps link down--mention of link master.
4649679		Add code to support common msg framework, FWARC case 2000/131
4649681		LED support for diagnostics and the env-mon
4651097		May have to power-cycle after incompatible OpenBoot image downloaded
4651300		diag-console command cannot be set to 'rsc'
4660215		Dak/Cstone env monitor incorrectly displays negative values.
4658179		Cassini selftest fails if diag-level is an unsupported value
4673710		General fault LED not lit for obdiag normal script faults.
4678087		OBP 4.6.0 env. monitor reports the wrong PCI fan failure in P2 Cherrystones
4679282		Env mon 'unknown' power supply fault message is causing confusion among users.
4680725		System fails to boot after a watchdog/XIR when error-reset-recovery set to boot
4680727		System fails to boot after a watchdog/XIR when error-reset-recovery set to sync
4692532		Fatal configuration error occurs after mtst fault injector program is executed
4401839		SETENV command should show possible keyword values for NVRAM parameters
4519545		w/ keyswitch in locked position flashupdate should gives misleading error msg
4618714		Get a "RIO-USB control register" error
4437441		Node Name and Port Name should be different on Crystal+
4618641		Hanging I2C SEG5 bus causes OBP to set diag-level to JTAG_INIT
4465159		(generic) Provide a summary of any commponents that are removed due to failure
4465165		(Generic) Provide a alternate location for all error messages during POST
4465752		(SCH01_ATRANSID_L0) messages do not identify the correct FRU
4465780		(SCH01_INCOMING_L) unable to identify the failing component
4465817		(SCH1_DTRANSID_L0) Error messages do not help determine failure
4465906		(I2C_SEG5_SCL_SSC) Message presented is unclear or inaccurate
4509642		(C1_ECDATA_0) POST drops to debug when a fault is detected on C1_ECDATA_0
4631546		ELE is not properly initialized by OBP, DMA doesn't work.
4465736		(A_ATRANSID_L0) Error messages do not help isolate failing FRU
4616733		Grounding I2C_SEG5_CLK or I2C_SEG5_DATA, causes OBP to set incorrect ECCR values
4619706		FIT: Grounding the JTAG signals of the switch chip ring, causes hangs in obp
4660720		OBP wants to suppress output during JTAG POST
4677356		Hardware specific failure: test SBa: Board initialization failed
4458995		qlc: Incorrect Node WWN returned in device tree (actually the Port WWN)
4503153		Optimize the implementation of vocabulary based config. variables
4517140		'make depend' not working: unneeded dependency
4524793		Update Ultrasparc-III+ 1050 Mhz cfg file
4461253		ISP2200 selftest accesses reserved register space (legacy code from ISP2100)
4526771		Certain bad disks can cause FC-AL test to hang when read is attempted.
4522404		need to improve setenv/ptintenv interface for flag types of conf. vars.
4528335		error-reset-sync-or-boot get broken by the changes in voc. based conf. variables
4546596		xir reset code error
4529777		In silent mode, Elapsed time can become unclear
4532261		Reorganize i2c test to only fload needed device subtests
4466040		Need to verify cases when methods are defined multiple times in obdiag
4618633		base backplane: empty loop test fails after probe-scsi
4620265		any selftest using i2c bus needs to be tolerent of multiple instances using bus
4621997		Improve obdiag menu tool to accept multiple commands on single line
4533255		Boot time WARNING: invalid vector intr: number 0x7de, pil 0x0 (OBP fix)
4632351		init interrupt state to pending on safari platforms 
4636885		IDE selftest restructuring to support the southbridge IDE controller
4690089		OBP may clear some memory that is not on the available list
4523685		prefetch bit in pci bars not reflected in regs property
4515832		glm FCode does not implement scsi-reset-delay
4617168		Remove 'version' command from menutool; 'selftest-version' from device selftests
4531883		maxwait needed for isp2200 FCode
4621189		lsi1010 and friends (glm fcode) uses wrong value for selection timeout
4631950		auto gen of depend.mk needs copyright updated
4622592		first device tested fails obdiag when 'diag-script' is set to 'all'
4510826		(SCH01_INCOMING_L) POST does not identify the centerplane as the faulty FRU. TP
4511292		(C1_P_DATA_L0) Fatal reset post fails to detect failing FRU, bails to debug mode
4617083		POST should refer to Schizo as IO-Bridge
4669037		run higher bus traffic tests in thrasher

Patch Installation Instructions:
===============================
 
 
Intro
-----
 
    This README is intended for users who wish to upgrade the firmware
    in their Sun Fire V480.  
 
 
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-SunFire480-latest" line
 
      Available Firmware Revisions
      ----------------------------
 
-LATEST flash-update-SunFire480-latest
	OBP 4.15.1 2004/06/02 16:06 Sun Fire 4XX
        POST 4.15.0 2004/05/27 13:25
 
-13 flash-update-SunFire480-13
        OBP 4.13.6 2004/06/22 13:25 Sun Fire 480R
        POST 4.13.0 2004/02/12 19:17
 
3)  Is the UPGRADE NECESSARY?
 
    If the current Flash PROM revision matches the version numbers given under
    the flash-update-SunFire480-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 J1104 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-SunFire480-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.8
                        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
                        Sun Fire (tm) V480R
                        Sun Fire (tm) V880
                        Netra(tm) T4
 
 
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.4 2002/05/31 05:00          no
POST 4.5.6 2002/01/04 15:54         POST 4.6.2 2002/05/21 10:27          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.4 2002/05/31 05:00         YES 
POST 4.5.6 2002/01/04 15:54         POST 4.6.2 2002/05/21 10:27         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-SunFire480-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:
----------------------------- 
 
**************************************************************************
**************************************************************************
**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:  Monday, October 18, 2004

