The C2K* is a 6U PICMG 2.16 compatible Single Board Computer intended for both system controller and peripheral slot applications. The board provides a CPU core, PICMG 2.16 compatible
backplane interface, and several peripheral devices/interfaces. The CPU core circuitry consists of
a Freescale MPC7448 or MPC7447A CPU operating at up to 1.4GHz, the Marvell® MV64460
PCI controller, up to 1GB of 167MHz DDR system memory, up to 512MB of boot memory, and
general support logic. An expanded feature list is below.
•6U PICMG 2.16 compatible Single Board Computer, with full hot-swap support per
PICMG 2.1.
•IPMI controller with IPMB0 serial interface, per PICMG 2.9. Peripheral and BMC functions.
•500MHz to 1.4GHz MPC7448 CPU, or 500MHz to 1.0GHz MPC7447A CPU with
Marvell MV64460 PCI Controller.
•Up to two 512MB banks of 167MHz DDR SDRAM, with ECC.
•PLX PCI 6254 PCI-to-PCI Interface for CPCI backplane.
•Two selectable 115kbps RS-232 or 2Mbps source-synchronous RS-422 ports available to
the backplane connectors.
•Six additional 460kbps source-synchronous RS-422/485 ports available to the backplane
connectors.
•Two 10/100/1000T Ethernet ports available to the backplane connector J3, wired per
PICMG 2.16.
•One 10/100/1000T Ethernet port available to the backplane J4.
•One 64-bit, PCI 33/66MHz or PCI-X 133MHz PMC site, with selectable +3.3V/+5.0V
VIO.
•One 64-bit PCI 33/66MHz PMC site with selectable +3.3V/+5.0V VIO.
•One bank of 64MB to 512MB Boot FEPROM with protected area feature.
•Three USB2.0 ports to the backplane connectors.
•One USB2.0 port to the front panel, on convection models.
•Thermal probe to monitor CPU die temperature and board ambient temperature.
Most issues can be resolved by referring to this manual. If any problems cannot be resolved,
please contact GEIP Technical Support:
If products must be returned, contact GE for a Return Material Authorization (RMA) Number.
This RMA Number must be obtained prior to any return.
RMA request forms can be obtained from:
www.ge-ip.com/rma
GE Technical Support is available at: 1-800-433-2682 in North America,
or +1-780-401-7700 for international calls. Requests for Technical Support can be sent to:
support.huntsville.ip@ge.com
Or, visit our website:
www.ge-ip.com
1.7 Related Documents
For more information on C2K components, refer to the following documents:
•C8051F120/1/2/3/4/5/6/7 C8051F130/1/2/3 Mixed Signal ISP Flash MCU Family—Silicon Laboratories Inc., Rev 1.3, August 2004
•M41T62 Serial Access Real-Time Clock with Alarms - STMicroelectronics, Rev 10.0,
November 2005
•LTC4244/LTC4244-1 Rugged, CompactPCI Bus Hot Swap Controllers—Linear Technology Corporation, 42441f, February 2004
•Maxim MAX6657/MAX6658/MAX6659 ±1°C, SMBus-Compatible Remote/Local Temperature Sensors with Overtemperature Alarms—Maxim Integrated Products, 19-2034;
Rev. 2, March 2002
Specifications
•ICMB 1.0 Rev 1.3—Intelligent Chassis Management Bus Bridge Specification, April
2003.
•IEEE Std. 802.3-2002—IEEE Standard for Information Technology- Telecommunications
and information exchange between systems- Local and metropolitan area networks - Specific requirements Part 3: Carrier sense multiple access with collision detection
(CSMD/CD) access method and physical layer specifications, March 2002.
•IEEE Std. 1101.2-1992(2001)—IEEE Standard for Mechanical Core Specifications for
Conduction-Cooled Eurocards, January 1993.
•IEEE Std. 1101.10-1996—IEEE Standard for Additional Mechanical Specifications for
Microcomputers using the IEEE Std 1101.1-1991 Equipment Practice, December 1996.
•IEEE Std. 1149.1-1990—IEEE Standard Test Access Port and Boundary Scan Architecture, June 1993.
Introduction
•IEEE Std. 1284-2000—IEEE Standard Signaling Method for a Bidirectional Parallel
Peripheral Interface for Personal Computers, September 2000.
•IEEE1386-2001—IEEE Standard for a Common Mezzanine Card (CMC) Family, June,
2001.
•IEEE1386.1-2001—IEEE Standard Physical and Environmental Layers for PCI Mezzanine Cards (PMC), June, 2001.
•IEEE Std. 802.3-2002—Part 3: Carrier Sense Multiple Access Collision Detection
(CSMA/CD) Access Method and Physical Layer Definitions, March 2002.
•Phillips Semiconductors—The I2C Specification, version 2.1, document 9398-393-40011,
January 2000.
•TIA / EIA-232-F-1997, Telecommunications Industry Association—Interface Between
Data Terminal Equipment and Data Circuit-Terminating Equipment Employing Serial
Binary Data Interchange, October 1997.
•TIA / EIA-485-F-1997, Telecommunications Industry Association—
•VITA Standards Organization, VITA 20-2001—American National Standard for Conduction Cooled PMC, August, 2001.
•VITA Standards Organization, VITA 30.1-2002—American National Standard for 2mm
Connector Practice on Conduction Cooled Euroboards, August, 2002.
•VITA Standards Organization, VITA 32-2002—Processor PMC Standard for Processor
PCI Mezzanine Cards, September 2002.
•VITA Standards Organization, VITA 39-2003—PCIX Auxiliary Standard for PMCs and
Processor PMCs, August 2003.
•Universal Serial Bus Specification, Revision 2.0, April 2000.
1. PICMG Specifications are available to PICMG members only. GEIP is not authorized to distribute copies of
these specifications. More information can be found at http://www.picmg.org.
2. VITA Specifications are available to VITA members only. GEIP is not authorized to distribute copies of these
specifications. More information can be found at http://www.vita.com.
3. Data sheets from hardware components can be downloaded from individual vendors web sites.
The C2K requires +5.0V and +3.3V from the CompactPCI backplane and Hot Swap functions
require +12V. Installed PMC modules may require ±12V.
2.4 Configurations Jumpers
The C2K provides the following configuration header/jumpers:
2.4.1 FLASH_WP# (P6)
P6 is a 2-pin Flash Write-Protect header/jumper that enables write-protection for the flash memory.
If a jumper is installed on P6, the FLASH_WP# signal is asserted preventing writes to the
flash ROM.
If a jumper is not installed on P6, the FLASH_WP# signal is de-asserted allowing writes the
flash ROM.
2.4.2 EM_BOOTSEL# (P7)
P7 is a 2-pin Emergency Boot Select header/jumper that determines which boot code the C2K will
execute after reset. Boot code provided by GEIP is stored in the upper 8MB of flash memory.
If a jumper is installed on the EM_BOOTSEL header (P7), the GEIP firmware will boot
from the GEIP provided emergency boot code stored in the Emergency Boot area of flash.
If a jumper is not installed on the EM_BOOTSEL header (P7), the firmware will jump to
user boot code area and begin executing custom boot code (see “Boot Code Selection” on page 4-3).
2.4.3 PCI VIO Select (P9, P12)
P9 and P12 are 3-pin header/jumpers that set the VIO for PCI Busses (PMC sites) at +3.3V or
+5V. P12 controls the VIO for PCI Bus 0 (PMC0) and P9 controls VIO for PCI Bus 1 (PMC1).
If a jumper is installed on pins 1 and 2, the VIO is set to +3.3V.
If a jumper is installed on pins 2 and 3, the VIO is set to +5V
P10 is a 2-pin COP Enable header/jumper that isolates the MPC7448 processor from the JTAG
Scan chain and connects the COP header (J6) to the processor to enable software debugging (see “JTAG circuitry” on page 4-18).
If a jumper is installed on P10, the on-board COP header (J6) is connected to the MCP7448
processor for software debugging.
If a jumper is not installed on P10, the COP header (J6) is disconnected from the processor.
2.4.5 C8051 Debug (P11)
P11 is a 2-pin C8051 Debug header/jumper that isolates the C8051 Microcontroller from the
JTAG Scan chain to enable IPMI software debugging.
If a jumper is installed on P11, the C8051 debugging is enabled.
If a jumper is not installed on P11, the C8051 debugging is disabled.
2.4.6 Header/Jumper Locations
For header/jumper locations, please refer to Figure 3-2 on page 3-2.
NOTE: With the exception of the PCI Bus VIO Select header/jumpers (P9 and P12), none of the
preceding header/jumpers need to have a jumper installed for C2K initial power-up.
2.5 Installation
Caution! Do not attempt to install the C2K in a backplane where the J4 connector is
bused or routed in accordance with the CompactPCI H110 specification. The C2K is
equipped with an IEC key to prevent such installation but if the backplane is not
keyed, installation is still possible.
Caution! Do not attempt to install the C2K in a Fabric slot of a PICMG 2.16 Packet
Switching Backplane. The C2K is equipped with an IEC key to prevent such
installation, but if the backplane is not keyed installation is still possible.
2.5.1 C2K C-style Installation
1. Remove the C2K from the static-safe envelope (see “E.S.D. Caution” on page 2-1).
2. Install optional PMC module(s) per manufacturers instructions (see “PMC Sites” on
page 4-14 for restrictions).
3. Configure the PMC VIO using VIO configuration jumpers P9, P12 (see “PCI VIO Select
(P9, P12)” on page 2-2).
4. Install the C2K in a 6U C-style CompactPCI-compliant chassis.
5. Slide the C2K into the slot guide, applying even pressure to the upper and lower extraction
handles. Be careful not to bend connector pins.
NOTE: The C-style C2K is Hot Swap-compliant and can be installed in and removed from
a powered-on Hot Swap-compliant chassis.
After sliding the C2K in the slot guide until the card engages the pins, wait for the blue
front-panel Hot Swap LED to turn off before closing the ejector handle switch (bottom
ejector handle).
6. Push up on the lower extraction handle and down on the upper handle to seat the CompactPCI connectors in the backplane connectors. The red tab on the extraction handles should
“click” when the board is locked into the chassis.
7. Tighten the small phillips-head screws embedded in the upper and lower extraction handles
to secure the C2K to the chassis.
8. Apply power to the chassis.
NOTE: C2K can be installed in a system controller or peripheral slot. If the C2K is not installed
in a system slot, a system controller card must be installed in the system slot to supply a PCI reference clock to C2K.
2.5.2 C2K N-style Installation
1. Remove the C2K SBC from the static-safe envelope (see “E.S.D. Caution” on page 2-1).
2. Install optional PMC module(s) per manufacturers instructions (see “PMC Sites” on page 4-14 for restrictions).
3. Configure the PMC VIO using VIO configuration jumpers P9, P12 (see “PCI VIO Select (P9, P12)” on page 2-2).
4. Install the C2K in a 6U N-style CompactPCI-compliant chassis.
5. Slide the C2K into the slot guide, applying even pressure to the upper and lower extraction
handles. Be careful not to bend connector pins.
6. Tighten upper and lower Wedge-Loks™ to 115inch/ounces using a 3/32-inch hex driver.
This secures the C2K in the system chassis and ensures proper heat conduction. Do not
overtighten.
7. Apply power to the chassis.
NOTE: C2K can be installed in a system controller or peripheral slot. If the C2K is not installed
in a system slot, a system controller card must be installed in the system slot to supply a PCI reference clock to C2K.
The C2K includes a universal boot loader (U-Boot) utility that is pre-installed in flash ROM.
U-Boot is designed to work with any operating system including Linux and VxWorks® and performs the following functions:
•Load the O/S kernel from Ethernet, user flash area, or USB
•Program the user flash
•Program the boot flash (self update)
•Load the O/S kernel from user flash
•Set the Real-Time Clock
•Save boot parameters in EEPROM
•Configure the MV64460 Memory Controller
2.6.1 Installation
The C2K is shipped with U-Boot pre-installed in flash memory.
2.6.2 Initialization
The C2K has been initialized during production and testing.
2.6.3 Commands
The following is a summary of commands the U-Boot utility uses for the C2K:
?
autoscr
base
bdinfo
bootboots default, e.g., run ‘bootcmd’
bootdboots default, e.g., run ‘bootcmd’
bootelf
bootm
bootp
bootvx
cmp
coninfo
cp
crc32
date
echo
erase
flinfo
alias for ‘help’
runs script from memory
prints or sets address offset
prints Board Info structure
boots from an ELF image in memory
boots application image from memory
boots image from the network using BootP/TFTP protocol
prints board information used by U-Boot, such as memory addresses and sizes, clock frequencies
and MAC addresses.
coninfo
C2K=> help coninfo
cp [.b, .w, .l] source target count:
displays console I/O device information.
flinfo
C2K=> help flinfo
flinfo:
Installation
prints information for all flash memory banks.
flinfo N:
prints information for flash memory bank # N.
iminfo
C2K=> help iminfo
iminfo addr [addr ...]:
prints header information for application image starting at address ‘addr’ in memory; this includes verification of the image contents (magic number, header and payload checksums).
imls
C2K=> help imls
imls:
prints information about all images found at sector boundaries in flash.
help
C2K=> help
help [command ...]:
shows help information (for ‘command’).
prints online help for the monitor commands.
without arguments, it prints a short usage message for all commands.
to get detailed information about specific commands, type ‘help’ with one or more command names
as arguments.
BATT+:External battery input. The +3.3V supply from the system is used as a battery backup
a.
for the NVRAM and RTC devices.
BIT_PASS#:Built-In Test (BIT) Status output. At power-up or after reset, this signal is de-asserted
b.
(high). After the firmware Built-In-Test has successfully completed, this signal is
asserted (low).
EM_BOOTSEL#:Emergency Boot Select input. When this signal is not asserted (high), the boot code is
c.
allowed to exit GEIP-provided boot code. When this input is asserted (low), the boot
code continues to execute from GEIP-provided (Emergency Boot code) boot code.
This signal is pulled high.
GPIO:General purpose I/O (GPIO_4–GPIO_14)
d.
ICMB:Inter-Chassis Management Bus
e.
NMI#:GPIO_15 or Non-Maskable Interrupt input. To make this signal non-maskable, the
f.
CPU_MRS[EE] interrupt mask bit, as well as the bridge mask, must be set.
PB_RST_IN#:Push-button reset button signal from backplane (C2K-TM).
PMC1_VIO: +5V or +3.3V according to PMC1 VIO Selection header/jumper—P9.
i.
PMC_JTAG_
j.
EN#:
Includes the PMC sites in the JTAG Scan chain. When this signal is asserted (low),
the PMC modules installed on the PMC sites are included in the JTAG Scan chain.
NOTE: This function is intended to be used during manufacturing test time.
PROCFAIL#:GPIO_14 or Processor Fail output. This signal is asserted when a processor failure
k.
(watchdog timer expire) has been detected.
ROM_WP#:Flash write-protect input. When asserted (active low) the flash memory is write-pro-
l.
tected. This signal is pulled up enabling writes to flash memory for backplanes that do
not support a write-protect feature.
Serial ATA:1.5Gb/s serial ATA (SATA1, SATA2).
m.
Serial I/O:These ports are configured as RS-232 (transmit and receive signals only) (COM1,
The C2K includes an on-board 2 x 10-pin COP Port header (J6) for stepping through code at the
MPC7448 processor. The VDD_SENSE signal is fixed at +2.5V. Table 3-10 shows the COP Port
pin assignments.
NOTE: A jumper must be installed on the COP_EN header/jumper (P10) to enable the J6 interface (see “COP_EN (P10)” on page 2-3).
Table 3-10 COP Port (J20) pin assignments
PinAssignmentPinAssignment
12
COP_TDOCOP_QACK#
34
COP_TDICOP_TRST#
56
RUN_STOP#VDD_SENSE
78
COP_TCKCOP_CKSTP_IN#
910
COP_TMSn/c
1112
COP_SRESET#GND
1314
COP_HRESET#KEY
1516
CKSTP_OUT#GND
1718
n/cn/c
1920
n/cn/c *
* This pin may be pulled to ground by the COP adapter cable
to automatically enable the COP port instead of installing a
jumper on COP_EN header P10.
3.2.5 JTAG Port (J7) Pin Assignments
The C2K includes an onboard 2 x 5-socket JTAG header (J7) for FPGA programming and JTAG
Boundary Scan Chain.
3.2.7 Serial I/O COM Port Termination Header (P15) Pin Assignments
The C2K provides a 2 x 8-pin header (P15) for enabling line terminations for COM5–COM8
RS-422/485 ports. Line termination for a port is enabled when a jumper is installed across the corresponding pins shown in Table 3-13.
NOTE: Receive termination must always be enabled when a port is configured for RS-422 operation.
Table 3-13 Serial I/O COM port termination header (P15) pin assignments
The C2K is driven by the MPC7447A /MPC7448 PowerPC G4 processor, a high-performance,
superscaler, low-power, 32-bit processor based on PowerPC RISC architecture. The processor
core can run at speeds from 500MHz to 1.4GHz, and includes separate 32kB L1 instruction and
data caches. It also includes an on-chip 512kB/1MB L2 cache.
The MPC7448 processor is connected to the MV64460 PowerPC System Controller through a
64-bit 167MHz system bus operating in MPX mode. The system bus provides address decoding,
data transfer operations, and interrupt signaling.
4.2 DDR SDRAM
The C2K provides system memory in configurations of 512MB on the standard build, or 256MB,
or 1GB densities available as build options. The DDR SDRAM is organized in a memory array of
one bank (256MB/512MB) or two banks (1GB) of devices. System memory is controlled by the
MV64460’s DDR SDRAM Memory Controller through a 64-bit 167MHz Memory Bus. System
memory includes full Error Checking and Correction (ECC) protection with one bit error detect
and correct; multiple bit error detect and report functions.
4.3 Flash Memory
The C2K includes 64–512MB of flash memory configured in one 32-bit bank of 8-bit Spansion
MirrorBit™ flash ROM devices. The flash devices are located on the 32-bit asynchronous parallel
Device Bus, mastered by the MV64460 System Controller. The processor can read, erase, and
program the contents of flash memory.
4.3.1 Flash Write Protection
Operating firmware can write and erase data from the flash devices. Each flash device provides
‘chip erase’ functionality as well as separate erase and write protection of sectors. The C2K
provides several write-protect mechanisms to prevent boot code data loss during power cycling
and system initialization. Flash write-protection functions are OR’ed together so that any
write-protection function can override other write-protection functions for that area of flash.
The C2K provides the following write-protection options:
NOTE: Some operating systems or environments, such as Linux, require the ability to identify
the flash ROM device during the boot process. This requires writing to the command interface to
retrieve the device ID. If the Permanent Write Protect, External Write-Protect, On-board
Write-Protect, or Device Write-Protect functions are active, the device ID cannot be retrieved.
The FLASH_SIZE bits (bits 9, 8) in the FPGA Status Register (
see “Status Register” on
page 5-8) provide the flash ROM size, which a custom OS can use to determine the correct device
ID.
Permanent Write-Protect
The C2K includes a jumper-resistor site to permanently write-protect all flash ROM devices. If
the resistor is installed, all flash memory write and erase operations are permanently disabled. The
resistor is typically unpopulated.
NOTE: This resistor option is configured during the manufacturing process on a special-order
basis. This is not a user-configurable option.
External Write-Protect
The C2K provides a ROM_WP# pin at the backplane (cPCI_J5 A8) to allow an external
mechanism to enable global write-protection.
If the ROM_WP# signal is asserted (active low), all write/erase functions are disabled.
If the ROM_WP# signal is de-asserted, all write/erase functions are enabled.
NOTE: GEIP offers an optional C2K-TM companion board that provides a ROM_WP#
header/jumper for asserting the backplane ROM_WP# signal.
On-board Write-Protect
The C2K provides an on-board FLASH_WP# header/jumper site (P6) for manually asserting the
ROM_WP# signal to enable global flash write-protection (see “FLASH_WP# (P6)” on page 2-2).
If the ROM_WP# signal is asserted (active low), all write/erase functions are disabled.
If the ROM_WP# signal is de-asserted, all write/erase functions are enabled.
Device Write-Protect
A device driver embedded in firmware and the FPGA Control Register bit—ROM_WP (bit 1)
(see “Control Register” on page 5-9) provide an internal mechanism that write-protects the flash
ROM during hardware reset. The ROM_WP bit is forced to set (write-protect enabled) during
hardware reset, to prevent inadvertent write accesses to the flash ROM devices until after BSP
firmware has initialized the board and started OS operation. Firmware must clear this bit before
performing any write or erase operations to the associated flash ROM.
Boot Area Write-Protect
The FPGA Control Register bit—BOOT_AREA_WP (bit 0) (see “Control Register” on
page 5-9) enables write-protection for the flash ROM emergency boot area, at and above the
upper 8MB of flash memory, to protect emergency boot code.
If the BOOT_AREA_WP bit (bit 0) is set (1), the boot area of Flash ROM is write-protected.
If the BOOT_AREA_WP bit (bit 0) is cleared (0), the boot area is not write-protected.
When the boot area write-protect is enabled, the user area can still be modified.
a.
The flash ROM must be mapped to an even 8MB boundary for the boot area write-protect to work correctly.
b.
Since the flash ROM device erase command is issued at address 0x0, a device erase will erase the boot area.
c.
4.3.2 Boot Code Selection
Flash memory is segmented into two sections: emergency boot code area (upper 8MB of flash)
and user boot code area (remaining memory space). GEIP provides emergency boot code that is
stored in the emergency boot code area. Application developers can store custom boot code or
other custom software in the user boot code area.
Selection of which boot code is used to boot the C2K is controlled through the EM_BOOT_SEL
bit (bit 6) in the FPGA Status Register (see “Status Register” on page 5-8). Upon power-up or
after a hard reset, the GEIP-provided firmware will check the EM_BOOT_SEL bit to determine
which boot code area to execute boot code from. When the EM_BOOT_SEL bit is cleared, the
processor will jump to the user boot code area and boot up using the code stored in that area,
provided that a boot description header with a valid checksum is detected. If the bit is set, the
processor will continue to execute boot code from the emergency boot code area.
The EM_BOOTSEL# signal controls the setting of the EM_BOOT_SEL bit. The C2K provides
two methods for asserting (driving low) the EM_BOOTSEL# signal: an 2-pin on-board
header/jumper site (P7) (see “EM_BOOTSEL# (P7)” on page 2-2), or an external jumper (see Note b. below) attached to a backplane connector pin (cPCI_J5 B9).
Boot Code Selection Notes:
A jumper is not typically installed on P7, however a jumper will need to be installed on P7 for initial power-up.
a.
GEIP offers an optional C2K-TM companion board that provides a EM_BOOTSEL# header/jumper for
b.
asserting the backplane EM_BOOTSEL# signal.
4.4 PCI Busses
The C2K includes two PCI busses controlled by the MV64460 System Controller’s PCI Bus
interface:
PCI Bus 0 is configured for 64-bit 33/66MHz PCI or 133MHz PCI-X operation and is dedicated
to the PMC0 site.
PCI Bus 1 is configured for 64-bit 33/66MHz PCI 2.2 and is shared by PMC1 site, the USB 2.0
Controller through the PCI2050B PCI/PCI Bridge, the GD31244 Serial ATA Controller, and the
PCI 6254 cPCI Bridge.
Both PCI busses can be configured for +3.3V or +5V VIO through on-board 3-pin PCI VIO
Configuration jumpers P12 for PCI Bus 0 and P9 for PCI Bus 1
NOTE: Each PCI Bus is limited to 33MHz PCI when configured for +5V VIO.
The C2K provides a 32-bit 133MHz asynchronous Device Bus mastered by the MV64460 System
Controller. The Device Bus services the following devices:
•FPGA
•Flash memory
4.6 SMBus
The MV64460 System Controller includes a SMBus Host Controller to master an on-board serial
interface. The SMBus hosts the following slave devices:
•Temperature Sensor
•Board Configuration EEPROM
•User Configuration EEPROM
•RTC
4.7 Gigabit Ethernet
The C2K provides three 10/100/1000Base-T Ethernet ports to the backplane: ETH0 and ETH1 to
cPCI_J3 and ETH2 to cPCI_J4. The MV64460 System Controller provides three Ethernet Media
Access Controllers (MACs). The VSC8244 PHY provides the physical interfaces.
The C2K provides nine on-board LEDs to monitor link activity and data transfer speeds for the
three Ethernet ports as described in Table 4-1.
The MV64460 System Controller includes two Multi-Protocol Serial Controllers (MPSC),
mapped through the MPP interface (see “Multi-Purpose Pins (MPP)” on page 5-3), that provide
two serial I/O ports (COM1 and COM2) to the backplane. Each port is provided with separate
RS-232 and RS-422 transceivers.
When either or both of these ports are configured as RS-232, they can operate at transfer rates up
to 115kb/s and are routed to the backplane through cPCI_J5.
When either or both of these ports are configured as RS-422, they can operate at rates up to
460kb/s in asynchronous mode or up to 2Mb/s in source-synchronous mode and are routed to the
backplane through cPCI_J4.
These ports are configured (RS-232/422) through the COM1_TYPE (bit 13) and COM2_TYPE
(bit 12) bits in the FPGA Control Register (see “Control Register” on page 5-9).
4.8.2 Serial RS-232/422 Ports—COM3, COM4
The FPGA provides multiple USART channels which include COM3 and COM4. These serial
ports can also be independently configured as RS-232 or RS-422.
When either or both of these ports are configured as RS-232, they can operate at transfer rates up
to 115kb/s and are routed to the backplane through cPCI_J4.
When either or both of these ports are configured as RS-422, they can operate at rates up to
230kb/s in asynchronous mode or up to 460kb/s in source-synchronous mode and are routed to
the backplane through cPCI_J4.
These ports are configured (RS-232/422) through the COM3_TYPE (bit 7) and COM4_TYPE
(bit 6) bits in the FPGA Control Register (see “Control Register” on page 5-9).
4.8.3 Serial RS-422/485 Ports—COM5–COM8
The FPGA USARTs also provide four independently configurable RS-422/485 serial ports:
COM5–COM8.
When any of these ports are configured as RS-485, they can operate at transfer rates up to 230kb/s
in asynchronous mode and are routed to the backplane through cPCI_J4.
When any of these ports are configured as RS-422, they can operate at rates up to 230kb/s in
asynchronous mode or up to 460kb/s in source-synchronous mode and are routed to the backplane
through cPCI_J4.
NOTE: Serial I/O COM Port Termination Header (P15) enables line termination for
COM5–COM8 serial ports configured as RS-485. When these ports are configured as RS-422, the
receive termination must always be enabled and the transmit termination must always be disabled.
The C2K includes an ISP1563 Hi-Speed USB PCI Host Controller, attached to PCI Bus 1 through
the PCI2050B PCI/PCI Bridge, that provides three USB 2.0 ports—USB1, USB2, and USB3—to
the backplane through the cPCI_J4 connector. A fourth USB port—USB4— is routed to a
standard front-panel Type A USB connector (P8) on C-style versions only.
The USB 2.0 Controller supports three data transfer speeds—USB 1.0 (1.5MHz), USB 1.1
(12MHz), and USB 2.0 (480MHz).
The PCI2050B PCI/PCI Bridge provides a 32-bit 33MHz PCI bus to the USB 2.0 Controller to
prevent the USB 2.0 Controller from limiting PCI Bus 1 to 33MHz.
The PCI2050B arbitrates the secondary PCI bus with its internal arbiter. The USB 2.0 Controller
on the secondary bus uses the arbiters request/grant pair 0# and AD bit 16 for IDSEL. The
PCI2050B secondary clock outputs are not used and should be disabled by application software.
The C2K provides four on-board green LEDs to diagnose USB port activity as listed in Table 4-2.
Table 4-2 USB on-board indicator LEDs
LEDUSB Port LED Indication
D12USB1LED Off:Port not operational
D13USB2LED On:Port fully operational
D14USB3LED Blinking:Software attention
D15USB4 (C-style versions only)
4.10 General-Purpose I/O
The C2K provides 16 General-Purpose I/O (GPIO) lines to the cPCI backplane: GPIO_0–3 to
cPCI_J4 and GPIO_4–15 through cPCI_J5. The FPGA provides internal registers for status,
control and interrupt masking (see “GPIO Registers” on page 5-16). Each GPIO line can be
configured as a input or output. The inputs can be configured as inverted or non-inverted and the
outputs can be configured as TTL or open-drain. Each line can generate an interrupt that can be
masked through the FPGA Interrupt Mask Register. Each interrupt can be configured as
edge-triggered or level-triggered. The GPIO lines are +5V tolerant.
4.11 Serial ATA I/O
The C2K provides two 1.5Gb/s Serial ATA 1.0 interfaces to the backplane through cPCI_J5. A
GD31244 Quad Serial ATA Host Controller located on PCI Bus 1 provides termination for the
SATA ports. The SATA controller’s default configuration is set for Master/Slave operation.
NOTE: Each SATA interface is capable of data transfer rates of 150MB/s, however, the PCI interface must be operating at 66MHz to sustain the combined transfer rate of 300MB/s for both interfaces. If a 33MHz PMC module is installed on PMC1, the SATA transfer rate will be degraded.
The C2K provides two on-board LEDs to monitor SATA interface activity. The LED output is as
shown in Table 4-3.
NOTE: On Rev. 10 and Rev. 20 level boards, D10 indicates activity on either SATA1 or SATA2
and D11 is never on.
4.12 Counter/Timers
The MV64460 System Controller provides sixteen 32-bit general-purpose timers derived from the
FPGA (see “Counter/timers” on page 5-37).
4.12.1 Watchdog Timer
The MV64460 also includes a 32-bit programmable watchdog timer that can reset the processor if
development application software forces the processor into an unstable condition. The watchdog
timer is referenced from the 133MHz TCLK reference. It has a maximum interval duration of
approximately 32 seconds.
The MV64460 watchdog circuitry can output the WDOG_NMI and WDOG_EXP signals
mapped to the MV64460 MPP pins. If the watchdog counter reaches the value programmed in the
Watchdog Value Register NMI_VAL field, the watchdog timer asserts the WDOG_NMI output to
the FPGA, which generates a SMI# to interrupt the processor. If the watchdog timer expires, it
asserts the WDOG_EXP output to the FPGA, which will initiate a board reset as shown in Figure
4-1 on page 4-8.
The FPGA provides internal registers for the following functions (see “FPGA Registers” on
page 5-4):
•GPIO
•Counters/timers
•Interrupt Aggregation
•Reset management
•USARTs
•Device Bus management
•SMI#
4.13.1 System Management Interrupt
The FPGA can generate the System Management Interrupt (SMI) input to the processor. The SMI
is a level-sensitive processor input which the FPGA asserts if one or more of the following
interrupt sources are asserted:
•Backplane NMI# (maskable)
•Backplane DEG# (maskable)
•Backplane FAL# (maskable)
•Watchdog NMI# (maskable)
Each interrupt source is maskable through the FPGA SMI Mask Register (see “SMI Mask Register” on page 5-14). These mask bits are set at reset.
The C2K includes an M41T62 RTC device to provide and a real-time clock feature for CPU
timekeeping functions. The C2K provides the BATT+ input from the backplane to supply +3.3V
battery backup power to the RTC when the board is powered-down.
NOTE: Power is not maintained to the real-time clock functions when the C2K is removed from
the system.
4.15 CompactPCI Backplane Interface
The C2K employs the PCI 6254 Dual Mode PCI/PCI Bridge to transfer PCI data between the PCI
Bus 1 and the backplane PCI 2.2 compatible cPCI bus. The PCI 6254 provides all the power entry,
system control, and cPCI bus interface wiring defined for 6U system controller and peripheral slot
boards defined in PICMG 2.0. Interface functionality for system controller and peripheral slot
applications is selected in hardware based on slot address information in the backplane.
The PCI 6254 supports either 33MHz and 66MHz bus clocks on the backplane, using 32-bit or
64-bit data transfers and provides bus arbitration logic support for seven peripheral slots. The PCI
6254 also supports 33/66MHz operation on the internal (primary side) PCI bus interface.
NOTE: If the internal PCI bus (primary interface) is operating at 33MHz, the cPCI bus (secondary interface) also operates at 33MHz. PCI Bus 1 will operate at 33MHz when it is configured to
+5V VIO or when a 33MHz PMC module is installed on PMC1.
The PCI 6254 is configured to operate in one of two modes: Universal Transparent Mode and
Universal Non-transparent Mode. When the C2K is installed in a system slot, it functions as a
system controller and the PCI 6254 operates in the Universal Transparent Mode. In this mode,
PCI transactions pass transparently from the primary interface to the secondary interface.
When the C2K is installed in a peripheral slot, the PCI 6254 operates in the Universal
Non-transparent mode. To the PCI host, which would be located on the system controller board,
the PCI 6254 appears to be another PCI device. The mode in which the PCI 6254 operates is
controlled by the SYSEN# signal from the backplane (cPCI_J2 C2). SYSEN# is asserted when
the C2K is installed in a system slot and de-asserted when the C2K is installed in a peripheral slot.
NOTE: The cPCI 64EN# backplane signal is connected to the PCI 6254 64EN# input pin. The
state of 64EN# can be determined by an internal PCI 6254 register. If the 64EN# indicates 32-bit
only, no 64-bit accesses should be allowed to the PCI 6254 primary side.
The C2K includes cPCI full Hot Swap and IPMI features with the following components.
•Hot Swap Controller (HSC)
•CPLD
•PCI 6254 cPCI Bus Bridge (backplane bridge)
•C8051F127 Microcontroller (C8051)
4.16.1 Hot Swap Controller
The LTC4244-1 Hot Swap Controller (HSC) allows the C2K to be installed or removed from a
CompactPCI chassis while the chassis is powered-up. The HSC provides the PCI signal
pre-charge voltage and controls the C2K’s main power. The HSC also monitors the main on-board
voltage rails: +5V, +3.3V, and ±12V.
4.16.2 CPLD
The C2K provides a small CPLD to assist the HSC. The CPLD monitors the M66EN, PCIXCAP,
BDSEL#, and PCI_RST# signals from the backplane to control the blue front-panel Hot Swap
LED and generates the HEALTHY# signal to the backplane. The CPLD also initiates the board
power-on sequencing.
4.16.3 PCI 6254 cPCI Bus Bridge
The PCI 6254 provides ENUM# support and monitors ejector handle status and Geographic
Address inputs. It also contributes to the software control of the blue front-panel Hot Swap LED.
4.16.4 C8051 Microcontroller
The IPMI Controller consists of the C8051F127 Microcontroller (C8051), support logic, and
GEIP’s IPMI software. The C8051 Microcontroller includes the following features:
•128kbytes of internal flash storage for program code
•8kbytes of internal SRAM for scratchpad and general use
•Full-duplex asynchronous UART
•Five counter/timers
•24.5MHz oscillator
•Watchdog timer
•JTAG/Debug interface
C8051 8-bit I/O Ports
The C8051 Microcontroller includes four 8-bit I/O ports. Port 0 and Port 1 provide I/O for
external SRAM and UART signals. Port 0 also provides the on-board SPI Bus and IIC Bus
interface used for IPMI features. Port 1 provides several device chip selects and a serial interface
for communicating to MPC7448 processor. Port 2 and Port 3 are configured as multiplex
address/data buses for the external SRAM. lists the pin assignments for the four I/O ports.
An external 128kB SRAM is attached to the C8051 Controller by an 8-bit multiplexed A/D Bus
created from Port 2 and Port 3, and portions of Port 0 and Port 1. The SRAM_CS# signal on
Port 1 provides access to the SRAM. The RAM is organized as two 64kB pages. The IO1
Controller SRAM_A16 signal selects the page prior to access.
External UART
An external 16550-compatible UART is also attached to the C8051 Controller through the A/D
bus to provide the ICMB interface. The C8051 software implements the ICMB Bridge feature
described in ICMB 1.0. The external UART and a half-duplex RS-485 transceiver provide the
physical layer.
The UART_CS# signal on Port 1 provides access to the UART. The UART_INT# signal indicates
the UART has asserted an interrupt. The crossbar must map UART_INT# to the INT0# interrupt.
SPI-based EEPROM
An SPI-based 64kB EEPROM provides non-volatile storage for data records and event logs. The
EEPROM_CS# signal on Port 1 provides access to the EEPROM.
SPI-based I/O
Two SPI-based I/O controllers monitor and control signals as listed in Table 4-5 on page 4-13.
The IO1_CS# and IO2_CS# signals provide access to the I/O controllers. The I/O controller
perform two functions: provide sufficient I/O to support C8051 features, and hold the state of the
output signals (UART_RESET#, FPGA_INT#, and BRD_RST#) during a watchdog-initiated
C8051 Controller reset.
Table 4-5 lists the I/O controller pin assignments.
Table 4-5 I/O controller pin assignments
PinIO1 AssignmentsIO2 Assignments
9SRAM A16PGOOD_1.2V
8ICMB_ARB_CTLPGOOD_1.25V
7ICMB_ARB_SELPGOOD_1.5V
6SYSEN#PGOOD_2.5V / 1.1V
5BDSEL#HSC_PWRGOOD#
4GA4FPGA_INT#
3GA3BRD_RESET#
2GA2YELLOW_LED
1GA1UART_RST#
0GA0SMB_ALERT#
NOTES:
The PCI_PRESENT# input does not directly affect the C2K operation. The Hot-Swap function operates as
a.
normal, whether the backplane PCI_PRESENT# signal is asserted or not.
The ALERT# input is an optional signal used to support legacy IPMI devices. This signal is made available to
b.
the IPMC, should the feature be demanded. A pull-up on the C2K ensures this signal remains in the negated
state, if unused.
The SYSEN#, BDSEL#, and GA4-0 inputs are monitored, and used as described in PICMG 2.9, PICMG 2.1,
c.
and PICMG 2.0. BDSEL# may be driven by the C8051 under certain conditions.
The PWRGOOD monitor inputs, PGOOD_V12, PGOOD_V125, PGOOD_V15, PGOOD_V25_V11 are all
d.
active-high power-good indications from the on-board regulators. The HSC_PWRGOOD# input is the HSC
active-low power-good indication that represents valid power for on-board +5V, +3.3V, and +12V supplies.
BRD_RST# is an open-drain output with an external pull-up that is used to initiate a board reset. The C2K is
e.
held in reset while this signal is active.
Functional Blocks
IIC Bus
The HSC uses the IIC Bus to generate the Hot Swap-compliant IPMB0 Bus.
Serial Interface
The internal UART1 must be connected to Port 1 through the crossbar to provide a serial interface
for in-system programming and other messaging between the MPC7448 processor and the C8051
Controller. This serial interface is connected to the FPGA UART #8.
Analog Compare Inputs
The CP0+/- and CP1+/- inputs are intended to works as digital input monitors. CP1 is attached to
the M66EN_COS# signal from the CPLD. When a change of M66EN state is encountered during
operation, the IMPC issues an orderly shutdown and reboot of the C2K
. The CP0+/- input
monitors the ICMB receive data, to support the ICMB arbitration feature.
D/A Outputs
The C8051 Controller provides two digital-to-analog converter outputs. The C2K does not use
these outputs.
The C8051 Controller provides eight analog-to-digital converter inputs. The C2K does not use
these inputs.
JTAG Interface
The C8051 Controller provides a JTAG interface for in-system device programming, debugging,
and boundary-scan.
4.17 PMC Sites
The C2K hosts either two single-wide PMC sites or one double-wide site that include the
following features:
•Both PMC sites support IEEE1386.1 PMC modules.
•Both PMC can dissipate a maximum of 15W can be dissipated from modules on sites
across all power rails. This may be distributed as 15W on a single PMC site or 7.5W
distributed across two PMC sites.
•Both PMC sites support N-style PMC modules per VITA 20.
•The cPCI backplane interface provides all power and ground signals.
•Each PMC site’s JTAG interface is biased “inactive” and as such is not available to the
C2K JTAG Scan chain.
•BUSMODE[4–2] signals are fixed to “Return ‘Card Present’ if PCI-capable and uses PCI
Protocol” mode as defined in IEEE 1386-2001. The C2K ignores BUSMODE[1].
•+3.3Vaux is not supported.
•Reserved pins are not connected.
•Reset signals from each PMC site are isolated from the C2K, such that the C2K can drive
the PMC reset, but the PMC reset will not be acknowledged by the C2K. This prevents the
C2K from being reset when an installed PMC module initiates a reset.
4.17.1 PMC0 Site Features
•PMC0 is located on dedicated PCI Bus 0 connected to the MV64460 System
Controller.
•PMC0 supports 64-bit 33/66MHz PCI operation as well as 64-bit 133MHz PCI-X
operation per VITA 39 (if the installed PMC module is configured for that bus mode).
•VIO for PCI Bus 0 is configurable to either +5V or +3.3V through PCI Bus 0 VIO Select
jumper (P12) (
see “PCI VIO Select (P9, P12)” on page 2-2).
NOTE: Setting PCI Bus 0 VIO to +5V forces the bus speed to 33MHz.
•PMC0_P14 is routed to cPCI_J3 using PICMG 2.3 wiring definitions. It also supports the
differential signal PCB trace requirements defined for Sentiris S4110 PMC LVDS interface
and G2 PMC.
•PMC0 is intended for higher capacity I/O or video processing and can host a PMC module
with a power rating of 15W or lower.
NOTE: Combined power dissipation for both PMC sites cannot exceed 15W.
•PMC1 shares PCI Bus 1 with the cPCI backplane interface (PCI 6254 cPCI Bridge), the
USB 2.0 Host controller interface through the PCI2050B PCI/PCI Bridge, and the
GD31244 SATA Host Controller.
•PCI Bus 1 supports 64-bit 33/66MHz operation.
NOTE: PCI Bus 1 will operate at 66MHz if a PMC module supporting 66MHz operation
is installed. If the installed PMC module only supports 33MHz operation, PCI Bus 1 will
revert to 33MHz operation. This will impact I/O transfer rates to and from the cPCI backplane but not backplane transfer rates between other boards.
•VIO for PCI Bus 1 is configurable to either +5V or +3.3V through PCI Bus 1 VIO Select
jumper (J9) (see “PCI VIO Select (P9, P12)” on page 2-2).NOTE: Setting PCI Bus 1 VIO to +5V forces the bus speed to 33MHz.
•PMC1_P24 is routed to cPCI_J5 using PICMG 2.3 wiring definitions. It also supports the
differential signal PCB trace requirements defined for Sentiris S4110 PMC LVDS interface
and G2 PMC.
•PMC1 is intended for lower capacity I/O and may host a PMC with power rating of 7.5W
or lower, if the module on PMC0 is 7.5W or less. PMC 1 can host a 15W PMC module if
no PMC module is installed on PMC0.
NOTE: Combined power dissipation for both PMC sites cannot exceed 15W.
4.18 Temperature Sensor
The C2K includes a MAX6658 Dual Channel Temperature Sensor that monitors the MPC7448
processor temperature through an on-die thermal diode and board temperature with an on-chip
sensor. The Temperature Sensor is attached to the MV64460 Bridge chip through the I2C SMBus
at address 0x4C.
Boot code must program the temperature sensor to generate an over-temperature alarm if the CPU
die reaches 102ºC or if the ambient temperature exceeds 85ºC. The over-temperature alarm will
initiate a hard-reset of the board, holding the board in reset until the alarm condition clears. The
default, power-up, values are:
•Generate interrupt at -55 ºC or below or +70ºC and above
•Generate over-temperature alarm at +85ºC or above
The over-temperature alarm is ignored unless the OVRTEMP_RST_EN bit (bit 15) in the FPGA
Control Register (see “Control Register” on page 5-9) is set. This avoids resetting the C2K prior
to the CPU reprogramming the sense thresholds.
4.19 Interrupt Circuitry
The C2K uses the FPGA Interrupt Summary registers (see “Interrupt Registers” on page 5-11), to
capture external (cPCI and PMC) interrupts and board interrupts as shown in Figure 4-3. When
one of these interrupts is asserted, the FPGA asserts an interrupt to the MV64460 System
Controller MPP port. In addition to the FPGA interrupt, the Ethernet PHY interrupt, the
Real-Time Clock interrupt, Serial ATA interrupt, Temperature interrupt, and the USB interrupt are
also routed to the MV64460 MPP port (see “Multi-Purpose Pins (MPP)” on page 5-3).
If one of the MV64460 MPP pins assigned as an interrupt is asserted, it sets the corresponding pin
in the Interrupt Cause Register in the MV64460 Interrupt Controller. This causes the Interrupt
Controller to assert the CPU_INT interrupt to the MCP7447A processor.
MV64460
FPGA
PMC0_INTA–D
System
Controller
MPC7448
Processor
PMC1_INTA–D
cPCI_INTA–D
C8051_INT
PCI 6254_PINT
USART_INT0–7
FPGA_INT
ETH_PHY0_INT
RTC_INT
SATA_INT
TEMP_INT
USB_INT
MPP
CPU_INT0
Ext_INT
Figure 4-3 Interrupt circuitry
4.20 EEPROMS
The C2K provides the following programmable configuration serial EEPROMS located on the
IIC SMBus:
EEPROMTy peAddressFunction
Board ConfigurationAT24C64AN
(64kb)
User ConfigurationAT24C512N
(512kb)
0x50Provides storage for product configuration data such as: assem-
bly serial number, build data, etc.
NOTE: MAC address for the three Gigabit Ethernet MACs must
be stored in this device so the processor can program the MAC
addresses into the MV64460 after power-up or reset.
The JTAG circuitry provides a boundary scan chain for checking major components on C2K for
open and short circuits, and grounds. It can also be configured for special functions such as COP
software debugging through the COP header (J6) and C8051 Microcontroller software debugging.
The JTAG Scan chain can use the cPCI backplane through cPCI_J1 (default) or the on-board
JTAG header (J7) as its interface.
The components included in the JTAG Boundary Scan Chain include:
•IPMI C8051 Microcontroller
•IPMI CPLD
•FPGA EEPROM
•FPGA
•G31244 Serial ATA Controller
•PCI 6254 cPCI Bridge
•PCI2050B PCI/PCI Bridge
•PMC0 site
•PMC1 site
•MPC7448 processor
•MV64460 System Controller
4.21.1 Configuration Headers
C8051 Microcontroller Isolation (P11)
The C8051 Isolation header/jumper (P11) isolates the C8051 Microcontroller from the JTAG
Boundary Scan Chain for software debugging as shown in Figure 4-4 on page 4-18. When a
jumper is installed on header P11, the C8051 Controller is isolated from the JTAG Scan chain (see “C8051 Debug (P11)” on page 2-3). When a jumper is not installed, all JTAG-equipped devices
on the board are included in the JTAG chain.
COP Port Enable (J6)
The COP Port Enable header/jumper (P10) enables a bus switch to isolate the MPC7448
processor from the JTAG Scan chain, and connects the COP header to the processor for
debugging application code as shown in Figure 4-4 on page 4-18 (see “COP_EN (P10)” on page 2-3). When a jumper is installed on header P10, the COP header J6 provides the interface to
the processor’s COP interface. When a jumper is not installed, all JTAG-equipped devices on the
board are included in the JTAG chain.
The C2K provides two PCI buses controlled through the MV64460 System Controller’s two PCI
bus interfaces.
PCI Bus 0 is dedicated to the PMC0 site and supports 64-bit 33/66MHz PCI or 133MHz PCI-X
operation.
PCI Bus 1 is a 64-bit 33/66MHz PCI 2.2 bus that transfers data between the MV64460 System
Controller and the cPCI backplane through the PCI 6254 cPCI Bridge. It also connects to PMC1
site, the USB 2.0 Controller through the PCI2050B PCI/PCI Bridge, and the GD31244 SATA
Host Controller.
Table 5-1 summarizes the C2K PCI local bus configurations. The MV64460 System Controller
provides arbitration for both local busses so its interfaces do not require an arbitration number.
The C2K provides a System Management Bus (SMBus), a two-wire IIC interface that can communicate configuration or status information with other components following the I2C protocol.
The MV64460 System Controller provides the SMBus Host Controller to five slave ports. Table
5-2 lists the slave devices and their 7-bit addressing used by the devices.
Table 5-2 SMBus addressing
DeviceAddress
MAX6658 Thermal Monitor0x4C
Board Configuration EEPROM0x50
User Configuration EEPROM0x51
C2K CPLD0x10
RTC0x68
5.1.3 Device Bus
The C2K provides an asynchronous 32-bit multiplexed Device Bus, mastered by the MV64460
System Controller with bus control and address decoding provided by the FPGA. Table 5-3 lists
the accessible devices and default address ranges set by the MV64460 following power-up or hard
reset. Addressing for these devices is according to MV64460 instructions for interfacing 8-bit,
16-bit, and 32-bit devices.
NOTE: MV64460 default values may be redefined in U-Boot boot loader utility.
Table 5-3 Device bus devices, access, size and default address range
The C2K includes a FPGA to provide programmable logic circuitry for peripheral resources and
miscellaneous ‘glue logic’. The FPGA, located on the 32-bit Device Bus, contains registers that
perform the following functions:
•Board status and control
•Interrupt status and control
•GPIO status and control
•USART
•Counter/timers
Table 5-5 lists the FPGA memory map for the 16-bit chip select. Addresses are given as word
addresses as required by the MV64460.
Table 5-6 lists the FPGA memory map for the 8-bit chip select. Addresses are given as word
addresses as required by the MV64460.
Table 5-6 FPGA memory map - 8-bit Chip Select
AddressDescription
USART
0x00-0x07USART 0
0x10-0x17USART 1
0x20-0x27USART 2
0x30-0x37USART 3
0x40-0x47USART 4
0x50-0x57USART 5
0x60-0x67Unused
0x70-0x77Unused
0x80-0x86UART 8 (dedicated to C8051)
5.2.1 Main Registers
The main registers provide revision information for the FPGA firmware, as well as status and
control for various functions. Table 5-7 lists the main registers.
0x8StatusProvides status information for various board functions.
0x10ControlProvides configure and control settings for various board functions.
0x12Reset ControlProvides software control of the on-board reset lines.
FPGA Revision Register
The FPGA Revision Register contains the binary-coded decimal revision number for the current
FPGA firmware. It is formatted as version number (most significant 16-bits) and revision number
(least significant 16-bits).
The Status Register provides C2K status information such as flash and system memory size, flash
write-protect, and emergency boot select settings.
NOTE: Bits 15–12 only revert to the default value during power-up and are not affected by resets.
Address offset:0x8
Access:Read-only
BitsFieldAccessDefaultDescription
15RST_CAUSE_TEMP RW0*Reset Cause Register - Temp—indicates that a CPU
Over-Temperature alarm initiated the last board reset.
0 = other cause initiated last board reset
1 = Over-temp alarm initiated last board reset
14RST_CAUSE_CPURW0*Reset Cause Register - CPU—indicates that the processor,
through the BRD_RST bits, initiated the last board reset
(see BRD_RST bits (bit 9–6) in Control Register).
0 = other cause initiated last board reset
1 = BRD_RST bits initiated last board reset
13RST_CAUSE_WDOG RW0*Reset Cause Register - Watchdog timer—indicates that a
watchdog timer expiration initiated the last board reset.
0 = other cause initiated last board reset
1 = watchdog timer expiration initiated last board reset
12RST_CAUSE_CPCI RW0*Reset Cause Register - cPCI—indicates that the PRST# or
PCI_RST# signal from the cPCI backplane initiated the last
board reset.
0 = other cause initiated last board reset
1 = PRST# or PCI_RST# signal initiated last board
reset
11SYS_SLOTR-CPCI System Slot status—indicates whether the C2K is
installed in a system or peripheral slot.
0 = C2K installed in peripheral slot
1 = C2K installed in system slot
10PCI_PRESENTR-cPCI Bus Present—indicates the presence of a cPCI bus.
0 = no cPCI bus present
1 = cPCI bus present
9EM_BOOT_SELR-Emergency Boot Jumper Select—indicates whether the
EM_BOOTSEL# signal has been asserted either by installing a jumper at EM_BOOTSEL# header/jumper (P7) or
through the EM_BOOTSEL# backplane pin to force the C2K
to boot from emergency boot code.
0 = boot from user boot area of flash
1 = boot from emergency boot area of flash
8ROM_WP_INR-Boot ROM write protect input active.
0 = boot ROM write protection disabled
1 = boot ROM write protection enabled
7ROM_PERM_WP_INR-Boot ROM permanent write protection active.
0 = boot ROM permanent write protection disabled
1 = boot ROM permanent write protection enabled
6FLASH_BUSYR-Flash Busy—indicates whether a program or erase cycle is
currently executing in flash.
0 = flash is ready for next command
1 = flash is busy
Table 5-8 lists the interrupt registers included in the FPGA that provide interrupt status and interrupt blocking (masking).
Table 5-8 Interrupt summary registers
OffsetRegisterDescription
0x20Interrupt Mask Reg 1Provides interrupt masking for PMC sites and
integrated USART ports.
0x22UnusedUnused
0x24Interrupt Status Reg 1Provides interrupt status for PMC sites and inte-
grated USART ports.
0x26UnusedUnused
0x28SMI MaskProvides masking for inputs to CPU_SMI#.
0x2ASMI StatusProvides status of inputs to CPU_SMI#.
Interrupt Mask Register 1
The Interrupt Mask Register 1 provides interrupt masking for the PMC sites and integrated
USART.
Address offset:0x20
Access:Read/write
BitsFieldDefaultDescription
15PMC1_CPCI_INTA_MSK0x1PMC1/[CPCI Interrupt A or CPCI_BRG_P] Interrupt Mask— blocks
(masks) INTA from the PMC module installed on PMC1. When the
Board is in the system slot, the CPCI_BRG_P_INT signal is or’ed
with the PMC1 INTA signal. When the board is not in the system
slot, the CPCI INTA signal is or’ed with the PMC1 INTA signal .
0 = enable interrupt
1 = disable (mask) interrupt
14PMC1_CPCI_INTB_MSKXx7PMC1 INTB Mask—blocks (masks) INTB from the PMC module
installed on PMC1. Each bit indicates a logic or of the PMC and
CPCI interrupt. When the board is not in the system controller slot,
the CPCI interrupts are disabled.
0 = enable interrupt
1 = disable (mask) interrupt
13PMC1_CPCI_INTC_MSKPMC1 INTB Mask—blocks (masks) INTB from the PMC module
installed on PMC1. Each bit indicates a logic or of the PMC and
CPCI interrupt. When the board is not in the system controller slot,
the CPCI interrupts are disabled.
0 = enable interrupt
1 = disable (mask) interrupt
12PMC1_CPCI_INTD_MSKPMC1 INTB Mask—blocks (masks) INTB from the PMC module
installed on PMC1. Each bit indicates a logic or of the PMC and
CPCI interrupt. When the board is not in the system controller slot,
the CPCI interrupts are disabled.
The Interrupt Status Register 1 provides interrupt status information for the PMC sites and integrated USART.
Address offset:0x24
Access:Read-only
BitsFieldDefaultDescription
15PMC1_CPCI_INTA_STAT-PMC1 [CPCI Interrupt A or CPCI_BRG_P] INTA Status—
indicates the status of INTA from a PMC module installed
on PMC1. When the board is in the system slot, the
CPCI_BRG_P_INT signal is or’ed with the PMC1 INTA
signal. When the board is not in a system slot, the CPCI
INTA signal is or’ed with the PMC1 INTA signal.
0 = interrupt is de-asserted
1 = interrupt is asserted
14PMC1_CPCI_INTB_STAT-PMC1/CPCI INTB Status—indicates the status of INTB
from a PMC module installed on PMC1. Each bit indicates a logic or of the PMC and CPCI interrupt. When the
board is not in the system controller slot, the CPCI interrupts are disabled.
0 = interrupt is de-asserted
1 = interrupt is asserted
13PMC1_CPCI_INTC_STAT-PMC1/CPCI INTC Status—indicates the status of INTC
from a PMC module installed on PMC1. Each bit indicates a logic or of the PMC and CPCI interrupt. When the
board is not in the system controller slot, the CPCI interrupts are disabled.
0 = interrupt is de-asserted
1 = interrupt is asserted
12PMC1_CPCI_INTD_STAT-PMC1/CPCI INTD Status—indicates the status of INTD
from a PMC module installed on PMC1. Each bit indicates a logic or of the PMC and CPCI interrupt. When the
board is not in the system controller slot, the CPCI interrupts are disabled.
0 = interrupt is de-asserted
1 = interrupt is asserted
11PMC0_INTA_STAT-PMC0 INTA Status—indicates the status of INTA from a
PMC module installed on PMC0.
0 = interrupt is de-asserted
1 = interrupt is asserted
10PMC0_INTB_STAT-PMC0 INTB Status—indicates the status of INTB from a
PMC module installed on PMC0.
0 = interrupt is de-asserted
1 = interrupt is asserted
9PMC0_INTC_STAT-PMC0 INTC Status—indicates the status of INTC from a
PMC module installed on PMC0.
0 = interrupt is de-asserted
1 = interrupt is asserted
8PMC0_INTD_STAT-PMC0 INTD Status—indicates the status of INTD from a
PMC module installed on PMC0.
0 = interrupt is de-asserted
1 = interrupt is asserted
The C2K includes 16 General-Purpose Input/Output ports. The FPGA provides the GPIO interrupt masking, data, and control registers for configuring, masking interrupts, and sending/receiving data on the GPIO lines connected to the backplane. The FPGA also includes an optional
de-bounce circuit that can be applied to each port designated as an input for use with external
switches, contacts, or relays. The GPIO registers set the following configuration parameters:
•Direction (input or output)
•Output drive type (TTL or open-drain)
•Input polarity (inverted or non-inverted)
•Interrupt type (edge or level-sensitive)
•Debounce filter on input
When the GPIO lines are configured as outputs, they can be driven as either standard TTL or
open-drain (drive-low only). When configured as inputs, the GPIO lines can be treated as positive
or negative logic and can be enabled as either edge or level-type interrupt sources for generating
the MPC7448 processor’s interrupt input (the FPGA interrupt output passes through the
MV64460 interrupt logic). The selected logic polarity for GPIO inputs affects the value read in
the GPIO Data Register and affects which logic level will cause an interrupt assertion. The registers’ default bit values occur after a power-up reset.
Table 5-9 lists the GPIO registers.
Table 5-9 GPIO registers
OffsetRegisterDescription
0x30GPIO Direction Enables a direction for each GPIO line.
0x32GPIO PolarityEnables polarity for each GPIO line.
0x34GPIO Output TypeEnables output type for each GPIO line.
0x36GPIO Interrupt TypeConfigures each interrupt for type (edge, level)
0x38GPIO De-Bounce Enable Enables a de-bounce circuit for each GPIO line.
0x40GPIO Input Data ReadEnables input data read for each GPIO line.
0x42GPIO IO DataEnable input IO data state for each GPIO line.
0x44GPIO Interrupt StatusProvides the interrupt status for each GPIO line.
0x46GPIO Interrupt MaskEnables interrupt masking for each GPIO line.
0x4CGPIO ClearClears the GPIO bit for each GPIO line.
The GPIO De-bounce Enable Register enables a de-bounce circuit to be applied to any GPIO line
designated as an input to filter relays, switches, and contacts. The circuit waits for 15ms of
glitch-free input signal before registering a change-of-state in the Data Register.
Address offset:0x38
Access:Read/write
BitsFieldDefaultDescription
15GPIO15_DEBOUNCE_EN0GPIO15 Debounce Enable—enables a debounce circuit
for GPIO15 line if designated as an input in the Control
Register.
The GPIO Input Data Read Register reports the state of the GPIO inputs, as configured in the
GPIO Polarity Register. When a bit is defined as active-high this register will read a “1” when the
input is high, and a “0” when it is low. When a bit is defined as active-low, this register will read a
“1” when the input is low, and a “0” when it is high. This register contains the same contents as
the GPIO Data Register, only it is read only.
Address offset:0x40
Access:Read-only
BitsFieldDefaultDescription
15GPIO15_INPUT_DATA-GPIO15 I/O Data Read—Input Data Read—reads the GPIO
Polarity Register
0 = inactive state
1 = active state
14GPIO14_INPUT_DATA-GPIO14 Input Data Read—reads the GPIO Polarity Register
for the GPIO14 line
0 = inactive state
1 = active state
13GPIO13_INPUT_DATA-GPIO13 Input Data Read—reads the GPIO Polarity Register
for the GPIO13 line
0 = inactive state
1 = active state
12GPIO12_INPUT_DATA-GPIO12 Input Data Read—reads the GPIO Polarity Register
for the GPIO12 line
0 = inactive state
1 = active state
11GPIO11_INPUT_DATA-GPIO11 Input Data Read—reads the GPIO Polarity Register
for the GPIO11 line
0 = inactive state
1 = active state
10GPIO10_INPUT_DATA-GPIO10 Input Data Read—reads the GPIO Polarity Register
for the GPIO10 line
0 = inactive state
1 = active state
9GPIO9_INPUT_DATA-GPIO9 Input Data Read—reads the GPIO Polarity Register
for the GPIO9 line
0 = inactive state
1 = active state
8GPIO8_INPUT_DATA-GPIO8 Input Data Read—reads the GPIO Polarity Register
for the GPIO8 line
0 = inactive state
1 = active state
7GPIO7_INPUT_DATA-GPIO7 Input Data Read—reads the GPIO Polarity Register
for the GPIO7 line
0 = inactive state
1 = active state
6GPIO6_INPUT_DATA-GPIO6 Input Data Read—reads the GPIO Polarity Register
5GPIO5_INPUT_DATA-GPIO5 Input Data Read—reads the GPIO Polarity Register
for the GPIO5 line
0 = inactive state
1 = active state
4GPIO4_INPUT_DATA-GPIO4 Input Data Read—reads the GPIO Polarity Register
for the GPIO4 line
0 = inactive state
1 = active state
3GPIO3_INPUT_DATA-GPIO3 Input Data Read—reads the GPIO Polarity Register
for the GPIO3 line
0 = inactive state
1 = active state
2GPIO2_INPUT_DATA-GPIO2 Input Data Read—reads the GPIO Polarity Register
for the GPIO2 line
0 = inactive state
1 = active state
1GPIO1_INPUT_DATA-GPIO1 Input Data Read—reads the GPIO Polarity Register
for the GPIO1 line
0 = inactive state
1 = active state
0GPIO0_INPUT_DATA-GPIO0 Input Data Read—reads the GPIO Polarity Register
for the GPIO0 line
0 = inactive state
1 = active state
GPIO I/O Data Register
The GPIO I/O Data Read Register both controls the GPIO output states, as well as reports the
input states. The states are controlled as configured in the GPIO Polarity, Direction and Output
Type registers.
When an output bit is defined as active-high, the output will be high when register bit is written to
“1” and low when the register bit is written to “0”. When an output bit is defined as active-low,
the output will be low when the register bit is written to “1” and high when the register bit is written to “0”.
Address offset:0x42
Access:Read/Write
BitsFieldDefaultDescription
15GPIO15_IO_DATA-GPIO15 I/O Data Read—controls the GPIO output states, as
well as reports the input states for the GPIO Polarity Register
for the GPIO15 line
0 = inactive state
1 = active state
14GPIO14_IO_DATA-GPIO14 I/O Data Read—controls the GPIO output states, as
well as reports the input states for the GPIO Polarity Register
for the GPIO14 line
3GPIO3_IO_DATA-GPIO3 I/O Data Read—controls the GPIO output states, as
well as reports the input states for the GPIO Polarity Register
for the GPIO3 line
0 = inactive state
1 = active state
2GPIO2_IO_DATA-GPIO2 I/O Data Read—controls the GPIO output states, as
well as reports the input states for the GPIO Polarity Register
for the GPIO2 line
0 = inactive state
1 = active state
1GPIO1_IO_DATA-GPIO1 I/O Data Read—controls the GPIO output states, as
well as reports the input states for the GPIO Polarity Register
for the GPIO1 line
0 = inactive state
1 = active state
0GPIO0_IO_DATA-GPIO0 I/O Data Read—controls the GPIO output states, as
well as reports the input states for the GPIO Polarity Register
for the GPIO0 line
0 = inactive state
1 = active state
GPIO Interrupt Status
The GPIO Interrupt Status may be configured with trigger level or edge-sensitive interrupts. The
input polarity is used in conjunction with the interrupt type to determine how to handle input
interrupts. When configured as an active high input, edge interrupts will be generated on the rising edge and level interrupts will be active when the input is high. When configured as an active
low input, edge interrupts will be generated on the falling edge and level interrupts will be active
when the input is low.
Address offset:0x44
Access:WC*
* When configured as edge-sensitive
interrupts, the corresponding bits are
clear-on-write of “1.” Otherwise, this
register is read-only.
BitsFieldDefaultDescription
15GPIO15_INT_STAT-GPIO15 Interrupt Status—provides the GPIO interrupt status
for the GPIO15 line
0 = interrupt not active
1 = interrupt active
14GPIO14_INT_STAT-GPIO14 Interrupt Status—provides the GPIO interrupt status
for the GPIO14 line
0 = interrupt not active
1 = interrupt active
13GPIO13_INT_STAT-GPIO13 Interrupt Status—provides the GPIO interrupt status