mobile | classic
Dataweek Electronics & Communications Technology Magazine





Follow us on:
Follow us on Facebook Share via Twitter Share via LinkedIn


Search...

Electronics Buyers' Guide

Electronics Manufacturing & Production Handbook 2017


 

Choosing the right mezzanine module for embedded systems
19 July 2017, This Week's Editor's Pick, Computer/Embedded Technology

Open architecture embedded systems for military/aerospace applications have always relied on mezzanine or daughter cards to provide flexibility and modularity because they are very effective in handling the large

breadth of I/O functions required.

Thanks to widespread adoption of industry standards defining these mezzanine products, carrier boards are able to accept mezzanine boards from a wide range of vendors, each specialising in niche technologies and interfaces.

Today, three popular mezzanine standards dominate the embedded market: PMC (PCI mezzanine card), XMC (Switched mezzanine card) and FMC (FPGA mezzanine card). These mezzanines support all popular industry architectures including VME, VXS, VPX, AMC, CompactPCI and CompactPCI Serial for both 3U and 6U form factors, and across a range of cooling techniques and ruggedisation levels – especially important for Mil/Aero electronics. Each of these three mezzanine standards presents a unique set of advantages and disadvantages.

Mezzanine module standards

Defined under the IEEE 1386.1 standard more than 15 years ago, PMC uses the mechanical dimensions of the CMC (common mezzanine card) from IEEE 1386 with the addition of up to four 64-pin connectors to implement a 32- or 64-bit PCI bus as well as user I/O.

Two connectors, P11 and P12 (see Figure 1), handle a 32-bit PCI bus, expandable to 64 bits with the addition of the P13 connector. Operating at PCI bus clock speeds of 33 or 66 MHz, the 32-bit interface delivers a peak transfer rate of 132 or 264 MB/sec, respectively, and twice that for a 64-bit interface.

Figure 1. Single PMC, XMC, FMC, and FMC+ module outline dimensions and connectors (drawn to scale, for comparison).
Figure 1. Single PMC, XMC, FMC, and FMC+ module outline dimensions and connectors (drawn to scale, for comparison).

A later extension, called PCI-X, boosts the clock rate to 100 or 133 MHz for a peak transfer rate of 800 or 1000 MB/sec for 64-bit implementations. The optional P14 connector supports 64 bits of user-defined I/O. As interconnect technology for mass-market PCs began shifting away from parallel PCI buses towards the faster PCIe (PCI Express) gigabit serial links, the need for a similar migration for mezzanine modules became apparent.

XMC modules are defined under VITA 42 as the switched fabric extension of the PMC module. It requires either one or two multi-pin connectors called the primary (P15) and secondary (P16) XMC connectors shown in Figure 1. Each connector can handle eight bidirectional serial lanes, using a differential pair of pins for each direction. The VITA 42.3 sub-specification defines pin assignments for PCIe, while VITA 42.2 covers SRIO (SerialRapidIO).

Typically, each XMC connector is used as a single x8 logical link or as two x4 links, although other configurations are also defined. Data transfer rates for XMC modules depend on the gigabit serial protocol and number of lanes per logical link. Table 1 shows the peak rates for different configurations and protocols, which compare favourably with peak PMC rates.

Table 1: Peak data transfer rates for various XMC serial link configurations and protocols.
Table 1: Peak data transfer rates for various XMC serial link configurations and protocols.

FMC modules are defined in the VITA 57 specification and are intended as I/O modules for FPGAs. They depart from the CMC form factor, with less than half the real estate, as shown in the top right of Figure 1. Two different connectors are supported: a low pin-count (LPC) connector with 160 contacts and a high pin-count (HPC) connector with 400 contacts. Connector pins are generically defined for power, data, control and status with specific implementation depending on the design.

FMC modules rely on the carrier board FPGA to provide the necessary interfaces to the FMC components. These can be single-ended or differential parallel data buses, gigabit serial links, clocks and control signals for initialisation, timing, triggering, gating and synchronisation. For data, the high-density FMC connector provides 80 differential pairs or 160 single-ended lines. It also has 10 high-speed gigabit serial lanes, with differential pairs for each direction.

