Exporting files

Designer supports different types of files to export.

Supported file types

The following table shows a complete list of files that you can export along with the supported family.

Note: Designer does not support exporting VHDL 87 format.

Files	File Extension	Export Type	Family
Actel Flattened Netlist	.afl	Netlist file	All
Actel Internal Netlist	.adl	Netlist file	All
Standard Delay Format	.sdf	Timing file	All
STAMP	.mod, .data	Timing file	SX-A, eX, Axcelerator, ProASIC3/E, , Fusion, ProASIC, ProASIC ^PLUS
Tcl script file	.tcl	Script file	All
Verilog Netlist	.v	Netlist file	All
VHDL Netlist	.vhd	Netlist file	All
EDIF Netlist file	.edn	Netlist file	All
Log File	.log	Log file	All
STAPL	.stp	Programming file	Fusion, ProASIC3/E, ProASIC, ProASIC ^PLUS
Bitstream	.bit	Programming file	Fusion, ProASIC3/E, ProASIC, ProASIC ^PLUS
Programming file (legacy)	.fus	Programming file	ACT1, ACT2, ACT3, MX, 1200XL, 3200DX
Actel programming file	.afm	Programming file	ACT1, ACT2, ACT3, MX, 1200XL, 3200DX, SX, SX-A, eX, Axcelerator
Routing Segmentation file	.seg	Other file	Axcelerator, ProASIC3/E, Fusion, ProASIC, ProASIC ^PLUS
Silicon Explorer Probe file	.prb	Debugging file	ACT1, ACT2, ACT3, MX, 1200XL, 3200DX, SX, SX-A, eX, Axcelerator
ProASIC Constraints file	.gcf	Constraints file	ProASIC
ProASIC ^PLUS Constraints file	.gcf	Constraints file	ProASIC ^PLUS (Timing constraints in GCF are not supported)
Combiner Info	.cob	Other file	ACT1, ACT2, ACT3, MX, 1200XL, 3200DX, SX, SX-A, eX, Axcelerator, ProASIC3/E
BSDL file	.bsd	Debugging file	3200DX, MX, SX, SX-A, eX, Axcelerator, Fusion, ProASIC3/E, ProASIC, ProASIC ^PLUS
Criticality	*.crt	Constraints file	ACT1, ACT2, ACT3, MX, 1200XL, 3200DX
PIN	*.pin	Constraints file	ACT1, ACT2, ACT3, MX, 1200XL, 3200DX, SX, SX-A, eX
SDC	*.sdc	Constraints file	SX-A, eX, Axcelerator, ProASIC ^PLUS, ProASIC3/E, Fusion
Physical Design Constraint	*.pdc	Constraints file	Axcelerator, ProASIC3/E, Fusion
Design Constraint file	*.dcf	Constraints file	ACT1, ACT2, ACT3, MX, 1200XL, 3200DX, SX, SX-A, eX

Note: If you have launched Designer software from Libero IDE, you cannot change some exported file names because the root of the file name is tied to the design name. These include *.bit, *.afm, *.prb, and *.stp file names. For example, if your design name is design_name, Libero IDE names the files as <design_name>.bit, <design_name>.afm, <design_name>.prb and <design_name>.stp. You cannot rename these files in Designer.

To export a file:

1. From the File menu, choose Export and then select the type of file you wish to export.

2. Specify file name and file type and click OK.

Note: You must compile your design before you export an SDC file.

To export a GCF file:

1. From the File menu, choose Export > Constraint Files.

2. Specify the file name and click OK.

3. Select the type of information you want to export:

· Pin locations: Select to export the I/O placement and region constraints related to the I/Os only.

· Placement constraints: Select to export all placement constraints, including I/O and core constraints.

· All GCF constraints: Select to export all constraint information.

4. Click OK.

To export a PDC file:

1. From the File menu, choose Export > Constraint Files.

2. Specify the file name and select a directory for it. Click Save. The Export Physical Design Constraints (PDC) dialog box appears.

3. Select the type of information you want to export:

· Pin locations and attributes: Select to export information about the pin locations and attributes only.

· Placement constraints: Select to export all user-defined constraints.

· Complete placement information: Select to export all the information about the I/O locations, I/O attributes, and logic placement.

4. Click OK.

A message appears in the Log window telling you if the Export command succeeded.

Note: The content of the exported PDC file depends on the state of your design.

· Pre-Compile: The exported PDC file will contain constraints that are stored in the database from the last valid compile state. Export may fail if you did not run Compile at least once before running Export.

· Post-Compile: The exported PDC file will contain constraints that are currently stored in the database.