Answers Database

CADENCE GXILINX: FAST property not translated to XNF file / adding support for user properties


Record #1479

Product Family:  Software

Product Line:  Cadence

Problem Title:
CADENCE GXILINX: FAST property not translated to XNF file / adding
support for user properties



Problem Description:
In the 9402, pre-Unified Library Xilinx Interface to Concept, GXILINX may
not translate the FAST property when it writes out an XNF file for the
user's design schematic.


Solution 1:

In order for any property in a Concept schematic to translate to an
XNF file by GXilinx (and Concept2xnf as well), the property must
be defined in the appropriate Cadence property files.  In 9402, there
were two property-related files that had to support the property--

   - xilinx.format, and
   - xilinx.prop.

The XILINX.FORMAT file told the netlister how to write out the property
(with the value only, with both the name and value, and/or with an "="
prefix).  XILINX.PROP indicated where the property could be attached (on a
body, net, etc.).

In the 9402 xilinx.format and xilinx.prop files there apparently
is no support for the FAST property.  To add this support, you need
to do the following:


1. Copy the system copies of the xilinx.format and xilinx.prop files
from $CDS/tools/interface to your design directory.

2. Add the following lines to xilinx.prop to allow you to attach
the property to either a body or a signal:

SLEW_RATE:	permit(body);
SLEW_RATE:	permit(signal);

3. Add the following lines to xilinx.format to specify the format
in which GXILINX should write out the property:

SLEW_RATE:	  ;


Thus, if you specify the property with the name, "SLEW_RATE", and
value, "FAST", the property should be written out simply as "FAST".
Contrast to the entry for the LOC= property:

LOC:		  LOC=


With the above changes to your xilinx.format and xilinx.prop files,
you should be able to translate the FAST property to XNF.  Support for
other properties can be added in a similar fashion.



End of Record #1479