cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
martin.elliott
Visitor
Visitor
4,907 Views
Registered: ‎06-14-2019

[Board 49-67] The board_part definition was not found

Jump to solution

Hi,  I'm using Vivado 2019.2.1

and I'm getting a critical warning

[Board 49-67] The board_part definition was not found for trenz.biz:te0820_2cg_1i:part0:2.0. This can happen sometimes when you use custom board part. You can resolve this issue by setting 'board.repoPaths' parameter, pointing to the location of custom board files. Valid board_part values can be retrieved with the 'get_board_parts' Tcl command.

 

When I use 'get_board_parts' trenz.biz:te0820_2cg_1i:part0:2.0 is in the list.

 

I have also used

set_property board_part trenz.biz:te0820_2cg_1i:part0:2.0 [current_project]

 

I know this is not a xilinx board but this was the forum that seemed to have the most messages relating to this subject.

 

Thanks

 

 

 

0 Kudos
1 Solution

Accepted Solutions
ashishd
Xilinx Employee
Xilinx Employee
4,878 Views
Registered: ‎02-14-2014

Hi @martin.elliott ,

Yes you can safely ignore them. They'll be removed in 2020.1.

Regards,
Ashish
----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------

View solution in original post

19 Replies
dpaul24
Scholar
Scholar
4,895 Views
Registered: ‎08-07-2014

@martin.elliott,

You might proceed ahread with project development by using the FPGA part number rather than the board part number.

------------FPGA enthusiast------------
Consider giving "Kudos" if you like my answer. Please mark my post "Accept as solution" if my answer has solved your problem
Asking for solutions to problems via PM will be ignored.

ashishd
Xilinx Employee
Xilinx Employee
4,890 Views
Registered: ‎02-14-2014

Hi @martin.elliott ,

Do you want to report this issue for redundant critical warnings or is this a complaint about using the board which you wish to use? 

Just FYI, board files can also be downloaded from GitHub using this link -

https://github.com/Xilinx/XilinxBoardStore/tree/master/boards/Trenz_Electronic

Regards,
Ashish
----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------
martin.elliott
Visitor
Visitor
4,882 Views
Registered: ‎06-14-2019

It was more a question of is it safe to ignore the critical warning or is there a way to clear it?

ashishd
Xilinx Employee
Xilinx Employee
4,879 Views
Registered: ‎02-14-2014

Hi @martin.elliott ,

Yes you can safely ignore them. They'll be removed in 2020.1.

Regards,
Ashish
----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------

View solution in original post

TobiasWeber1
Visitor
Visitor
4,747 Views
Registered: ‎03-28-2020

Hello,

I am having the same issue. But I don't think it can be ignored. When ever I am running into this issue a bunch of other topics comes up. With that project in VIVADO, the related projects in VITIS and even new projects in VIVADO.

 

So what I did:

  1. Creating a new very simple project in VIVADO for the Zybo_Z7_20, following ug1165 tutorial CH2. Doeing the export to VITIS, reating platform, system and app (HelloWorld). Succesfull run! Perfect!
  2. Creating a new, empty, project in VIVADO for the Zybo_Z7_20. Creating new block_design. Adding Zynq PS ip. Run automatic_block_initialization, use board_presets enabled. But none of the components gets initilized! Strange as I re-did exeactly what I have done before (see 1.)
  3. Now restart VIVADO and re-open the project succsefully created and tested under 1. Running it to the issue you mention we can safley ignor:

 

See the unexpected error, when loading a project that went well before:

 

[Board 49-67] The board_part definition was not found for digilentinc.com:zybo-z7-20:part0:1.0. This can happen sometimes when you use custom board part. You can resolve this issue by setting 'board.repoPaths' parameter, pointing to the location of custom board files. Valid board_part values can be retrieved with the 'get_board_parts' Tcl command.

 

Error is strange as the board is included in the list of avaiable parts.

 

