mmc data sheet - productssamwayelectronic.com/products/files/56_mmc data sheet rev 1.4.pdf · mmc...

MMC Data Sheet Rev 1.4

Module Management Controller (MMC) Data Sheet

Revision History: Rev 1.4 24.03.2015 Added information for selecting the GPIO sensor typeRev 1.3 17.07.2014 Added AMC Evaluation Board ConnectivityRev 1.2 23.06.2014

• Second Generation micro-controller: Freescale Kinetis K10• Updated Table 2. Standard Set of sensor• Added List of supported IPMI commands• Added Payload sensor chapter

Rev 1.1 01.10.2013 Added List of CLI commandsRev 1.0 09.08.2013 First Draft

www.samwayelectronic.com 1 /30

Key features• Compliant to IPMI 2.0.• Compliant to MCTA.4:• Compliant to HPM.1 firmware upgrade • Easy to integrate• Flexible ordering options:

◦ preprogrammed micro-controller◦ source code

• Evaluation Board Available• Reference Designs Provided• GUI software for configuration• Cost Effective:

◦ No upfront costs for standard version◦ No royalties

• Analog inputs for voltage, current or temperature measurements

• External I2C for temperature measurements and communication with payload

• External thermal-diode for monitoring FPGA,or in-chip sensors

• Hot swap switch input, LEDs and payload power control outputs

http://Www.samwayelectronic.com/


Table of ContentsKey features...............................................................................................................................................1Description................................................................................................................................................4List of supported IPMI Commands...........................................................................................................4FRU Information.......................................................................................................................................6Sensors......................................................................................................................................................7Configuring Sensors..................................................................................................................................9GPIO Sensors..........................................................................................................................................12

Selecting GPIO type ..........................................................................................................................13Controlling GPIOs using the CLI.......................................................................................................14Controlling GPIOs using IPMI commands........................................................................................15

User Defined Payload Sensors................................................................................................................16Using Payload Sensors.......................................................................................................................16Controlling Payload Sensors using IPMI commands.........................................................................20

AMC Evaluation Board Connectivity.....................................................................................................21Payload Interface signals.........................................................................................................................25uRTM Interface signals...........................................................................................................................25LEDs........................................................................................................................................................26Command Line Interface (CLI) ..............................................................................................................26List of CLI commands.............................................................................................................................26

gpio command ...................................................................................................................................26help command ...................................................................................................................................27info command ....................................................................................................................................27payload_reset command ....................................................................................................................27payload_signals command .................................................................................................................27reboot command ................................................................................................................................28sensor command ................................................................................................................................28uptime command ...............................................................................................................................28version command ...............................................................................................................................28xmodem command ...........................................................................................................................28

Updating the Firmware............................................................................................................................29Updating the FRU and SDR files............................................................................................................30Order codes.............................................................................................................................................30

Illustration IndexIllustration 1: SDR Compiler....................................................................................................................9Illustration 2: Selecting a subset of sensors............................................................................................10Illustration 3: Window for changing parameters for an analog sensor...................................................10Illustration 4: Various Embedded formula selection windows................................................................11Illustration 5: Change GPIO type step 1.................................................................................................13Illustration 6: Change GPIO type step 2.................................................................................................14




Illustration 7: Read Payload Sensor Value I2C Operation......................................................................18Illustration 8: Write Sensor Value I2C Operation...................................................................................19Illustration 9: AMC Evaluation Board....................................................................................................21Illustration 10: AMC Evaluation Board Connectors...............................................................................22Illustration 11: Firmware update example...............................................................................................29Illustration 12: Tera Term Screen shot for sending a file using xmodem...............................................30

Index of TablesTable 1: List of supported IPMI Commands.............................................................................................5Table 2: Standard Set of Sensors...............................................................................................................8Table 3: GPIO sensor Type.....................................................................................................................13Table 4: Set Sensor Reading and Event Status command for controlling GPIOs...................................16Table 5: Set Sensor Reading and Event Status command for controlling Payload Sensors...................20Table 6: J1 connector Pin-out..................................................................................................................23Table 7: J2 connector Pin-out..................................................................................................................23Table 8: J3 connector Pin-out..................................................................................................................24Table 9: RTM connector Pin-out.............................................................................................................24Table 10: Payload Interface Signals........................................................................................................25Table 11: uRTM Interface Signals...........................................................................................................25Table 12: Available LEDs........................................................................................................................26




DescriptionThe Module Management Controller (MMC) Software allows quick development of AMCs

without prior IPMI knowledge. It provides all the mandatory IPMI functionality required by the μTCA, MCTA.4 and AMC specifications, thus allowing easy and fast development of AMCs.

