Supported carrier boards

List of supported boards

Carrier board

FMC

Zynq-7000 ZedBoard

LPC

Zynq-7000 PicoZed FMC Carrier Card V2 with PicoZed 7030

LPC

Zynq-7000 ZC706 Evaluation board

LPC, HPC

Zynq UltraScale+ UltraZed-EG PCIe Carrier Card

LPC

Zynq UltraScale+ UltraZed EV Carrier Card

HPC

Zynq UltraScale+ ZCU102 Evaluation board

HPC0, HPC1

Zynq UltraScale+ ZCU104 Evaluation board

LPC

Zynq UltraScale+ ZCU106 Evaluation board

HPC0

Zynq UltraScale+ ZCU111 Evaluation board

FMC+

Zynq UltraScale+ ZCU208 Evaluation board

FMC+

Zynq UltraScale+ PYNQ-ZU Evaluation board

LPC

Unlisted boards

If you need more information on whether the Ethernet FMC is compatible with a carrier that is not listed above, please first check the compatibility list. If the carrier is not listed there, please contact Opsero, provide us with the pinout of your carrier and we’ll be happy to check compatibility and generate a Vivado constraints file for you.

Board specific notes

ZCU106

  • The HPC0 connector on this board supports all 4 ports of the Ethernet FMC. This design uses up all 4 GEMs, leaving the ZCU106’s on-board Ethernet port unusable.

ZCU102

  • This design supports the ZCU102 Rev 1.0 board. Use a commit before 2017/02/13 for the older Rev-D board design. Note that the FMC pinouts differ between Rev 1.0 and Rev D: Answer record 68050

  • The HPC0 design uses 4x GEMs to connect to ports 0-3 of the Ethernet FMC. This design uses up all 4 GEMs, leaving the ZCU102’s on-board Ethernet port unusable.

  • The HPC1 design uses 3x GEMs to connect to ports 0-2 of the Ethernet FMC. The 4th port is left unconnected because certain pins required by the Ethernet FMC (namely LA30, LA31 and LA32) are left unconnected on the HPC1 connector of the ZCU102 board. The ZCU102’s on-board Ethernet port connects to GEM3 and is usable in this design.

UltraZed-EG and UltraZed-EV

  • The UltraZed designs use 4x GEMs to connect to ports 0-3 of the Ethernet FMC. These designs use up all 4 GEMs, leaving the on-board Ethernet port unusable.

ZedBoard and PicoZed

When changing ETH_FMC_PORT from 0-2 to 3 (ie. when switching to GEM1), it has been noticed that you have to power cycle the board. When the SDK project is configured for AXI Ethernet, it must make some Zynq configurations that are not compatible with the GEM1 configuration.

The on-board Ethernet port on all of these designs is connected to GEM0 and is usable.