2 boot flash selection by oem ipmi command, 4 os boot order selection by oem ipmi, Boot flash selection by oem ipmi command – Kontron CP6002 IPMI User Manual

Page 15: Cp6002 ipmi firmware user guide

Advertising
background image

CP6002

IPMI Firmware User Guide

ID: 1039-1613, Rev. 2.0

Page 15

• The contents of a user (payload) writeable register (refer to the CP6002 User Guide)

defines which Boot Flash to use. This is the primary selection.

• The firmware's parameter EEPROM contains a parameter whose value is used to

determine whether or not to invert the primary selection register's contents when the
Management Controller's firmware selects the Boot Flash. For this the Management
Controller sets or resets a control signal which does or does not invert the Boot Flash
selection.

4.3.1

Boot Flash Selection by Writing to a Board Register

Refer to the CP6002 User Guide for further information concerning Boot Flash selection using
a board register setting.

4.3.2

Boot Flash Selection by OEM IPMI Command

The OEM IPMI command “Set Control State” specifies whether or not the Management
Controller is to invert the register based Flash selection from the next boot process on. The
Management Controller stores this requirement in a parameter in the EEPROM.

4.3.3

Automatic Boot Flash Selection During the Boot Process

After each payload reset the Management Controller selects the Boot Flash by applying the
related EEPROM parameter.

Physically the Management Controller sets or resets a signal line. Afterwards it waits for a
special message from the EFI. This message contains the checksum report, i.e. it indicates the
validity of the Boot Flash's checksum.

If the checksum is wrong or the message is not received within 60 seconds, then the currently
used EFI Flash is assumed to contain an invalid or a corrupted image. In this case, the
Management Controller toggles the parameter value in the EEPROM and issues a “Boot Error
(Invalid boot sector) event” by setting the appropriate sensor value (sensor 'FWHx Boot Err'. x
= 0..1). x is simply the value of the parameter in EEPROM and not the absolute number of the
used Boot Flash. Afterwards it causes a payload off-on cycle and continues as described at the
beginning of this chapter.

When a timeout error is recognized and the count of boot errors exceeds 2, or when a
checksum error is recognized and the count of boot errors exceeds 4 the Management
Controller makes no further attempt to reset/restart the payload. Only at the next power off/on
of the CP6002, will the Management Controller again attempt to start the payload.

4.4

OS Boot Order Selection by OEM IPMI

Normally the EFI will apply the OS boot order which was selected in the EFI menu “Boot/Boot
Option Priorities”. But there is another alternative boot order which is stored in the Management
Controller's non-volatile memory. This boot order can be set and read by IPMI OEM
commands. At payload start the Management Controller writes it into a register where the EFI
can read it. If this Management Controller's boot order has a non-zero value the EFI will use it
instead of its own boot order.

Advertising