get_board_parts
WARNING: [Board 49-26] cannot add Board Part xilinx.com:au280_es1:part0:1.0 available at /home/tobias/.Xilinx/Vivado/2019.2/xhub/board_store/XilinxBoardStore/Vivado/2019.2/boards/Xilinx/au280/es1/1.0/1.0/board.xml as part xcu280-fsvh2892-2l-e-es1 specified in board_part file is either invalid or not available
WARNING: [Board 49-26] cannot add Board Part xilinx.com:au280_es1:part0:1.1 available at /home/tobias/.Xilinx/Vivado/2019.2/xhub/board_store/XilinxBoardStore/Vivado/2019.2/boards/Xilinx/au280/es1/1.1/1.1/board.xml as part xcu280-fsvh2892-2l-e-es1 specified in board_part file is either invalid or not available
WARNING: [Board 49-26] cannot add Board Part xilinx.com:kcu105:part0:1.6 available at /home/tobias/.Xilinx/Vivado/2019.2/xhub/board_store/XilinxBoardStore/Vivado/2019.2/boards/Xilinx/kcu105/1.6/1.6/board.xml as part xcku040-ffva1156-2-e specified in board_part file is either invalid or not available
WARNING: [Board 49-26] cannot add Board Part xilinx.com:kcu116:part0:1.4 available at /home/tobias/.Xilinx/Vivado/2019.2/xhub/board_store/XilinxBoardStore/Vivado/2019.2/boards/Xilinx/kcu116/1.4/1.4/board.xml as part xcku5p-ffvb676-2-e specified in board_part file is either invalid or not available
WARNING: [Board 49-26] cannot add Board Part xilinx.com:vcu108:part0:1.6 available at /home/tobias/.Xilinx/Vivado/2019.2/xhub/board_store/XilinxBoardStore/Vivado/2019.2/boards/Xilinx/vcu108/1.6/1.6/board.xml as part xcvu095-ffva2104-2-e specified in board_part file is either invalid or not available
WARNING: [Board 49-26] cannot add Board Part xilinx.com:vcu110:part0:1.4 available at /home/tobias/.Xilinx/Vivado/2019.2/xhub/board_store/XilinxBoardStore/Vivado/2019.2/boards/Xilinx/vcu110/1.4/1.4/board.xml as part xcvu190-flgc2104-2-e specified in board_part file is either invalid or not available
WARNING: [Board 49-26] cannot add Board Part xilinx.com:vcu128:part0:1.0 available at /home/tobias/.Xilinx/Vivado/2019.2/xhub/board_store/XilinxBoardStore/Vivado/2019.2/boards/Xilinx/vcu128/production/1.0/1.0/board.xml as part xcvu37p-fsvh2892-2l-e specified in board_part file is either invalid or not available
WARNING: [Board 49-26] cannot add Board Part xilinx.com:vcu128_es:part0:1.0 available at /home/tobias/.Xilinx/Vivado/2019.2/xhub/board_store/XilinxBoardStore/Vivado/2019.2/boards/Xilinx/vcu128/es/1.0/1.0/board.xml as part xcvu37p-fsvh2892-2l-e-es1 specified in board_part file is either invalid or not available
WARNING: [Board 49-26] cannot add Board Part xilinx.com:vcu128_es:part0:1.1 available at /home/tobias/.Xilinx/Vivado/2019.2/xhub/board_store/XilinxBoardStore/Vivado/2019.2/boards/Xilinx/vcu128/es/1.1/1.1/board.xml as part xcvu37p-fsvh2892-2l-e-es1 specified in board_part file is either invalid or not available
WARNING: [Board 49-26] cannot add Board Part xilinx.com:vcu129:part0:1.0 available at /home/tobias/.Xilinx/Vivado/2019.2/xhub/board_store/XilinxBoardStore/Vivado/2019.2/boards/Xilinx/vcu129/production/1.0/1.0/board.xml as part xcvu29p-fsga2577-2l-e specified in board_part file is either invalid or not available
WARNING: [Board 49-26] cannot add Board Part xilinx.com:vcu129_es:part0:1.0 available at /home/tobias/.Xilinx/Vivado/2019.2/xhub/board_store/XilinxBoardStore/Vivado/2019.2/boards/Xilinx/vcu129/es/1.0/1.0/board.xml as part xcvu29p-fsga2577-2l-e-es1 specified in board_part file is either invalid or not available
WARNING: [Board 49-26] cannot add Board Part xilinx.com:zcu216_es:part0:1.0 available at /home/tobias/.Xilinx/Vivado/2019.2/xhub/board_store/XilinxBoardStore/Vivado/2019.2/boards/Xilinx/zcu216/1.0/1.0/board.xml as part xczu49dr-ffvf1760-2-e-es1 specified in board_part file is either invalid or not available
alpha-data.com:adm-pcie-7v3:part0:1.0 alpha-data.com:adm-pcie-7v3:part0:1.1 digilentinc.com:arty-a7-100:part0:1.0 digilentinc.com:arty-a7-35:part0:1.0 digilentinc.com:arty-s7-25:part0:1.0 digilentinc.com:arty-s7-50:part0:1.0 digilentinc.com:arty-z7-10:part0:1.0 digilentinc.com:arty-z7-20:part0:1.0 digilentinc.com:arty:part0:1.1 digilentinc.com:basys3:part0:1.1 digilentinc.com:cmod-s7-25:part0:1.0 digilentinc.com:cmod_a7-15t:part0:1.1 digilentinc.com:cmod_a7-35t:part0:1.1 digilentinc.com:cora-z7-07s:part0:1.0 digilentinc.com:cora-z7-10:part0:1.0 digilentinc.com:genesys2:part0:1.1 digilentinc.com:nexys4:part0:1.1 digilentinc.com:nexys4_ddr:part0:1.1 digilentinc.com:nexys_video:part0:1.1 digilentinc.com:sword:part0:1.0 digilentinc.com:zedboard:part0:1.0 digilentinc.com:zybo-z7-10:part0:1.0 digilentinc.com:zybo-z7-20:part0:1.0 digilentinc.com:zybo:part0:1.0 em.avnet.com:minized:part0:1.2 em.avnet.com:picozed_7010_fmc2:part0:1.2 em.avnet.com:ultra96:part0:1.2 em.avnet.com:zed:part0:0.9 em.avnet.com:zed:part0:1.0 em.avnet.com:zed:part0:1.1 em.avnet.com:zed:part0:1.2 em.avnet.com:zed:part0:1.3 em.avnet.com:zed:part0:1.4 trenz.biz:te0712_100_1i:part0:1.0 trenz.biz:te0712_100_2c:part0:1.0 trenz.biz:te0712_100_2c:part0:2.0 trenz.biz:te0712_200_1i:part0:1.0 trenz.biz:te0712_200_2c:part0:1.0 trenz.biz:te0712_200_2i:part0:1.0 trenz.biz:te0712_35_2i:part0:1.0 trenz.biz:te0720_14s:part0:1.0 trenz.biz:te0720_1c:part0:1.0 trenz.biz:te0720_1c:part0:2.0 trenz.biz:te0720_1il:part0:1.0 trenz.biz:te0720_1q:part0:1.0 trenz.biz:te0720_2e:part0:1.0 trenz.biz:te0720_2i:part0:1.0 trenz.biz:te0722:part0:1.0 trenz.biz:te0722_7s:part0:1.0 trenz.biz:te0722_i:part0:1.0 trenz.biz:te0724_10_1i:part0:1.0 trenz.biz:te0724_20_1i:part0:1.0 trenz.biz:te0725_100_2c:part0:1.0 trenz.biz:te0725_100_2i:part0:1.0 trenz.biz:te0725_15_1c:part0:1.0 trenz.biz:te0725_35_2c:part0:1.0 trenz.biz:te0725lp_100:part0:1.0 trenz.biz:te0726_01:part0:1.0 trenz.biz:te0726_7s:part0:3.1 trenz.biz:te0726_m:part0:3.1 trenz.biz:te0726_r:part0:2.1 trenz.biz:te0729_20_2i:part0:1.0 trenz.biz:te0729_20_2i:part0:2.0 trenz.biz:te0803_2cg_1e:part0:1.0 trenz.biz:te0803_2cg_1e_tebf0808:part0:2.0 trenz.biz:te0803_2eg_1e:part0:1.0 trenz.biz:te0803_2eg_1e_tebf0808:part0:2.0 trenz.biz:te0803_3cg_1e:part0:1.0 trenz.biz:te0803_3cg_1e_tebf0808:part0:2.0 trenz.biz:te0803_3eg_1e:part0:1.0 trenz.biz:te0803_3eg_1e:part0:3.0 trenz.biz:te0803_3eg_1e_tebf0808:part0:2.0 trenz.biz:te0803_3eg_1e_tebf0808:part0:4.0 trenz.biz:te0803_4cg_1e:part0:1.0 trenz.biz:te0803_4cg_1e_tebf0808:part0:2.0 trenz.biz:te0803_4eg_1e:part0:1.0 trenz.biz:te0803_4eg_1e_tebf0808:part0:2.0 trenz.biz:te0803_4eg_1i:part0:5.0 trenz.biz:te0803_4eg_1i_tebf0808:part0:6.0 trenz.biz:te0803_4ev_1e:part0:1.0 trenz.biz:te0803_4ev_1e_tebf0808:part0:2.0 trenz.biz:te0803_5ev_1e:part0:1.0 trenz.biz:te0803_5ev_1e_tebf0808:part0:2.0 trenz.biz:te0803_5ev_1i:part0:1.0 trenz.biz:te0803_5ev_1i_tebf0808:part0:2.0 trenz.biz:te0808_15eg_1e:part0:3.0 trenz.biz:te0808_15eg_1e_tebf0808:part0:4.0 trenz.biz:te0808_6eg_1e:part0:3.0 trenz.biz:te0808_6eg_1e_tebf0808:part0:4.0 trenz.biz:te0808_9eg_1e:part0:1.0 trenz.biz:te0808_9eg_1e:part0:3.0 trenz.biz:te0808_9eg_1e_tebf0808:part0:2.0 trenz.biz:te0808_9eg_1e_tebf0808:part0:4.0 trenz.biz:te0808_9eg_2i:part0:3.0 trenz.biz:te0808_9eg_2i_tebf0808:part0:4.0 trenz.biz:te0820_2cg_1e:part0:1.0 trenz.biz:te0820_2eg_1e:part0:1.0 trenz.biz:te0820_2eg_1e:part0:2.0 trenz.biz:te0820_3cg_1e:part0:1.0 trenz.biz:te0820_3eg_1e:part0:1.0 trenz.biz:te0820_4cg_1e:part0:1.0 trenz.biz:te0820_4ev_1e:part0:1.0 trenz.biz:teb0911_9eg_1e:part0:1.0 trenz.biz:tec0850_15eg_1e:part0:1.0 xilinx.com:ac701:part0:1.0 xilinx.com:ac701:part0:1.1 xilinx.com:ac701:part0:1.2 xilinx.com:ac701:part0:1.3 xilinx.com:ac701:part0:1.4 xilinx.com:au200:part0:1.0 xilinx.com:au200:part0:1.1 xilinx.com:au200:part0:1.2 xilinx.com:au200:part0:1.3 xilinx.com:au250:part0:1.0 xilinx.com:au250:part0:1.1 xilinx.com:au250:part0:1.2 xilinx.com:au250:part0:1.3 xilinx.com:au280:part0:1.0 xilinx.com:au280:part0:1.1 xilinx.com:au50:part0:1.0 xilinx.com:au50dd:part0:1.0 xilinx.com:kc705:part0:0.9 xilinx.com:kc705:part0:1.0 xilinx.com:kc705:part0:1.1 xilinx.com:kc705:part0:1.2 xilinx.com:kc705:part0:1.3 xilinx.com:kc705:part0:1.4 xilinx.com:kc705:part0:1.5 xilinx.com:kc705:part0:1.6 xilinx.com:kcu1500:part0:1.0 xilinx.com:kcu1500:part0:1.1 xilinx.com:kcu1500:part0:1.2 xilinx.com:pico_m505:part0:1.0 xilinx.com:sp701:part0:1.0 xilinx.com:vc707:part0:1.0 xilinx.com:vc707:part0:1.1 xilinx.com:vc707:part0:1.2 xilinx.com:vc707:part0:1.3 xilinx.com:vc707:part0:1.4 xilinx.com:vc709:part0:1.0 xilinx.com:vc709:part0:1.1 xilinx.com:vc709:part0:1.2 xilinx.com:vc709:part0:1.3 xilinx.com:vc709:part0:1.4 xilinx.com:vc709:part0:1.5 xilinx.com:vc709:part0:1.6 xilinx.com:vc709:part0:1.7 xilinx.com:vc709:part0:1.8 xilinx.com:vcu118:part0:2.0 xilinx.com:vcu118:part0:2.1 xilinx.com:vcu118:part0:2.2 xilinx.com:vcu118:part0:2.3 xilinx.com:vcu1525:part0:1.0 xilinx.com:vcu1525:part0:1.1 xilinx.com:vcu1525:part0:1.2 xilinx.com:vcu1525:part0:1.3 xilinx.com:zc702:part0:1.0 xilinx.com:zc702:part0:1.1 xilinx.com:zc702:part0:1.2 xilinx.com:zc702:part0:1.3 xilinx.com:zc702:part0:1.4 xilinx.com:zc706:part0:1.0 xilinx.com:zc706:part0:1.1 xilinx.com:zc706:part0:1.2 xilinx.com:zc706:part0:1.3 xilinx.com:zc706:part0:1.4 xilinx.com:zcu102:part0:3.1 xilinx.com:zcu102:part0:3.2 xilinx.com:zcu102:part0:3.3 xilinx.com:zcu104:part0:1.0 xilinx.com:zcu104:part0:1.1 xilinx.com:zcu106:part0:2.0 xilinx.com:zcu106:part0:2.1 xilinx.com:zcu106:part0:2.2 xilinx.com:zcu106:part0:2.3 xilinx.com:zcu106:part0:2.4 xilinx.com:zcu106:part0:2.5 xilinx.com:zcu111:part0:1.1 xilinx.com:zcu111:part0:1.2 xilinx.com:zcu1275:part0:1.0 xilinx.com:zcu1285:part0:1.0

 

 

