Answers Database
M1.3/M1.4 NGDBUILD: ERROR:basxn:68 - The XNF file does not contain a valid PART
Record #2912
Product Family: Software
Product Line: Merged Core
Problem Title:
M1.3/M1.4 NGDBUILD: ERROR:basxn:68 - The XNF file does not contain a
valid PART
Problem Description:
Keywords: NGDBUILD, M1, ERROR:basxn:68, XNF, part
Urgency: Standard
General Description:
The following error message is received while processing an XNF file
through the Design Manager or within NGDBUILD:
ERROR:basxn:68 - The XNF file does not contain a valid PART record.
Please use the "-l" option to specify the device-family library with
which the design was originally entered.
Launcher: "xnf2ngd" exited with an exit code of 2.
ERROR:basnb:48 - Cannot find or build NGO from "/path/filename.xnf".
Please make sure the source file exists and is of a legal netlist format
(e.g., NGO, EDIF or XNF).
One or more errors were found during NGDBUILD. No NGD file will be
written.
Solution 1:
One workaround is to add the ngdbuild "-l part" option in the
Implementation Template Manager. For example, with an XC4010E device, the
Template Manager Customize window would contain:
ngdbuild -l xc4000e
Solution 2:
Another workaround is to modify the XNF file so that it contains the
required part declaration. For example, the following line would be added
before any SYM lines for an XC4010E in a PC84 package with a -1 speed
grade:
PART,4010pc84-1
End of Record #2912
For the latest news, design tips, and patch information on the Xilinx design environment, check out the Xilinx Expert Journals! |