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!

Page Bookmarked

AR# 9837

3.1i XST - "ERROR:NgdBuild:393 - Could not find INST(S) '<instance_name>' in design '<design_name>'." (IOSTANDARD)


Keywords: XST, VHDL, Verilog, HDL, IOSTANDARD, attribute, meta, comment, NCF

Urgency: Standard

General Description:
Contrary to the information stated in the XST User Guide, XST will produce an incorrect netlist constraint file (.ncf) if the IOSTANDARD attribute is declared on a port in VHDL or Verilog. This results in the following errors in NGDBuild:

"ERROR:NgdBuild:393 - Could not find INST(S) '<instance_name>' in design '<design_name>'.

ERROR:NgdBuild:134 - Unable to process the "<design_name>.ncf" constraints file; please see the above messages for details. Check to make sure the file exists and that you have read permission for it. If this is the case, check the syntax of the file using the "Attributes, Constraints, and Carry Logic" section of the Libraries Guide as a reference.

ERROR:NgdBuild:276 - edif2ngd exited with errors (return code 1).

ERROR:NgdBuild:28 - Top-level input design file "<design_name>.edn" cannot be found or created. Please make sure the source file exists and is of a recognized netlist format (e.g., NGO, EDIF or XNF)."


The work-around for both VHDL and Verilog is to place the IOSTANDARD attribute on a temporary signal in the architecture/module. The temporary signal is then connected to the appropriate port.

Another option is to instantiate the appropriate buffer.

NOTE: This problem was fixed in the 4.1i software release.
AR# 9837
Date 08/20/2002
Status Archive
Type General Article