Skip to content

ANSI/VITA 57.1 FMC LPC and HPC connectors.

KiCad Bot requested to merge github/fork/ObKo/vita-fmc into master

Created by: ObKo

ANSI/VITA 57.1 standard defines both physical, electrical and some functional part for mezzanine extension boards. This mezzanine boards is mostly used on FPGA development boards to add high-speed peripherials. Standard isn't free available, but you can find some information here

Connectors used both on mezzanine card (M) and base (carrier) board (C) are called FMC. Here is some FMC connectors photo:

VITA57_FMC_CONNECTORS_HPC

Top is carrier board side receptacle, bottom is mezzanine board side plug. Footprint on both sides looks like 40x10 BGA with 1.27mm pitch.

There is two variants of FMC connectors used: FMC HPC (High-Pin Count, 40x10 pins) and FMC LPC (Low-Pin Count, 40x4 pins). LPC is just HPC with only 4 of 10 rows used, so LPC mezzanine can be inserted into HPC carrier.

Functionaly, FMC pins divided into groups:

  • Main: Power, GND, Power-good, Clocks, I2C, JTAG and some controls.
  • LA, Bank A Lower: 34 diff pairs or 68 single-ended I/O pins.
  • HA, Bank A Higher: 24 diff pairs or 48 single-ended I/O pins. HPC-only
  • HB, Bank B: 22 diff pairs or 44 single-ended I/O pins with I/O supply provided by mezzanine. HPC-only
  • DP: Bank with high-speed multi-gigabit diff pairs (MGTs) and reference clocks for them. LPC: 1 TX/1 RX pairs, 1 clock HPC: 10 TX/10 RX pairs, 2 clocks

This PR adds symbols for FMC LPC and HPC connectors as they seen from both mezzanine and carrier board side. Each symbol is splitted into functional units.

HPC symbol (as seen from mezzanine side): HPC

LPC symbol LPC

I'm not sure, how to specify footprint for those connectors. Currently, there is two major manufacturers for the connectors: Samtec and Molex, each has it's own nomenclature. Standard itself has own naming, but they are refering to samtec part numbers for drawings.

ANSI/VITA-57 Samtec Molex Description
CC-LPC-10 ASP-134603-01 45971-4305 female, baseboard side, Low-pin count (LPC), 160 I/O, tin-lead
CC-LPC-10L ASP-127796-01 45971-4307 female, baseboard side, Low-pin count (LPC), 160 I/O, tin-lead
CC-HPC-10 ASP-134486-01 45971-4315 female, baseboard side, High-pin count (HPC), 400 I/O, lead-free
CC-HPC-10L ASP-134485-01 45971-4317 female, baseboard side, High-pin count (HPC), 400 I/O, tin-lead
MC-LPC-8.5 ASP-134606-01 45970-4105 male, mezzanine card side, Low-pin count (LPC), 160 I/O, lead-free, 8.5 mm mated stack height
MC-LPC-8.5L ASP-134605-01 45970-4107 male, mezzanine card side, Low-pin count (LPC), 160 I/O, tin-lead, 8.5 mm mated stack height
MC-HPC-8.5 ASP-134602-01 45970-4115 male, mezzanine card side, High-pin count (HPC), 400 I/O, lead-free, 8.5 mm mated stack height
MC-HPC-8.5L ASP-134601-01 45970-4117 male, mezzanine card side, High-pin count (HPC), 400 I/O, tin-lead, 8.5 mm mated stack height
MC-LPC-10 ASP-134604-01 45970-4305 male, mezzanine card side, Low-pin count (LPC), 160 I/O, lead-free, 10 mm mated stack height
MC-LPC-10L ASP-127797-01 45970-4307 male, mezzanine card side, Low-pin count (LPC), 160 I/O, tin-lead, 10 mm mated stack height
MC-HPC-10 ASP-134488-01 45970-4315 male, mezzanine card side, High-pin count (HPC), 400 I/O, lead-free, 10 mm mated stack height
MC-HPC-10L ASP-134487-01 45970-4317 male, mezzanine card side, High-pin count (HPC), 400 I/O, tin-lead, 10 mm mated stack height

KiCad already has footprints for ASP-134486, ASP-134602 and ASP-134604.

For now, I've just added lead-free Molex and Samtec partnumbers into filters, should I also create generic footprint? According to Molex and Samtec's drawing they have same footprint across all female and all male connectors.

Currently, there is symbol for FMC connectors, but it only defines 400 pins without any information about pin functions.

All contributions to the kicad library must follow the KiCad library convention

Thanks for creating a pull request to contribute to the KiCad libraries! To speed up integration of your PR, please check the following items:

  • Provide a URL to a datasheet for the symbol(s) you are contributing
  • An example screenshot image is very helpful
  • Ensure that the associated footprints match the official footprint library
    • A new fitting footprint must be submitted if the library does not yet contain one.
  • If there are matching footprint PRs, provide link(s) as appropriate
  • Check the output of the Travis automated check scripts - fix any errors as required
  • Give a reason behind any intentional library convention rule violation.
Edited by cpresser

Merge request reports