In order to support the new class of data converter devices that use JESD204B gigabit serial interfaces instead of parallel LVDS, the FMC specification has been enhanced to FMC+. Defined in VITA 57.4, it increases the number of gigabit serial lanes from 10 to 24 through a new, higher-speed version of the HPC connector with four more rows of pins. The new connector for FMC+ is rated for data rates up to 28 Gbits/sec.

VITA 57.4 optionally adds 8 more gigabit serial lanes to the FMC+ module by extending the length of the original FMC module by 12 mm to support a new 40-pin connector, as shown in the bottom right of Figure 1. This boosts the total number of full-duplex gigabit serial lanes to 32 when maximum I/O data rates are required.

It should be noted that all three of these mezzanines are also available in double-width versions, fully defined in the specifications. This provides additional real estate for more components. However, the vast majority of mezzanines available in the marketplace today are single-width designs.

Lastly, all three specifications (PMC, FMC, and FMC) include complete specifications for rugged and conduction-cooled versions of these mezzanine products so they can be deployed in extreme Mil/Aero environments.

Data transfer capabilities

Regarding the data transfer rates, PMC and XMC modules are well determined by the interface standard installed. Nevertheless, these rates are often affected by the carrier board in several ways. A shared PCI bus supporting other traffic will effectively block all transfers to a PMC until it is granted use of the bus. For example, this problem occurs on dual PMC SBCs (single board computers) where the two PMCs often share the same local PCI bus.

Also, when PMCs are installed on simple 3U CompactPCI carriers, the common PCI backplane must be shared across all boards installed in the card cage. Lastly, a carrier card or adapter that presents a lower speed PCI bus to the PMC module will force the module to operate its interface at that lower speed.

XMCs have an inherent data rate advantage over PMCs because they use fast gigabit serial links. Even the slowest x4 PCIe 1.0 interface still matches the fastest PCI-X 64-bit bus at 133 MHz. However, a major system level implication for the gigabit serial interfaces is that they are dedicated point-to-point links and are not subject to the sharing penalty of parallel buses. Table 1 shows the peak data transfer rates for PCIe and SRIO for different width gigabit serial links.

Ultimately, any system will have CPU and memory bandwidth limitations, but new multi-core processors and chipsets feature more than 40 PCIe Gen3 lanes, each handling 1 GB/sec, and four DDR3 memory banks, each delivering transfer rates of 12,8 GB/sec. In these systems, a dedicated x8 PCIe link between the XMC and the system supports a respectable transfer rate of 8 GB/sec.

Unlike PMCs and XMCs, FMCs do not use industry standard interfaces like PCI or PCIe. Instead, each FMC has a unique set of control lines and data paths, each one differing in signal levels, quantity, bit widths and speed. At a 1 GHz data clock rate, the 80 differential data lines can deliver 10 GB/sec, although the new FMC+ specification doubles these rates.

The original FMC specification set a design goal of 10 Gbits/sec for each of the 10 serial lanes, delivering peak aggregate data rates of 10 GB/sec. The new FMC+ specification of 28 Gbits/sec for a maximum of 32 serial lanes, boosts this aggregate peak data rate to nearly 90 GB/sec.

Real estate and power considerations

FMC modules are less than half the size of PMCs and XMCs, and less real estate means less freedom to strategically place components for shielding, isolation and heat dissipation. For example, A/D converters are extremely sensitive to spurious signal pickup from power supplies, voltage planes and adjacent copper traces. Often, the required power supply lines must be re-regulated and filtered locally on the same board as the A/D converters for best results, rather than on the carrier board. Arranging this circuitry on a small FMC module can be challenging. Even though XMC modules have more components, they can often be rearranged more easily because of the larger board size.

FMCs require the FPGA to reside on the carrier board, while FPGA-based XMC modules include the FPGA on the mezzanine board. Schematically, the overall circuitry between the front end and the system bus may be nearly identical, but the physical partitioning occurs at two different points.

