beautypg.com

11 asynchronous event notification, Table 8-10, Ipmc boot parameter storage format – Artesyn ATCA-9405 Installation and Use (May 2014) User Manual

Page 138: Intelligent peripheral management controller

background image

Intelligent Peripheral Management Controller

ATCA-9405 Installation and Use (6806800M71G)

138

The boot options should be stored as a sequence of zero terminated strings.

Table 8-10 on

page 138

, describes in detail the format of the boot options to be used when setting or reading

the System Boot Options parameter #100.

When writing or reading from the storage area, you can only read or write chunks of 16 bytes
at a time. For this reason, the IPMC memory is divided into numbered blocks of 16 bytes which
need to be addressed individually. For this purpose the block selector field in the request data
field is used.

8.11 Asynchronous Event Notification

To inform payload applications about graceful shutdown/reboot requests, the FRU
Activate (Deactivate)

and FRU Control (Graceful Reboot) command

message is routed as a LUN2 message to payload interface.

If the payload application has registered to these commands via OpenIPMI library, it gets
informed and can take all necessary actions before the payload is gracefully rebooted/shut-
down.

Table 8-10 IPMC Boot Parameter Storage Format

Byte

Description

0-1

Number of bytes used for boot parameters (LSB first)

The number of bytes must be calculated and written into these two bytes
by the software which writes into the storage area. The values 0x0000
and 0xFFFF indicate that no data has been written to the storage area. If
you are reading from the storage area and you find any of these two
values, your software assumes that no boot firmware boot options have
previously been written to the storage area.

2-n

Boot Parameters data

The boot parameters are stored as ASCII text with the following general
format: =, where all name/value pairs are separated by
a zero byte. The end of the boot parameter data is indicated by two zero
bytes. Allowed and supported name/value pairs are blade specific.

N+1 - n+2

16 bit checksum over the boot parameters data section (LSB first)