Answers Database

SYNPLIFY: Synthesizes XBLOX components for 3100A and 3000A devices targeting M1


Record #3372

Problem Title:
SYNPLIFY: Synthesizes XBLOX components for 3100A and 3000A devices
targeting M1



Problem Description:
Keywords: synplify, M1, 3000a, 3100a

Urgency: Hot

General Description:  When targeting a 3100a/3000a to M1, synplify is
generating an .xnf with components from XBLOX.	XBLOX is no longer
supported in M1, and has been replaced by LogiBLOX.  Even when M1
is selected as a target, synplify makes no distinction.  The .xnf is
the same if this button is clicked or not clicked.


Solution 1:

If the customer is targeting a xc3000A/xc3100A series part, then the
customer should simply target a non-A series (xc3000) part with Synplify.
This netlist will not use XBLOX and can be retargeted to a xc3000A/xc3100A
part using M1.



Solution 2:

The customer will have to process the .xnf from Synplify to a .xtf
using the utility available on the FTP site at

ftp://ftp.xilinx.com/pub/swhelp/M1.3_alliance/xblox2m1.zip
or
ftp://ftp.xilinx.com/pub/swhelp/M1.3_alliance/xblox.tar.Z

This basically encompasses xnfmerge, xnfprep, and xblox. So, it
will not work with .edn or .ngo black-box instantiation.



End of Record #3372