Post Go back to editing

ADRV9364-z7020 in ADRV1CRR-FMC

Category: Hardware
Product Number: ADRV-9364-z7020
Software Version: Vivado 2021.2

Hey guys,

I wanted to reach out because I am planning to do a temporary development step of using the ADRV1CRR-FMC carrier to power/connect to my newly acquired z7020. My current FPGA image/kuiper software stack ran well on this carrier with the z7035, but I wanted to check for the latest information on installing the "smaller" FPGA card onto this carrier. It would seem that there would be no IO conflicts/bus contention risks in any of the documentation, but I want to be sure.

My plan is the implement a custom version of the BOB, which is in the works, but to continue the software porting work I need to use the ADRV1CRR-FMC.

I know you guys have said it can work, but has there been any change to this? I assume I would just use the same Vivado project as the BOB to do this, since it shares a common header set.

Am I on the right track? Should I reconsider? I will be scrutinizing both schematics to see if there is anything sus, but I also wanted to reach out.

Thank you,


Parents Reply
  • Hi Andrei,

    I am trying to work from ../hdl/projects/adrv9364z7020 (or z7035) and using vivado. When I scrutinize the XDC for the z7020 I do not see any ethernet parameters or pins called out. I want to use the PHY on the card. Is this just a constraint that Vivado knows to apply for this device? I really would like some clear instructions on how to build the z7020 image ensuring ethernet is included. Right now, in Vivado, I see no indication that ethernet is being included in the design. Am I missing something?

    Thank you,


  • Andrei,

    I believe I have figured this out. The key is Vivado (and more specifically the Zynq IP) configures the "fixed" IO from its own knowledge of each device. When I look at the output of the z7020 example that can be built I see my ethernet pins are completely routed to MIO "fixed IO" pins and are consistent with my schematic for the PHY interface. These are then consistent with the IP configuration tool in Vivado for the Zynq. I appreciate all of your help, but this seems very clear now.