Return to Support Page
 homesearchagentssupportask xilinxmap

Answers Database


XSIMMAKE 5.0, 5.1, 5.2: Possible cause of XNFBA error 301.


Record #495

Product Family:  Software

Product Line:  FPGA Core

Problem Title:
XSIMMAKE 5.0, 5.1, 5.2: Possible cause of XNFBA error 301.


Problem Description:
ERROR MESSAGE:

XNFBA error 301: delay <value> on PIN <pin> of <symbol instance> is not annotate
d.
The pin is connected to the signal <signal>.


XSIMMAKE may accidentally read an old .XG file and cause ERROR 301 from XNFBA.

If XBLOX optimization was used before but not during the final iteration of
placement and routing, or if XBLOX symbols were previously used in a design
but are no longer present, a file with a .xg extension will exist in the
directory. XSIMMAKE can become confused about which file to use in this case;
the existence of the .xg file implies the use of XBLOX, but since XBLOX
has been removed, the .xg file is no longer up to date, and the .xff file
should be used instead. XSIMMAKE runs XNFBA and tries to back-annotate using
the .xg file, even though this is not your most recent netlist file.


Solution 1:

Delete the .XG file and re-run XSIMMAKE.







End of Record #495

For the latest news, design tips, and patch information on the Xilinx design environment, check out the Xilinx Expert Journals!

© 1998 Xilinx, Inc. All rights reserved
Trademarks and Patents