Size:
3.03 Mb
Download

Section 9

System Management

The KAT4000 provides an intelligent hardware management system, as defined in the AdvancedTCA® Base Specification (PICMG® 3.0; AMC.0). This system implements an Intelligent Platform Management Controller (IPMC) based on the proprietaryBMR-H8S-ATCA®reference design from Pigeon Point Systems.

The KAT4000 IPMC implements all the standard Intelligent Platform Management Interface (IPMI) commands and provides hardware interfaces for other system management features such as Hot Swap control, LED control, power control, and temperature and voltage monitoring. The IPMC also supports an EIA-232interface for serial communications via the Serial Interface Protocol Lite (SIPL) IPMI commands.

IPMC OVERVIEW

The basic features of the KAT4000 IPMC include:

Conformance to ATCA Base Specification (PICMG 3.0)

Geographical addressing according to PICMG 3.0

Ability to read and write Field Replaceable Unit (FRU) data on each capable AMC site

Ability to reset IPMC from IPMB-0

Ability to read an inlet and outlet temperature sensor

Ability to read payload voltage/current levels

Ability to send event messages to a specified receiver

All sensors generate assertion and/or de-assertionevent messages

Support for fault tolerant field upgrades

Support for field updates of firmware via the payload processor interface

Hardware added to accommodate console redirection over IPMB

10007175-02

KAT4000 User’s Manual

9-1

 

 

 

System Management:IPMC Overview

The following block diagram shows the IPMC connections for the KAT4000.

Figure 9-1: IPMC Connections Block Diagram

 

 

Payload

 

Payload

 

Processor

 

 

Interface

Boot

Power Enables and

Payload

 

AMC Sites (B1-B4):

 

Device

Management

Reset

 

Select

Temperature Sensors

 

 

 

CPU Inlet

CPU Outlet

...

 

 

Temp Sensor

Temp Sensor

 

 

0x90

0x92

 

 

 

 

 

UART

 

 

I2C Bus

 

 

 

 

3_3V

 

 

 

 

2_5V

 

IPMC

 

 

1_5V

 

 

 

1_0V

 

 

 

 

CPU_Core

Voltage

Pigeon Point

 

 

1_8V

Sensors

 

 

1_2V

 

 

 

 

 

Reference Design

IPMC Debug

UART

(proprietary)

 

 

Console

 

 

ShMC Present

 

 

 

(from JP7)

 

 

 

IPMC Reset

 

 

 

 

Switch

 

I2C

I2C

 

 

 

HAI7:0J 8

ENABLE A-IPMB

A-IPMB

B-IPMB

ENABLE B-IPMB

Isolation Isolation

CPU Present

AMC Sites (B1-B4):

Ready,

Payload Power Current Monitor

RTM: Present

AMC Sites(B1-B4):Enable

RTM: Payload Power Enable

RTM: Management Power Enable

HSLED

 

LED1A

Front

LED1R

Panel

LED2

LEDs

LED3

 

Hot Swap Switch

IPMB-0

9-2

KAT4000 User’s Manual

10007175-02

 

 

 

Table 9-1

System Management:IPMI Messaging

IPMI MESSAGING

All IPMI messages contain a Network Function Code field, which defines the category for a particular command. Each category has two codes assigned to it–onefor requests and one for responses. The code for a request has the least significant bit of the field set to zero, while the code for a response has the least significant bit of the field set to one.

lists the network function codes (as defined in the IPMI specification) used by the IPMC.

Table 9-1: Network Function Codes

HexCode

 

 

 

Value(s):

Name:

Type:

Description:

00, 01

Chassis

chassis device

00 = command/request, 01 = response:

 

 

requests/responses

common chassis control and status functions

 

 

 

 

02, 03

Bridge

bridge requests/

02 = request, 03 = response:

 

 

responses

message contains data for bridging to the next

 

 

 

bus. Typically, the data is another message,

 

 

 

which also may be a bridging message. This

 

 

 

function is only present on bridge nodes.

 

 

 

 

04, 05

Sensor/

sensor and event

04 = command/request, 05 = response:

 

Event

requests/responses

for configuration and transmission of Event

 

 

 

Messages and system Sensors. This function

 

 

 

may be present on any node.

 

 

 

 

06, 07

App

application

06 = command/request, 07 = response:

 

 

requests/responses

