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!

AR# 14814

4.2i NGDBUILD - An environment variable now reports name mismatches as warnings instead of errors

Description

Keywords: NgdBuild:393, NgdBuild:397, mismatches, name

Urgency: Standard

General Description:
NGDBuild normally reports an error when a UCF (User Constraints File) contains constraints on objects (instance, net, pin) in which the name specified does not exist in the design. An environment variable has been created that allows NGDBuild to instead flag these errors as warnings and continue processing the design.

For example, a BLKNM constraint on a nonexistent logical instance named "xyz" previously resulted in the error:

"ERROR:NgdBuild:393 - Could not find INST(S) 'xyz' in design 'abc'.
INST entry is 'INST "xyz" BLKNM = def ;"

With the new variable set, the following warning is issued instead:

"WARNING:NgdBuild:393 - Could not find INST(S) 'xyz' in design 'abc'.
INST entry is 'INST "xyz" BLKNM = def ;"

Solution

This change is in the latest 4.2i Service Pack, available at:
http://support.xilinx.com/support/techsup/sw_updates
The first service pack containing the change is 4.2i Service Pack 3.

Workstations:
setenv XIL_NGDBUILD_ALLOWUNMATCHEDUCF 1

PCs:
SET XIL_NGDBUILD_ALLOWUNMATCHEDUCF=1
AR# 14814
Date Created 06/04/2002
Last Updated 08/20/2003
Status Archive
Type General Article