The MMC Software is a cost effective solution that enables very fast development of AMCs. There are no royalties and for the standard version there aren't any upfront costs. The standard version of the MMC Software can be customized to fulfill any particular requirements.

The software is accompanied by reference schematics and a complete set of GUI compilers for the SDR and FRU files.

The standard version of the software is the starting point for all AMC designs. It supports the Hot Swap Handle, Blue Led, Led1 and Led2.

The MMC Software is compliant to HPM.1 and thus can be easily upgraded over IPMB-L using a MCH with no need for external cables or custom software.

The MMC Software can implement discrete, temperature, voltage, current, fan or OEM sensors . The SDRs for the standard version of software implement only a basic set of sensors.

Samway's MMC Software is easy to use and has flexible ordering options. It can be delivered on a preprogrammed micro controller or as source code (the IPMI library is delivered as object code). The microcontroller used is a Freescale Kinetis K10 hosted in a 64 pin LQFP package that needs 10 mm x 10 mm of PCB space.

List of supported IPMI Commands

Command Name Spec Reference [section/Table]

NetFn CMD

Get Device ID IPMI 1.5 [17.1] App 01hGet Self Test Results IPMI 1.5 [17.4] App 04hSet Event Receiver IPMI 1.5 [23.1] S/E 00hGet Event Receiver IPMI 1.5 [23.2] S/E 01hPlatform Event(a.k.a „Event Message“) IPMI 1.5 [23.3] S/E 02hGet Device SDR Info IPMI 1.5 [29.2] S/E 20hGet Device SDR IPMI 1.5 [29.3] S/E 21hReserve Device SDR Repository IPMI 1.5 [29.4] S/E 22hSet Sensor Hysteresis IPMI 1.5 [29.6] S/E 24hGet Sensor Hysteresis IPMI 1.5 [29.7] S/E 25hSet Sensor Threshold IPMI 1.5 [29.8] S/E 26hGet Sensor Threshold IPMI 1.5 [29.9] S/E 27hSet Sensor Event Enable IPMI 1.5 [29.10] S/E 28hGet Sensor Event Enable IPMI 1.5 [29.11] S/E 29h




Command Name Spec Reference [section/Table]

NetFn CMD

Get Sensor Reading IPMI 1.5 [29.14] S/E 2DhSet Sensor Reading and Event Status IPMI 2.0 [35.17] S/E 30hGet FRU Inventory Area Info IPMI 1.5 [28.1] Storage 10hRead FRU Data IPMI 1.5 [28.2] Storage 11hWrite FRU Data IPMI 1.5 [28.3] Storage 12hGet PICMG Properties PICMG 3.0 [Table 3.9] PICMG 00hFRU Control PICMG 3.0 [Table 3.22] PICMG 04hGet FRU Led Properties PICMG 3.0 [Table 3.24] PICMG 05hGet Led Color Capabilities PICMG 3.0 [Table 3.25] PICMG 06hSet FRU Led State PICMG 3.0 [Table 3.26] PICMG 07hGet FRU Led State PICMG 3.0 [Table 3.27] PICMG 08hGet Device Locator Record ID PICMG 3.0 [Table 3.29] PICMG 0DhFRU Control Capabilities PICMG 3.0 [Table 3.24] PICMG 1EhSet AMC Port State AMC.0 [Table 3.27] PICMG 19hGet AMC Port State AMC.0 [Table 3.28] PICMG 1AhGet Target Upgrade Capabilities HPM.1 [Table 3.3] PICMG 2EhGet Component Properties HPM.1 [Table 3.5] PICMG 2FhInitiate Upgrade Action HPM.1 [Table 3.8] PICMG 31hUpload Firmware Block HPM.1 [Table 3.9] PICMG 32hFinish Firmware Upload HPM.1 [Table 3.10] PICMG 33hGet Upgrade Status HPM.1 [Table 3.2] PICMG 34hActivate Firmware HPM.1 [Table 3.11] PICMG 35h

Table 1: List of supported IPMI Commands




FRU Information

The MMC will be used in an IPMI environment. In order to interact to the other FRUs in the system, the board will have to host a FRU information file. This type of file contains important information concerning the board:

• Manufacturers name

• Part Number

• Serial Number

• Revision

• Manufacturing data

• Information related to the communication protocols implemented over the Base, Fabric, Timing and Local Bus interfaces

• other IPMI related information

All the required information can be saved in the FRU file format using the GUI FRU compiler.


Figure 5: FRU File Compiler



