This document provides procedures for updating the firmware on DIGITAL Alpha VME 5/352 and 5/480 Single Board Computers. It is intended for manufacturing, repair, and maintenance personnel (including field service representatives and system managers).
Key aspects covered:
- Firmware Location: The firmware resides in Flash Erasable Programmable Read Only Memory (FEPROM) and includes PALcode, diagnostics, console interface, and bootstrap. The update process involves erasing, reprogramming, and verifying the entire FEPROM image in-circuit, which creates a brief "window of vulnerability."
- Supported Systems: The V1.2 firmware update supports Alpha VME 5/352 and 5/480 CPU modules.
- Operating System Requirements: Specifies minimum SRM firmware revisions required for DIGITAL UNIX (4.0B or higher) and VxWorks (5.2 or higher).
- New Features (V1.2): Includes support for multifunction PCI devices, a fix for extended network downloads (collision detection), correction of a spurious keyboard/mouse interrupt issue on PMC I/O expansion, and an adjusted timeout for VxWorks network booting.
- Overall Update Process (approx. 5 minutes):
- Preparation: Involves shutting down the operating system, enabling firmware updates by closing I/O module DIP switch #2, halting the system, disabling automatic boot (
AUTO_ACTION=HALT), disabling power-on diagnostics (MODE=FASTBOOT), resetting the system, and identifying current firmware/PALcode versions. Users are advised to record original environment settings.
- Updating: Firmware can be updated from either a CD-ROM or a network server (using MOP or BOOTP protocols). Both methods require booting a Firmware Update Utility and then issuing an
update command from the console prompt, with confirmation. Users are warned not to interrupt the process.
- Post-Update: Requires restoring original environment variables (AUTO_ACTION, MODE), opening I/O module DIP switch #2 to disable further updates, cycling power or resetting the system to load the new firmware, and rebooting the operating system.
If the update fails, users are instructed to contact their local Customer Support Center.