Error even gets worse. Just open the PS7 block and close without any change! And boom, complains abut Ethernet interface not configured properly. Btw. the config is fine, it ran before.

Vivado-Screen-Shot-1.png

 

So to make it short. The error cannot be ignored! How long do you expect we need to wait for 2020.1?

For me it is a high priority item. As when ever I run into this situation. I don't have a stable way to get VIVIADO and VITIS back to a stable behaviour (doeing what was posible before and documented in the xilinx tutorials). As also new projects are affected and I cannot do any modify to previously successful projects. Sofar the only success is. Purge all workspaces VIVADO, VITIS, reload board-files from xHub and start all over again.

 

0 Kudos
tcs6770
Visitor
Visitor
3,278 Views
Registered: ‎09-14-2018

I am using Vivado 2020.2 and I still recieve this critical warning after generating a bitstream file.

[Board 49-67] The board_part definition was not found for digilentinc.com:zybo-z7-20:part0:1.0. This can happen sometimes when you use custom board part. You can resolve this issue by setting 'board.repoPaths' parameter, pointing to the location of custom board files. Valid board_part values can be retrieved with the 'get_board_parts' Tcl command.

I have all the proper board and parts installed from the Xhub store but the warning always persists.  

It doesnt seem to break the hardware xsa wrapper generation in Vitis though so I have been ignoring this.  Its just my paranoia OCD hates seeing critical warnings everytime I create a bitstream file :).

