2 firmware upgrade, 3 firmware / module identification, 3 the payload boot process – Kontron CP6002 IPMI User Manual

Page 14: Firmware upgrade, Firmware / module identification, Ipmi firmware user guide cp6002

Advertising
background image

IPMI Firmware User Guide

CP6002

Page 14

ID: 1039-1613, Rev. 2.0

4.2.2

Firmware Upgrade

Firmware upgrading is only possible when write protection is not set.

The standard way to upgrade the IPMI controller's operational code is to use the open tool
‘ipmitool’ together with an image file.

‘ipmitool’ allows the downloading (‘ipmitool fwum download …’) and activation (‘ipmitool fwum
upgrade’) of the new operational code and saves an existing one. The rollback to the formerly
running operational code is possible as well (‘ipmitool fwum rollback’). The status command
(‘ipmitool fwum status’) displays what firmware is stored and in what state it is (‘last known
good’ = running, ‘previous good’ = running before upgrade).

All IPMI interfaces which are offered by ‘ipmitool’ except LAN are usable for the upgrade. This
allows local upgrade and remote upgrade. Please note that the KCS interface is only usable
with a powered payload.

Files which contain an image of operational code have the firmware ID "B340" and the string
"FWUM" in its name.

During the download process the currently running operational code is still operating in a nor-
mal way until the upgrade command is issued. During the upgrade start, the IPMI controller is
off line for about 20 seconds while the boot code re-organizes the firmware storage. Afterwards
the new operational code is started. If the new operational code doesn't operate properly (e.g.
hangs up) the boot code will perform an automatic rollback to the last working operational code
and start this again.

4.2.3

Firmware / Module Identification

There are two ways to verify by means of IPMI that a Management Controller resides on a
CP6002.

Invoking the IPMI command “Get Device ID” returns among other information the following
data:

• Manufacturer ID = 3A98h (Kontron IANA ID)

• Product ID = B340 for the firmware

• Firmware Revision in bytes 4:5 - depends on the core version of the running firmware.

• The SDR revision in byte 13 (OEM part of the response) is a sub-revision of the firmware

revision. It is unique for all versions of the board's firmware.

• The Device ID String which can be found by reading the Management Controller Device

Locator Record (SDR Type 12h) contains the string "BMC:x ... x". For example, invoking
the ipmitool command 'ipmitool sdr list mcloc' will return the Device ID Strings of all
available boards. If the CP6002 is a BMC, this string will be displayed without change. If
the CP6002 is an SMC, then the string will be changed into "Sxx: x ... x" where xx is the
slot number where the board is residing, e.g. "S09: x ... x".

4.3

The Payload Boot Process

When the CP6002's payload starts, the first code to be executed is the EFI. There are two Flash
devices, numbered 0 and 1, which may contain different EFI code. Which one of them will be
utilized from the next boot process on is defined by one of two ways:

Advertising