AR# 3067: Migrating XBLOX designs to M1: XBLOX2M1 archive now exists on ftp site
AR# 3067
Migrating XBLOX designs to M1: XBLOX2M1 archive now exists on ftp site
説明
Keywords: xblox, xblox2m1, conversion
Urgency: standard
General Description:
The M1 tools will not accept a XNF netlist that has unresolved XBLOX symbols in it. The design should be either converted to use LogiBLOX symbols (recommended), or the design must be run through the XACT 5.2.x flow (XNFMERGE,XNFPREP, and XBLOX) to produce the .xtf file (where XBLOX has been resolved into primitives), which M1 will accept.
For more information on changing the design to use LogiBLOX symbols, refer to the "Conversion Guide", located at:
If you have XACT 5.2.x/6.0.x installed, and you are authorized for XBLOX, then you may produce the .xtf file by either:
1) Running "xmake -n" (-n will cause xmake to halt upon producing the .xtf file; otherwise PPR will execute) 2) On the PC, create a project in Design Manager (6.0.1) and indicate within Flow Engine to stop after Trimming but before Place/Route 3) Manually execute the steps: xnfmerge <design.xnf> xnfprep <design.xff> xblox <design> xnfprep <design.xg>
2
If you do not have XACT 5.2.x/6.0.x installed, or if you have XACT 5.2.x/6.0.x but you are not licensed for XBLOX, then you may download the "xblox2m1" archive on our FTP site. This will contain the programs XNFMERGE, XNFPREP, and a de-licensed version of XBLOX, as well as all the supporting data files required for these programs to execute. This archive will also contain the scripts "xblox2m1" and "xblox2m1.bat" (for Sun/HP and PC, respectively), which will allow you to automate the translation to .xtf (although you may run the individual steps yourself, if you wish). Details of installation and usage are included in the README.TXT file that comes with the archive. This archive does not contain XMAKE, XDM or Design Manager.