0 Kudos
_risc_
Visitor
Visitor
2,635 Views
Registered: ‎03-24-2021

I too can confirm 2020.2 still produces this critical warning for me.

0 Kudos
GuinnessTrinke_
Visitor
Visitor
1,792 Views
Registered: ‎02-17-2021

> I too can confirm 2020.2 still produces this critical warning for me.

 

same here

0 Kudos
ashishd
Xilinx Employee
Xilinx Employee
1,527 Views
Registered: ‎02-14-2014

Hi @GuinnessTrinke_ @_risc_ ,

I verified this with 2021.1 and didn't observe these warnings for board file whose part is absent in this Vivado version.

If you see same problem with 2021.1, please share steps you followed before landing into these warnings. I'll take a look and update.

Regards,
Ashish
----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------
AndrewJ
Visitor
Visitor
925 Views
Registered: ‎08-13-2021

Hi  @ashishd 

I'm running Vivado ML 2021.1 on Ubuntu 20.04 with an Avnet Ultra96-V2 board and I see this message after generating a bitstream.  To reproduce:

  • Use Vivado Store to install the Ultra96-V2 board.
  • Create a new project: RTL, no sources, select board Ultra96-V2.
  • Create Block Design: add Ultrascale Zynq, run board automation, connect pl_clk0 to maxihpm0_fpd_aclk and maxihpm1_fpd_aclk.  Verify design.
  • Generate output products
  • Create HDL Wrapper
  • Run Synthesis
  • Run Implementation
  • Generate Bitstream