SensorsThe MMC supports a predefined set of sensors. Each supported sensor has a predefined sensor

number and if it is used,it shall have a Sensor Data Record (SDR) associated to it. Using the set of SDRs the IPMI software knows what sensors are implemented by the card and how to monitor them.So, no software update is needed when different sensors are required.

The standard sensor list is defined by the following table. To this set other custom sensors can be added on request.

Sensor Number

Default Sensor Name

Description

1 Hot Swap Handle Discrete sensor: offers information about the hot swap handle 0 = Module Handle Closed1 = Module Handle Opened2 = Quiesced3 = Backend Power Failure4 = Backend Power Shut Down5 = μRTM Present6 = μRTM Absent7 = μRTM Compatible8 = μRTM Incompatible

2 An01 Analog Sensor: can be used to monitor a voltage, current or temperature signal.




6 An4 Analog Sensor: can be used to monitor a voltage, current or temperature signal




10 Temp1 Analog Sensor: connected to a TMP75 I2C temperature sensor I2C_Address = 0x90

11 Temp2 Analog Sensor: connected to a TMP75 I2C temperature sensorI2C_Address = 0x92

1 The analog input pins withstand signals in the range 0..2.5 Volts. If the signals that need to be monitored are outside this range, additional circuitry will be necessary (voltage dividers).




Sensor Number

Default Sensor Name

Description

12 Temp3 Analog Sensor: connected to a LM86 I2C External thermal-diode temperature sensorI2C_Address = 0x98

12 Temp4 Analog Sensor: connected to Temp 1 of a LM95231CIMM I2C External thermal-diode temperature sensorI2C_Address = 0x56

12 Temp5 Analog Sensor: connected to Temp 2 of a LM95231CIMM I2C External thermal-diode temperature sensorI2C_Address = 0x56

32 GPIO1 Digital General Pourpose I/O sensor33 GPIO2 Digital General Pourpose I/O sensor34 GPIO3 Digital General Pourpose I/O sensor35 GPIO4 Digital General Pourpose I/O sensor

>100 User defined User defined Payload Sensor

Table 2: Standard Set of Sensors




Configuring Sensors

The MMC uses standard, IPMI compliant SDR records in order to monitor the board parameters.

The SDR repository of a board will be a software image of the hardware sensors. For each board there may be a different set-up as the requirements are different. So, in order to allow a quick and simple set-up, a GUI SDR compiler is provided.

Using the GUI compiler a subset of all of the supported sensors can be defined by a simple select operation.


Illustration 1: SDR Compiler



After the SDR set has been defined, all the sensors can be customized:

• threshold and hysteresis values can be changed for analog sensors

• names can be changed for all sensors


Illustration 2: Selecting a subset of sensors

Illustration 3: Window for changing parameters for an analog sensor



• for the analog inputs the raw SDR formulas of a few hardware circuits have been implemented. This feature allows easy integration of common analog set-ups: positive voltage divider, negative voltage divider, and gain block. For these common circuits only the divider/gain value has to be inputed, and the raw conversion formula will be automatically computed by the software. For more complex circuits, the raw formula can be inputed manually.


Illustration 4: Various Embedded formula selection windows



GPIO Sensors

The IPMC supports 3 General Purpose Input Output (GPIO) sensors. Each sensor is assigned to a micro-controller pin equipped with an open collector driver.

The GPIO sensors can be configured as:

• Active Low Input

• Active High Input

• Active Low Input – Output

For all types of GPIO sensors the pin state is checked at regular intervals and the sensor state is refreshed acourdingly. The GPIOs have been implemented using a discrete sensor having two states:

• 1 Asserted: physical pin is at the active level

• 0 Deasserted: physical pin is not at the active level

For input-output GPIO sensors,besides checking out the state of the micro-controller pin, the user can also control it using an override state.

The input - output GPIOs can only be used as active low signals, because the GPIO output driver is implemented using an open collector architecture.

Input-Output Overide states:

• 1 Asserted: physical pin is held low (GND) by the micro-controller

• 0 Deasserted: physical pin is a high impedance input, and can be controlled by other drivers.

To figure out who is keeping an input-output signal asserted, you can use the gpio command. For an input-output GPIO asserted by the micro-controller the override state is active and displayed accordingly by the command. Input-output GPIOs that are asserted by another driver do not have the override state active. In the following example GPIO2 is asserted by the micro-controller and GPIO3 is asserted by another driver: %>gpio----------------------GPIO List-----------------------------------------GPIO Sensor Active-no---No---Type----Level---Name-------------State-----------Override----* 1 32 Input Low GPIO1 0 De-Asserted * 2 33 Output Low GPIO2 1 Asserted 1 Asserted* 3 34 Output Low GPIO3 1 Asserted