message is implementation-specificfor a

 

 

 

particular device, as defined by the IPMI

 

 

 

specification

 

 

 

 

08, 09

Firmware

firmware transfer

08 = command/request, 09 = response:

 

 

requests/responses

firmware transfer messages match the format

 

 

 

of application messages, as determined by the

 

 

 

particular device

 

 

 

 

0A, 0B

Storage

non-volatile

0A = command/request, 0B = response:

 

 

storage requests/

may be present on any node that provides

 

 

responses

nonvolatile storage and retrieval services

 

 

 

 

0C-2F

Reserved

reserved: 36 network functions (18 pairs)

 

 

 

 

30-3F

OEM

vendor specific: 16 network functions (8 pairs).

 

 

 

The vendor defines functional semantics for

 

 

 

cmd anddata fields. Thecmd field must hold

 

 

 

the same value in requests and responses for a

 

 

 

given operation to support IPMI message

 

 

 

handling and transport mechanisms. The

 

 

 

controller’s Manufacturer ID value identifies

 

 

 

the vendor or group.

 

 

 

 

10007175-02

KAT4000 User’s Manual

9-3

 

 

 

System Management:IPMI Messaging

IPMI Completion Codes

All IPMI response messages contain a hexadecimal Completion Code field that indicates the status of the operation. Table 9-2 lists the Completion Codes (as defined in the IPMI specification) used by the IPMC.

Table 9-2: Completion Codes

Code:

Description:

Generic Completion Codes 00, C0-FF

00

Command completed normally

 

 

C0

Node busy–commandcould not be processed becausecommand-processing

 

resources are temporarily unavailable

 

 

C1

Invalid command–indicatesan unrecognized or unsupported command

 

 

C2

Command invalid for given LUN

 

 

C3

Time-outwhile processing command, response unavailable

 

 

C4

Out of space–commandcould not be completed because of a lack of storage space

 

required to execute the given command operation

 

 

C5

Reservation canceled or invalid Reservation ID

 

 

C6

Request data truncated

 

 

C7

Request data length invalid

 

 

C8

Request data field length limit exceeded

 

 

C9

Parameter out of range–oneor more parameters in the data field of the Request are

 

out of range. This is different from Invalid data field code (CC) because it indicates that

 

the erroneous field(s) has a contiguous range of possible values.

 

 

CA

Cannot return number of requested data bytes

 

 

CB

Requested sensor, data, or record not present

 

 

CC

Invalid data field in Request

 

 

CD

Command illegal for specified sensor or record type

 

 

CE

Command response could not be provided

 

 

CF

Cannot execute duplicated request–fordevices that cannot return the response

 

returned for the original instance of the request. These devices should provide separate

 

commands that allow the completion status of the original request to be determined.

 

An Event Receiver does not use this completion code, but returns the 00 completion

 

code in the response to (valid) duplicated requests.

 

 

D0

Command response could not be provided, SDR Repository in update mode

 

 

D1

Command response could not be provided, device in firmware update mode

 

 

D2

Command response could not be provided, Baseboard Management Controller (BMC)

 

initialization or initialization agent in progress

 

 

D3

Destination unavailable–cannotdeliver request to selected destination. (This code can

 

be returned if a request message is targeted to SMS, but receive message queue

 

reception is disabled for the particular channel.)

 

 

D4

Cannot execute command, insufficient privilege level

 

 

D5

Cannot execute command, parameter(s) not supported in present state

 

 

FF

Unspecified error

 

 

9-4

KAT4000 User’s Manual

10007175-02

 

 

 

Table 9-3

System Management:IPMB Protocol

Code: Description: (continued)

Device-Specific(OEM) Codes01-7E

01-7EDevice specific (OEM) completioncodes–command-specificcodes (also specific for a particular device and version). Interpretation of these codes requires prior knowledge of the device command set.

Command-SpecificCodes80-BE

80-BE

Standard command-specificcodes–reservedforcommand-specificcompletion codes

 

(described in this chapter)

 

 

IPMB PROTOCOL

The IPMB message protocol is designed to be robust and support many different physical interfaces. The IPMC supports messages over the IPMB interface. Messages are defined as either a request or a response, as indicated by the least significant bit in the Network Function Code of the message. shows the format of an IPMI request message followed by each byte description.

Table 9-3: Format for IPMI Request Message

Byte:

Bits:

 

 

 

 

 

 

 

 

 

 

 

7

6

5

 

4

 

3

2

1

 

0

1

 

 

 

 

 

rsSA

 

 

 

 

2

 

 

 

netFn

 

 

 

 

rsLUN

 

 

 

 

 

 

 

 

 

 

 

3

 

 

 

 

 

Checksum

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

4

 

 

 

 

 

rqSA

 

 

 

 

5

 

 

 

rqSeq

 

 

 

 

rqLUN

 

 

 

 

 

 

 

 

 

 

 

6

 

 

 

 

 

Command

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

7:N

 

 

 

 

 

Data

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

N+1

 

 

 

 

 

Checksum

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The first byte contains the responder’s Slave Address, rsSA.

The second byte contains the Network Function Code, netFn, and the responder’s Logical Unit Number, rsLUN.

The third byte contains the two’s-complementchecksum for the first two bytes.

The fourth byte contains the requester’s Slave Address, rqSA.

The fifth byte contains the requester’s Sequence Number, rqSeq, and requester’s Logical Unit Number, rqLUN. The Sequence number may be used to associate a specific response to a specific request.

The sixth byte contains the Command Number.

10007175-02

KAT4000 User’s Manual

9-5

 

 

 

System Management:SIPL Protocol

The seventh byte and beyond contain parameters for specific commands (if required).

The final byte is the two’s-complementchecksum of all of the message data after the first checksum.

An IPMI response message (see Table 9-4)is similar to a IPMI request message. The main difference is that the seventh byte contains the Completion Code, and the eighth byte and beyond hold data received from the controller (rather than data to send to the controller). Also, the Slave Address and Logical Unit Number for the requester and responder are swapped.

Table 9-4: Format for IPMI Response Message

Byte:

Bits:

 

 

 

 

 

 

 

 

 

 

 

7

6

5

 

4

 

3

2

1

 

0

1

 

 

 

 

 

rqSA

 

 

 

 

2

 

 

 

netFn

 

 

 

 

rqLUN

 

 

 

 

 

 

 

 

 

 

 

3

 

 

 

 

 

Checksum

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

4

 

 

 

 

 

rsSA

 

 

 

 

5

 

 

 

rsSeq

 

 

 

 

rsLUN

 

 

 

 

 

 

 

 

 

 

 

6

 

 

 

 

 

Command

 

 

 

 

 

 

 

 

 

 

 

 

 

 

7

 

 

 

 

Completion Code

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

8:N

 

 

 

 

 

Data

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

N+1

 

 

 

 

 

Checksum

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

SIPL PROTOCOL

The KAT4000 IPMC supports the Serial Interface Protocol Lite (SIPL) protocol. It supports raw IPMI messages in SIPL and handles these messages the same way as it handles IPMI messages from the IPMB-Obus, except that the replies route to either the payload or serial debug interface. Messages are entered ascase-insensitivehex-ASCIIpairs, separated optionally by a space, as shown in the following examples:

[18 00 22]<newline>

[180022]<newline>

The IPMC does not, however, support SIPL ASCII text commands, as defined by the IPMI specification.

The KAT4000 IPMC does support Pigeon Point Systems extension commands, implemented as OEM IPMI commands. These commands use Network Function Codes 2E/2F (hex), and the message body is transferred similarly to raw IPMI messages, as described previously.

9-6

KAT4000 User’s Manual

10007175-02

 

 

 

System Management:Message Bridging

The following figures show an example of an extension command request and response, respectively.

Figure 9-2: Extension Command Request Example

[B8 00 01 0A 40 00 12]

Data

Pigeon Point IANA

Command Code

rqSeq (0016) / Bridge (002)

NetFn Code (2E16) / LUN (002)

Figure 9-3: Extension Command Response Example

[BC 00 01 00 0A 40 00 34]

Data

Pigeon Point IANA

Completion Code

Command Code

rqSeq (0016) / Bridge (002)

NetFn Code (2F16) / LUN (002)

MESSAGE BRIDGING

The Message Bridging facility is responsible for bridging messages between various interfaces of the KAT4000 IPMC. As required by the AMC.0 specification, the KAT4000 IPMC supports message bridging between the IPMB-0andIPMB-Linterfaces using the standard Send Message command.

10007175-02

KAT4000 User’s Manual

9-7

 

 

 