get_param board.repoPaths reports:

/home/andrewjohnson/.Xilinx/Vivado/2021.1/xhub/board_store/xilinx_board_store

Check in Messages for critical warnings.  There are 2 the same and are the warning referred to in this set of posts.  I believe the warnings can be ignored as I've successfully created a very simple PS to PL interrupt application with no problems.

Hope that helps,

 

EDIT 25th August: If Run Synthesis, Run Implementation and Generate Bitstream are executed as three distinct steps, the critical warnings are generated.  If I start with Generate Bitstream and from the presented dialog/warning allow it to run synthesis and run implementation (i.e. I take one step rather than three) then no critical warnings are generated.

regards,

Andrew

dcomer
Visitor
Visitor
803 Views
Registered: ‎02-12-2021

Doh!!! Still exists in 2021.1

etnapoli
Visitor
Visitor
505 Views
Registered: ‎12-25-2013

Windos 10. Vivado 2021.1

Designing a blimnking LED using only the PL on the zedboard.

Getting twice the critical warning:

  • [Board 49-67] The board_part definition was not found for avnet.com:zedboard:part0:1.4. This can happen sometimes when you use custom board part. You can resolve this issue by setting 'board.repoPaths' parameter, pointing to the location of custom board files. Valid board_part values can be retrieved with the 'get_board_parts' Tcl command.

