9.15.11.1 Arguments

-name {name}

Specifies the device name. This argument must be specified only in chain programming mode.

-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). The recommendation is 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}].

-signature {value}

Optional argument that identifies and tracks Actel designs and devices.

-from_content {name}

Optional argument that identifies the source file for the FlashROM content. The file type is UFC or PDB (default). This argument only applies when programming the FlashROM (prog_from option).

-from_config_file {name}

Optional argument that specifies the location of the FlashROM configuration file. This argument only applies when programming the FlashROM (prog_from option) and the from_content is set to UFC.

-number_of_devices{value}

Optional argument that specifies the number of devices to be programmed. This argument only applies when FlashROM has serialization regions. This argument only applies when programming the FlashROM (prog_from option).

-from_program_pages {value}

Optional argument that identifies the program pages in FlashPoint. This argument only applies when programming the FlashROM (prog_from option).

-custom_security {value}

Optional argument that specifies the security level. This argument only applies when programming the security settings (setup_security) or programming previously secured devices. The following table shows the acceptable values for this argument:

-security_permanent {value}

Optional argument that specifies whether the security settings for this file are permanent or not. This argument only applies when programming the security settings (setup_security) or programming previously secured devices. The following table shows the acceptable values for this argument:

-fpga_security_level {value}

Optional argument that specifies the security level for the FPGA Array. This argument only applies when programming the security settings (setup_security) or programming previously secured devices. Possible values:

-from_security_level {value}

Optional argument that specifies the security level for the FlashROM. This argument only applies when programming the security settings (setup_security) or programming previously secured devices.

-efm_block_security{location:X;security_level: value}

This option is available only for SmartFusion and Fusion; X identifies an Embedded Flash Memory Block instance from 0-3.

-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.

-efm_content {location:X;source: value}

This option is available only for SmartFusion and Fusion; X identifies an Embedded Flash Memory Block from 0-3. Option identifies the source file for the Embedded Flash Memory Block configuration content, either an EFC or PDB file. If you specify EFC as your source, you need to specify the -efm_block parameter. Possible values:

-efm_block {location:X;config_file: value}

This option is available only for SmartFusion and Fusion; X identifies an Embedded Flash Memory Block (EFMB) from 0-3.

Config_file specifies the location of the EFMB 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 SmartFusion and Fusion; X identifies an EFMB 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 you want to program a client with a PDB or EFC file memory content (as defined by the -efm_content argument), the mem_file path should be empty (see Fusion example 3); but if a mem_file path is specified, the memory content from this file will overwrite the client content in PDB or EFC (as defined by the -efm_content argument).

-tie_off_arch {value}

This optional argument is used only for IT6X6M2 and M7IT6X6M2 devices.

-set_io_state {value}

Sets the I/O state during programming by port name or pin number.

To set the I/O by port name, use the following:

-set_io_state {portName:<port name>; state:<state>}.

To set the I/O by pin number, use the following:

-set_io_state {pinNumber:<pin number>; state:<state>}.

To set all I/Os to the specified state, use the following:

-set_io_state {all; state:<state>}.

-pdb_file {name}

Optional PDB filename; if not specified the default is 'expresspdbX'.

-enable_m3debugger {yes | no}

SmartFusion only; .enables the M3 debugger.