System Management:Message Bridging

The KAT4000 IPMC also supports message bridging between the Payload Interface and IPMB-O,which allows the payload to send custom messages to and receive them from other shelf entities, such as the shelf manager. Message bridging is implemented using the Send/Get Message commands and also via LUN 10 of the KAT4000 IPMC.

The following example illustrates how the Send/Get Message and Get Address Info commands can be used by the payload software to get the physical location of the board in the shelf:

1The payload software sends the Get Address Info command to the BMR-H8S-ATCA.Using the SIPL protocol:

[B0 xx 01 00]

2The BMR-H8S-ATCAreturns its IPMB address in the Get Address Info reply. In this example, 7216 is theIPMB-Oaddress of the H8S ATCA.

{B4 00 01 00 00 FF 72 FF 00 01 07]

3The payload software composes a Get Address Info command requesting the responder to provide its addressing information for FRU device 0. The request is composed in the IPMB

format. The responder address is set to 2016 (for the shelf manager). The requester address is set to the value obtained in the previous step.

{20 B0 30 72 00 01 00 8D]

4The payload software forwards the command composed in the previous step to the shelf manager using the Send Message command. The Send/Get Message in SIPL format is:

[18 xx 34 40 20 B0 30 72 00 01 00 8D]

5The BMR-H8S-ATCAfirmware sends the Get Address Info request to the shelf manager, waits for a reply to this request, and sends this reply to the payload software in the Send/Get Message response.

[1C 00 34 00 72 B4 DA 20 00 01 00 00 41 82 FF 00 FF 00 1E]

6The payload software extracts the Get Address info reply from the Send/Get Message response and gets the physical address of the board from it.

The second message bridging implementation, bridging via LUN 10, allows the payload to receive responses to requests sent to IPMB-0via the Send Message command with request tracking disabled, as well as receive requests fromIPMB-0.To provide this functionality, the KAT4000 IPMC places all messages coming to LUN 10 fromIPMB-0in a dedicated Receive Message Queue, and those messages are processed by the payload instead of the IPMC firmware. To read messages from the Receive Message Queue, the payload software uses the standard Get Message command. The payload software is notified about messages coming to LUN 10 via the Get Status command of the SIPL protocol and the payload notification mechanism, or, if theLPC/KCS-basedPayload Interface is used, using the KCS interrupt. The Receive Message Queue of the KAT4000 IPMC is limited to 128 bytes, which is

9-8

KAT4000 User’s Manual

10007175-02

 

 

 

System Management:Standard Commands

sufficient for storing at least three IPMB messages, but may be not enough for a larger number of messages. Taking this into account, the payload software must read messages from the queue as fast as possible, caching them on the on-carrierpayload side for further handling, if it is necessary. If the Receive Message Queue is full, the KAT4000 IPMC rejects all requests coming to LUN 10 with the C0h (Node Busy) completion code and discards all responses coming to this LUN.

STANDARD COMMANDS

The intelligent peripheral management controller (IPMC) supports standard IPMI commands to query board information and to control the behavior of the board. These commands provide a means to:

identify the controller

reset the controller

return the controller’s self-testresults

read and write the controller’s SROMs

read the temperature, voltage, and watchdog sensors

get specific information, such as thresholds, for each sensor

read and write the Field Replaceable Unit (FRU) data

reserve and read the Sensor Data Record (SDR) repository

configure event broadcasts

bridge an IPMI request to the public IPMB and return the response

Table 9-5 lists the IPMI commands supported by the IPMC along with the hexadecimal values for each command’s Network Function Code (netFn), Logical Unit Number (LUN), and Command Code (Cmd).

Note: All values are hexadecimal.

Table 9-5: IPMC IPMI Commands

Command:

netFn:

 

LUN:

Cmd:

Set Event Receiver

Sensor/Event

04, 05

00

00

 

 

 

 

 

Get Event Receiver

Sensor/Event

04, 05

00

01

 

 

 

 

 

Platform Event (Event Message)

Sensor/Event

04, 05

00

02

 

 

 

 

 

Get Device SDR Information

Sensor/Event

04, 05

00

20

 

 

 

 

 

Get Device SDR

Sensor/Event

04, 05

00

21

 

 

 

 

 

Reserve Device SDR Repository

Sensor/Event

04, 05

00

22

 

 

 

 

 

