Each carrier channel provides a set of 12 digital general purpose I/O (GPIO) signals.

The GPIO signals route between the interface adapter module and the FPGA. These signals are typically used for side-channel communication such as auxiliary control, synchronization, and application specific signaling.

The carrier reserves one pair of the GPIO lines in each channel for the primary I2C configuration interface. The FlexRIO driver allows you to control the primary I2C configuration interface through the I2C API. Use the I2C API to configure the components mapped to that channel.

The LabVIEW FPGA I/O node exposes all GPIO signals to the LabVIEW FPGA application logic. A provided mask indicates if the carrier is actively using any of the GPIO outside of your application logic. The FlexRIO driver blocks GPIO control while the carrier configures during power on and after a commit or reset. Your application logic can also independently control the direction and value of each I/O signal.

The Interface Adapter Module exposes 12 bidirectional GPIO signals per carrier channel through LabVIEW FPGA I/O nodes. Use the associated data, direction, and mask nodes to control the signals and identify those reserved for carrier functions such as primary I2C communication.

Tip GPIO FPGA I/O nodes are automatically included in the generated Getting Started example projects.
Note For information about how to add GPIO I/O nodes, refer to Adding GPIO I/O Nodes to the LabVIEW Project.

Primary I2C Interface

The carrier reserves one pair of GPIO nodes on each channel for the primary I2C configuration interface. Device initialization, configuration commits, and FlexRIO API I2C transactions can temporarily block application access to these I/O nodes.

You can still use this pair of GPIO signals that are reserved for the primary I2C interface. The I2C Tap feature drives I2C transactions to the SerDes through these signals. This capability is useful when an I2C Tap application needs to send I2C transactions to the SerDes through the same GPIO signals.

Use the GPIO mask registers to determine which GPIO signals are available for user application control:
  • GPIO Input Mask = 0xFFF: The LabVIEW FPGA application can monitor GPIO input signals GPIO[11:0].
  • GPIO Output Mask = 0xFFF: GPIO[11:0] are available for FPGA control. The LabVIEW FPGA application might write to the GPIO output nodes for GPIO[11:0].
  • GPIO Output Mask = 0xFFC: GPIO[1:0] are owned by the Host FlexRIO API for an I2C operation. The LabVIEW FPGA application must not write to the GPIO[1:0] output nodes until GPIO Output Mask[1:0] returns to 1.
  • GPIO Output Enable Mask = 0xFFF: GPIO[11:0] direction control is available to the FPGA. The LabVIEW FPGA application might configure GPIO[11:0] as inputs or outputs.
  • GPIO Output Enable Mask = 0xFFC: GPIO[1:0] direction control is owned by the Host FlexRIO API for an I2C operation. The LabVIEW FPGA application must not modify the direction of GPIO[1:0] until the GPIO Output Enable Mask[1:0] returns to 1.

The maximum GPIO toggle rate is 100 MHz. You must use the GPIO in a single-cycle timed loop (SCTL) with PXIe_Clk100 as the clock source. Use application logic to generate lower toggle rates, if needed.