AnsweredAssumed Answered

Vivado-Error Loading Fmcomms2 Project

Question asked by elta on Apr 27, 2015
Latest reply on May 15, 2015 by rejeesh

Hello guys,

I would like to open a project with the HDL source files of the zynq Board.

I downloaded the HDL directory from GitHub : here.

I work with Vivado 14.2 as required. I follow this AD guide.


I want to open the fmcomms2 project running on zc706 with the ad9361 library. By the way, what I really want is the fmcomms3 but the hdl files of the fmcomms2 and fmcomms3 are identical, aren't they?


I ran the following tcl commands:

-     cd F:/Vivado/hdl-master/library/axi_ad9361

-     source ./axi_ad9361_ip.tcl

-     cd F:/Vivado/hdl-master/projects/fmcomms2/zc706

-     source ./system_project.tcl


Loading the ad9361 library looks ok. I just have errors about file outside of the project directory but it is ok.

When it comes to the project, I have this error message:


ERROR: [BD 5-216] VLNV <> is not supported for this version of the tools.

ERROR: [Common 17-39] 'create_bd_cell' failed due to earlier errors.


    while executing

"create_bd_cell -type ip -vlnv axi_hdmi_clkgen"

    invoked from within

"set axi_hdmi_clkgen [create_bd_cell -type ip -vlnv axi_hdmi_clkgen]"

    (file "../../../projects/common/zc706/zc706_system_bd.tcl" line 57)


    while executing

"source $ad_hdl_dir/projects/common/zc706/zc706_system_bd.tcl"

    (file "system_bd.tcl" line 2)


    while executing

"source system_bd.tcl"

    (procedure "adi_project_create" line 107)

    invoked from within

"adi_project_create fmcomms2_zc706"

    (file "./system_project.tcl" line 7)



I looked for topic about this issue and it seems that it is not really a problem of version but rather of "vnlv".

Looking at the error message, we can observe that my "vendor" is definitely and not Then..I don't know .



Question 1 : To work with FMCOMMS3 board, do I have to work with FMCOMMS2 project?


Question 2 : How to fix my problem?

To help I copied the messages returned in the console by Vivado in a logfile (see Attachment)



Thanks for your help