S2C.
S2C.

Choosing the Best Pin Multiplexing Method | System Design Engineering

Choosing the Best Pin Multiplexing Method | System Design Engineering Sep 12, 2016
Table of Content [Hide]

    Gabe Moretti Senior Editor


    S2C has recently published a white paper “Choosing the best pin multiplexing method for your multiple-FPGA partition”.  You can read the entire paper at www.s2ceda.com.  I think that a portion of the paper is interesting enough on its own merit to be published separately.


    Using multiple FPGAs to prototype a large design requires solving a classic problem: the number of signals that must pass between devices is greater than the number of I/Os pins on an FPGA. The classic solution is to use a TDM (Time Domain Multiplexing) scheme that muxes two or more signals over a single wire or pin.


    This solution is still widely employed, and coupled with the advances in FPGAs, the obstacles to constructing a multi-device prototype are greatly reduced. The latest FPGAs offer advantages such as a very high number of industry-standard I/O, integrated high-speed transceivers, and LVDS (Low Voltage Differential Signaling) signaling.



    Single-ended Signals vs. LVDS


    Single-ended TDM uses a single-ended signal which can transmit physical signals at a speed up to 290 MHz (Virtex UltraScale). This is determined by dividing the TDM ratio (or signal multiplexing ratio) and taking into account setup, synchronization and board delays.


    With a TDM ratio of 4:1, the system clock speed will be around 17.8 MHz. If the TDM ratio is increased to 16:1, the system clock speed will drop to less than 10 MHz. From this we can see that as the TDM ratio increases, the performance drop linearly.


    However, using the LVDS I/O standard supported by Xilinx FPGAs, the physical transmission data rate between FPGAs can achieve up to 1.6 Gbps. This offers tremendous advantages over single-ended transmission, even when considering that a single LVDS signal requires a pair of single-ended pins.


    This shows that for a system with a clock speed of 11 MHz, if 12800 virtual connections are needed, single-ended TDM consumes 1600 physical I/O. With LVDS TDM, this number is cut in half to 800.


    Given the physical I/O limitation of FPGAs, partitioning becomes easier if less physical interconnections are needed. LVDS TDM has clear advantages over traditional Single-Ended TDM.



    Partitioning and Automatic TDM Insertion


    Combining the technique of using asynchronous LVDS TDM with a single clock cycle design, it’s possible to create a tool that can partition a design and perform automatic TDM insertion. Ideally, such a tool would be able to:


    • Optimizes buses and match the LVDS resources in each bank considering such factors as trace lengths, matching impedances, and impedance continuity.


    • Avoid consuming FPGA design resources for the TDM circuity by taking advantage of built-in reference clocks (e.g.: IODELAY) to drive TDM clocks and resets


    S2C's Prodigy Play Pro is a tool that provides design partitioning across multiple FPGAs, and offers automatic TDM insertion based on an asynchronous TDM using LVDS.

    Back to list Back to list
    Related S2C Complete Prototyping Solutions
    Memory Modules
    DDR3 Memory Module, DDR3 Memory Module Type B, 8GB DDR4 Non-ECC,16GB DDR4 ECC
    Prodigy S7 Series (Virtex UltraScale+)
    The 7th generation SoC/ASIC prototyping solution from S2C, the Prodigy S7 series Logic System, is equipped with AMD's(Xilinx)Virtex UltraScale+™ FPGA. The Prodigy Logic System are supported by S2C'...
    High Speed GT Peripherals​
    PCIe Gen, PGT Module, PGT I/O connector, MCIO Module, Module Type B, QSFP+ connctors, QSFP + PGT Module, SFP+PGT Module, SATA PGT Module, SerDes, SMA PGT Module, Mini-SAS Module
    What's New at S2C
    Request for Quote
    What type of chip are you designing
    What is the capacity of the ASIC gate included in the design?
    5 million-20 million
    20 million-50 million
    50 million-100 million
    100 million-1 billion
    More than 1 billion
    Which FPGA do you prefer to use?
    Xilinx VU440
    Xilinx KU115
    Xilinx VU19P
    Xilinx VU13P
    Xilinx VU9P
    AMD VP1802
    AMD VP1902
    Intel S10-10M
    Intel S10-2800
    Not sure, need professional advice
    What kind of FPGA configuration do you need?
    Single FPGA
    Dual FPGA
    Four FPGAs
    Eight FPGAs
    Not sure, need professional advice
    What kind of peripheral interface do you need?
    How many prototype verification platforms do you need?
    Do you need the following tools?
    Segmentation tool
    Multiple FPGA debugging tools
    Co-modeling tool (allows large amounts of data to interact between FPGA and PC host)
    When do you need to use our products?
    0-6 months
    6-12 months
    More than 12 months
    Not sure
    Any additional comments?