Firmware Version/ CPU Silicon Evolution /Revision /PALcode etc

[Mainak]

Hi ,

Could you please let me know how to fetch Firmware Version/ CPU Silicon Evolution /Revision /PALcode, chipset type/version etc from Micro VAX 4000-105A & VAX 4000-105A servers running on VMS 7.1.

Show config command on savron prompt is returning –

>>> show config
KA54-A V2.6, VMB 2.15

Does it mean the firmware version is 2.15.

It would be very helpful if someone can let me know how to fetch all the above mentioned information from VMS , console prompt or using any 3rd party tool.

Thanks
Mainak

[Steven Schweda]

I believe that, in your example, V2.6 is the
console firmware version. VMB is Virtual
Memory Boot, the primary bootstrap image,
here, in ROM.

There is no PALcode on a VAX.

Why do you care?

[Kris Clippeleyr]

Hi,

KA54-A is CPU type & revision.
V2.6 is firmware version.

Regards,
Kris (aka Qkcl)

[Peter Zeiszler]

Are you trying to find firmware upgrade or just trying to find the version to have the system fully documented?

[Mainak]

I am trying to find the firmware version and all the related information to have the system fully documented? Is there any way to find these from the VMS without shuting down the system?

[Karl Rohwedder]

I've never heard of a way to get this information from a running VAX/VMS system.
On Alpha you have the CLUE extension for SDA wich can get the firmware revisions.
Ferry Bolhar once wrote a CLUE extension for VAX also, but this misses the firmware info also (see http://vms.process.com/scripts/fileserv/fileserv.com?CLUE$SDA_VAX).

I've attached the output on AX for you information.

regards Kalle

[Volker Halle]

Mainaik,

$ ANAL/ERROR may display some of this information in the header of every errlog entry:

...
TIME STAMP KA53 CPU Microcode Rev # 3. CONSOLE FW REV# 2.1
Standard Microcode Patch Patch Rev # 16.
...

Volker.

[Volker Halle]

Mainak,

the CPU revision information etc. is typically encoded in the SID or XSID system registers.

The SID is available via F$GETSYI("SID"), but this doesn't decode the various - CPU type specific - fields.

The XSID can be obtained from the per-CPU database structure with SDA, but will also not decode the bits.

It's best to rely on the information in the errlog headers.

Volker.