7.1 Important considerations when using the LFU
The LFU makes upgrading firmware on Laser platform devices fairly easy and safe, provided
a few points are taken into account:
1. On most of the modules the firmware is stored in a Flash ROM. This is a serial device
which has to be completely loaded every time, in one go. Therefore, the LFU update
must not be interrupted. If it is, the module can be left in a completely unuseable and
unrecoverable state. If this happens it has to be replaced. This implies a very slight
risk to every update due to power failure etc.
2. Upgrading the firmware on the CPU module(s) requires special care. This firmware
includes parts which affect the Operating System as well as the hardware. This means
the revisions of software and hardware must be taken into account. EG: You could
change the firmware to fix a hardware bug and then find OSF/VMS won’t boot due to a
PALcode mismatch (an extreme case to make the point!) The SID also gets changed.
3. In a multi-CPU system, all CPUs must have the same firmware revision. There is a
console UPDATE command which copies the contents of the Flash ROM from one CPU
module to another. However, this does not aways work between different revisions. So
if you’re changing the firmware revision always use the LFU.
4. Point 3 becomes especially interesting when a CPU module in a multi-CPU system has
to be replaced. The new one may be at a different firmware revision to the originals.
Therefore, the LFU will be required to bring them all into line. Therefore, the correct
version of LFU must be available on site.
5. The CPUs also have an EEPROM. The image in this has to match the Flash ROM.
You have to "build" the EEPROM every time the Flash ROM is updated, (see console
Release Notes).
6. Some other modules have a SEEPROM (serial EEPROM). At console V3.0, this also has
to be "built" after a console upgrade. Various serial number type information may be
required, (see console Release Notes).
7. If you skip versions when upgrading consoles, you must read the release notes for the
skipped versions to be aware of all changes. Also, some versions are only compatible
with the next, and so may not boot if there is a gap. This applies to downgrading too;
you may have to step up or down through each version. The bottom line, as always, is:
read the release notes!
7.2 Booting the LFU
If your system has a console RRD42, you can boot the console or update CD from that (see
below), if not you need to find an Infoserver. See Section 8.1, Booting a 7000/10000 from a
CD in an Infoserver .
If your "console or update CD" is on tape, see Section 8.2, Putting a service on the Infoserver
system disk , or Section 7.2.3, Booting the LFU from another system .
25
Komentarze do niniejszej Instrukcji