Answers Database

CONCEPT2XNF: Property RLOC_ORIGIN and RLOC_RANGE may be ignored by XNFMERGE (Warning 260)


Record #566

Product Family:  Software

Product Line:  Cadence

Problem Title:
CONCEPT2XNF: Property RLOC_ORIGIN and RLOC_RANGE may be ignored by
XNFMERGE (Warning 260)



Problem Description:
Warning 260: User parameter 'RLOC_ORIGIN=R0C0' on non-primitive symbol 48P_1
ignored.

The RLOC_ORIGIN property  is attached to a user created symbol which has RLOC pr
operties on
the underlying schematic.  RLOC_RANGE is used in a similar fashion to specify th
e range of list of
locations over which the components underlying a symbol can be placed. Xnfmerge
complains that the
attribute is a user parameter and that therefore it will be ignored.



Solution 1:

CAUSE:

In the XNF netlist file, there is an extra '=' in front of the attribute.

.
.
.
SYM,48P_1,al_unit, FILE=al_unit_.xnf,=RLOC_ORIGIN=R0C0
PIN,OFL,O,OFL,
PIN,CLK,O,CLK,
.
.


An "=" sign in front of a Xilinx property indicates that it is either a user pro
perty or
an X-BLOX property.  Xnfmerge does not expect a '=' in front of the RLOC_ORIGIN
(or RLOC_RANGE)
property, and as a result, it ignores it.

There is an error in the concept2xnf.prop file, which contains the
information used by concept2xnf for property translation:
.
.
.
USE_RLOC:	  =USE_RLOC=;		{ Xblox }
COUNT_TO:	  =COUNT_TO=;		{ Xblox }
RLOC_ORIGIN:	  =RLOC_ORIGIN=;	{ Xblox }    <========= Problem is here
RLOC_RANGE:	  =RLOC_RANGE=; 	{ Xblox }
ASYNC_VAL:	  =ASYNC_VAL=;		{ Xblox }
SYNC_VAL:	  =SYNC_VAL=;		{ Xblox }
.
.
.

SOLUTION:

The user can delete the '=' in front of the Rloc_Origin and RLOC_RANGE
statements in either the concept2xnf.prop file directly or from the xnf file.






End of Record #566