I run the suggested TCL command 'get_board_parts' and nothing changed.

I have to say that a similar design that only uses the PL but is a combinatorial circuit without clock does not show the same critical warning.

Both designs work fine.

 

ashishd
Xilinx Employee
Xilinx Employee
435 Views
Registered: ‎02-14-2014

@etnapoli @etnapoli @AndrewJ 

I have tried exactly same steps as mentioned @AndrewJ 's reply. I didn't observe any Critical Warning similar to the one mentioned in this thread. I have attached vivado.log file for your reference. Considering this, here are some steps which can be performed to get rid of those Critical Warnings -

1. Before launching Vivado, make sure to delete xhub folder if it is already present at <home>/.Xilinx/Vivado/2021.1

2. Make sure that you don't have any 'set_param board.repoPaths ...' command in Vivado_init.tcl file

3. After launching Vivado, use below command first and then start with downloading board files for board which you need -

set_param board.repoPaths ""

If you still observe Critical Warnings, it would be good if you record a video of your steps and share it with us to debug this further.

Regards,
Ashish
----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------
dcomer
Visitor
Visitor
395 Views
Registered: ‎02-12-2021

Thank you ashishd, I will give this a try. I appreciate your time and help.

 

Dave

0 Kudos
ashishd
Xilinx Employee
Xilinx Employee
132 Views
Registered: ‎02-14-2014

Hi @dcomer @etnapoli @AndrewJ ,

Did you get a chance to check steps which I have mentioned? Let us know if these Critical Warnings still exist so that we can try to reproduce and get them fixed.

Regards,
Ashish
----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------
0 Kudos
AndrewJ
Visitor
Visitor
124 Views
Registered: ‎08-13-2021

Hi,

 Not yet, but I’ll try today.  I’m very new to Vivado so I was working from a fresh install and it was reporting this ‘out of the box’.  It may be a Ubuntu thing as I’m sure that someone using Windows didn’t have the issue, although their copy of Vivado is well established.  I’ll let you know.

0 Kudos
AndrewJ
Visitor
Visitor
99 Views
Registered: ‎08-13-2021

@ashishd I have tried today.  I followed your steps and then the steps I outlined above and at the end had the Critical Warning.  I created a video to show the steps taken and the specific order and it can be viewed at this link:  Vivado Test It is 15 mins long so about 1Gb - I will remove it once you confirm you have it.

0 Kudos
ashishd
Xilinx Employee
Xilinx Employee
88 Views
Registered: ‎02-14-2014

Hi @AndrewJ ,

Thanks for the video. You can remove it now as my download is complete.

Regards,
Ashish
----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------
0 Kudos
ashishd
Xilinx Employee
Xilinx Employee
42 Views
Registered: ‎02-14-2014

Hi All,

After reproducing the issue by following steps in video, I am able to replicate it and I've reported it through CR. Will keep you updated with its progress.

Regards,
Ashish
----------------------------------------------------------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.
Give Kudos to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------