Selecting GPIO type The IPMC supports 3 types of sensor for the GPIOs:

GPIO type SDR Sensor TypeActive Low Input 0xC0

Active Low Input – Output

0xC1

Active High Input 0xC3

Table 3: GPIO sensor Type

The GPIO type can be configured using the SDR compiler. To do so you have to select the sensor from the list and use the Edit Sensor button.

The next step is writing the SDR type necessary for the desired GPIO type, in the dedicated SDR field. The SDR type values are defined in Table 2.


Illustration 5: Change GPIO type step 1



Controlling GPIOs using the CLIThe Command Line interface (CLI) is available over the RS232 interface. For controlling

GPIOs a dedicated command has been implemented:

gpio [no as | de]

The parameters entered are GPIO number: 1..4, and desired action as – assert, de – deassert.Example 1:%>gpio 2 as Done! GPIO2 Asserted!

The command can also be used to check out the state of the GPIOs. For reading the state the command is entered without any parameters.

Example 2:%>gpio------GPIO List------------------------------------------------- Sensor-no---No---Type----Name-------------State-----------Override----* 1 32 Input GPIO1 0 De-Asserted* 2 33 Output GPIO2 0 De-Asserted* 3 34 Output GPIO3 1 Asserted 1 Asserted* 4 35 Output GPIO4 1 Asserted


Illustration 6: Change GPIO type step 2



In the example above:

• GPIO1 is configured as input only, while GPIOs 2,3, and 4 are configured as input-output.

• GPIO3 is asserted locally (the local override is also asserted)

• GPIO4 is asserted by another driver (the local override is not active)

The state of the GPIOs can also be checked out using the sensor command:%>sensor---------------------Sensor List--------------------------------no--Name--------------Value---Unit---State------------------

* 1 Hot Swap Handle Closed* 2 AN0 VCC 3.27 V Ok* 3 AN1 +12V 12.31 V Ok* 4 AN2 0.00 V Ok* 5 AN3 0.00 V Ok* 6 AN4 0.00 V Ok* 7 AN5 0.01 V Ok* 8 AN6 0.00 V Ok* 9 AN7 0.00 V Ok* 10 Temp1 26.00 deg C Ok* 11 Temp2 26.00 deg C Ok* 12 Temp3 LM86 28.00 deg C Ok* 13 Temp4 LM95231 -128.00 deg C LC* 14 Temp5 LM95231 -128.00 deg C LC* 32 GPIO1 0 De-Asserted* 33 GPIO2 0 De-Asserted* 34 GPIO3 0 De-Asserted* 35 GPIO4 0 De-Asserted

The sensor command identifies the GPIOs using the sensor number and not the GPIO number. The correspondence between the two set of numbers is displayed by the gpio command.

Controlling GPIOs using IPMI commands

The GPIOs that have been configured as input-output pins can also be controlled over IPMB using the IPMI 2.0 Set Sensor Reading and Event Status command. In order for the MMC to acknowledge the command and control the GPIOs the following values have to be used for the parameters:




Field Description Value

Responder's Slave Addr.(RsSA)

IPMB address of the MMC It depends on the physical slot in which the AMC is inserted: 0x72 – slot 1,0x74 – slot 2 ...

NetFn/RsLUN Sensor/Event request + LUN = 0 0x10

Command Set Sensor Reading and Event Status 0x30

Request Data

Byte 1 Sensor Number GPIO sensor number displayed by the sensor CLI command

Byte 2 Operation 0x10

Byte 3 Sensor reading- not used 0x00

Byte 4 GPIO state 0x00 - deassert0x01 – assert

Table 4: Set Sensor Reading and Event Status command for controlling GPIOs

Example 1: turn GPIO1 (sensor no. 32 = 0x20) onRequest from MCH 0x76 0x10 0x7A 0x20 0xB8 0x30 0x20 0x10 0x00 0x01 0xC8Response from AMC 0x20 0x14 0xCC 0x76 0xB8 0x30 0x00 0xA2

User Defined Payload SensorsBesides the standard set of sensors described in Table 2, the MMC also supports user defined

sensors. This feature allows users to define sensors that meet their custom requirements:

• more analog measurements than the MMC supports (8 channels)• discrete state sensors related to the payload• payload configuration registers

The MMC monitors all the user defined sensors and represents them over IPMI:

• monitors thresholds infringements for analog payload sensors• sends events for threshold sensors• allows remote change for sensor state of discrete payload sensors

