Answers Database


XNFPREP 5.0.0: Possible cause of error 3520, invalid primitive


Record #406

Problem Title:
XNFPREP 5.0.0: Possible cause of error 3520, invalid primitive


Problem Description:




Solution 1:




PROBLEM: XNFPREP 5.0.0 does not recognize legal primitives such as IBUF
and OBUF. Issues an error similar to the following:

     XNFPREP: ERROR 3520:
       The following are invalid primitives in part `3042APC84-7'.

       Symbol Type = OBUF ; Symbol Name = U1 ;
       Output Signal = OUT

       Symbol Type = IBUF ; Symbol Name = IO3 ;
       Output Signal = I8MHZ

       Symbol Type = AND ; Symbol Name = M1/U2 ;
       Output Signal = M1/$U2_O

       Symbol Type = OR ; Symbol Name = M1/U1 ;
       Output Signal = OOUT

SOLUTION: XNFPREP uses the file xlxlgl##.xnf (where ## is 2k, 3k, or 4k)
to identify valid primitives. If this file is missing or corrupted,
xnfprep will flag error 3520 on valid symbols. XNFPREP looks for these
files in the local project directory and in XACT/DATA. Verify that there
is not an invalid file in the local directory and that a valid one is in
XACT/DATA.





End of Record #406 - Last Modified: 04/01/97 07:57

For the latest news, design tips, and patch information on the Xilinx design environment, check out the Technical Tips!