contents or use of this manual, and specifically disclaims any express or implied warranties of
merchantability or fitness for any particular purpose.
Kontron Modular Computers makes no representations or warranties with respect to this
embedded Linux package, and specifically disclaims any express or implied warranties of
merchantability or fitness for any particular purpose.
Permission is granted to make and distribute verbatim copies of this manual provided that the
copyright notice and this permission notice are preserved on all copies.
Permission is granted to copy and distribute modified versions of this documentation under
the conditions for verbatim copying, provided also that the entire resulting derived work is
distributed under the terms of a permission notice identical to this one.
Permission is granted to copy and distribute translations of this documentation into another
language, under the above conditions for modified versions.
The PICMG® and CompactPCI® names and the PICMG®, CompactPCI®, ATCA®, and
AdvancedTCA® logos are registered trademarks and AdvancedMC is a trademark of the PCI
Industrial Computer Manufacturers Group.
Intel is a registered trademark of Intel Corporation.
I2C is a trademark of Phillips Semiconductors.
Linux is a registered trademark of Linus Torvalds.
All other trademarks, registered trademarks, and trade names are the property of their
Revision Index Brief Description of Changes Date of Issue
Draft / 0.0 Initial Issue May 3, 2007
1.0 Completed May 22, 2007
1.1 Revised June 12, 2007
IPMI Firmware User Guide for the AM4010 Module
Imprint
Kontron Modular Computers GmbH may be contacted via the following:
MAILING ADDRESS TELEPHONE AND E-MAIL
Kontron Modular Computers GmbH +49 (0) 800-SALESKONTRON
Sudetenstraße 7 sales@kontron.com
D - 87600 Kaufbeuren Germany
For further information about other Kontron products, please visit our Internet web site:
AMC Advanced Mezzanine Card
BSP Board Support Package
DMI Desktop Management Interface
FRU Field Replaceable Unit
FWH Firmware Hub
2
C Inter-Integrated Circuit
I
IPMB Intelligent Platform Management Bus
IPMB-0 AdvancedTCA shelf-level IPMB
IPMB-L Local, on-carrier IPMB that links the carrier IPMC with the MMCs of installed modules
IPMC Intelligent Platform Management Controller located on AMC carrier
IPMI Intelligent Platform Management Interface
IOL IPMI over LAN. An MMC is accessed via LAN, not IPMB
KCS Keyboard Controller Style
MMC Module Management Controller – an IPMI controll er located on the AMC mo dule
MP Management Power
PICMG PCI Industrial Computer Manufacturer Group
PWR Payload Pow er
SDR Sensor Data Record
SDRR Sensor Data Record Repository
SEL System Event Log
SMBIOS System Management BIOS
SMS System Management Software (designed to run under the OS)
SOL Serial over LAN. A serial interface is redirected by LAN using the RM CP+ protocol.
Kontron manuals and specifications: http://www.kontron.com/
• AM4010 User’s Guide
• [3] AM4010 Linux Board Support Package
As a hot-swappable field replaceable unit (FRU), the AM4010 follows the stringent carrier
grade RASM feature set, namely - Reliability, Availability, Serviceability, Maintainability.
Built in accordance to the AMC.0 specification, the AM4010 is also AMC.1 and AMC.2
compliant and is easily managed via IPMI v1.5/v2.0.
As with every Advanced Mezzanine Card (AMC) the AM4010 is equipped with a Module
Management Controller (MMC).
The Module Management Controller is a crucial component of any AMC module. Besides
acting as a regular IPMI management controller (sensor monitoring, event logging, etc.), it
also provides an interface to all necessary data related to module power requirements and
implemented interfaces (E-Keying). Further, it plays an active role in the module hot swap
state management. The carrier IPMI Controller (IPMC) communicates with the MMC using
the local IPMB (IPMB-L) bus. In an ATCA/AMC environment, it is the IPMC that actually
turns on/off module (payload) power. However, before the IPMC enables the module payload
power, various criteria must be satisfied by both the carrier and the module, including power
requirements and capabilities, matching interfaces, current module hot swap state, and any
other special conditions as specified by the Shelf Manager policy.
5.2 The Module Management Controller Hardware
On the AM4010 module, the MMC is implemented using the Renesas H8S/2166 controller
with 512 kB of internal flash and 40 kB of RAM. An additional 1 MB serial EEPROM chip
provides redundant firmware image storage. A separate 32 kB serial EEPROM chip is used
for firmware private data and 4 kB FRU Inventory storage.
The MMC circuit implements two local Keyboard Style Interfaces (KCS) with interrupt
support for communication with system side management software and the IPMB-L bus for
interconnection with the IPMC.
IPMI over LAN (IOL) is supported by two Ethernet channels.
The MMC implements a wide range of sensors that permit the monitoring of:
• main power voltages: +12V (PWR), +5V, +3.3V, +3.3V (MP), +1.5V, +1.8V,
+0.9V (DDR)
• temperatures: CPU die, MCH die, board inlet and outlet near CPU, board inlet and
outlet near MCH
• Power Good, LAN links, IPMB link, NMI and SMI lines, board reset, post code,
boot error, processor hot (>100 °C), IPMB-L state, Health error, IPMI watchdog
etc.
Part of the command list in IPMI specification 2.0
M = mandatory, O = optional
IPMI 2.0
Spec. section
NetFn CMD
Kontron
support
On MMC
IPM Device “Global” Commands
Get Device ID 20.1 App 01h M / Yes [3]
Cold Reset 20.2 App 02h
Warm Reset 20.3 App 03h
Get Self Test Results 20.4 App 04h
Manufacturing Test On 20.5 App 05h
Set ACPI Power State 20.6 App 06h
Get ACPI Power State 20.7 App 07h
Get Device GUID 20.8 App 08h
Broadcast “Get Device ID”
BMC Watchdog Timer
Commands
Reset Watchdog Timer 27.5 App 22h O / Yes
Set Watchdog Timer 27.6 App 24h
Get Watchdog Timer 27.7 App 25h
20.9 App 01h
M
O / Yes
O / No
O / Yes
O / No
O / No
O / No
O / No
M / Yes
Get BMC Global Enables 22.2 App 2Fh
Clear Message Flags 22.3 App 30h
Get Message Flags 22.4 App 31h
Enable Message Channel Receive 22.5 App 32h
Get Message 22.6 App 33h
Send Message 22.7 App 34h
Read Event Message Buffer 22.8 App 35h
Get BT Interface Capabilities 22.9 App 36h
Get System GUID 22.14 App 37h
Get Channel Authentication
Capabilities
Get Session Challenge 22.15 App 39h
Activate Session 22.17 App 3Ah
Set Session Privilege Level 22. 18 App 3Bh
Close Session 22.19 App 3Ch
Get Session Info 22.20 App 3Dh
Get AuthCode 22.21 App 3Fh
Set Channel Access 22.22 App 40h
Get Channel Access 22.23 App 41h
Get Channel Info 22.24 App 42h
Set User Access 22.26 App 43h
Get User Access 22.27 App 44h
Set User Name 22.28 App 45h
Get User Name 22.29 App 46h
Set User Password 22.30 App 47h
Activate Payload 24.1 App 48h
Deactivate Payload 24.2 App 49h
Get Payload Activation Status 24.4 App 4Ah
Get Payload Instance Info 24.5 App 4Bh
Set User Payload Access 24.6 App 4Ch
Get User Payload Access 24.7 App 4Dh
Get Channel Payload Support 24.8 App 4Eh
Get Channel Payload Version 24.9 App 4Fh
Get Channel OEM Payload Info 24.10 App 50h
Master Write-Read 22.11 App 52h
Get Channel Cipher Suits 22.15 App 54h
Suspend/Resume Payload
Encryption
Set Channel Security Keys 22.25 App 56h
Get System Interface Capabilities 22.9 App 57h
22.13 App 38h
24.3 App 55h
O
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / No
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / No
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / Yes
O / No
O / Yes