UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Explorer
Explorer
987 Views
Registered: ‎03-17-2011

ZCU106 -ES board file not detected

Jump to solution

Hello,

 

I have a ES version of the ZCU106 board. I've retrieve from the xilinx web site the board file for Vivado 2018.1.

I copied the files into my vivado installation directory (Vivado/2018.1/data/boards/board_files/zcu106).

 

Restarted vivado, created a new project targetting the board.. unfortunately, I can't see the board... in the selection list.

(and yes, I've selected "view all" and not only "latest").

 

Does anybody knows how to solve this?

 

Sébastien

 

 

 

--Sebastien
0 Kudos
1 Solution

Accepted Solutions
Explorer
Explorer
1,304 Views
Registered: ‎03-17-2011

Re: ZCU106 -ES board file not detected

Jump to solution

Problem is solved by creating the Vivado_init.tcl file and adding "enable_beta_device*" in it.

 

enable_beta_device* in the tcl console is not the solution as it does not apply to all vivado processes (it seems like it anyway).

 

Sébastien

--Sebastien
0 Kudos
6 Replies
Explorer
Explorer
984 Views
Registered: ‎03-17-2011

Re: ZCU106 -ES board file not detected

Jump to solution

Note that I can't select the ES version of a ZCU7EV. Only "EG".

It is not available in vivado 2018.1...

So I think that's the reason why the board is not seen.

 

Is there a way to add these devices?

--Sebastien
0 Kudos
Moderator
Moderator
889 Views
Registered: ‎11-09-2015

Re: ZCU106 -ES board file not detected

Jump to solution

Hi @sebo,

 

1. Make sure you have installed the ES devices during the installation of vivado (you can change this from the Xilinx information center)

instal.JPG

 

2.You need a license for the ES devices, make sure you are pointing to it

 

3. Make sure you do "enable_beta_device *" when starting vivado or in the vivado_init.tcl file.

 

Regards,


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
0 Kudos
Explorer
Explorer
871 Views
Registered: ‎03-17-2011

Re: ZCU106 -ES board file not detected

Jump to solution

Hello Florent,

 

I've checked all that.

I was able to start (on linux) a project for that board. however, the selected part was not found.

That's a problem that I don't find on windows.

 

Regards,

 

Sébastein.

--Sebastien
0 Kudos
Moderator
Moderator
861 Views
Registered: ‎06-24-2015

Re: ZCU106 -ES board file not detected

Jump to solution

@sebo

 

You can store the files in a location and use the following command in tcl console :
set_param board.repoPaths <location to ZCU106 Board files>

 

It will be much better if you could place this command in the Vivado_init.tcl file in the Xilinx/Vivado/<version>/scripts folder as you can see the board on startup.

Thanks,
Nupur
--------------------------------------------------------------------------------------------
Google your question before posting. If someone's post answers your question, mark the post as answer with "Accept as solution". If you see a particularly good and informative post, consider giving it Kudos (click on the 'thumbs-up' button).
0 Kudos
Moderator
Moderator
851 Views
Registered: ‎11-09-2015

Re: ZCU106 -ES board file not detected

Jump to solution

Hi Sebastien @sebo,

 

Try to use enable_beta_devices* in the vivado_init.tcl file not directly from the tcl console.

 

Regards,


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
0 Kudos
Explorer
Explorer
1,305 Views
Registered: ‎03-17-2011

Re: ZCU106 -ES board file not detected

Jump to solution

Problem is solved by creating the Vivado_init.tcl file and adding "enable_beta_device*" in it.

 

enable_beta_device* in the tcl console is not the solution as it does not apply to all vivado processes (it seems like it anyway).

 

Sébastien

--Sebastien
0 Kudos