How to update CIXCD firmware.



Updating AS8400

===============



The CIXCD firmware is built into a MOP loadable image that can be loaded with

the LFU (Loadable Firmware Update Utility). The following example accesses the

firmware through the network. Customize the CIXCD device name and the network

device name to match your configuration.



	P00>>>sho net

	polling for units on demna0, slot 1, bus 0, xmi0...

	exa0.0.0.1.6       08-00-2B-23-45-92

	P00>>>LFU



	          ***** Loadable Firmware Update Utility *****



		...



	UPD>update cixcd0 -path mopdl:cixcdg27/exa0



To load from the CDROM use the following "update" command customized for your

configuration. Note that this method was broken on the V5.6 CD. Following is an

example:



	P00>>>ls iso9660:[cixcd]*/dkh500

	iso9660:[CIXCD]CIXCD027.SYS/dkh500.5.0.11.1

	iso9660:[CIXCD]CIXCDD27.SYS/dkh500.5.0.11.1

	iso9660:[CIXCD]CIXCDG27.SYS/dkh500.5.0.11.1

	iso9660:[CIXCD]CIXCDV49.BIN/dkh500.5.0.11.1

	iso9660:[CIXCD]CIXCDV49.SYS/dkh500.5.0.11.1

	iso9660:[CIXCD]CIXCDV69.BIN/dkh500.5.0.11.1

	iso9660:[CIXCD]CIXCDV69.SYS/dkh500.5.0.11.1

	iso9660:[CIXCD]READ_ME_FIRST.TXT/dkh500.5.0.11.1

	iso9660:[CIXCD]UPDATING_FIRMWARE.TXT/dkh500.5.0.11.1

	P00>>>lfu



	          ***** Loadable Firmware Update Utility *****



	Select firmware load device (cda0, dva0, ewa0), or

	Press <return> to bypass loading and proceed to LFU: 



	---------------------------------------------------------------------

	 Function    Description

	---------------------------------------------------------------------

	 Display     Displays the system's configuration table.

	 Exit        Done exit LFU (reset).

	 List        Lists the device, revision, firmware name, and update ...

	 Lfu         Restarts LFU.

	 Modify      Modifies port parameters and device attributes.

	 Readme      Lists important release information.

	 Create      Make a custom Console Grom Image.

	 Update      Replaces current firmware with loadable data image.

	 Verify      Compares loadable and hardware images.

	 ? or Help   Scrolls this function table.



	---------------------------------------------------------------------

	Console ARC firmware ARCROM not found

	Console firmware kn7cc_fw not found



	UPD> up cixcd0 -path iso9660:[CIXCD]CIXCD027.SYS/dkh500

	WARNING: updates may take several minutes to complete for each device.

	cixcd0          Updating to 27...  Verifying 27...  PASSED.



	UPD> exit







Updating DEC7000/DEC10000 and VAX7000/VAX10000

==============================================



The CIXCD firmware is built into a bootable LFU image. The image that contains

the console also contains the normal version of the CIXCD firmware. Special

versions of the CIXCD firmware are built into an LFU images that will only load

the CIXCD firmware. 



To load the LFU image over the network use the command:



	P00>>>boot exa0 -file cixcdd27	(for DEC7000)

	P00>>>boot exa0 -file cixcdv69	(for VAX7000)





Updating VAX6000 and VAX9000

============================



The VAX6000 and VAX9000 are updated by the VDS(VAX Diagnostic Supervisor).

Before starting the update procedure, the new firmware files (CIXCDV69.BIN or

CIXCDV49.BIN) must be copied to the [SYS0.SYSMAINT] directory so that it will

be conviently available to VDS. After VDS is booted the CIXCD must be attached

and selected. before the update diagnostic EVGEA or EVGEB can be run to update

the firmware. The arguments for the ATTACH command are type, bus, name, bus

slot and CI node. The following example demonstates the procedure:



    DS> ATTACH CIXCD HUB PAA0 C 5

    DS> SELECT PAA0

    DS> RUN EVGEA/SECTION=UPDATE

                ...

    input the CIXCD BINARY filename to use (default= CIXCD.BIN]: CIXCD_V69.BIN

                ...

    DS>



Setting up to for network updates using MOP

===========================================



The MOP network protocol is the primary method used to load firmware on

platforms that use the LFU utility to update firmware. Another system will be

used to serve as the MOP server. The subject firmware should be copied into the

"MOM$SYSTEM:" directory. Make sure MOP serving is enabled on your system either

using NCP or LANACP. 



It is important that the file attributes are not corrupted when you move the

file to the "MOM$SYSTEM:" directory. If the CD is loaded in a PC then use FTP

in binary mode to move the file. If the CD is mounted on the VMS system then

access the files as follows:



	$ mount/media=cd/over=id $1$dka500



regardless of the method used to copy the file, it should end up with the

attributes of:  

	record format = Fixed length 512 byte records

	Record attributes:  None