For discrete sensors the MMC supports remote write access to alter the sensor states, by implementing the IPMI 2.0 Set Sensor Reading and Event Status command. This feature allows payload configuration registers to be written remotely over IPMI.

Using Payload SensorsIn order to use Payload Sensors, first the MMC needs to know they exist and how they were

setup. This is accomplished by adding SDRs for the new sensors in the SDR file of the MMC. The additional SDRs will have to be created using the SDR Compiler provided, because they will have to be tailored to your exact requirements.




The MMC identifies sensors using their sensor number. For Payload Sensors the MMC has reserved the sensor numbers between 100 and 254. The sensor number has to be unique for any sensor in the SDR file.

At start-up the MMC loads it's SDR file and if it finds any sensors that have the sensor number larger than 100 it will register them as Payload sensors and start monitoring them.

Sensor values for payload sensors are obtained over the Payload_I2C bus from the sensor owner. The sensor owner is defined by the sensor SDR. The SDR has a field called Sensor Owner Id that will be loaded with the I2C address of the device that implements the sensor. The Sensor Owner Id will be an I2C slave device capable of simple slave operation. The address can be setup using the SDR compiler.

The protocol between the MMC and the sensor owner will consist in I2C read and write transactions, where the MMC will act as an I2C master and the Sensor Owner will act as an I2C slave.

The sensor owner should mimic the actions of a simple memory device that stores the sensor value using 2 bytes in a LSB (least significant byte first) arrangement . The sensor value will be stored at the offset equal to sensor number*2.

Threshold sensor values will be encoded using the formula defined by the SDR and will only use 1 byte. The sensor owner should use the LSB to store the value for threshold sensors.

Discrete sensors use both bytes available at their respective offset.

For both threshold and discrete sensors, getting a sensor value will translate into reading the 2 bytes stored by the sensor owner at the offset equal to (sensor number *2). The sensor owner should return the value starting with the LSB.




The sensor value read operation is composed of a 2 byte I2C write operation and a 2 byte read operation: the MMC sends START and then the I2C address for the sensor owner with the R/W# bit set to 0, signaling an I2C write operation. The I2C address is followed by the sensor value offset(sensor number *2).After the write operation is complete, the MMC sends a repeated START and resends the I2C addresses of the sensor owner, this time with the R/W# bit set to 1, signaling an I2C read operation. After acknowledging it's address, the sensor owner can start sending the sensor value starting with the LSB. After both bytes have been received, the MMC ends the I2C transaction by sending a STOP.

Example: in order to read sensor number 102 managed by a device with an 8 bits I2C address of 0xC0 the MMC sends Start , 0xC0 , 0x00, 0xCC (102*2=204), Start, 0xC1, reads 2 bytes and sends Stop.

For discrete sensors the MMC can also change the sensor state. This operation will translate into sending the sensor owner a write transaction for the (sensor number *2) offset and containing the new value.


Illustration 7: Read Payload Sensor Value I2C Operation



The write new sensor value operation consists in a 4 byte write operation: 2 bytes sensor offset, and 2 bytes sensor value. The MMC begins the operation by sending Start followed by the sensor owner I2C address with the R/W# bit set to 0, signaling a write operation. After that the MMC sends the sensor offset (sensor number *2) MSB first and the sensor value LSB first.

Example: in order to write the new value of 0x23CE to sensor number 155 managed by a device with an 8 bits I2C address of 0xC0 the MMC sends Start , 0xC0 , 0x01, 0x36 (155*2=310=0x0136), 0xCE, 0x23 and Stop.


Illustration 8: Write Sensor Value I2C Operation



Controlling Payload Sensors using IPMI commandsDiscrete Payload sensors can be controlled over IPMB using the IPMI 2.0 Set Sensor Reading

and Event Status command. In order for the MMC to acknowledge the command and change the payload sensor value the following values have to be used for the parameters:

Field Description Value

Responder's Slave Addr.(RsSA)

IPMB address of the MMC It depends on the physical slot in which the AMC is inserted: 0x72 – slot 1,0x74 – slot 2 ...

NetFn/RsLUN Sensor/Event request + LUN = 0 0x10

Command Set Sensor Reading and Event Status 0x30

Request Data

Byte 1 Sensor Number Payload Sensor – sensor number

Byte 2 Operation 0x10 – bytes 4 & 5 are copied to the sensor valueSensorValue = byte4 + bytes 5 <<8

0x20 – if a bit is set to 1 in bytes 4 & 5 it is also set in the sensor value

