Critical warning with block design

Post a reply

Confirmation code
Enter the code exactly as it appears. All letters are case insensitive.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:
BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: Critical warning with block design

Re: Critical warning with block design

Post by support » Tue Dec 18, 2018 3:24 pm

Hello,

Vivado allows demoting critical warnings into messages with lower level. This can be done with GUI, or with set_msg_config -new_severity Tcl commands.

This issue will be fixed on the next update of bundles. The said critical warning appeared on relatively recent versions of Vivado.

Regards,
Eli

Re: Critical warning with block design

Post by Litchford » Tue Dec 18, 2018 1:30 pm

Hi Eli, is there a fix for this warning so that it stops showing up? I'd like to get rid of it even if it's safe to ignore.

Re: Critical warning with block design

Post by support » Fri Dec 14, 2018 10:02 am

Hello,

This warning can be ignored safely. The issue is with the EDIF file which is included in the Xillybus block design component, however this doesn't cause any confusions if the replacement of the block design with a custom one (from the IP Core Factory) is done according to the instructions.

Regards,
Eli

Critical warning with block design

Post by Guest » Fri Dec 14, 2018 9:47 am

Hey there,

I run Xillybus for Ultrascale+ with block design and get this critical warning:

[filemgmt 20-1440] File 'blockdesign/blockdesign/ip/core/xillybus_core.edf' already exists in the project as a part of sub-design file 'blockdesign/blockdesign/ip/blockdesign_xillybus_bundled_0_0/blockdesign_xillybus_bundled_0_0.xci'. Explicitly adding the file outside the scope of the sub-design can lead to unintended behaviors and is not recommended.

What to do?

Top