Answers Database
M1.5 LogiBlox introduces .ngc as new file extension for the implementation netlist
Record #3904
Product Family: Software
Product Line: FPGA Implementation
Problem Title:
M1.5 LogiBlox introduces .ngc as new file extension for the
implementation netlist
Problem Description:
Keywords: logiblox, lbgui, edn, ngc
Urgency: Standard
General Description: The implementation netlist produced
by LogiBLOX in the M1.5 release will have a .NGC extension
instead of .NGO.
Solution 1:
Currently, when LogiBLOX is asked to make an NGD model for a
module through the Options tab of the Setup dialog,
it creates a file with the ".ngo" extension. NGDBUILD is
supposed to read this ".ngo" file as the implementation model
for the LogiBLOX module.
However, in some cases, there have been problems where
NGDBUILD finds the EDIF simulation netlist (".edn" file)
created by LogiBLOX for that module, and tries to use it as
the source netlist to recreate the ".ngo" file. Since the
LogiBLOX-created EDIF netlist is intended only for simulation,
and does not contain the required implementation information,
NGDBUILD (EDIF2NGD) will reject the EDIF and issue an error.
To eliminate this problem, the M1.5 version of LogiBLOX will
write the implementation netlist to a file with the ".ngc"
extension (instead of ".ngo"). When NGDBUILD finds a ".ngc"
file to define a module, it will use this file directly, and
not look for any associated "source" netlists. In all other
respects, the ".ngc" file serves the same purpose as the
".ngo" file.
End of Record #3904
For the latest news, design tips, and patch information on the Xilinx design environment, check out the Xilinx Expert Journals! |