SensorValue |= (byte4 + bytes 5 <<8) 0x30 – if a bit is cleared to 0 in bytes 4 & 5 it is also cleared in the sensor value

SensorValue &= (byte4 + bytes 5 <<8)

Byte 3 Sensor reading- not used 0x00

Byte 4 Sensor state 0 LSB

Byte 5 Sensor state 1 MSBTable 5: Set Sensor Reading and Event Status command for controlling Payload Sensors

Example 1: Set value 0x1234 to sensor number 103(0x67) managed by I2C addres 0xA0 Request from MCH 0x76 0x10 0x7A 0x20 0xB8 0x30 0x67 0x10 0x00 0x34 0x12 0x3BResponse from AMC 0x20 0x14 0xCC 0x76 0xB8 0x30 0x00 0xA2

Example 2: Set bit 4 of the sensor value of sensor number 103(0x67) managed by I2C addres 0xA0 Request from MCH 0x76 0x10 0x7A 0x20 0xB8 0x30 0x67 0x20 0x00 0x10 0x00 0x61Response from AMC 0x20 0x14 0xCC 0x76 0xB8 0x30 0x00 0xA2

Example 3: Clear bit 0 of the sensor value of sensor number 103(0x67) managed by I2C addres 0xA0 Request from MCH 0x76 0x10 0x7A 0x20 0xB8 0x30 0x67 0x30 0x00 0x01 0x00 0x60Response from AMC 0x20 0x14 0xCC 0x76 0xB8 0x30 0x00 0xA2




AMC Evaluation Board ConnectivityFor the MMC an evaluation board is available. The board implements all the additional

circuitry and offers all the connectivity required to test the various features of the MMC software.

The front panel of the AMC Evaluation Board implements the uTCA leds (Blue LED, LED1 and LED 2), the hot swap handle and an RS232 connection that can be used to access the MMC Command Line Interface.

For accessing the CLI the necessary settings are:

• Baud rate 115200 bits per second• Data bits: 8• Parity: none• Stop bit: 1

The AMC Evaluation Board uses three I2C temperature sensors (two TMP75 sensors and one LM86 sensor) that correspond to TEMP1, TEMP2 and TEMP3 MMC sensors. The MMC also supports 2 additional temperature sensors: TEMP4, TEMP5 that can be used to monitor two channels of a LM95231CIMM device. In order to monitor the LM95231CIMM device, it has to be connected to the Local_I2C MMC bus that is available on connector J2.


Illustration 9: AMC Evaluation Board



The AMC Evaluation Board uses 4 connectors to allow access to user available signals on the MMC.

PIN Signal Name Description

1 AN2_MON Analog Input 2 corresponds to AN2 sensor. Maximum allowed voltage 2.5V

2 GND Ground



5 GND Ground


7 AN0_MON Analog Input 0 corresponds to AN0 sensor. ReservedUsed to monitor board VCC (3.3V)

8 GND Ground

9 AN1_MON Analog Input 1 corresponds to AN1 sensor. ReservedUsed to monitor board Payload Power PP (12V)


11 GND Ground


13 SHUTDOWN_REQ Payload interface signal

14 VCC Board supply voltage = Management Power (MP) = 3.3V

15 SHUTDOWN_RDY# Payload interface signal

16 GPIO1 General Purpose Input Output Pin 1. Output Driver is open collector. 10K Pull up resistor to 3.3V populated.

17 GPIO4 General Purpose Input Output Pin 4.Output Driver is open collector. 10K Pull up resistor to 3.3V populated.

18 GPIO2 General Purpose Input Output Pin 2.Output Driver is open collector. 10K


Illustration 10: AMC Evaluation Board Connectors




Pull up resistor to 3.3V populated.

19 PAYLOAD_RST# Payload interface signal

20 GPIO3 General Purpose Input Output Pin 3.Output Driver is open collector. 10K Pull up resistor to 3.3V populated.

Table 6: J1 connector Pin-out


1 SPI_MISO SPI Data Input Pin (Master In Slave Out pin). The MMC is always the SPI master.

2 GND Ground

3 SPI_MOSI SPI Data Output Pin (Master Out Slave In pin).

4 SPI_SCK SPI Clock Output Pin

5 GND Ground

6 SPI_CS0 SPI Chip Select Signal

7 PAYLOAD_SDA Serial Data pin for the Payload_I2C bus. This bus is used to communicate to the payload in order to read/write payload sensors.

8 GND Ground

9 PAYLOAD_SCL Serial Clock pin for the Payload_I2C bus.