Get Sensor Reading Factors

Sensor/Event

04, 05

00

23

 

 

 

 

 

10007175-02

KAT4000 User’s Manual

9-9

 

 

 

System Management:Standard Commands

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Command: (continued)

 

netFn:

 

 

 

 

 

 

 

 

LUN:

 

 

 

Cmd:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Set Sensor Hysteresis

 

Sensor/Event

 

04, 05

 

00

 

 

 

24

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get Sensor Hysteresis

 

Sensor/Event

 

04, 05

 

00

 

 

 

25

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Set Sensor Thresholds

 

Sensor/Event

 

04, 05

 

00

 

 

 

26

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get Sensor Thresholds

 

Sensor/Event

 

04, 05

 

00

 

 

 

27

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Set Sensor Event Enable

 

Sensor/Event

 

04, 05

 

00

 

 

 

28

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get Sensor Event Enable

 

Sensor/Event

 

04, 05

 

00

 

 

 

29

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Rearm Sensor Events

 

Sensor/Event

 

04, 05

 

00

 

 

 

 

2A

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get Sensor Events

 

Sensor/Event

 

04, 05

 

00

 

 

 

 

2B

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get Sensor Reading

 

Sensor/Event

 

04, 05

 

00

 

 

 

 

2D

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Set Sensor Type

 

Sensor/Event

 

04, 05

 

00

 

 

 

 

2E

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get Sensor Type

 

Sensor/Event

 

04, 05

 

00

 

 

 

 

2F

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get Device ID

 

Application

 

06, 07

 

00

 

 

 

01

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Broadcast 'Get Device ID'

 

Application

 

06, 07

 

00

 

 

 

01

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Cold Reset

 

Application

 

06, 07

 

00

 

 

 

02

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Warm Reset

 

Application

 

06, 07

 

00

 

 

 

03

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get Self Test Results

 

Application

 

06, 07

 

00

 

 

 

04

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get Device GUID

 

Application

 

06, 07

 

00

 

 

 

08

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Reset Watchdog Timer

 

Application

 

06, 07

 

00

 

 

 

22

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Set Watchdog Timer

 

Application

 

06, 07

 

00

 

 

 

24

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get Watchdog Timer

 

Application

 

06,07

 

00

 

 

 

25

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Send Message

 

Application

 

06,07

 

00

 

 

 

34

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get FRU Inventory Area Info

 

Storage

 

 

0A, 0B

 

00

 

 

 

10

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Read FRU Data

 

Storage

 

 

0A, 0B

 

00

 

 

 

11

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Write FRU Data

 

Storage

 

 

0A, 0B

 

00

 

 

 

12

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get PCIMG Properties

 

PICMG

 

 

2C, 2D

 

00

 

 

 

00

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get Address Info

 

PICMG

 

 

2C, 2D

 

00

 

 

 

01

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

FRU Control

 

PICMG

 

 

2C, 2D

 

00

 

 

 

04

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get FRU LED Properties

 

PICMG

 

 

2C, 2D

 

00

 

 

 

05

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get LED Color Capabilities

 

PICMG

 

 

2C, 2D

 

00

 

 

 

06

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Set FRU LED State

 

PICMG

 

 

2C, 2D

 

00

 

 

 

07

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get FRU LED State

 

PICMG

 

 

2C, 2D

 

00

 

 

 

08

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Set IPMB State Command

 

PICMG

 

 

2C, 2D

 

00

 

 

 

09

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Set FRU Activation Policy

 

PICMG

 

 

2C, 2D

 

00

 

 

 

 

0A

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get FRU Activation Policy

 

PICMG

 

 

2C, 2D

 

00

 

 

 

 

0B

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Set FRU Activation

 

PICMG

 

 

2C, 2D

 

00

 

 

 

 

0C

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get Device Locator Record ID

 

PICMG

 

 

2C, 2D

 

00

 

 

 

 

0D

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Get Port State

 

PICMG

 

 

2C, 2D

 

00

 

 

 

 

0E

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Set Port State

 

PICMG

 

 

2C, 2D

 

00

 

 

 

 

0F

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Compute Power Properties

 

PICMG

 

 

2C, 2D

 

00

 

 

 

10

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Set Power Level

 

PICMG

 

 

2C, 2D

 

00

 

 

 

11

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

9-10

KAT4000 User’s Manual

10007175-02