Post Go back to editing

Failed build of axi_jesd204_tx while generating HDL reference design for ADRV0926 (ZCU102)

Thread Summary

The user encountered an error 'Failed to load feature 'ipservices'' while building the axi_jesd204_tx IP from the ADRV9026 ZCU102 repository. The issue was resolved after updating the Xilinx license file, confirming that the problem was related to licensing. The user also followed a suggested build process using Vivado's GUI and the adi_make.tcl script, which helped ensure the environment was correctly set up.
AI Generated Content
Category: Software
Product Number: ADRV9026
Software Version: Vivado/Vitis 2023.2; Windows 11 (64-bit); Cygwin

Dear all,

I tried to build and generate a hardware file (.xsa) based on this repository (https://github.com/analogdevicesinc/hdl/tree/main/projects/adrv9026/zcu102), but I got the following error while trying to build axi_jesd204_tx which was indicated in axi_jesd204_tx_ip.log: ERROR: [Common 17-217] Failed to load feature 'ipservices'.

I have been following this guide for building the HDL:

(https://wiki.analog.com/resources/fpga/docs/build?rev=1683209213).

I would appreciate any help for solving this issue.

Best regards,

Parents
  • Do you have a license from Xilinx to build projects with ZCU102?

  • We have a Vivado ML Enterprise Edition license. I do not honestly know if there is any other one required for building projects with ZCU102.

  • In this case, I think you're ok with the license.
    That's a very strange error. I haven't seen it before, and to me it looks like a Vivado issue.
    Could you post the contents of the $PATH variable from your environment? To check the Vivado paths.

    Another thing I would try, is to build the project in another way, by using the GUI.
    In the project's folder, open Vivado by typing vivado&.
    Then when it opens, in the Tcl console, run the following commands: 

    source ../../scripts/adi_make.tcl
    adi_make::lib all

    The last one builds all libraries on which the project is depending on, and I would like to see the outcome in Vivado. If somehow, by some miracle, it passes, the next command to run is source ./system_project.tcl, again in the Tcl console.
    I'm not sure this will solve the issue, but I would like to make sure this is checked from the beginning.
    I recreated your setup almost entirely, the exception being the Windows version, and for me it worked. I have Windows 10.

    In the meantime, I'll think of some other ways.

    Best regards,
    Iulia

  • First of all, we just updated the Xilinx license file. As a result, the license manager report looks like this now:

    Regarding the $PATH variable from my environment, I added the following lines to my .bashrc file (C:\cygwin64\etc\bash.bashrc) based on the Xilinx installation directory (C:\Xilinx\Vivado\2023.2) as follows:

    export PATH=$PATH:/cygdrive/C/Xilinx/Vivado/2023.2/bin
    export PATH=$PATH:/cygdrive/C/Xilinx/Vivado_HLS/2023.2/bin
    export PATH=$PATH:/cygdrive/C/Xilinx/Vitis/2023.2/bin
    export PATH=$PATH:/cygdrive/C/Xilinx/Vitis/2023.2/gnu/microblaze/nt/bin
    export PATH=$PATH:/cygdrive/C/Xilinx/Vitis/2023.2/gnu/arm/nt/bin
    export PATH=$PATH:/cygdrive/C/Xilinx/Vitis/2023.2/gnu/microblaze/linux_toolchain/nt64_be/bin
    export PATH=$PATH:/cygdrive/C/Xilinx/Vitis/2023.2/gnu/microblaze/linux_toolchain/nt64_le/bin
    export PATH=$PATH:/cygdrive/C/Xilinx/Vitis/2023.2/gnu/aarch32/nt/gcc-arm-none-eabi/bin

    I will try to build the project in the way you are suggesting, and then I will be back to you.

Reply
  • First of all, we just updated the Xilinx license file. As a result, the license manager report looks like this now:

    Regarding the $PATH variable from my environment, I added the following lines to my .bashrc file (C:\cygwin64\etc\bash.bashrc) based on the Xilinx installation directory (C:\Xilinx\Vivado\2023.2) as follows:

    export PATH=$PATH:/cygdrive/C/Xilinx/Vivado/2023.2/bin
    export PATH=$PATH:/cygdrive/C/Xilinx/Vivado_HLS/2023.2/bin
    export PATH=$PATH:/cygdrive/C/Xilinx/Vitis/2023.2/bin
    export PATH=$PATH:/cygdrive/C/Xilinx/Vitis/2023.2/gnu/microblaze/nt/bin
    export PATH=$PATH:/cygdrive/C/Xilinx/Vitis/2023.2/gnu/arm/nt/bin
    export PATH=$PATH:/cygdrive/C/Xilinx/Vitis/2023.2/gnu/microblaze/linux_toolchain/nt64_be/bin
    export PATH=$PATH:/cygdrive/C/Xilinx/Vitis/2023.2/gnu/microblaze/linux_toolchain/nt64_le/bin
    export PATH=$PATH:/cygdrive/C/Xilinx/Vitis/2023.2/gnu/aarch32/nt/gcc-arm-none-eabi/bin

    I will try to build the project in the way you are suggesting, and then I will be back to you.

Children
No Data