10 SCL_RTM Serial Clock pin for the RTM_I2C bus. This bus is used to communicate to a uTCA.4 URTM. The bus is located on the MMC side of the I2C buffer

11 GND Ground

12 SDA_RTM Serial Data pin for the RTM_I2C bus

13 LOCAL_SCL Serial Clock pin for the local_I2C bus. This bus is used to communicate to the I2C temperature sensors (TMP75,Lm86, LM95231CIMM) and the EEPROM


15 LOCAL_SDA Serial Clock pin for the local_I2C bus

16 UC_URTM_PS Present signal for the URTM, buffered and inverted

17 READY_URTM_I2C I2C buffer signal for the URTM

18 TXD0 Transmit Pin for Payload available serial interface

19 EN_URTM_I2C Enable signal for the URTM

20 RXD0 Transmit Pin for Payload available serial interface



1 SDA_L Serial Data pin of the IPMB bus

2 GND Ground

3 SCL_L Serial Clock pin of the IPMB bus





4 SLOT_ID3 Bit3 (MSb)of the Slot ID. This can be used to identify the physical position of the AMC in the chassis

5 GND Ground

6 SLOT_ID2 Bit2 of the Slot ID

7 SLOT_ID1 Bit1 of the Slot ID

8 GND Ground

9 SLOT_ID0 Bit0 (LSb) of the Slot ID

10 NC Not Connected

11 GND Ground

12 COMP2 Component 2 select pin

13 COMP1 Component 1 select pin


15 I/O_5 Latched Input – Output pin 5. Output Voltage swing 0-3.3V5V tolerant input

16 COMP_0 Component 0 select pin







1 URTM_MP URTM Management Power (3.3V)

2 GND Ground

3 URTM_PS# URTM present signal. Active low

4 GND Ground

5 URTM_PP URTM Payload Power (+12V)

6 GND Ground

7 URTM_SCL Serial Clock Pin for the URTM_I2C bus. This bus is on the URTM side of the I2C buffer

8 GND Ground

9 URTM_SDA Serial Data Pin for the URTM_I2C bus.

10 GND Ground

Table 9: RTM connector Pin-out




Payload Interface signalsSignal Name Type Active level Description

PAYLOAD_RST# Output Low Resets the payload when active. MUST BE PULLED HIGH ON PAYLOAD SIDE

SHUTDOWN_READY# Input Low When the signal is active the payload is ready to be shutdown. If the signal is not used it has to be tied to GND.The signal can be connected to GND on the AMC Evaluation Board if the cap for JP3 is populated.

SHUTDOWN_REQ Output High When active, signals the payload that a shutdown has been requested

Payload_SCL In-Out I2C serial clock

Payload_SDA In-Out I2C serial data

SPI_MOSI Output SPI interface signal : master output , slave input– reserved for future use

SPI_MISO Input SPI interface signal : master input, slave output – reserved for future use

SPI_SCK Ouput SPI interface signal : serial clock – reserved for future use

SPI_CS Output SPI interface signal : chip select – reserved for future use

Table 10: Payload Interface Signals

uRTM Interface signalsThe MMC software is compliant to MTCA.4, so it supports a micro Rear Transmission Module

(uRTM). The signals of the uRTM interface are described in the following table:

Signal Name Type Active level DescriptionEN_uRTM_I2C Output High Enable signal for the uRTM I2C buffer.

At start-up this signal also acts as a Enable MTCA.4 functionality:

• pull down assembled: MTCA.4 enabled• pull up assembled: MTCA.4 disabled.

Ready_uRTM_I2C Input High Ready signal for I2C buffer

uRTM_SCL Output I2C serial clock

uRTM_SDA In-Out I2C serial data

uRTM_PS Input High Present signal for uRTM board

Table 11: uRTM Interface Signals

If MCTA.4 functionality is not used (uRTM is not needed), the EN_uRTM_I2C signal has to be pulled down.




LEDsName Color Control Description

Blue Led Blue MMC Hot swap led

Led 1 Red MMC,Payload Status Led:off – ok

Red - error

Led 2 Green MMC On - power is present

Table 12: Available LEDs

Command Line Interface (CLI) The MMC provides a RS232 serial interface through which the commands of the Command

Line Interface (CLI) can be sent. On Windows systems, we recommend the use of “Tera Term” or “Hyperterminal” as the

terminal programs.

Terminal settings: • 19200 bits per second • data bits: 8 • parity: none • stop bit: 1

For file transfer the CLI implements the xmodem protocol.

List of CLI commands