To illustrate this, Figure 2 shows two different implementations of a 4-Channel A/D converter software radio module for 3U OpenVPX, highly suitable for Mil/Aero applications. Notice that both block diagrams feature the same A/D converters and FPGAs and provide the same x8 PCIe interface to the OpenVPX backplane. The XMC implementation on top uses the XMC connector between the FPGA and the backplane, while the FMC implementation below uses the FMC connector between the A/Ds and the FPGA.

Figure 2. Simplified block diagrams comparing XMC and FMC 4-channel A/D software radio modules for 3U OpenVPX.
Figure 2. Simplified block diagrams comparing XMC and FMC 4-channel A/D software radio modules for 3U OpenVPX.

Because most of the power is consumed by the FPGA, comparing power dissipation between FMC and XMC modules will strongly favour the FMC. However, since the same resources are used in both block diagrams, the overall 3U module power dissipation is nearly identical.

In a comparison among PMC, XMC and FMC modules, there is one additional factor. Gigabit serial interfaces implemented in FPGAs typically consume more power than parallel bus interfaces. So when considering PMC products versus XMC/FMC products, the PCI bus of the PMC module will typically draw less power than a PCIe link. Of course, the extra power required for PCIe delivers tremendous benefits in both speed and connectivity.

Software and FPGA development issues

Each FMC presents a unique electrical interface that must be connected to an FPGA configured precisely to handle that specific device. This may be a reasonable solution if the FMC module and the FMC carrier are both supplied by the same vendor, and the FPGA on the carrier is preconfigured by the vendor for the specific FMC module installed.

For 6U carriers with two or three FMC sites, the FPGAs must be configured to match the specific combination of each of the FMC modules installed at each site. This FMC-to-FPGA dependency creates a potentially large number of combinations resulting in configuration management and customer support issues. It may mean longer delivery times for first-time combinations, and higher costs. Also, the vendor may not offer an FMC carrier for the desired form factor or system architecture required.

When a customer purchases an FMC module from one vendor and an FMC carrier from a different vendor, additional challenges arise. Someone must develop custom FPGA configuration code for the carrier to support the FMC module. Perhaps the FMC vendor will agree to develop code for a third-party carrier. Perhaps the carrier vendor will develop code for a third party FMC module.

Failing either of these strategies, the customer must configure the FPGA himself, or hire a consultant to do the job. In this case, both the FMC module and the FMC carrier are third-party products with two different technical support resources. If something doesn’t work, it can be difficult to resolve problems in an efficient and effective way. And, if either the FMC module vendor or the FMC carrier vendor should revise his product, it may affect the interoperability of the two boards.

Perhaps the most challenging aspect of FMCs is the development of software drivers and board support libraries covering the myriad combinations of modules and carriers. Unless this is supplied from a single vendor who also supplies the FMC module and carrier, the same support and development issues discussed above for FPGA development may arise.

In contrast, PMCs and XMCs use industry standard system interfaces, typically PCI and PCIe, with a strong trending towards XMCs with PCIe. Nearly all recent embedded systems take advantage of the widely-adopted PCIe standard for interconnecting system elements. This includes VXS, VPX, AMC and CompactPCI, as well as high-performance PC platforms using PCIe cards installed in motherboard expansion slots.

Since PCIe is the system interface on most XMCs, they can be installed directly or with simple mechanical adaptors into all of these system architectures. Most importantly, these adaptors can be obtained from a variety of vendors since they are simply redirecting the PCIe bus, thus eliminating the need for anyone to develop custom FPGA code for new combinations.

Device drivers and application software developed for popular embedded operating systems simply work, regardless of the architecture. This is due to the inherent

connectivity of PCIe through bridges, switches, extender cables and expansion chassis regardless of the form factor of the boards, modules and backplanes.

All of these factors greatly reduce dependency on the XMC vendor and problems resolving multi-vendor responsibility. XMCs take advantage of an industry standard system interface, eliminate the need for custom FPGA development, easily support a wide range of system architectures, and come with complete software drivers and board support libraries. This can result in dramatic savings in systems integration and software development costs so important to Mil/Aero programme budgets and schedules.


Credit(s)
Supplied By: Rugged Interconnect Technologies
Tel: +27 21 975 8894
Fax: +27 21 975 6456
Email: sales@ri-tech.co.za
www: www.ri-tech.co.za
  Follow us on Facebook Share via Twitter Share via LinkedIn    

