Answers Database

PPR 5.1:Possible cause of ERROR 9015 on XC3000 design (placement constraints)


Record #527

Problem Title:
PPR 5.1:Possible cause of ERROR 9015 on XC3000 design (placement
constraints)



Problem Description:



Solution 1:




PROGRAM: ppr

VERSION: 5.1

PLATFORM: all

SHORT DESCRIPTION:

Possible cause of ppr internal error 9015 is a notplace block applied to the
global clock buffers of the 3k family.

ERROR MESSAGE: ppr: error 9015: internal_error Contact Xilinx Technical Support.


LONG DESCRIPTION:

PROBLEM: ppr fails with internal error 9015 for a 3k design

CAUSE:

A possible cause of ppr internal error 9015 is the use of a constraint file,
which has a placement constraint which applies to all logic in a 3k device.
e.g.

notplace block *: p1 p2 p3;

A bug in ppr v5.1 applies placement constraints to global buffers in 3k
family.

SOLUTION:

When using placement constraints, do not use the wildcard `*` in placement
constraints.  For example do not use notplace block *: p1 p2;.	Instead,
name the blknames(which can be found in the .crf file) in your placement
constraints.  For example, assume that there are only two block names in
your crf file, then the notplace line above becomes:

notplace block1 block2: p1 p2;

In most cases, one only needs to use the IOB blocknames, but you might have
to use the IOB and CLB blocknames depending on the design.





End of Record #527