| Standards and Interfaces |
| CompactPCI Standard | PICMG 2.0 CompactPCI Rev. 3.0PICMG 2.9 System Management Bus Rev. 1.0PICMG 2.16 Packet Switching Backplane Rev.1.0 |
| Switch Fabric, PHY | Broadcom BCM56150 24-port GbE switch with two 10G SFP+ uplink portsBroadcom BCM54685 Octal-port 10/100/1000BASE-T PHYBroadcom BCM5221 10/100BASE-TX management port |
| Networking | 3x 10/100/1000BASE-T ports to front panel (BCM56150)20x 10/100/1000BASE-T ports to rear (BCM56150, 9x to J3, 11x to J5)1x inter-switch link 1000BASE-T2x 10G SFP+ ports for uplink through BCM561501x 10/100BASE-TX for management |
| Front Panel IO | 3x 10/100/1000BASE-T RJ-45 ports2x 10G SFP+ interfaces for uplink interface1x 10/100 RJ-45 management port1x UART port via RJ-45 |
| Rear IO | 20x 10/100/1000BASE-T ports to J3 and J5 |
| Mechanical & Environmental |
| Dimensions | 233.35mm x 160mm (L x W), 6U 4HP single slot |
| Operating Temp. | Standard: 0°C to 60°CETT version upon request |
| Storage Temp. | -50°C to 100°C |
| Humidity | 95% non-condensing |
| Shock | 15G peak-to-peak, 11ms duration, non-operating |
| Vibration | Non-operating: 2Grms, 5 to 500 Hz, each axis |
| Compliance | CE, FCC Class A |
| Power Consumption (under Linux) | Idle (w/o RTM): 12.2WFull loading (w/o RTM): 15WIdle (w/ RTM): 15.5WFull loading (w/ RTM): 20W |
Table 2-1: cPCI-6S10 Specifications
Specifications are subject to change without prior notice.
# 2.2 Board Layout
Figure 2-1: cPCI-6S10 Board Layout
| Description | Code |
| IPMI_SUCCESS | 0x00 |
| IPMI_NODE_BUSY | 0xC0 |
| IPMI_INVALID_COMMAND | 0xC1 |
| IPMI_COMMAND_INVALID_FOR_LUN | 0xC2 |
| IPMI_TIMEOUT | 0xC3 |
| IPMI_OUT_OF_SPACE | 0xC4 |
| IPMI_RESERVATION_INVALID_OR_CANCELED | 0xC5 |
| IPMI_REQUEST_DATA_TRUNCATED | 0xC6 |
| IPMI_REQUEST_DATA_LENGTH_INVALID | 0xC7 |
| IPMI_REQUEST_DATA_LENGTH_LIMIT_EXCEEDED | 0xC8 |
| IPMI_PARAMETER_OUT_OF_RANGE | 0xC9 |
| IPMI_CANNOT_RETURN_NUMBER_OF_REQUESTED_BYTE S | 0xCA |
| IPMI_REQUESTED_DATA_NOT_PRESENT | 0xCB |
| IPMI_INVALID_DATA_IN_REQUEST | 0xCC |
| IPMI_COMMAND_ILLEGAL_FOR_SPECIFIED_OBJECT | 0xCD |
| IPMI_CANNOT Provide_COMMAND_RESPONSE | 0xCE |
| IPMI_CANNOT EXECUTE_DUPLICATED_REQUEST | 0xCF |
| IPMI_SDR_REPOSITORY_IN_UPDATE_MODE | 0xD0 |
| IPMI_DEVICE_IN_FIRMWARE_UPDATE_MODE | 0xD1 |
| IPMI_INITIALIZATION_IN_PROGRESS | 0xD2 |
| IPMI_DESTINATION_UNAVAILABLE | 0xD3 |
| IPMI_INSUFFICIENT_PRIVILEGE_LEVEL | 0xD4 |
| IPMI_COMMAND_NOT_SUPPORTED_IN_PRESENT_STATE | 0xD5 |
| IPMI_READ_ONLY_PARAMETER | 0x82 |
| IPMI_UNSPECIFIED_ERROR | 0xFF |
Table 3-2: Response Codes
# Message Length
The IPMI standard overall message for “no-bridging” messages is specified as 32 bytes, maximum, including slave address. For bridging messages to other interfaces, Master Write-Read and Send Message commands are allowed to exceed 32-bytes on IPMI.
The table below shows the required interface length in IPMI 1.5. Some interfaces have extra recommended values in the IPMI specification.
| 1 | Time use[7] -1b = don't log[6] -1b = do not stop timer on set Watchdog Timer command.[5:3] – reserved[2:0] – timer use000b = reserved001b = BIOS FRB2010b = BIOS/POST011b = OS Load100b = SMS/OS101b = OEM110b – 111b = reserved |
| 2 | Timer actions[7] – reserved[6:4] – pre-timeout interrupt000b = none001b = SMI010b = NMI / Diagnostic Interrupt011b = Messaging interrupt110b,111b = reserved[3] – reserved[2:0] = timeout action000b = no action001b = Hard reset010b = Power down011b = Power cycle110b,111b = reserved |
| 3 | Pre-timeout interval in seconds. |
| 4 | Timer use expiration flags clear(0b = leave alone, 1b = clear timer use expiration bit)[7] – reserved[6] – reserved[5] – OEM[4] – SMS/OS[3] – OS/Load[2] – BIOS/POST[1] – BIOS FRB2[0] – reserved |
| 5 | Initial countdown value, lsbyte(100ms/count) |
| 6 | Initial countdown value, msbyte |
# Get Watchdog Timer
| 1 | Completion code |
| 2 | Timer use[7] -1b = don't log[6] -1b = timer started.0b = timer stopped.[5:3] – reserved[2:0] – timer use000b = reserved001b = BIOS FRB2010b = BIOS/POST011b = OS Load100b = SMS/OS101b = OEM110b – 111b = reserved |
| 3 | Timer actions[7] – reserved[6:4] – pre-timeout interrupt000b = none001b = SMI010b = NMI / Diagnostic Interrupt011b = Messaging interrupt110b,111b = reserved[3] – reserved[2:0] = timeout action000b = no action001b = Hard reset010b = Power down011b = Power cycle110b,111b = reserved |
| 4 | Pre-timeout interval in seconds. |
| 5 | Timer use expiration flags(1b = timer expired while associated ‘use’ was selected)[7] – reserved[6] – reserved[5] – OEM[4] – SMS/OS[3] – OS/Load[2] – BIOS/POST[1] – BIOS FRB2[0] – reserved |
| 6 | Initial countdown value, lsbyte(100ms/count) |
| 7 | Initial countdown value, msbyte |
| 8 | Preset countdown value, lsbyte |
| 9 | Preset countdown value, msbyte |
# Master Write-Read
| 1 | Bus ID:[7:4] channel number[3:1] bus ID, 0-based (always 000b for public bus)[0] bus type:0 = public (e.g. IPMB or PCI Management Bus)1 = private bus |
| 2 | [7:1] - Slave Address[0] - reserved. Write as 0. |
| 3 | Read count. Number of bytes to read, 1 based. 0 = no bytes to read. The maximum read count should be at least 34 bytes. This allows the command to be used for an SMBus Block Read. This is required if the command provides access to an SMBus or IPMB. Otherwise, if FRU SEEPROM devices are accessible, at least 31 bytes must be supported. Note that an implementation can support fewer bytes can be supported if none of the devices to be accessed can handle the recommended minimum. |
| 4:N | Data to write. This command should support at least 35 bytes of write data. This allows the command to be used for an SMBus Block Write with PEC. Otherwise, if FRU SEEPROM devices are accessible, at least 31 bytes must be supported. Note that an implementation is allowed to support fewer bytes if none of the devices to can handle the recommended minimum. |
# Response Data Fields
| 1 | Sensor number( FFh = reserved) |
| 2 | [7] – 0b = disable all event message from this sensor[6] – 0b = disable scanning on this sensor[5:4] – 00b = do not change individual enables01h = enable selected event messages10b = disable selected event messages11b = reserved |
| 3 | For sensors with threshold based events:[7] – 1b = select assertion event for upper non-critical going high[6] – 1b = select assertion event for upper non-critical going low[5] – 1b = select assertion event for lower non-recoverable going high[4] – 1b = select assertion event for lower non-recoverable going low[3] – 1b = select assertion event for lower critical going high[2] – 1b = select assertion event for lower critical going low[1] – 1b = select assertion event for lower non-critical going high[0] – 1b = select assertion event for lower non-critical going lowFor Sensors with discrete event:[7] – 1b = select assertion event for state bit 7[6] – 1b = select assertion event for state bit 6[5] – 1b = select assertion event for state bit 5[4] – 1b = select assertion event for state bit 4[3] – 1b = select assertion event for state bit 3[2] – 1b = select assertion event for state bit 2[1] – 1b = select assertion event for state bit 1[0] – 1b = select assertion event for state bit 0 |
| 4 | For sensors with threshold base events:[7:4] – reserved.[3] – 1b = select assertion event for upper non-recoverable going high[2] – 1b = select assertion event for upper non-recoverable going low[1] – 1b = select assertion event for upper critical going high[0] – 1b = select assertion event for upper critical going lowFor sensors with discrete events:[7] – reserved[6] – 1b = select assertion event for state bit 14[5] – 1b = select assertion event for state bit 13[4] – 1b = select assertion event for state bit 12[3] – 1b = select assertion event for state bit 11[2] – 1b = select assertion event for state bit 10[1] – 1b = select assertion event for state bit 9[0] – 1b = select assertion event for state bit 8 |
| 5 | For sensors with threshold based events:[7] – 1b = select deassertion event for upper non-critical going high[6] – 1b = select deassertion event for upper non-critical going low[5] – 1b = select deassertion event for lower non-recoverable going high[4] – 1b = select deassertion event for lower non-recoverable going low[3] – 1b = select deassertion event for lower critical going high[2] – 1b = select deassertion event for lower critical going low[1] – 1b = select deassertion event for lower non-critical going high[0] – 1b = select deassertion event for lower non-critical going lowFor Sensors with discrete event:[7] – 1b = select deassertion event for state bit 7[6] – 1b = select deassertion event for state bit 6[5] – 1b = select deassertion event for state bit 5[4] – 1b = select deassertion event for state bit 4[3] – 1b = select deassertion event for state bit 3[2] – 1b = select deassertion event for state bit 2[1] – 1b = select deassertion event for state bit 1[0] – 1b = select deassertion event for state bit 0 |
#
For sensors with threshold base events:
[7:4] – reserved.
[3] – 1b = select deassertion event for upper non-recoverable going high
[2] – 1b = select deassertion event for upper non-recoverable going low
[1] – 1b = select deassertion event for upper critical going high
[0] – 1b = select deassertion event for upper critical going low
For sensors with discrete events:
[7] – reserved
[6] – 1b = select deassertion event for state bit 14
[5] – 1b = select deassertion event for state bit 13
[4] – 1b = select deassertion event for state bit 12
[3] – 1b = select deassertion event for state bit 11
[2] – 1b = select deassertion event for state bit 10
[1] – 1b = select deassertion event for state bit 9
[0] – 1b = select deassertion event for state bit 8
# Response Fields
# 1
Completion code
# Get Sensor Event Enable
| 3 | For sensors with threshold based events:[7] – 1b = select assertion event for upper non-critical going high[6] – 1b = select assertion event for upper non-critical going low[5] – 1b = select assertion event for lower non-recoverable going high[4] – 1b = select assertion event for lower non-recoverable going low[3] – 1b = select assertion event for lower critical going high[2] – 1b = select assertion event for lower critical going low[1] – 1b = select assertion event for lower non-critical going high[0] – 1b = select assertion event for lower non-critical going lowFor Sensors with discrete event:[7] – 1b = select assertion event for state bit 7[6] – 1b = select assertion event for state bit 6[5] – 1b = select assertion event for state bit 5[4] – 1b = select assertion event for state bit 4[3] – 1b = select assertion event for state bit 3[2] – 1b = select assertion event for state bit 2[1] – 1b = select assertion event for state bit 1[0] – 1b = select assertion event for state bit 0 |
| 4 | For sensors with threshold base events:[7:4] – reserved.[3] – 1b = select assertion event for upper non-recoverable going high[2] – 1b = select assertion event for upper non-recoverable going low[1] – 1b = select assertion event for upper critical going high[0] – 1b = select assertion event for upper critical going lowFor sensors with discrete events:[7] – reserved[6] – 1b = select assertion event for state bit 14[5] – 1b = select assertion event for state bit 13[4] – 1b = select assertion event for state bit 12[3] – 1b = select assertion event for state bit 11[2] – 1b = select assertion event for state bit 10[1] – 1b = select assertion event for state bit 9[0] – 1b = select assertion event for state bit 8 |
| 5 | For sensors with threshold based events:[7] – 1b = select deassertion event for upper non-critical going high[6] – 1b = select deassertion event for upper non-critical going low[5] – 1b = select deassertion event for lower non-recoverable going high[4] – 1b = select deassertion event for lower non-recoverable going low[3] – 1b = select deassertion event for lower critical going high[2] – 1b = select deassertion event for lower critical going low[1] – 1b = select deassertion event for lower non-critical going high[0] – 1b = select deassertion event for lower non-critical going lowFor Sensors with discrete event:[7] – 1b = select deassertion event for state bit 7[6] – 1b = select deassertion event for state bit 6[5] – 1b = select deassertion event for state bit 5[4] – 1b = select deassertion event for state bit 4[3] – 1b = select deassertion event for state bit 3[2] – 1b = select deassertion event for state bit 2[1] – 1b = select deassertion event for state bit 1[0] – 1b = select deassertion event for state bit 0 |
| 6 | For sensors with threshold base events:[7:4] – reserved.[3] – 1b = select deassertion event for upper non-recoverable going high[2] – 1b = select deassertion event for upper non-recoverable going low[1] – 1b = select deassertion event for upper critical going high[0] – 1b = select deassertion event for upper critical going lowFor sensors with discrete events:[7] – reserved[6] – 1b = select deassertion event for state bit 14[5] – 1b = select deassertion event for state bit 13[4] – 1b = select deassertion event for state bit 12[3] – 1b = select deassertion event for state bit 11[2] – 1b = select deassertion event for state bit 10[1] – 1b = select deassertion event for state bit 9[0] – 1b = select deassertion event for state bit 8 |
# Re-arm Sensor Event
| 1 | sensor number (FFh = reserved) |
| 2 | [7] - 0b = re-arm all event status from this sensor. If 0, following parameterbytes are ignored, but should still be written as 0, if sent.[6:0] - reserved. Write as 000_0000b. |
| (3)* | For sensors with threshold based events:[7] - 1b = re-arm assertion event for upper non-critical going high[6] - 1b = re-arm assertion event for upper non-critical going low[5] - 1b = re-arm assertion event for lower non-recoverable going high[4] - 1b = re-arm assertion event for lower non-recoverable going low[3] - 1b = re-arm assertion event for lower critical going high[2] - 1b = re-arm assertion event for lower critical going low[1] - 1b = re-arm assertion event for lower non-critical going high[0] - 1b = re-arm assertion event for lower non-critical going lowFor sensors with discrete events:[7] - 1b = re-arm assertion event for state bit 7[6] - 1b = re-arm assertion event for state bit 6[5] - 1b = re-arm assertion event for state bit 5[4] - 1b = re-arm assertion event for state bit 4[3] - 1b = re-arm assertion event for state bit 3[2] - 1b = re-arm assertion event for state bit 2[1] - 1b = re-arm assertion event for state bit 1[0] - 1b = re-arm assertion event for state bit 0 |
| (4)* | For sensors with threshold based events:[7:4] - reserved. Write as 0000b.[3] - 1b = re-arm assertion event for upper non-recoverable going high[2] - 1b = re-arm assertion event for upper non-recoverable going low[1] - 1b = re-arm assertion event for upper critical going high[0] - 1b = re-arm assertion event for upper critical going lowFor sensors with discrete events:(00h otherwise)[7] - reserved. Ignore on read.[6] - 1b = re-arm assertion event for state bit 14[5] - 1b = re-arm assertion event for state bit 13[4] - 1b = re-arm assertion event for state bit 12[3] - 1b = re-arm assertion event for state bit 11[2] - 1b = re-arm assertion event for state bit 10[1] - 1b = re-arm assertion event for state bit 9[0] - 1b = re-arm assertion event for state bit 8 |
| (5)* | For sensors with threshold based events:[7] - 1b = re-arm deassertion event for upper non-critical going high[6] - 1b = re-arm deassertion event for upper non-critical going low[5] - 1b = re-arm deassertion event for lower non-recoverable going high[4] - 1b = re-arm deassertion event for lower non-recoverable going low[3] - 1b = re-arm deassertion event for lower critical going high[2] - 1b = re-arm deassertion event for lower critical going low[1] - 1b = re-arm deassertion event for lower non-critical going high[0] - 1b = re-arm deassertion event for lower non-critical going lowFor sensors with discrete events:(00h otherwise)[7] - 1b = re-arm deassertion event for state bit 7[6] - 1b = re-arm deassertion event for state bit 6[5] - 1b = re-arm deassertion event for state bit 5[4] - 1b = re-arm deassertion event for state bit 4[3] - 1b = re-arm deassertion event for state bit 3[2] - 1b = re-arm deassertion event for state bit 2[1] - 1b = re-arm deassertion event for state bit 1[0] - 1b = re-arm deassertion event for state bit 0 |
# (6)\*
For sensors with threshold based events:
[7:4] - reserved. Write as 0000b.
[3] - 1b = re-arm deassertion event for upper non-recoverable going high
[2] - 1b = re-arm deassertion event for upper non-recoverable going low
[1] - 1b = re-arm deassertion event for upper critical going high
[0] - 1b = re-arm deassertion event for upper critical going low
For sensors with discrete events:
(00h otherwise)
[7] - reserved. Ignore on read.
[6] - 1b = re-arm deassertion event for state bit 14
[5] - 1b = re-arm deassertion event for state bit 13
[4] - 1b = re-arm deassertion event for state bit 12
[3] - 1b = re-arm deassertion event for state bit 11
[2] - 1b = re-arm deassertion event for state bit 10
[1] - 1b = re-arm deassertion event for state bit 9
[0] - 1b = re-arm deassertion event for state bit 8
# Response Fields
#
Completion code
# Get Sensor Reading
| 1 | Completion code |
| 2 | SDR Version - version number of the SDR command set for the SDR Device.51h for this specification. (BCD encoded with bits 7:4 holding the Least Significant digit of the revision and bits 3:0 holding the Most Significant bits.) |
| 3 | Record count LS Byte - number of records in the SDR Repository |
| 4 | Record count MS Byte - number of records in the SDR Repository |
| 5:6 | Free Space in bytes, LS Byte first. 0000h indicates ‘full’, FFFEh indicates64KB-2 or more available. FFFFh indicates ‘unspecified’. |
| 7:10 | Most recent addition timestamp. LS byte first. |
| 11:14 | Most recent erase (delete or clear) timestamp. LS byte first. |
| 15 | Operation Support[7] - Overflow Flag. 1=SDR could not be written due to lack of space in the SDR Repository.[6:5] - 00b = modal/non-modal SDR Repository Update operation unspecified01b = non-modal SDR Repository Update operation supported10b = modal SDR Repository Update operation supported11b = both modal and non-modal SDR Repository Update supported[4] - reserved. Write as 0b[3] - 1b=Delete SDR command supported[2] - 1b=Partial Add SDR command supported[1] - 1b=Reserve SDR Repository command supported[0] - 1b=Get SDR Repository Allocation Information command supported |
Get SDR
| Command | Display list of commands |
| ASSert | Assert |
| BackGround | Execute a command in the background. |
| BCM | Set shell mode to BCM. |
| BCMX | Set shell mode to BCMX. |
| CASE | Execute command based on string match |
| CD | Change current working directory |
| cint | Enter the C interpreter |
| CONFig | Configure Management interface |
| CONSole | Control console options |
| CoPy | Copy a file |
| DATE | Set or display current date |
| DeBug | Enable/Disable debug output |
| DeBugMod | Enable/Disable debug output per module |
| DELAY | Put CLI task in a busy-wait loop for some amount of time |
| DEVice | Device add/remove |
| DISPatch | BCM Dispatch control. |
| Echo | Echo command line |
| EDline | Edit file using ancient line editor |
| EXIT | Exit the current shell (and possibly reset) |
| EXPR | Evaluate infix expression |
| FLASHINIT | Initialize on board flash as a file system |
| FLASHSYNC | Sync up on board flash with file system |
| FOR | Execute a series of commands in a loop |
| Help | Print this list OR usage for a specific command |
| HISTORY | List command history |
| IF | Conditionally execute commands |
| JOBS | List current background jobs |
| KILL | Terminate a background job |
| LOCal | Create/Delete a variable in the local scope |
| LOG | Enable/Disable logging and set log file |
| LOOP | Execute a series of commands in a loop |
| LS | List current directory |
| MKDIR | Make a directory |
| MODE | Set shell mode |
| MORe | Copy a file to the console |
| MoVe | Rename a file on a file system |
| NOEcho | Ignore command line |
| Pause | Pause command processing and wait for input |
| PRINTENV | Display current variable list |
| PWD | Print platform dependent working directory |
| RCCache | Save contents of an rc file in memory |
| RCLoad | Load commands from a file |
| REBOOT | Reboot the processor |
| RM | Remove a file from a file system |
| RMDIR | Remove a directory |
| SAVE | Write data to a file |
| SET | Set various configuration options |
| SETENV | Create/Delete a variable in the global scope |
| SHell | Invoke a system dependent shell |
| SLeep | Suspend the CLI task for specified amount of time |
| TIME | Time the execution of one or more commands |
| Version | Print version and build information |
# 5.4 Packet Manager
Users can use the ADLINK proprietary API tool, PacketManager, to configure the cPCI-6S10. For detailed information, please go to the ADLINK portal: www.adlinktech.com/Products/
AdvancedTCA/ARiPSoftware/PacketManager to download the PacketManager user’s manuals:
X ADLINK PacketManager Configuration Guide
X ADLINK PacketManager API Programming Guide
# Important Safety Instructions
For user safety, please read and follow all instructions, WARNINGS, CAUTIONS, and NOTES marked in this manual and on the associated equipment before handling/operating the equipment.
X Read these safety instructions carefully.
X Keep this user’s manual for future reference.
X Read the specifications section of this manual for detailed information on the operating environment of this equipment.
X When installing/mounting or uninstalling/removing equipment:
Z Turn off power and unplug any power cords/cables.
X To avoid electrical shock and/or damage to equipment:
Z Keep equipment away from water or liquid sources;
Z Keep equipment away from high heat or high humidity;
Z Keep equipment properly ventilated (do not block or cover ventilation openings);
Z Make sure to use recommended voltage and power source settings;
Z Always install and operate equipment near an easily accessible electrical socket-outlet;
Z Secure the power cord (do not place any object on/over the power cord);
Z Only install/attach and operate equipment on stable surfaces and/or recommended mountings; and,
Z If the equipment will not be used for long periods of time, turn off and unplug the equipment from its power source.
X Never attempt to fix the equipment. Equipment should only be serviced by qualified personnel.
A Lithium-type battery may be provided for uninterrupted, backup or emergency power.
Risk of explosion if battery is replaced with one of an incorrect type. Dispose of used batteries appropriately.
X Equipment must be serviced by authorized technicians when:
Z The power cord or plug is damaged;
Z Liquid has penetrated the equipment;
Z It has been exposed to high humidity/moisture;
Z It is not functioning or does not function according to the user’s manual;
Z It has been dropped and/or damaged; and/or,
Z It has an obvious sign of breakage.
# Getting Service
Ask an Expert: http://askanexpert.adlinktech.com
# ADLINK Technology, Inc.
9F, No.166 Jian Yi Road, Zhonghe District
New Taipei City 235, Taiwan
Tel: +886-2-8226-5877
Fax: +886-2-8226-5717
Email: service@adlinktech.com
# Ampro ADLINK Technology, Inc.
5215 Hellyer Avenue, #110
San Jose, CA 95138, USA
Tel: +1-408-360-0200
Toll Free: +1-800-966-5200 (USA only)
Fax: +1-408-360-0222
Email: info@adlinktech.com
# ADLINK Technology (China) Co., Ltd.
300 Fang Chun Rd., Zhangjiang Hi-Tech Park
Pudong New Area, Shanghai, 201203 China
Tel: +86-21-5132-8988
Fax: +86-21-5132-3588
Email: market@adlinktech.com
# ADLINK Technology GmbH
Hans-Thoma-Strasse 11
D-68163 Mannheim, Germany
Tel: +49-621-43214-0
Fax: +49-621 43214-30
Email: emea@adlinktech.com
Please visit the Contact page at www.adlinktech.com for information on how to contact the ADLINK regional office nearest you.
[🔗 Link to the original document](.cpci-6s10-50-15099-1000-10/cpci-6s10-50-15099-1000-10.pdf)