Further reading:

  • Effort required to manage ICT e-waste
    13 September 2017, Arrow Altech Distribution (AAD), This Week's Editor's Pick, News
    Arrow Value Recovery Services specialises in reducing the environmental impact of e-waste by recycling ICT products through lifecycle programmes that recondition and return them to the business ICT stream.
  • Op-amp balancing resistors are not a given
    13 September 2017, Arrow Altech Distribution (AAD), This Week's Editor's Pick, Analogue, Mixed Signal, LSI
    Analog Devices’ Harry Holt explains why balancing resistors are not always a given, the way they were in the days of the old 741 op-amp.
  • Thermocouple signal conditioning challenges and solutions
    13 September 2017, Tempe Technologies, This Week's Editor's Pick, Analogue, Mixed Signal, LSI
    When measuring temperature, the thermocouple is one of the oldest and most widely used components. Especially useful in applications that require temperature measurements in hostile environments, such ...
  • Ghana repurposes communications antenna for astronomy
    16 August 2017, This Week's Editor's Pick, News
    The 32 metre converted telecommunications antenna will be integrated into the African VLB Network in preparation for the second phase construction of the Square Kilometre Array.
  • Bluetooth updated for mesh networking
    16 August 2017, This Week's Editor's Pick, News, Telecoms, Datacoms, Wireless
    A highly anticipated mesh networking standard has been introduced to the Bluetooth specification by the Bluetooth Special Interest Group (SIG).
  • LoRa technology explained
    16 August 2017, Otto Wireless, This Week's Editor's Pick, Telecoms, Datacoms, Wireless
    The technical manager of Otto Wireless Solutions delves into one of the latest additions to the collection of Internet networking and mobile communication protocols.
  • Optical calculations for SSL applications
    16 August 2017, OSRAM Opto Semiconductor SA, This Week's Editor's Pick, Opto-Electronics
    Back-of-the-envelope calculations are useful at the beginning of a project for estimating LED type and count. This article presents techniques for calculating optical quantities and estimating LED count ...
  • Industrial IoT gateway
    16 August 2017, Rugged Interconnect Technologies, Telecoms, Datacoms, Wireless, Computer/Embedded Technology
    Adlink’s new Matrix MXE-110i industrial IoT gateway, supporting Intel Gateway Solutions for the Internet of Things (IoT), provides versatile RF connectivity and fanless rugged construction, all in a more ...
  • From the chairman’s desk: Manufacturing in South Africa
    19 July 2017, AREI, This Week's Editor's Pick, News
    Warren Muir reflects on his attendance at the 2017 Manufacturing Indaba, and how it fits in with arei’s plans for the South African electronics industry.
  • Training structure the key to successful content
    19 July 2017, This Week's Editor's Pick, News
    The structure and assessment of training programmes are just as important as their content when it comes to up-skilling production staff, explains Bob Willis.
  • Cape Town hosts Dynamic Spectrum Alliance global summit
    14 June 2017, This Week's Editor's Pick, News
    The three-day event brought together representatives from five continents and 21 countries around the world, including policy makers, regulators, academia, and public and private sector representatives.
  • UL presents new smart meter standards
    14 June 2017, This Week's Editor's Pick, News
    Users throughout the supply chain need to be assured of the fact that common, consensus-based standards are being used on both a national and international basis to test and certify all smart meters.

 
 
         
Contact:
Technews Publishing (Pty) Ltd
1st Floor, Stabilitas House
265 Kent Ave, Randburg, 2194
South Africa
Publications by Technews
Dataweek Electronics & Communications Technology
Electronic Buyers Guide (EBG)

Hi-Tech Security Solutions
Hi-Tech Security Business Directory

Motion Control in Southern Africa
Motion Control Buyers’ Guide (MCBG)

South African Instrumentation & Control
South African Instrumentation & Control Buyers’ Guide (IBG)
Other
Terms & conditions of use, including privacy policy
PAIA Manual





 

         
    Classic | Mobile

Copyright © Technews Publishing (Pty) Ltd. All rights reserved.