FMCOMMS8 HDL reference design

The HDL reference design is an embedded system built around a processor core either ARM, NIOS-II or Microblaze. A functional block diagram of the system is shown below. The two ADRV9009’s digital interface is handled by the transceiver IP followed by the JESD204B and device specific cores. The JESD204B lanes are shared among the 8 transmit, 4 receive and 4 observation/sniffer receive data paths by the same set of transceivers within the IP. The cores are programmable through an AXI-lite interface. The delineated data is then passed on to independent DMA cores for the transmit, receive and observation/sniffer paths.

Supported boards

Supported carriers

Evaluation board

Carrier

FMC slot

AD-FMCOMMS8-EBZ

A10SoC

FMCA

ZCU102

FMC HPC0

Block design

Block diagram

The data path and clock domains are depicted in the below diagrams:

Digital Interface

The digital interface consists of 8 transmit, 4 receive and 4 observation/sniffer lanes running up to 9.8Gbps. The transceivers then interface to the cores at 256bits @245.76MHz in the transmit and 128bits @245.76MHz for the receive channels. The sniffer/observation rates depend on the mode selected. The data is sent or received based on the configuration (programmable) from separate transmit and receive chains.

DAC Interface

The DAC data may be sourced from an internal data generator (DDS or pattern) or from the external DDR via DMA. The internal DDS phase and frequency are programmable. DAC unpack IP allows transfering data from the DMA to a reduced number of channels, at a higher rate.

ADC Interface

The ADC data is sent to the DDR via DMA. The ADC pack IP allowsc apturing only part of the channels.

Control and SPI

The device control and monitor signals are interfaced to a GPIO module. The SPI signals are controlled by a separate AXI based SPI core.

Configuration modes

The block design supports configuration of parameters and scales.

We have listed a couple of examples at section Building the HDL project and the default modes for each project.

Note

The parameters for Rx or Tx links can be changed from the system_project.tcl file, located in hdl/projects/fmcomms8/$CARRIER/system_project.tcl

LaneRate=SampleRateMLN108

The following are the parameters of this project that can be configured:

  • [RX/TX/RX_OS]_JESD_M: number of converters per link

  • [RX/TX/RX_OS]_JESD_L: number of lanes per link

  • [RX/TX/RX_OS]_JESD_S: number of samples per frame

CPU/Memory interconnects addresses

The addresses are dependent on the architecture of the FPGA, having an offset added to the base address from HDL (see more at CPU/Memory interconnects addresses).

Instance

ZynqMP

rx_adrv9009_fmc_tpl_core

0x85A0_0000

tx_adrv9009_fmc_tpl_core

0x85A0_4000

obs_adrv9009_fmc_tpl_core

0x85A0_8000

axi_adrv9009_fmc_rx_xcvr

0x85A4_0000

axi_adrv9009_fmc_tx_xcvr

0x85A2_0000

axi_adrv9009_fmc_obs_xcvr

0x85A6_0000

axi_adrv9009_fmc_tx_jesd

0x85A3_0000

axi_adrv9009_fmc_rx_jesd

0x85A5_0000

axi_adrv9009_fmc_obs_jesd

0x85A7_0000

axi_adrv9009_fmc_rx_dma

0x9D42_0000

axi_adrv9009_fmc_tx_dma

0x9D40_0000

axi_adrv9009_fmc_obs_dma

0x9D44_0000

SPI connections

SPI type

SPI manager instance

SPI subordinate

CS

PS

spi0

ADRV9009-C

0

ADRV9009-D

1

HMC7044

2

GPIOs

GPIO signal

Direction

HDL GPIO EMIO

Software GPIO

(from FPGA view)

Zynq MP

hmc7044_gpio_4

INOUT

67

145

hmc7044_gpio_3

INOUT

66

144

hmc7044_gpio_2

INOUT

65

143

hmc7044_gpio_1

INOUT

64

142

hmc7044_sync

INOUT

63

141

hmc7044_reset

INOUT

62

140

adrv9009_tx2_enable_d

INOUT

61

139

adrv9009_tx1_enable_d

INOUT

60

138

adrv9009_rx2_enable_d

INOUT

59

137

adrv9009_rx1_enable_d

INOUT

58

136

adrv9009_reset_b_d

INOUT

57

135

adrv9009_gpint_d

INOUT

56

134

adrv9009_gpio_{08:00}_d

INOUT

55:47

133:125

adrv9009_tx2_enable_c

INOUT

46

124

adrv9009_tx1_enable_c

INOUT

45

123

adrv9009_rx2_enable_c

INOUT

44

122

adrv9009_rx1_enable_c

INOUT

43

121

adrv9009_reset_b_c

INOUT

42

120

adrv9009_gpint_c

INOUT

41

119

adrv9009_gpio_{08:00}_c

INOUT

40:32

118:110

Interrupts

Below are the Programmable Logic interrupts used in this project.

Instance name

HDL

Linux ZynqMP

Actual ZynqMP

axi_adrv9009_fmc_obs_jesd

8

104

136

axi_adrv9009_fmc_tx_jesd

9

105

137

axi_adrv9009_fmc_rx_jesd

10

106

138

axi_adrv9009_fmc_obs_dma

11

107

139

axi_adrv9009_fmc_tx_dma

12

108

140

axi_adrv9009_fmc_rx_dma

13

109

141

Building the HDL project

The design is built upon ADI’s generic HDL reference design framework. ADI distributes the bit/elf files of these projects as part of the ADI Kuiper Linux. If you want to build the sources, ADI makes them available on the HDL repository. To get the source you must clone the HDL repository.

Then go to the project location, choose your carrier and run the make command by typing in your command prompt:

Linux/Cygwin/WSL

~$
cd hdl/projects/fmcomms8/zcu102
~/hdl/projects/fmcomms8/zcu102$
make

The following dropdowns contain tables with the parameters that can be used to configure this project, depending on the carrier used.

Parameter

Default value of the parameters depending on carrier

A10SoC/ZCU102

RX_JESD_M

8

RX_JESD_L

4

RX_JESD_S

1

TX_JESD_M

8

TX_JESD_L

8

TX_JESD_S

1

RX_OS_JESD_M

4

RX_OS_JESD_L

4

RX_OS_JESD_S

1

A more comprehensive build guide can be found in the Build an HDL project user guide.

Other considerations

ADC - lane mapping

Due to physical constraints, Rx lanes are reordered as described in the following table.

ADC phy Lane

FPGA Rx lane / Logical Lane

0

0

1

1

2

4

3

5

ADC OBS phy Lane

FPGA Rx lane / Logical Lane

0

2

1

3

2

6

3

7

DAC - lane mapping

Due to physical constraints, Tx lanes are reordered as described in the following table.

DAC phy lane

FPGA Tx lane / Logical lane

0

1

1

0

2

2

3

3

4

4

5

5

6

6

7

7

Resources

More information

Support

Analog Devices, Inc. will provide limited online support for anyone using the reference design with ADI components via the EngineerZone FPGA reference designs forum.

For questions regarding the ADI Linux device drivers, device trees, etc. from our Linux GitHub repository, the team will offer support on the EngineerZone Linux software drivers forum.

For questions concerning the ADI No-OS drivers, from our No-OS GitHub repository, the team will offer support on the EngineerZone microcontroller No-OS drivers forum.

It should be noted, that the older the tools’ versions and release branches are, the lower the chances to receive support from ADI engineers.