CSM Software and Diagnostic Executive V1.6.1 Release Notes: Updating PROMs in Replacement CSM Boards


Appendix A
Updating PROMs in Replacement CSM Boards

Use this procedure when a replacement CSM board has been installed and the version of Level-A firmware in the PROMs either is unknown or is an earlier version than the current Level-B software.

  1. Verify that updating is needed.

    Display the system configuration by entering the config command at the Level-B prompt (--->). The configuration entry for the CSM board shows two version numbers: Aver (firmware in PROMs) and Bver (software on disk). If Aver shows a version earlier than Bver, you must update the flash PROMs.

    Before proceeding, write down any custom NVRAM data (boot string settings, etc.) Beginning with CSM SW V1.5, the firmware checks a format revision number in NVRAM. If that number does not match the number for the firmware level being installed, the firmware overwrites the NVRAM with factory default data. And of course that would erase any custom boot strings or other NVRAM data.


    ATTENTION

    If your Level-B power-up tests are not in the default location (qd(0,1)ssw/fw/csm), the power-up tests will fail when the NVRAM is scrubbed because the lvlBTests bootpath will be reset to the factory default. In this case, you must use the pup command before the reboot to tell the system to skip the power-up tests after the NVRAM scrub. Be sure to reset the pup command flag after the reboot.



    ATTENTION

    If you put incorrect data into the flash PROMs, the system will not boot after the next power cycle.


  2. At the Level-B prompt, enter fprog.

    1. Select option 2 from the menu. The CSM board SLIC ID will automatically be selected as the default value.

    2. Select option 1 from the fprog menu to update the flash PROMs and specify a filename.

      The file to program into the flash PROMs will be one of the following two:

      qd(0,1)ssw/fw/csm/lvlA.rom (WS5000 systems)

      qd(0,2)ssw/fw/csm/lvlA.rom (S5000 systems)

      After you select the file, the system displays the following:

      Verifying input data checksum Programming FPROM at slic address
      xx, 0x80000 bytes Using FPROM data file qd(0,1)ssw/fw/csm/lvlA.rom Continue?
      (y/n)
      

      (The filename might be different on your system.)

    3. If you are satisfied with the selections, enter y to continue.

      If you want to make a change, enter n. The system will return you to the fprog menu, where you have the option to select a different file or change the SLIC ID.

      The programming operation can take up to one minute.

      While the PROMs are being programmed, the system will display the following:

      Programming zeros Erasing FPROM Programming ..................................
      Verifying FPROM checksum FPROM programming complete.
      
    4. Exit fprog by choosing option " q" from the fprog menu.

  3. Verify matching Level-A and Level-B versions.


    ATTENTION

    CSM versions prior to V1.5 had revision format number 0, and versions later than V1.5 have format revision number 1. Beginning with CSM SW V1.5, the firmware checks the format revision number in NVRAM. If that number does not match the number for the firmware level being installed, the firmware overwrites the NVRAM with factory default data. And of course that would erase any custom boot strings or other NVRAM data.


    1. Boot a new Level-B using the zap command to simulate a system power-cycle and to activate the new software. When the Level-B software runs after the zap, it overwrites the NVRAM with factory defaults (if you're upgrading to V1.6.1 from a CSM version prior to V1.5). You'll need to restore any custom settings after you boot the new firmware. When the Level-B prompt appears, press any key within five seconds to stop the bootup at Level-B.

      ---> zap

    2. At the Level-B prompt, enter config and verify that the CSM board has matching Aver and Bver values.

      ---> config

  4. If you used the pup command skipTests flag to skip the power-up tests, reset the flag so that power-up tests will be run during subsequent reboots.

  5. At the Level-B prompt, use the bh command to boot all the way up to the operating system.