5.34.115.1 Arguments
-format value
Specifies the file format of the file to export. The exported files vary from one device family to another; see the Export help topic for a description of each file type and the list of supported families.
You can export the files listed in the table below using the value.
File Types | Value |
Netlist Files | adl |
afl | |
edn | |
v | |
vhd | |
Constraint Files | crt |
dcf | |
gcf | |
sdc | |
pdc | |
pin | |
Programming Files | afm |
File Types | Value |
bit | |
bts_stp | |
dat | |
fus | |
isc | |
pdb | |
1532 | |
svf | |
FlashPro Data File | fdb |
Debugging Files | bsd |
prb | |
Timing Files | mod |
sdf | |
stf | |
tcl | |
Script Files | tcl |
Log Files | log |
IBIS Files | ibs |
Other Files | cob |
loc | |
seg |
File Types | Value |
Block Files | cdb |
cxf | |
v | |
vhd |
-feature {value}
Select the silicon feature(s) you want to program. Possible values for this option are listed in the table below, or the instance-specific program options available only for specific families (as shown in the table below). Microchip recommends that you specify your program parameters for each Embedded Flash Memory Block (EFMB) instance, from 0-3. The instance specific program options replace [-feature {value}].
value | Family |
{setup_security:on/off} | SmartFusion |
{prog_fpga:on/off} | SmartFusion |
{prog_from:on/off} | SmartFusion |
{prog_nvm:on/off} | SmartFusion |
{setup_security} | Fusion |
{prog_from} | Fusion |
{all} | IGLOO; ProASIC3 |
In Tcl mode for Fusion, programming all features are turned off by default. If there is -feature {setup_security} or - feature {prog_from} the programming for the corresponding feature is activated.
In Tcl mode for SmartFusion, the programming option is read from the loaded PDB and then updated from the command if the is parameter specified. If programming of specific features is disabled, other parameters related to the feature programming are ignored. For example, if -feature {prog_fpga:off}, then -fdb_file and -fdb_source are ignored.
-secured_device value
Specifies whether the device you are programming is secured. You can specify yes or no to enable or disable secured programming.
-signature value
Optional argument that identifies and tracks Microchip designs and devices.
-pass_key value
Protects all the security settings for FPGA Array, FlashROM, and Embedded Flash Memory Block. The maximum length of this value is 32 characters. You must use hexadecimal characters for the pass key value.
-aes_key value
Decrypts FPGA Array and/or FlashROM and Embedded Flash Memory Block programming file content. Max length is 32 HEX characters.
-from_config_file value
Specifies the location of the FlashROM configuration file.
-number_of_devices value
Specifies the number of devices you want to program. Applicable only when FlashROM has serialization regions.
-from_progfile_type value
Applicable only when FlashROM has serialization regions and STAPL file generation. Possible values:
Value | Description |
single | Generates one programming file with all the generated incremental value(s) in the external source file |
multiple | Generates one individual programming file for each generated incremental value(s) in the external source file |
-target_programmer value
Applicable only when FlashROM has serialization regions and STAPL file generation. Possible values:
Value | Description |
specific | Silicon Sculptor, BP Auto Programmer, or FlashPro |
generic | Generic STAPL player |
-custom_security value
Possible values:
Value | Description |
yes | Custom security level |
no | Standard security level |
-fpga_security_level value
Possible values:
Value | Description |
write_verify_protect | The security level is medium (standard) and the FPGA Array cannot be written or verified without |
Value | Description |
a Pass Key | |
write_protect | The security level is write protected. The FPGA Array cannot be written without a Pass Key, but it is open for verification (custom FPGA) |
encrypted | The security level is high (standard) and uses a 128-bit AES encryption |
none | The FPGA Array can be written and verified without a Pass Key |
-from_security_level value
Possible values:
Value | Description |
write_verify_protect | The security level is medium (standard) and the FlashROM cannot be read, written or verified without a Pass Key |
write_protect | The security level is write protected. The FlashROM cannot be written without a Pass Key, but it is open for reading and verification (custom FlashROM) |
encrypted | The security level is high (standard) and uses a 128-bit AES encryption |
none | The FlashROM can be written and verified without a Pass Key |
-security_permanent value
Specifies whether the security settings for this file are permanent or not. Possible values:
Value | Description |
yes | Permanently disable future modification of security settings for FPGA Array and FlashROM |
no | Enable future modifications for FPGA Array and FlashROM |
-from_program_pages "value"
Specifies FROM program pages in FlashPoint. If you use FlashROM content from an ADB file and do not specify a value, FlashPoint uses the same pages that were selected for programming in the previous FlashPoint session.
Value may be a sequence of page numbers ("123") without a delimiter, or you can use any character or space as a delimiter, as in -from_program_pages "1 2 3".
You must specify pages for programming if you want FlashROM content from the UFC file.
-from_content "value"
Identifies the source file for the FlashROM content- a UFC or ADB file.
If this Tcl parameter is missing, FlashPoint tries to use the ADB as a source of FROM configuration and content data.
Values are shown in table below:
Value | Description |
adb | (default)FROM content is taken from your ADB. Configurations from your UFC and ADB files are not compared. |
ufc | FlashPoint uses FROM configuration and FROM content from the specified UFC file |
-set_io_state value
Sets the I/O state during programming by port name or pin number. You can also use this argument to save or load an IOS file.
To set the I/O by port name, use -set_io_state {portName:<name>; state:<state>}. To set the I/O port by pin number, use -set_io_state {pinNumber:<number>; state:<state>}. To set all I/Os to the specified state, use -set_io_state {all; state:<state>}.
To set BSR values for an I/O, use -set_io_state { pinNumber:<pin>; input:<state>; output_enable:<state>;output:<state> }. See the Boundary Scan Registers - Show BSR Details section of the FlashPoint help for more information on setting Boundary Scan Registers in your device.
The following table shows the possible values for this option if you have NOT set BSR values.
Value | Description |
Z | Tri-State - Sets the I/O state to tristate |
Last Known State | Sets the I/O to the last known state |
1 | High - Sets the I/O state to high |
0 | Low - Sets the I/O state to low |
The following table shows the possible values for this option if you have set custom BSR values.
Value | Description |
Value | Description |
Last State | Sets the I/O to the last known state |
1 | High - Sets the I/O state to high |
0 | Low - Sets the I/O state to low |
To save an IOS file use the argument -set_io_state { save:<filepath> }
To load an IOS file, use the argument -set_io_state { load:<filepath> }
-efm_block_security{location:X;security_level: value}
This option is available only for Fusion; X identifies an Embedded Flash Memory Block instance from 0-3. Possible values:
Value | Description |
write_verify_protect | The security level is medium (standard) and the Embedded Flash Memory Block cannot be read, written or verified without a Pass Key |
write_protect | The security level is write protected. The Embedded Flash Memory Block cannot be written without a Pass Key, but it is open for reading (custom FB) |
encrypted | The security level is high (standard) and uses a 128-bit AES encryption |
none | The Embedded Flash Memory Block can be written and read without a Pass Key |
-efm_content {location:X;source: value}
This option is available only for Fusion; X identifies an Embedded Flash Memory Blockinstance from 0-3. Option identifies the source file for the Embedded Flash Memory Block content, either an EFC or ADB file.
If you wish to program the entire Embedded Flash Memory Block including all its clients that were programmed in previous sessions, and use ADB content for this client, this is the only parameter you must specify. If you wish to program the entire Embedded Flash Memory Block including all its clients and use the Embedded Flash Memory Block map file (EFC) you also have to specify the –efm_block parameter.
Possible values:
Value | Description |
adb | (default) Embedded Flash Memory Block content is taken from your ADB |
Value | Description |
efc | FlashPoint uses the Embedded Flash Memory Block instance configuration and content from the EFC file specified in -efm_block_parameter |
-efm_block {location:X;source: value}
This option is available only for Fusion; X identifies an Embedded Flash Memory Block (EFMB) instance from 0-3. Config_file specifies the location of the EFMB instance configuration file (must be an EFC file with full pathname).
-efm_client {location:X;client:value; mem_file: value}
This option is available only for Fusion; X identifies an EFMB instance from 0-3.
You must specify the client name and its memory content file for each client of EFMB you wish to program.
Mem_file specifies the file with the memory content for the client. If a mem_file path is specified, the memory content from this file will overwrite the client content in ADB or EFC (as defined by the -efm_content argument). If the client memory file is not specified, the client memory content from the ADB or EFC file is used instead (as defined by the -efm_content argument).
{filename}
Specifies the path and name of the file you are exporting.