gpio command Syntax: gpio [no as | de]Function: Displays or changes the state of the GPIOs. No = 1..4Example 1:%>gpio----------------------GPIO List-----------------------------------------GPIO Sensor Active-no---No---Type----Level---Name-------------State-----------Override----

* 1 32 Input Low GPIO1 0 De-Asserted* 2 33 Input High GPIO2 1 Asserted* 3 34 Output Low GPIO3 1 Asserted 1 Asserted* 4 35 Output Low GPIO4 1 Asserted




Example 2:%>gpio 2 as Done! GPIO2 Asserted!

help command Syntax: helpFunction: Displays a list of the available commands.

info command Syntax: helpFunction: Displays various information about the MMC from the Product Area of the FRU Information File: Manufacturer Name, Product Name, Product Number, Product Version, Serial Number, and also the IPMB Address and Slot Id. %>info Manufacturer Name: Generic Manufacturer Product Name: AMC test card Product Number: AMC7865 Product Version: Rev. B Serial Number: 000999 IPMB Address: 0x74 Slot Id: 2

payload_reset command Syntax: payload_reset [active_time_10_ms]Function: Asserts the Payload_Reset# signal. The signal is de-asserted automatically after the timeout specified as parameter has passed. By default, if the command is used without any parameter, the timeout is set to 20 ms. Example 1:%>payload_reset 100 Payload Reset Asserted! It will remain active for 1000 ms!

payload_signals command Syntax: payload_signalsFunction: Displays the state of the payload signals.Example 1:%>payload_signals Payload Signals status: SHDN_REQ#: De-Asserted SHDN_RDY#: Asserted PP_RST#: De-Asserted




reboot command Syntax: rebootFunction: Restarts the MMCExample 1:%>reboot MMC will restart! Please wait...

sensor command Syntax: sensorFunction: Displays information for the installed set of sensors.Example 1:%>sensor---------------------Sensor List-------------------------------no--Name--------------Value--Unit---State------------------* 1 Hot Swap Handle Open* 2 AN0 VCC 3.18 V Ok* 5 AN3 0.01 V Ok* 6 AN4 0.01 V Ok* 7 AN5 0.00 V Ok* 8 AN6 0.01 V Ok* 9 AN7 0.01 V Ok* 10 Temp1 25.00 deg C Ok* 11 Temp2 26.00 deg C Ok* 12 Temp3 26.00 deg C Ok* 32 GPIO1 0 De-Asserted* 33 GPIO2 0 De-Asserted* 34 GPIO3 0 De-Asserted* 35 GPIO4 1 Asserted

uptime command Syntax: uptimeFunction:Displays the amount of time which has past since the MMC became operational.Example 1:%>uptime Uptime=0 days 03:05:12

version command Syntax: versionFunction: Displays the MMC firmware version.Example1:%>version MMC FW 1.0

xmodem command Syntax: xmodem fru | sdr Function: Upload the FRU or the SDR file for the MMC using the xmodem protocol




Example 1:%>xmodem fru Please upload the file...%>...Done!

Updating the Firmware

The Firmware of the MMC can be updated using the on board bootloader.For uploading a file the following steps are required :

1. Connect to the CLI interface(Terminal settings: 115200 bits per second, data bits: 8, parity: none, stop bit: 1 )

2. Stop the bootloader by pressing 'x'

3. Issue the xmodem firmware command

%> xmodem firmware

4. Upload the *.firm file using the terminal program

5. After the file transfer is completed the firmware will be updated.


Illustration 11: Firmware update example



Updating the FRU and SDR filesIn order to configure the MMC two files are required: the FRU and SDR file. Both can be

easily created using the GUI software suites that accompany the MMC: FRU File compiler and SDR File compiler.

Creating new files or modifying old ones is really straight forward due to the graphical interface. For more details on all the available options please refer to the respective software user manuals.

After the files are created they have to be uploaded using the CLI.

For uploading a file the following steps are required :

1. Connect to the CLI interface(Terminal settings: 115200 bits per second, data bits: 8, parity: none, stop bit: 1 )

2. Wait for the bootloader timeout to finish and the firmware to start

3. Issue the xmodem command, using the correct parameter:

%> xmodem fru | sdr

4. Upload the file using the terminal program

5. After the file transfer is completed a confirmation message will be displayed. At this point the file has been saved and a reboot is required in order to activate the changes.

Order codesP07038-A – Preprogrammed microcontroller with MMC softwareSMW06A001 – MMC software evaluation AMC


Illustration 12: Tera Term Screen shot for sending a file using xmodem


mmc data sheet - productssamwayelectronic.com/products/files/56_mmc data sheet rev 1.4.pdf · mmc...

Documents