Answers Database

FITNET, CONCEPT2XNF: Fitnet drops LOC= I/O constraints in XNF file generated by CONCEPT2XNF v5.2.


Record #745

Product Family:  Software

Product Line:  EPLD Core

Problem Title:
FITNET, CONCEPT2XNF:   Fitnet drops LOC= I/O constraints in XNF file
generated by CONCEPT2XNF v5.2.



Problem Description:
Fitnet drops LOC= I/O constraints in XNF file generated by CONCEPT2XNF v5.2.

VERSIONS:  Fitnet 5.1, 5.2;  CONCEPT2XNF v5.1, 5.2

Platforms:  Sun, HP

In XACT 5.2, Fitnet only recognizes LOC= parameters for I/O when they are
attached to  EXT records.  EXT records are generally written to represent PAD
symbols in a schematic.  However, because it is illegal to attach LOC properties

or any other properties to a PAD in Concept, what happens is that the user ends

up attaching the properties to I/O buffers and/or I/O registers instead.
CONCEPT2XNF correctly writes the LOC constraints to the corresponding I/O
buffer or register SYM record.	However, Fitnet 5.2 does not recognize LOC
properties on SYM records and simply ignores them.

The problem has been fixed in XACT 6.0, but XACT 6.0 is only available on the
PC as of 12/18/95.  Currently there is no support on the workstation platforms.


Solution 1:

A Perl script called MOVELOC is available that will copy the LOC constraints
in the I/O buffer SYM records to EXT records.  This program must be run before t
he XNF file is processed by XEMAKE.  The XNF output of MOVELOC must then be proc
essed by XEMAKE with the -x option.



End of Record #745