MICROCHIP FLASHPRO4 Programmer Unit User Manual

compare_analog_config compare_flashrom_client

close_project

configure_flashpro_prg configure_flashpro3_prg

configure_flashpro4_prg

configure_flashpro5_prg configure_flashproLite_prg

connect_cable

construct_chain_automatically copy_device

cut_device dump_tcl_support enable_device

enable_prg

Adds an Actel device to the chain

Adds a non-Actel device in the chain

Imports settings via a BSDL file that adds non-Actel or non-Microsemi devices to the device database

Performs diagnostics of the page status and data information

Closes the FlashPro project

Compares the content of the analog block configurations in your design against the actual values in the device

Compares the content of the FlashROM configurations in your design against the actual values in the selected device

Compares the memory client in a specific device and block

Changes FlashPro programmer settings

Changes FlashPro 3 programmer settings

Changes FlashPro 4 programmer settings

Changes FlashPro 5 programmer settings

Changes FlashPro Lite programmer settings

Connects a parallel cable to a port

Automatically starts chain construction for the specified programmer

Copies a device in the chain to the clipboard

Removes one or more devices from the chain

Unloads the list of supported FlashPro Tcl commands

Enables or disables a device in the chain

Enables or disables one or more

FlashPro User's Guide 135

Command

enable_prg_type

enable_procedure enable_serialization

export_config

export_script export_secured_pdb

export_single_1532 export_single_dat

export_single_stapl

export_single_svf

export_stapl

import_config new_project

open_project paste_device

ping_prg read_analog_block_config read_device_status

read_id_code recover_flash_memory

136

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Action programmers

Enables or disables all programmers of a specified programmer type

Enables/disables an optional procedure for an action

Enables/disables serialization for a device

Exports a configuration file

Exports the history in a Tcl script

Exports a single device secured PDB from the loaded PDB

Exports a single device 1532 file

Exports a single device DirectC data file

Exports a single device STAPL file

Exports a single device SVF file

Exports the ChainBuilder STAPL file in chain programming mode

Imports a configuration file

Creates a new FlashPro project or convert an old ChainBuilder project into a new FlashPro project

Opens a FlashPro project

Pastes the devices that are on the clipboard in the chain

Pings one or more programmers

Reads analog block configuration information

Compares the memory client in a specific device and block

Reads information from the eNVM modules

Reads the content of the FlashROM

Reads IDCode from the device without masking any IDCode fields

Removes ECC2 errors due to memory corruption by reprogramming specified flash

FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

About TCL Commands - FlashPro Tcl Command Reference

Command

refresh_prg_list

remove_device

Action memory (NVM) pages

Refreshes the programmer list

Removes the device from the chain

remove_non_actel_device_to_database Removes settings for non-Microsemi or non-

Actel device from the device database

remove_prg

Removes the programmer from the programmer list

run_selected_actions

Runs the selected action on the specified programmer and returns the exit code from the action

save_project save_project_as

Samples the configured analog channel with the ADC parameters you provided

save_log

scan_chain_prg select_from_region_name

select_libero_design_device

Saves the log file

Saves the FlashPro project

Saves the FlashPro project under a new project name

Runs scan chain on a programmer

Enables you to select the serialization region you want to add to the log file

Selects the Libero design device to resolve when there are two or more identical Libero design devices in the configured JTAG chain.

This TCL command is for Libero usage only.

Selects the serialization data

select_serial_range

select_target_device self_test_prg

set_bsdl_file set_chain_param

set_debug_device set_debug_programmer

set_device_to_highz

Sets the target device for programming in

Single Device Programming mode

Runs Self-Test on a programmer

Sets a BSDL file to a non-Actel device in the chain

Sets the chain parameters in single programming mode

Identifies the device you intend to debug

Identifies the programmer you want to use for debugging (if you have more than one)

Sets a disabled Microsemi or Actel device in

FlashPro User's Guide 137

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

set_device_ir

Command

set_device_name set_device_order

set_device_tck

set_device_type set_main_log_file

set_prg_name set_programming_action

set_programming_file set_programming_mode

set_serialization_log_file set_serialization_mode

update_programming_file

Action

Chain programming mode to HIGH-Z

Sets the IR length of a non-Actel device in the chain

Changes the user name of a device in the chain

Sets the order of the devices in the chain to the order specified

Sets the maximum TCK frequency of a non-

Actel device in the chain

Changes the family of an Actel device in the chain

Sets the FlashPro log file

Changes the user name of a programmer

Selects the action for a device

Sets the programming file for a device

Sets the programming mode

Sets the log file to be used for serialization

Sets the serialization mode

Updates the programming file with the selected parameters

Running Tcl Scripts from within FlashPro

Instead of running scripts from the command line, you can use FlashPro's Run Script dialog box to run a script.

To execute a Tcl script file within FlashPro:

1. From the File menu, choose Run Script to display the Execute Script dialog box.

138 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Running Tcl Scripts from the Command Line

Figure 150 · Execute Script Dialog Box

2. Click Browse to display the Open dialog box, in which you can navigate to the folder containing the script file to open. When you click Open, FlashPro enters the full path and script filename into the

Execute Script dialog box for you.

3. In the Arguments box, enter the arguments to pass to your Tcl script. Separate each argument by a space character. For information about accessing arguments passed to a Tcl script, see

4. Click Run.

Running Tcl Scripts from the Command Line

You can run Tcl scripts from your Windows command line.

To execute a Tcl script file in the FlashPro software from a shell command line:

1. At the prompt, type the path to the Microsemi software followed by the word "SCRIPT" and a colon, and then the name of the script file as follows:

<location of Microsemi software>/bin/flashpro.exe SCRIPT:<filename>

The example below executes in batch mode the script foo.tcl:

<location of Microsemi software>/bin/flashpro.exe script:foo.tcl

The example below executes in batch mode the script foo.tcl and exports the log in the file foo.txt:

<location of Microsemi software>/bin/flashpro.exe script:foo.tcl logfile:foo.txt

The example below executes in batch mode the script foo.tcl, creates a console where the log is displayed briefly, and exports the log in the file foo.txt:

<location of Microsemi software>/bin/flashpro.exe script:foo.tcl console_mode:brief logfile:foo.txt

If you leave console_mode unspecified or set it to 'hide' FlashPro executes without a console window. If you want to leave the console window open you can run the script with the console_mode parameter set to 'show', as in the following example:

<location of Microsemi software>/bin/flashpro.exe script:foo.tcl console_mode:show logfile:foo.txt

2. If you want to pass arguments to the Tcl script from the command line, then use the "SCRIPT_ARGS" variable as follows:

<location of Microsemi software>/bin/flashpro.exe SCRIPT:<filename> SCRIPT_ARGS:"param1 param2 param3"

Arguments passed to a Tcl script can be accessed through the Tcl variables argc and argv. The example below demonstrates how a Tcl script accesses these arguments: puts "Script name: $argv0" puts "Number of arguments: $argc" set i 0 foreach arg $argv {

puts "Arg $i : $arg"

incr i

}

FlashPro User's Guide 139

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Note: Script names can contain spaces if the script name is protected with double quotes: flashpro.exe script:"flashpro tcl/foo 1.tcl"

Exporting Tcl Scripts from within FlashPro

To export a set of Tcl commands from the FlashPro history:

1. From the File menu, choose Export > Export Script.

2. Enter the filename and click Save. The Script Export Options dialog is appears (see image below).

Figure 151 · Script Export Options Dialog Box

3. Check the Include commands from current project only to export commands of the current project only. You can specify the filename formatting by selecting Relative filenames (relative to the current directory) or Qualified filenames(absolute path, including the directory name).

4. Click OK.

add_actel_device

Adds an Actel device to the chain. Either the file or device parameter must be specified. Chain programming mode must have been set. add_actel_device [-file { filename }] [-device { device }] -name { name } [-ukey { ukey_value }]

Arguments

Where:

-file{ filename }

Specifies a programming filename.

-device { device }

Specifies the Actel device family(such as AFS600).

-name { name }

Specifies the device user name.

-ukey { ukey_value }

Optional (SmartFusion only) - Specifies the ukey value.

140 FlashPro User's Guide

Supported Families

All

Exceptions

None

Example add_actel_device –file {e:/design/stp/TOP.stp} –name {MyDevice1} add_actel_device –device {A3P250} –name {MyDevice2}

add_non_actel_device

Adds a non-Actel device in the chain. Either the file, or (-tck And -ir) parameters must be specified. The

Chain programming mode must have been set. add_non_actel_device [-file { file }] [-ir { ir }] [-tck { tck }] [-name { name }]

Arguments

-file { filename }

Specifies a BSDL file.

-ir { ir }

Specifies the IR length.

-tck { tck }

Specifies the maximum TCK frequency (in MHz).

-name { name }

Specifies the device user name.

Supported Families

All

Exceptions

None

Examples add_non_actel_device –file {e:/design/bsdl/DeviceX.bsdl } –name {MyDevice3} add_non_actel_device –ir 8 – tck 5 –name {MyDevice4}

add_non_actel_device_to_database

Imports settings via a BSDL file that adds non-Actel or non-Microsemi devices to the device database so that they are recognized during scan chain and auto-construction operations. add_non_actel_device_to_database [-file {bsdl_filename}]

Arguments

-file {bsdl_filename}

FlashPro User's Guide 141

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Specifies the path to the BSDL file and the BSDL filename add to the database.

Supported Families

All non-Microsemi and non-Actel families

Exceptions

N/A

Examples

The following example uses a BSDL file to add a non-Microsemi (1502AS J44) device to the device database: add_non_actel_device_to_database –file {c:/bsdl/atmel/1502AS_J44.bsd}

The following example uses a BSDL file to add a non-Microsemi (80200) device to the device database: add_non_actel_device_to_database –file {c:/bsdl/intel/80200_v1.0.bsd}

check_flash_memory

The command performs diagnostics of the page status and data information as follows:

• Page Status – includes ECC2 check of the page status information, write count

• Page Data - ECC2 check check_flash_memory

[-name { device_name }]

[-block { integer_value }]

[-client { client_name }]

[-startpage { integer_value }]

[-endpage { integer_value }]

[-access { all | status | data }]

[-show { summary | pages }]

[-file { filename }]

At a minimum you must specify -client < name > OR

-startpage < page_number > -endpage < page_number > -block < number >

Arguments

-name { device_name }

Optional user-defined device name. The device name is not required if there is only one device in the

current configuration, or a device has already been selected using the set_debug_device command.

-block { integer_value }

(Optional argument; you must set -client or –startpage, –endpage and –block before use.) Specifies location of block for memory check.

-client { client_name }

Name of client for memory check.

-startpage { integer_value }

Startpage for page range; value must be an integer. You must specify a –endpage and –block along with this argument.

-endpage { integer_value }

Endpage for page range; value must be an integer. You must specify a –startpage and -block along with this argument.

-access { all | status | data }

142 FlashPro User's Guide

(Optional argument; you must set -client or –startpage, –endpage and –block before use.) Specifies what

NVM information to check: page status, data or both.

Value Description all Shows the number of pages with corruption status, data corruption and out-of-range write count (default) status Shows the number of pages with corruption status and the number of pages with out-of-range write count data Shows only the number of pages with data corruption

-show { summary | pages }

(Optional argument; you must set -client or –startpage, –endpage and –block before use.) Specifies output level, as explained in the table below.

Value Description summary Displays the summary for all checked pages (default) pages Displays the check results for each checked page

-file { filename }

(Optional argument; you must set -client or –startpage, –endpage and –block before use.) Name of output file for memory check.

Supported Families

SmartFusion, Fusion

Exceptions

None

Example

The following command checks the page status for block 0 from starpage 0 to endpage 2: check_flash_memory -startpage 0 -endpage 2 -block 0

The following command checks the memory status for the client 'DS8bit' and saves it to the file

'checkFlashMemory.log': check_flash_memory -client {DS8bit} -file {checkFlashMemory.log}

close_project

Closes the FlashPro or FlashPro Express project. close_project

Arguments

None

Supported Families

All

FlashPro User's Guide 143

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Exceptions

None

Example close_project

compare_analog_config

Compares the content of the analog block configurations in your design against the actual values in the device. In a typical SoC project, this directory is located at

<project_root>/smartgen/<analog_block_core_name>. compare_analog_config

[-name " device_name "] -mem_file_dir " mem_file_directory "

[-file " filename "]

Arguments

Supported Families

Fusion

Exceptions

None

Example

-name { device_name }

Optional user-defined device name. The device name is not required if there is only one device in the

current configuration, or a device has already been selected using the set_debug_device command.

-mem_file_dir { mem_file_directory }

Location of memory file.

-file { filename }

Output filename.

The following command reads the analog block configuration in the directory F:/tmp/Analog_Block and saves the data in the logfile compare_analogReport.log: compare_analog_config -mem_file_dir {F:/tmp/Analog_Block} -file

{compare_analogReport.log}

The following command reads the analog block configuration information in the device 'AFS600' in the directory F:/tmp/Analog_Block and saves the data in the log file compare_analogReport.log: compare_analog_config –name {AFS600} -mem_file_dir {F:/tmp/Analog_Block} -file

{compare_analogReport.log}

compare_flashrom_client

Compares the content of the FlashROM configurations in your design against the actual values in the selected device. compare_flashrom_client [-name { device_name }] [-file { filename }]

Arguments

-name { device_name }

144 FlashPro User's Guide

Supported Families

SmartFusion, IGLOO, ProASIC3 and Fusion

Exceptions

None

Example

Optional user-defined device name. The device name is not required if there is only one device in the

current configuration, or a device has already been selected using the set_debug_device command.

-file { filename }

Optional file name for FlashROM compare log.

The following command saves the FlashROM data to the file 'FlashRomCompReport.log': compare_flashrom_client -file {FlashRomCompReport.log}

The following command compares the data in the device 'A3P250' and saves the data in the logfile

'FlashRomCompReport.log': compare_flashrom_client –name {A3P250} -file {FlashRomCompReport.log}

compare_memory_client

Compares the memory client in a specific device and block. compare_memory_client [-name { device_name }] [-block integer_value ] -client { client_name }

[-file { filename }]

Arguments

Supported Families

SmartFusion and Fusion

Exceptions

None

Example

-name { device_name }

Optional user-defined device name. The device name is not required if there is only one device in the

current configuration, or a device has already been selected using the set_debug_device command.

-block { integer_value }

(Optional argument; you must set -client.) Specifies location of block for memory compare.

-client { client_name }

Name of client for memory compare.

-file { filename }

Optional file name.

The following command compares the memory in the client 'DS32' on the device 'AFS600'. compare_memory_client -client DS32 -name AFS600

The following command compares the data at block '0' to the client 'DS8bit': compare_memory_client -block 0 -client {DS8bit}

The following command compares the memory in the device 'AFS600' at block '0' to the memory client

'DS8bit':

FlashPro User's Guide 145

The following command compares the memory at block '1' to the memory client 'DS8bit' and saves the information in a log file to F:/tmp/NVMCompReport.log: compare_memory_client -block 1 -client {DS8bit} -file {F:/tmp/NVMCompReport.log}

configure_flashpro_prg

Changes FlashPro programmer settings. configure_flashpro_prg [-vpp {ON|OFF}] [-vpn {ON|OFF}] [-vddl {ON|OFF}] [-force_vddp

{ON|OFF}] [-vddp {2.5|3.3}] [-drive_trst {ON|OFF}] [-force_freq {ON|OFF}] [-freq { freq }]

Arguments

-vpp {ON|OFF}

Enables FlashPro programmer to drive VPP. Set to ON to drive VPP.

-vpn {ON|OFF}

Enables FlashPro programmer to drive VPN; set to ON to drive VPN.

-vddl {ON|OFF}

Enables FlashPro programmer to drive VDDL; set to ON to drive VDDL.

-force_vddp {ON|OFF}

Enables FlashPro programmer to drive VDDP; set to ON to drive VDDP.

-vddp {2.5|3.3}

Sets VDDP to 2.5 or 3.3 volts.

-drive_trst {ON|OFF}

Enables FlashPro programmer to drive TRST; set to ON to drive TRST.

-force_freq {ON|OFF}

Forces the FlashPro software to use the TCK frequency specified by the software rather than the TCK frequency specified in the programmer file.

-freq { freq }

Specifies the TCK frequency in MHz.

Supported Families

ProASIC

PLUS

, ProASIC

Exceptions

None

Example

The following example enables the FlashPro programmer to drive the VPP, VPN, VDDL, VDDP, sets the drive voltage to 3.3v, disables the driver for TRST, and does not force the programmer to use the TCK frequency specified in the software. configure_flashpro_prg –vpp {ON} –vpn {ON} –vddl {ON} –force_vddp {ON} –vddp {3.3} – drive_trst {OFF} –force_freq {OFF}

configure_flashpro3_prg

Changes FlashPro3 programmer settings. configure_flashpro3_prg [-vpump {ON|OFF}] [-clk_mode {discrete_clk|free_running_clk}] [force_freq {ON|OFF}] [-freq { freq }]

146 FlashPro User's Guide

Arguments

vpump {ON|OFF}

Enables FlashPro programmer to drive VPUMP. Set to ON to drive VPUMP.

clk_mode {discrete_clk|free_running_clk}

Specifies free running or discrete TCK.

force_freq {ON|OFF}

Forces the FlashPro software to use the TCK frequency specified by the software rather than the TCK frequency specified in the programmer file.

freq { freq }

Specifies the TCK frequency in MHz.

Supported Families

SmartFusion, IGLOO, ProASIC3 and Fusion

Exceptions

None

Example

The following example sets the VPUMP option to ON, TCK to free running, and uses the TCK frequency specified in the programmer file (force_freq is set to OFF): configure_flashpro3_prg -vpump {ON} -clk_mode {free_running_clk} -force_freq {OFF} -freq

{4}

The following example sets VPUMP to ON, TCK to discrete, forces the FlashPro software to use the TCK frequency specified in the software (-force_freq is set to ON) at a frequency of 2 MHz. configure_flashpro3_prg -vpump {ON} -clk_mode {discrete_clk} -force_freq {ON} -freq {2}

configure_flashpro4_prg

Changes FlashPro4 programmer settings. configure_flashpro4_prg [-vpump {ON|OFF}] [-clk_mode {discrete_clk|free_running_clk}] [force_freq {ON|OFF}] [-freq { freq }]

Arguments

vpump {ON|OFF}

Enables FlashPro4 programmer to drive VPUMP. Set to ON to drive VPUMP.

clk_mode {discrete_clk|free_running_clk}

Specifies free running or discrete TCK.

force_freq {ON|OFF}

Forces the FlashPro software to use the TCK frequency specified by the software rather than the TCK frequency specified in the programmer file.

freq { freq }

Specifies the TCK frequency in MHz.

Supported Families

SmartFusion, IGLOO, ProASIC3 and Fusion

Exceptions

None

FlashPro User's Guide 147

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Example

The following example sets the VPUMP option to ON and uses a free running TCK at a frequency of 4 MHz

(force_freq is set to OFF). configure_flashpro4_prg -vpump {ON} -clk_mode {free_running_clk} -force_freq {OFF} -freq

{4}

The following example sets the VPUMP option to ON, uses a discrete TCK and sets force_freq to ON at 2

MHz. configure_flashpro4_prg -vpump {ON} -clk_mode {discrete_clk} -force_freq {ON} -freq {2}

configure_flashpro5_prg

Tcl command; changes FlashPro5 programmer settings. configure_flashpro5_prg [-vpump { ON|OFF }] [-clk_mode {free_running_clk}]

[-programming_method { jtag | spi_slave }] [-force_freq { ON|OFF }] [-freq { freq }]

Arguments

-vpump {ON|OFF}

Enables FlashPro5 programmer to drive VPUMP. Set to ON to drive VPUMP.

-clk_mode {free_running_clk}

Specifies free running TCK.

-programming_method {jtag | spi_slave}

Specifies the programming method to use. spi_slave works only with SF2 and IGLOO2. Default is jtag.

-force_freq {ON|OFF}

Forces the FlashPro software to use the TCK frequency specified by the software rather than the TCK frequency specified in the programmer file.

-freq { freq }

Specifies the TCK frequency in MHz.

Supported Families

RT ProASIC3, SmartFusion, IGLOO, ProASIC3, Fusion, SmartFusion2, IGLOO2, RTG4

Exceptions

None

Example

The following example sets the VPUMP option to ON and uses a free running TCK at a frequency of 4 MHz

(force_freq is set to OFF). configure_flashpro5_prg -vpump {ON} -clk_mode {free_running_clk} -force_freq

{OFF} -freq {4}

The following example sets the VPUMP option to ON, uses a free running TCK and sets force_freq to ON at

2 MHz. configure_flashpro5_prg -vpump {ON} -clk_mode {free_running_clk} -force_freq

{ON} -freq {2}

configure_flashproLite_prg

Changes FlashPro Lite programmer settings.

148 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content. connect_cable configure_flashproLite_prg [-vpp {ON|OFF}] [-vpn {ON|OFF}] [-drive_trst {ON|OFF}] [force_freq {ON|OFF}] [-freq { freq }]

Arguments

-vpp {ON|OFF}

Enables FlashPro programmer to drive VPP. Set to ON to drive VPP.

-vpn {ON|OFF}

Enables FlashPro programmer to drive VPN; set to ON to drive VPN.

-drive_trst {ON|OFF}

Enables FlashPro programmer to drive TRST; set to ON to drive TRST.

force_freq {ON|OFF}

Forces the FlashPro software to use the TCK frequency specified by the software rather than the TCK frequency specified in the programmer file.

freq { freq }

Specifies the TCK frequency in MHz.

Supported Families

ProASIC

PLUS

Exceptions

None

Example

The following example sets the programmer to drive the VPP, drive VPN, drive the TRST and uses the frequency set by the programmer file (sets force_freq to OFF): configure_flashprolite_prg –vpp {ON} –vpn {ON} –drive_trst {ON} –force_freq {OFF}

connect_cable

Connects a parallel cable to a port. connect_cable -cable_name { cable_name } -port_name { port_name } [-drive_trst {ON|OFF}]

Arguments

-cable_name { cable_name }

Identifies the name of the parallel port cable you wish to connect.

-port_name { port_name }

Specifies the parallel port where the parallel programmer is connected.

-drive_trst {ON|OFF}

Enables the parallel port cable to drive TRST.

Supported Families

All

Exceptions

None

FlashPro User's Guide 149

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Example

The following example connects the cable named Parallel_Port_Buffer_Cable to the port LPT1 and enables drive TRST: connect_cable -cable_name {Parallel_Port_Buffer_Cable} -port_name {Lpt1} -drive_trst

{ON}

construct_chain_automatically

Automatically starts chain construction for the specified programmer. construct_chain_automatically[(-name { name })+]

Arguments

-name { name }

Specifies the programmer(s) name(s).

Supported Families

All

Exceptions

N/A

Example

Example for one programmer: construct_chain_automatically -name {21428}

Example for two programmers: construct_chain_automatically -name {21428} –name {00579}

copy_device

Copies a device in the chain to the clipboard. Chain programming mode must be set. See the paste_device command for more information.

copy_device (-name {name})*

Arguments

-name {name}

Specifies the device name. Repeat this argument to copy multiple devices.

Supported Families

All

Exceptions

None

Example

The example copies the device 'mydevice1' to the same location with a new name 'mydevice2'. copy_device –name {MyDevice1} –name {MyDevice2}

150 FlashPro User's Guide

cut_device

Removes one or more devices from the chain. It places the removed device in the clipboard. Chain

programming mode must be set to use this command. See the paste_device command for more

information. cut_device (-name { name })*

Arguments

-name { name }

Specifies the device name. You can repeat this argument for multiple devices.

Supported Families

All

Exceptions

None

Example

The following example removes the devices 'mydevice1' and 'mydevice2' from the chain. cut_device –name {MyDevice1} –name {MyDevice2}

dump_tcl_support

Unloads the list of supported FlashPro or FlashPro Express Tcl commands. dump_tcl_support -file { file }

Arguments

-file { file }

Supported Families

All

Exceptions

None

Example

The following example dumps your Tcl commands into the file 'tcldump.tcl' dump_tcl_support -file {tcldump.tcl}

enable_device

Enables or disables a device in the chain (if the device is disabled, it is bypassed). Chain programming mode must be set. The device must be a Microsemi device. enable_device -name { name } -enable {TRUE|FALSE}

Arguments

-name { name }

FlashPro User's Guide 151

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Specifies your device name

-enable {TRUE|FALSE}

Specifies whether the device is to be enabled or disabled. If you specify multiple devices, this argument applies to all specified devices. (TRUE = enable. FALSE = disable)

Supported Families

All

Exceptions

None

Example

The following example disables the device 'mydevice1' in the chain. enable_device –name {MyDevice1} –enable {FALSE}

enable_prg

Enables or disables one or more programmers. enable_prg (-name { name })* -enable {TRUE|FALSE}

Arguments

-name { name }*

Specifies the programmer name. You can repeat this argument for multiple programmers.

-enable {TRUE|FALSE}

Specifies whether the programmer is to be enabled or disabled. If you specify multiple programmers, this argument applies to all of them (TRUE = enable. FALSE = disable).

Supported Families

All

Exceptions

None

Example

The following example enables the programmers 'FP300085' and 'FP300086'. enable_prg –name {FP300085} –name {FP300086} –enable {TRUE}

enable_prg_type

Enables or disables all programmers of a specified programmer type. enable_prg_type -prg_type {prg_type} -enable { TRUE | FALSE }

Arguments

-prgType { FP | FPLite | FP3 | PP }

Specifies the programmer type to be enabled/disabled (FP–FlashPro type programmers, FPLite–FlashPro

Lite type programers, FP3–FlashPro3 type programmers, PP–Parallel port cable type programmers).

-enable {TRUE|FALSE}

152 FlashPro User's Guide

Specifies whether the programmers are to be enabled or disabled (TRUE–enable, FALSE–disable).

Supported Families

All

Exceptions

None

Example

The following example enables the FlashPro3 programmer. enable_prog_type –prg_type{FP3} –enable{TRUE}

enable_procedure

To enable/disable an optional procedure of an action. The device name parameter must be specified only in chain programming mode. A programming file must have been loaded. enable_procedure [-name { name }] -action { action } -procedure { procedure } -enable

{TRUE|FALSE}

Arguments

-name { name }

-action { action }

-procedure { procedure }

-enable {TRUE|FALSE}

Supported Families

All

Exceptions

None

Example

In single programming mode: enable_procedure –action {PROGRAM} –procedure {DO_ERASE} –enable {TRUE}

In chain programming mode: enable_serialization –name {MyDevice2} –action {PROGRAM} –procedure {DO_ERASE} –enable

{FALSE}

enable_serialization

This Tcl command enables or disables serialization programming. enable_serialization –name { device_name } -enable { true|false }

Arguments

-name

Specifies the device name.

-enable

Enables (true) or disables (false) serialization programming.

FlashPro User's Guide 153

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Exceptions

Must be a Microsemi Device

Supported Families

See the Tcl Commands and Supported Families table for the list of families that support this command.

Example enable_serialization -name M2S/M2GL050{T|S|TS} -enable true

export_chain_stapl

Exports the ChainBuilder STAPL file in chain programming mode. export_chain_stapl -file { file }

Arguments

-file { file }

Specifies the file to be exported.

Supported Families

All

Exceptions

None

Example

The following example exports the STAPL file 'tcl_testing_chain.stp':

-export_chain_stapl -file {./tcl_testing_chain.stp}

export_config

Exports a configuration file. export_config -file { file }

Arguments

-file { file }

Specifies the file to export.

Supported Families

All

Exceptions

None

Example

The following example exports the configuration file 'myconfig1'

154 FlashPro User's Guide

export_secured_pdb

Exports a single device secured PDB from the loaded PDB. export_secured_pdb -file { file } [-name { name }]

Arguments

-file { file }

Specifies the file to export.

-name { name }

Specifies the name of the device in chain mode to export a single device currently secured PDB.

Supported Families

SmartFusion, Fusion

Exceptions

'-secured' is only supported for SmartFusion devices.

Example

In single mode, the following command exports the secured PDB 'my_design.pdb': export_secured_pdb -file {D:/TOP/my_design.pdb}

In chain mode, the following example exports the secured PDB 'my_design.pdb' from the A2F200M3F device in the chain: export_secured_pdb -name {A2F200M3F} -file {./my_design.pdb}

export_script

Exports the history in a Tcl script. export_script -file { file } -relative_path {TRUE|FALSE}

Arguments

-file { file }

Specifies the file to export.

-relative_path {TRUE|FALSE}

Specifies whether the file path must be exported as a relative path or an absolute path.

Supported Families

All

Exceptions

None

Example

The following example exports your Tcl history to the file 'history.tcl' with absolute pathnames. export_script –file {./history.tcl} –relative_path {FALSE}

FlashPro User's Guide 155

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

export_single_1532

Exports a single device IEEE 1532 file. export_single_1532 -file { file } [–name { name }] [-pdb { pdb_file }] [-secured]

Arguments

-file { file }

Specifies the file to export.

-name { name }

Specifies the name of the device in chain mode to export single device IEEE 1532 programming file.

-pdb { pdb_file }

Specifies the PDB to use for exporting a IEEE 1532 programming file. By default, the loaded PDB is used for exporting a IEEE 1532 programming file.

-secured

Exports a IEEE 1532 programming file for a secured device.

Supported Families

SmartFusion, IGLOO, ProASIC3 and Fusion

Exceptions

'-secured' is only supported for SmartFusion devices.

Example

Single Mode, exports the secured IEEE 1532 files 'my_design.isc' and 'my_design.bsd' into folder

'D:/TOP/my_design_1532' using the PDB 'my_design.pdb': export_single_1532 -file {D:/TOP/my_design_1532) -pdb {D:/TOP/my_design.pdb} -secured

Chain Mode example exports secured IEEE 1532 files 'my_design.isc' and 'my_design.bsd' into folder

'D:/TOP/my_design_1532' from a device in the chain named 'A2F200M3F' using the PDB 'my_design.pdb': export_single_1532 -name {A2F200M3F} -file {./my_design_1532} -pdb {./my_design.pdb} secured

export_single_dat

Exports a single device DirectC data file. export_single_dat -file { file } [-name { name }] [-pdb { pdb_file }] [-secured]

Arguments

-file { file }

Specifies the name of the file you are exporting.

-name { name }

Specifies the name of the device in chain mode to export a single device DirectC data file.

-pdb { pdb_file }

Specifies the PDB to use for exporting a DirectC data file. By default, the loaded PDB will be used for exporting a DirectC data file.

-secured

Use this argument to export a secured DirectC data file.

156 FlashPro User's Guide

Supported Families

SmartFusion, IGLOO, ProASIC3 and Fusion

Exceptions

'-secured' is only supported for SmartFusion devices.

Example

Single Mode, exports a secured DirectC DAT file 'my_design.dat' using the PDB file 'my_design.pdb': export_single_dat -file {D:/TOP/my_design.dat} -pdb {D:/TOP/my_design.pdb} -secured

Chain Mode, exports a secured DirectC DAT file 'my_design.dat' from a device in the chain named

'A2F200M3F', using the PDB 'my_design.pdb': export single_dat -name {A2F200M3F} -file {./my_design.dat} -pdb {./my_design.pdb} secured

export_single_stapl

Exports a single device STAPL file or single device chain STAPL file. export_single_stapl -file { file } [-name { name }] [-pdb { pdb_file }] [-secured] [-chain]

Arguments

-file { file }

Specifies the file to export.

-name { name }

Specifies the name of the device in chain mode to export a single device STAPL or single device chain

STAPL file.

-pdb { pdb_file }

Specifies the PDB to use for exporting a STAPL file. By default, the loaded PDB is used for exporting a

STAPL file.

-secured

Exports a secured STAPL file.

-chain

Indicates that you want to export a single device chain STAPL file.

Note: This parameter is only supported for SmartFusion2, IGLOO2, and RTG4 families.

Supported Families

SmartFusion2, IGLOO2, RTG4, SmartFusion, IGLOO, ProASIC3 and Fusion

Exceptions

None

Example

Single Mode example exports the secured file 'my_design.stp' using the PDB 'my_design.pdb': export_single_stapl -file {D:/TOP/my_design.stp} -pdb {D:/TOP/my_design.pdb} -secured

Chain Mode example exports secured STAPL file 'my_design.stp' from device 'A2F200M3F' using the PDB

'my_design.pdb': export single_stapl -name {A2F200M3F} -file {./my_design.stp} -pdb {./my_design.pdb} secured

FlashPro User's Guide 157

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

export_single_svf

Exports a single device SVF programming file. export_single_svf -file { file } [–name { name }] [-pdb { pdb_file }] [-secured]

Arguments

-file { file }

Specifies the file to export.

-name { name }

Specifies the name of the device in chain mode to export a single device SVF programming file.

-pdb { pdb_file }

Specifies the PDB to use for exporting a SVF programming file. By default, the loaded PDB is used for exporting a SVF programming file.

-secured

Exports a SVF programming file for a secured device.

Supported Families

SmartFusion, IGLOO, ProASIC3 and Fusion

Exceptions

'-secured' is only supported for SmartFusion devices.

Example

Single Mode, exports the secured SVF files for each programming ACTION with the following format

'my_design_ACTION.svf' into folder 'D:/TOP/my_design_SVF' using the PDB 'my_design.pdb': export_single_SVF -file {D:/TOP/my_design_SVF) -pdb {D:/TOP/my_design.pdb} -secured

Chain Mode example exports secured SVF files for each programming ACTION with the following format

'my_design_ACTION.svf' into folder 'D:/TOP/my_design_SVF' from a device in the chain named

'A2F200M3F' using the PDB 'my_design.pdb': export_single_SVF -name {A2F200M3F} -file {./my_design_SVF} -pdb {./my_design.pdb} secured

export_spi_directory

Tcl command; exports the SPI directory that contains address and design version information for the

Golden and Update SPI images. export_spi_directory [-golden_ver { decimal }] [-golden_addr { hex }] [-update_ver { decimal }]

[-update_addr { hex }] -file { file }

Arguments

-golden_ver { decimal }

Specifies Golden SPI Image design version where decimal is a decimal value and less than 65536

(exclusive).

-golden_addr { hex }

Specifies Golden SPI Image address where hex is 32-bit hexadecimal value with prefix 0x/0X.

-update_ver { decimal }

Specifies Update SPI Image design version where decimal is a decimal value and less than 65536

(exclusive).

-update_addr { hex }

158 FlashPro User's Guide

Specifies Update SPI Image address where hex is a 32-bit hexadecimal value with prefix 0x/0X.

-file { file }

Mandatory argument; specifies the file export location.

Supported Families

SmartFusion2, IGLOO2

Examples

Both golden* options go together. The same is true for both update* options.; the file argument is required: export_spi_directory -golden_ver {23} -golden_addr {0x40001234} -file

{D:\flashpro_files\m2s090t_spi_1\designer\m2s090t_spi_1_MSS\export\m2s090t_spi_1_MSS1.spi

Dir} export_spi_directory -update_ver {8} -update_addr {0x2000abcd} -file

{D:\flashpro_files\m2s090t_spi_1\designer\m2s090t_spi_1_MSS\export\m2s090t_spi_1_MSS2.spi

Dir} export_spi_directory -golden_ver {23} -golden_addr {0x40001234} -update_ver {8} update_addr {0x2000abcd} -file

{D:\flashpro_files\m2s090t_spi_1\designer\m2s090t_spi_1_MSS\export\m2s090t_spi_1_MSS3.spi

Dir}

FlashPro User's Guide 159

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

import_config

Imports a configuration file. import_config -file { file }

Arguments

-file { file }

Specifies the file to import.

Supported Families

All

Exceptions

None

Example

The following example imports the configuration file 'my_config1.ufc': import_config -file {my_config1.ufc'}

new_project

Creates a new FlashPro project or convert an old ChainBuilder project into a new FlashPro project (the mode parameter must be 'chain' in this case). new_project -name { name } -location { location } -mode {single|chain} [-convert_chb

{ convert_chb }]

Arguments

-name { name }

Specifies the project name.

-location { location }

Specifies the project location.

-mode {single|chain}

Specifies programming mode; either single or chain.

-convert_chb { convert_chb }

An optional argument that specifies the ChainBuilder project to be converted.

Supported Families

All

Exceptions

None

Example

Create a new FlashPro single device project named 'FPPrj1' in a directory with the name 'FPProject1': new_project -name {FPPrj1} -location {./FPProject1} -mode {single}

160 FlashPro User's Guide

Create a new FlashPro project named 'FPPrjChb' in the directory 'ChbProject1'; converts the ChainBuilder project 'prj1.chb' project to FlashPro. new_project -name {FPPrjChb} -location {./ChbProject1} -mode {chain} -convert_chb

{./chb_prj/prj1.chb}

open_project

Opens a FlashPro or FlashPro Express project. open_project -project { project }

Arguments

-project { project }

Specifies the location and name of the project you wish to open.

Supported Families

All

Exceptions

None

Example

Opens the 'FPPrj1.pro' project from the FPProject1 directory open_project -project {./FPProject1/FPPrj1.pro}

paste_device

Pastes the devices that are on the clipboard in the chain, immediately above the position_name device, if this parameter is specified. Otherwise it places the devices at the end of the chain. The chain programming mode must be enabled. paste_device [-position_name { position_name }]

Arguments

-position_name { position_name }

Optional argument that specifies the name of a device in the chain.

Supported Families

All

Exceptions

None

Examples

The following example pastes the devices on the clipboard immediately above the device 'mydevice3' in the chain. paste_device –position_name {MyDevice3}

FlashPro User's Guide 161

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

ping_prg

Pings one or more programmers. ping_prg (-name { name })*

Arguments

-name { name }

Specifies the programmer to be pinged. Repeat this argument for multiple programmers.

Supported Families

All

Exceptions

None

Example

The following example pings the programmers 'FP300085' and 'FP30086'. ping_prg –name {FP300085} –name {FP300086}

read_analog_block_config

Reads each channel configuration on your analog system, enabling you to identify if/how each channel is configured. read_analog_block_config [-name { device_name }] [-file { filename }]

Arguments

-name { device_name }

Optional user-defined device name. The device name is not required if there is only one device in the

current configuration, or a device has already been selected using the set_debug_device command.

-file { filename }

(Optional) Identifies the name of the file to which read results will be saved.

Supported Families

Fusion

Exceptions

None

Example

The following command reads the analog block configuration information in the device 'AFS600': read_analog_block_config –name {AFS600}

read_device_status

Displays the Device Information report; the Device Information report is a complete summary of your device state, analog block test values, user information, factory serial number and security information.. read_device_status [-name { device_name }] [-file { filename }]

162 FlashPro User's Guide

Arguments

Supported Families

SmartFusion, IGLOO, ProASIC3 and Fusion

Exceptions

None

Example

-name device_name

Optional user-defined device name. The device name is not required if there is only one device in the

current configuration, or a device has already been selected using the set_debug_device command.

-file { filename }

(Optional) Identifies the name of the file to which read results will be saved.

The following reads device info from the 'AFS600' device. read_device_status -name AFS600

read_flash_memory

The command reads information from the NVM modules. There are two types of information that can be read:

• Page Status – includes ECC2 status, write count, access protection

• Page Data read_flash_memory

[-name { device_name }]

[-block { integer_value }]

[-client { client_name }]

[-startpage { integer_value }]

[-endpage { integer_value }]

[-access { all | status | data }]

[-file { filename }]

At a minimum you must specify -client < name > OR

-startpage < page_number > -endpage < page_number > -block < number >

Arguments

-name { device_name }

Optional user-defined device name. The device name is not required if there is only one device in the

current configuration, or a device has already been selected using the set_debug_device command.

-block { integer_value }

(Optional argument; you must set -client or –startpage and –endpage before use.) Specifies location of block for memory read.

-client { client_name }

Name of client for memory read.

-startpage { integer_value }

Startpage for page range; value must be an integer. You must specify a –endpage and -block along with this argument.

-endpage { integer_value }

Endpage for page range; value must be an integer. You must specify a –startpage and -block along with this argument.

FlashPro User's Guide 163

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

-access { all | status | data }

(Optional argument; you must set -client or –startpage, –endpage and –block before use.) Specifies what eNVM information to check: page status, data or both.

-file { filename }

(Optional argument; you must set -client or –startpage, –endpage and –block before use.) Name of output file for memory read.

Supported Families

SmartFusion, Fusion

Exceptions

None

Example

The following command reads the flash memory for the client 'DS8bit' and reports the data in a logfile

'readFlashMemoryReport.log': read_flash_memory -client {DS8bit} -file {readFlashMemoryReport.log} read_flash_memory –startpage 0 –endpage 2 –block 0 –access {data}

read_flashrom

Reads the content of the FlashROM from the selected device. read_flashrom [-name { device_name }] [-mapping { logical | physical }] [-file { filename }]

Arguments

-name device_name

Optional user-defined device name. The device name is not required if there is only one device in the

current configuration, or a device has already been selected using the set_debug_device command.

-mapping { logical | physical }

(Optional) Specifies how the data read from the UFROM is mapped. Values are explained in the table below.

Value Description logical Logical mapping (default) physical Physical mapping

-file { filename }

(Optional) Identifies the name of the file to which read results will be saved.

164 FlashPro User's Guide

Supported Families

SmartFusion, IGLOO, ProASIC3 and Fusion

Exceptions

None

Example

The following reads the FROM content on the device 'AFS600' and sets to physical mapping: read_flashrom -name {AFS600} -mapping {physical}

read_id_code

The command reads IDCode from the device without masking any IDCode fields. This is the raw IDcode from the silicon.

Note: Being able to read the IDCode is an indication that the JTAG interface is working correctly. read_id_code [-name { device_name }]

Arguments

-name device_name

Optional user-defined device name. The device name is not required if there is only one device in the

current configuration, or a device has already been selected using the set_debug_device command.

Supported Families

SmartFusion, IGLOO, ProASIC3 and Fusion

Exceptions

None

Example

The following command reads the IDCODE from the device 'AFS600': read_id_code –name {AFS600}

recover_flash_memory

The command removes ECC2 errors due to memory corruption by reprogramming specified flash memory

(NVM) pages and initializing all pages to zeros. The recovery affects data blocks and auxiliary blocks.

The write counters of the corrupted pages might not be accurate due to corruption. The recovery operation will not change state of the page write counters.

Use the check_flash_memory command to detect flash memory errors. recover_flash_memory

[-name { device_name }]

[-block { integer_value }]

[-client { client_name }]

[-startpage { integer_value }]

[-endpage { integer_value }]

At a minimum you must specify

-client < name >

-startpage < page_number > -endpage < page_number > -block < number >

FlashPro User's Guide 165

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Arguments

Supported Families

SmartFusion, Fusion

Exceptions

None

Example

-name { device_name }

Optional user-defined device name. The device name is not required if there is only one device in the

current configuration, or a device has already been selected using the set_debug_device command.

-block { integer_value }

(Optional argument; you must set -client or –startpage and –endpage before use.) Specifies location of block for memory recovery.

-client { client_name }

Name of client for memory recovery.

-startpage { integer_value }

Startpage for page range; value must be an integer.You must specify a –endpage and -block along with this argument.

-endpage { integer_value }

Endpage for page range; value must be an integer. You must specify a –startpage and -block along with this argument.

The following command recovers flash memory data in the client 'DS8bit': recover_flash_memory -client {DS8bit}

The following command recovers flash memory from block 0, startpage 0, and endpage 3: recover_flash_memory -block 0 -startpage 0 -endpage 3

refresh_prg_list

Refreshes the programmer list. This is most often used to have FlashPro or FlashPro Express detect a programmer that you have just connected. refresh_prg_list

Arguments

None

Supported Families

All

Exceptions

None

Example refresh_prg_list

166 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

remove_device

Removes the device from the chain. Chain programming mode must be set. remove_device (-name { name })*

Arguments

-name { name }

Specifies the device name. You can repeat this argument for multiple devices.

Supported Families

All

Exceptions

None

Example

Remove a device 'A3P250' from the chain: remove_device (-name {A3P250})* refresh_prg_list

FlashPro User's Guide 167

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

remove_non_actel_device_from_database

Removes settings for non-Microsemi or non-Actel device from the device database. remove_non_actel_device_from_database [-name { device_name }]

Arguments

-name { device_name }

Specifies the non-Actel or non-Microsemi device name to be removed from the database. You can repeat this argument for multiple devices.

Supported Families

Non-Microsemi and non-Actel devices

Exceptions

None

Example

The following example removes the F1502AS_J44 device from the database: remove_non_actel_device_from_database –name {F1502AS_J44}

The following example removes the SA2_PROCESSOR device from the database: remove_non_actel_device_from_database –name {SA2_PROCESSOR}

remove_prg

Removes the programmer from the programmer list. remove_prg (-name { name })*

Arguments

-name { name }*

Specifies the programmer to be removed. You can repeat this argument for multiple programmers.

Supported Families

All

Exceptions

None

Example

The following example removes the programmer '03178' from the programmer list: remove_prg (name {03178})*

run_selected_actions

Runs the selected action on the specified programmer and returns the exit code from the action. If no programmer name is specified, the action is run on all connected programmers. Only one exit code is

168 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content. sample_analog_channel returned, so return code cannot be used when action is run on more than one programmer. A programming file must be loaded. run_selected_actions [(-name { name })*]

Arguments

-name { name }

Optional argument that specifies the programmer name. You can repeat this argument for multiple programmers.

Supported Families

All

Exceptions

None

Example

The following example runs the selected actionS on the programmers 'FP30085' and 'FP30086'. run_selected_actions –name {FP300085} –name {FP300086}

Example using return code: if {[catch {run_selected_actions} return_val]} {puts "Error running Action"} else {puts

"exit code $return_val"}

Example returning exit code to the command line (returns exit 99 on script failure, otherwise returns exit code from selected action): if {[catch {run_selected_actions} return_val]}{exit 99} else {exit $return_val}

sample_analog_channel

Performs analog-to-digital conversion of a selected analog channel. This command is used when debugging the Analog Subsystem and is performed on the pre-configured analog channel with user-supplied ADC conversion parameters. The command also performs digital filtering using a single-pole low-pass filter if you opt to use it. sample_analog_channel [(-name { name })*]

[-resolution { 8 | 10 | 12 }]

[-clock_periods { int_value }]

[-clock_divider { int_value }]

[-num_samples { int_value }]

[-filtering_factor { real_value }]

[-initial_value { int_value }]

[-show_details { yes | no }]

[-file { filename }]

Arguments

-name { name }

Specifies the analog channel to be sampled. Channel name is a combination of the channel type followed by the channel index. Valid channel names are listed in the table below.

Family Valid Channel Name

Fusion AV<n>, AT<n>, AC<n>

FlashPro User's Guide 169

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Family Valid Channel Name

SmartFusion AV<n>, AT<n>, AC<n>, ADC<n>

The maximum number of channels depends on particular device type; refer to the Analog Block specification in the device handbook.

-resolution {8 | 10 | 12}

ADC conversion resolution. Specifies bit size of the conversion results. Selection of certain resolutions may affect timing parameter valid ranges. See your device handbook for details.

-clock_periods {int_value }

Parameter specifying sampling time: Sampling_time = clock_periods * adc_clock_period.

-clock_divider {int_value }

Specifies clock prescaling factor.

-num_samples { int_value }

Optional argument that specifies the number of samples to be performed by the ADC. Default number of samples is 1. Selecting multiple vs single sample will change appearance of the generated report. For the single sample a single result is shown and if “show_details” is set to “yes” then detailed status of the ADC register is also shown.

If multiple samples are requested then the results are printed in a table. If the digital filtering is enabled the table also includes filtered results.

-filtering_factor {real_value}

Optional argument that specifies the filtering factor if multiple samples requested. The default value of 1.0 disables digital filtering.

-initial_value {int_value}

Optional argument that specifies the initial value for the digital averaging filter. The value is specified in

ADC register counts. Default value is set to 0. Specifying this parameter improves filtering process during initial samples.

-show_details {yes | no}

Optional argument that specifies the level of the report output. Detailed output includes initial usersupplied conversion parameters. For the single-sampling case final output also includes detailed content of ADC register after sampling.

-file {filename}

Optional argument. Specifies name of output file for conversion results.

Supported Families

SmartFusion and Fusion

Exceptions

None

Example

The following example performs single sample analog-to-digital conversion for channel AV0: sample_analog_channel –channel AV0 –resolution 8 –clock_periods 4 –clock_divider 4

Example with multiple sampling and digital signal filtering for AV0: sample_analog_channel –channel AV0 –resolution 10 –clock_periods 4 –clock_divider 4 – num_samples 10 –filtering_factor 2.5

save_log

Saves the log file.

170 FlashPro User's Guide

Arguments

-file { file }

Specifies the log filename.

Supported Families

All

Exceptions

None

Example

The following example saves the log file with the name 'my_logfile1.log': save_log -file {my_logfile1.log}

save_project

Saves the FlashPro or FlashPro Express project. save_project

Arguments

None

Supported Families

All

Exceptions

None

Example save_project

save_project_as

Saves the FlashPro project under a new project name. save_project_as -name { name } -location { location }

Arguments

-name { name }

Specifies the project name.

-location { location }

Specifies the project location.

FlashPro User's Guide save_project

171

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Supported Families

All

Exceptions

None

Example

The following example saves the FlashPro project 'FPPrj2' to the directory 'FPProject2': save_project_as -name {FPPrj2} -location {./FPProject2}

scan_chain_prg

In single mode, this command runs scan chain on a programmer.

In chain mode, this command runs scan and check chain on a programmer if devices have been added in the grid. scan_chain_prg [(-name { name })+]

Arguments

-name { name }

Specifies the programmer name.

Supported Families

All

Exceptions

None

Example

The following example runs scan chain on a single programmer (single mode) named '21428': scan_chain_prg -name {21428}

select_from_region_name

Enables you to select the serialization region you want to add to the log file. select_from_region_name –enable {1|0} –region_name { name }

Arguments

-enable {1|0}

Enable serialization region logging. '1' enables serialization region logging; '0' disables it.

-region_name { name }

The name of the target serialization/client within FlashRom you wish to log.

Supported Families

SmartFusion, IGLOO, ProASIC3 and Fusion

172 FlashPro User's Guide

Exceptions

None

Example

The following example enables select_from_region_name and adds the serialization region 'afs090_b' to the log file: select_from_region_name -enable {1} -region_name {afs090_b}

select_libero_design_device

FlashPro-specifc Tcl command. This command selects the Libero design device for the Programming

Connectivity and Interface tool within Libero. This command is needed when the tool cannot automatically resolve the Libero design device when there are two or more identical devices that match the Libero design device in the configured JTAG chain.

Syntax select_libero_design_device -name { device_name }

Arguments

-name { device_name }

Specifies a user-assigned unique device name in the JTAG chain.

Supported Families

SmartFusion2, IGLOO2

Exceptions

None

Example select_libero_design_device –name {M2S050TS (2)} select_libero_design_device –name {my_design_device}

Note

This Tcl command is typically used in a Flashpro Tcl command script file that is passed to the Libero run_tool command. run_tool –name {CONFIGURE_CHAIN} -script {<flashPro_cmd>.tcl}

select_serial_range

This Tcl command selects the range of indexes to program. select_serial_range -name device_name -from_data start_index_to_program -to_data end_index_to_program

Arguments

-name

Specifies the device name.

-from_data

Specifies the start index to program.

FlashPro User's Guide 173

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

-to_data

Specifies the end index.

Supported Families

See the Tcl Commands and Supported Families table for the list of families that support this command.

Exceptions

Must be a Microsemi Device

Example select_serial_range -name M2S/M2GL050{T|S|TS} -from_data 3 -to_data 5

select_target_device

Enables you to set a target device for programming in Single Device Programming mode. The command

is identical to the Select Target Device dialog box in FlashPro.

Select_target_device -name { device_name }

Arguments

-name { device_name }

Specifies the name of the target device.

Supported Families

SmartFusion, IGLOO, ProASIC3 and Fusion

Exceptions

None

Examples

The following example targets the A3P(L) / AGL1000 device for programming: select_target_device –name {A3P(L)/AGL1000 (1)}

self_test_prg

Runs Self-Test on a programmer. self_test_prg (-name { name })*

Arguments

-name { name }

Specifies the programmer name. You can repeat this argument for multiple programmers.

Supported Families

All

174 FlashPro User's Guide

Exceptions

None

Example

The following examples runs the self test on the programmer '30175': self_test_prg (-name {30175})*

set_bsdl_file

Sets a BSDL file to a non-Microsemi device in the chain. Chain programming mode must have been set.

The device must be a non-Microsemi device. set_bsdl_file -name { name } -file { file }

Arguments name { name }

Specifies the device name.

-file { file }

Specifies the BSDL file.

Supported Families

Any non-Microsemi device supported by FlashPro.

Exceptions

None

Example

The following example sets the BSDL file /design/bsdl/NewBSDL2.bsdl to the device 'MyDevice3': set_bsdl_file –name {MyDevice3} –file {e:/design/bsdl/NewBSDL2.bsdl}

set_chain_param

Sets the chain parameters in single programming mode. Single programming mode must be set . set_chain_param [-pre_ir {pre_ir}] [-pre_dr {pre_dr}] [-post_ir {post_ir}] [-post_dr

{post_dr}]

Arguments

-pre_ir {pre_ir}

Specifies the pre IR length.

-pre_dr {pre_dr}

Specifies the pre DR length.

-post_ir {post_ir}

Specifies the post IR length.

-post_dr {post_dr}

Specifies post DR length.

Supported Families

All

FlashPro User's Guide 175

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Exceptions

None

Example

The following example sets the chain parameters for pre IR length to 2, pre DR length to 3, post IR length to 4, and post DR length to 5: set_chain_param –pre_ir {2} –pre_dr {3} –post_ir {4} –post_dr {5}

set_debug_device

Identifies the device you intend to debug. set_debug_device -name { device_name }

Arguments name { device_name }

Device name. The device name is not required if there is only one device in the current configuration.

Supported Families

SmartFusion, IGLOO, ProASIC3 and Fusion

Exceptions

None

Example

The following example identifies the device 'A3P250' for debugging: set_debug_device –name {A3P250}

set_debug_programmer

Identifies the programmer you want to use for debugging (if you have more than one). The name of the programmer is the serial number on the bar code label on the FlashPro programmer. set_debug_programmer -name { programmer_name }

Arguments

-name { programmer_name }

Programmer name is the serial number on the bar code label of the FlashPro programmer.

Supported Families

SmartFusion, IGLOO, ProASIC3 and Fusion

Exceptions

None

Example

The following example selects the programmer 10841 set_debug_programmer -name {10841}

176 FlashPro User's Guide

set_device_ir

Sets the IR length of a non-Microsemi device in the chain. Chain programming mode must be set. The device must be a non-Microsemi device. set_device_ir -name { name } -ir { ir }

Arguments

-name { name }

Specifies the device name.

-ir { ir }

Specifies the IR length.

Supported Families

Any non-Microsemi device supported by FlashPro.

Exceptions

None

Example

The following example sets the IR length to '2' for the non-Microsemi device 'MyDevice4': set_device_ir –name {MyDevice4} –ir {2}

set_device_name

Changes the user name of a device in the chain. Chain programming mode must be set . set_device_name -name { name } -new_name { new_name }

Arguments

-name { name }

Identifies the old device name.

-new_name { new_name }

Specifies the new device name.

Supported Families

All

Exceptions

None

Example

The following example changes the user name of the device from 'MyDevice4' to 'MyDevice5': set_device_name –name {MyDevice4} –new_name {MyDevice5}

set_device_order

Sets the order of the devices in the chain to the order specified. Chain programming mode must have been set. Unspecified devices will be at the end of the chain.

FlashPro User's Guide 177

Arguments

-name { name }

Specifies the device name. To specify a new order you must repeat this argument and specify each device name in the order desired.

Supported Families

All

Exceptions

None

Example

The following example sets the device order for 'MyDevice1', 'MyDevice2', 'MyDevice3', and 'MyDevice4'.

'MyDevice2' is unspecified so it moves to the end of the chain. set_device_order –name {MyDevice3} –name {MyDevice1} –name {MyDevice4} the new order is:

MyDevice3 MyDevice1 MyDevice4 MyDevice2

set_device_tck

Sets the maximum TCK frequency of a non-Microsemi device in the chain. Chain programming mode must be set. The device must be a non-Microsemi device. set_device_tck -name { name } -tck { tck }

Arguments

-name { name }

Specifies the device name.

-tck { tck }

Specifies the maximum TCK frequency (in MHz).

Supported Families

Any non-Microsemi device supported by FlashPro.

Exceptions

None

Example

The following example sets the maximum TCK frequency of the non-Microsemi device 'MyDevice4': set_device_tck –name {MyDevice4} –tck {2.25}

set_device_to_highz

Sets a disabled Microsemi or Microsemi device in Chain programming mode to HIGH-Z. This Tcl

178 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content. set_device_type set_device_to_highz -name { device_name } –highz {1|0}

Arguments

-name { device_name }

Target device name in chain mode.

-highz {1|0}

Sets disabled device to HIGH-Z. '1' sets the device to HIGH-Z, '0' removes the setting.

Supported Families

SmartFusion, IGLOO, ProASIC3 and Fusion

Exceptions

None

Example

The following example sets the AFS090 device to HIGH-Z: set_device_to_highz –name {AFS090} –highz 1

The following example removes the HIGH-Z setting from the AFS1500 device: set_device_to_highz –name {AFS1500} –highz 0

set_device_type

Changes the family of a Microsemi device in the chain. The device must be a Microsemi device. The device parameter below is now optional. set_device_type -name { name } -type { type }

Arguments

-name { name }

Identifies the name of the device you want to change.

-type { type }

Specifies the device family.

Supported Families

Any Microsemi device supported by FlashPro.

Exceptions

None

Example

The following example sets the device 'MyDevice2' to the type A3PE600. set_device_type –name {MyDevice2} –type {A3PE600}

set_main_log_file

Sets the FlashPro log file. set_main_log_file -file { file }

FlashPro User's Guide 179

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Arguments

-file { file }

Specifies the log file.

Supported Families

All

Exceptions

None

Example

The following example sets the FlashPro log file to 'log1000.txt'. set_main_log_file –file {e:/log/log1000.txt}

set_prg_name

Changes the user name of a programmer. set_prg_name -name { name } -new_name { new_name }

Arguments

-name { name }

Identifies the old programmer name.

-new_name { new_name }

Specifies the new programmer name.

Supported Families

All devices supported by FlashPro.

Exceptions

None

Example

The following example changes the name of the programmer 'FP300086' to 'FP3Prg2': set_prg_name –name {FP300086} –new_name {FP3Prg2}

set_programming_action

Selects the action for a device. The device name parameter must be specified only in chain programming mode. A programming file must be loaded. The device must be a Microsemidevice. set_programming_action [-name { name }] -action { action }

Arguments

-name { name }

Specifies the device name.

-action { action }

Specifies the action.

180 FlashPro User's Guide

Supported Families

SmartFusion, IGLOO, ProASIC3, Fusion

Exceptions

Must be a Microsemi device

Example

The following example sets the programming action in single programming mode: set_programming_action –action {PROGRAM}

And in chain programming mode: set_programming_action –name {MyDevice1} –action {ERASE}

set_programming_file

Sets the programming file for a device. Either the file or the no_file flag must be specified. A programming file must be loaded. The device must be a Microsemi device . set_programming_file [-name { name }] [-file { file }] [-no_file { }]

Arguments

-name { name }

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

-file { file }

Specifies the programming file.

-no_file

Specifies to unload the current programming file.

Supported Families

SmartFusion, IGLOO, ProASIC3, Fusion

Exceptions

Must be a Microsemi device.

Examples

In single programming mode: set_programming_file –file {e:/design/pdb/TopA3P250.pdb}

In chain programming mode: set_programming_file –name {MyDevice2} –file {e:/design/pdb/TopA3P250.pdb} set_programming_file –name {MyDevice1} –no_file

set_programming_mode

Sets the programming mode. set_programming_mode -mode {single|chain}

Arguments

-mode {single|chain}

Specifies the mode, either single programming or chain programming.

FlashPro User's Guide 181

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Supported Families

All devices supported by FlashPro.

Exceptions

None

Example

The following example sets the programming mode to 'single': set_programming_mode -mode {single}

set_serialization_log_file

This Tcl command sets the path and name of the serialization log file. set_serialization_log_file -file { log_file_path }

Arguments

-file

Specifies the serialization log file path and name

Supported Families

See the Tcl Commands and Supported Families table for the list of families that support this command.

Exceptions

Must be a Microsemi Device

Example set_serialization_log_file -file {C:/local_z_folder/work/my_serial_log}

set_serialization_mode

Sets the serialization mode. set_serialization_mode -mode {skip|reuse}

Arguments

-mode {skip|reuse}

Supported Families

All devices supported by FlashPro.

Exceptions

None

Example

The following example sets the serialization mode to 'skip': set_serialization_mode -mode {skip}

182 FlashPro User's Guide

update_programming_file

Updates the programming file with the selected parameters. update_programming_file

[(-name { name })*]

-feature { value }

-signature { value }

-from_content { name }

-from_config_file { name }

-number_of_devices { value }

-from_program_pages { value }

-custom_security { value }

-security_permanent { value }

-fpa_security_level { value }

-from_security_level { value }

-efm_block_security{location:X;security_level: value }

-pass_key {value} -aes_key { value }

-efm_content {location:X;source: value }

-efm_block {location:X;config_file: value }

-efm_client {location:X;client: value ; mem_file: value }

-tie_off_arch { value }

-set_io_state { value }

-pdb_file { name }

-enable_m3debugger { value }

Arguments

{setup_security:on/off}

{prog_fpga:on/off}

{prog_from:on/off}

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

SmartFusion

{prog_nvm:on/off}

{setup_security}

{prog_from}

{all}

SmartFusion

Fusion

IGLOO; ProASIC3

To program the Embedded Flash Memory Block, use the following EFM arguments: -efm_block , efm_client

, and -efm_block_security .

-signature { value }

Optional argument that identifies and tracks Microsemi designs and devices.

FlashPro User's Guide 183

184

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

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

Value Description

Yes Custom security level

No Standard security level

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

Value Description

Yes Permanently disables future modification of security settings

No Enables future modifications of security settings

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

Value Description write_verify_protect The security level is medium (standard) and the FPGA Array cannot be written or verified without 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

The FPGA Array can be written and verified without a Pass Key none

FlashPro User's Guide

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

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)

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

-efm_block_security{location: X ;security_level: value }

This option is available only for SmartFusion and Fusion; this argument only applies when programming the security settings (setup_security) or programming previously secured devices.

'X' identifies an Embedded Flash Memory Block instance from 0-3.

Possible values for security_level:

Value Description clients_jtag_protect Enables eNVM client JTAG protection; a pass key is required for this option. 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 encrypted

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)

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

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

FlashPro User's Guide 185

186

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content. either an EFC or PDB file. If you specify EFC as your source, you need to specify the -efm_block parameter. Possible values:

Value Description

PDB Embedded Flash Memory Block configuration and content is taken from your

PDB

EFC FlashPoint uses the Embedded Flash Memory Block configuration and content from the EFC file specified in -efm_block parameter

-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 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. Possible values:

Value Description pull-down Pull-down resistor: reduced quiescent power consumption pull-up Pull-up resistor: compatible behavior for migrated ProASIC PLUS designs

-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 -set_io_state {portName:<port name>; state:<state>}.

To set the I/O by pin number, use -set_io_state {pinNumber:<pin number>; state:<state>} .

To set all I/Os to the specified state, use -set_io_state {all; state:<state>}.

Possible state values:

Value Description

Tri-State Sets the I/O state to tristate

Last Known State

High

Sets the I/O state to last known state

Sets the I/O state to high

Low Sets the I/O state to low

-pdb_file { name }

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

-enable_m3debugger { yes | no }

SmartFusion only; .enables the M3 debugger .

FlashPro User's Guide

Supported Families

All devices supported by FlashPro.

Exceptions

None

Example

Fusion example 1: update_programming_file \

-feature {setup_security} \

-feature {prog_from} \

-from_content {ufc} \

-from_config_file {D:/from_ah.ufc} \

-number_of_devices {1} \

-from_program_pages {1 2 3 4 5 6 7 } \

-custom_security {no} \

-security_permanent {no} \

-fpga_security_level {write_verify_protect} \

-from_security_level {write_verify_protect} \

-efm_block_security {location:1;security_level:write_verify_protect} \

-efm_content {location:1;source:efc} \

-efm_block {location:1;config_file:{D:\ nvm_all_new.efc}} \

-efm_client {location:1;client:asb;mem_file:{}} \

-efm_client {location:1;client:cfiData;mem_file:{D:\cfid.mem}} \

-efm_client {location:1;client:ds;mem_file:{D:\ds.hex}} \

-efm_client {location:1;client:init1;mem_file:{D:\init1.hex}} \

-efm_client {location:1;client:raminit;mem_file:{}}

Update loaded PDB file: use ufc file for FlashROM configuration and content; use efc file for block 1 configuration; efc memory content will be overwritten by memory content from specified mem files for each client.

Fusion example 2: update_programming_file \

-feature {prog_from} \

-from_content {pdb} \

-from_program_pages {1} \

-efm_content {location:1;source:pdb} \

-efm_client {location:1;client:cfiData;mem_file:{D:\cfid.mem}}

Update loaded PDB file: use pdb data for FlashROM; program only page 1; use pdb data for block 1; program only client cfiData; overwrite memory content for this client with memory content from the specified file.

Fusion example 3: update_programming_file \

-efm_content {location:1;source:pdb} \

-efm_client {location:1;client:cfiData;mem_file:{D:\cfid.mem}} \

-efm_client {location:1;client:init1;mem_file:{}}

Update loaded PDB file: use pdb data for block 1; program client cfiData using memory content from the specified file; program client init1 using memory content from pdb (no mem_file path is specified) .

SmartFusion example: update_programming_file \ update_programming_file \

FlashPro User's Guide 187

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

-feature {setup_security:on} \

-feature {prog_fpga:off} \

-feature {prog_from:off} \

-feature {prog_nvm:on} \

-custom_security {no} \

-security_permanent {no} \

-fpga_security_level {none} \

-from_security_level {none} \

-efm_block_security {location:0;security_level:clients_jtag_protect} \

-efm_block_security {location:1;security_level:clients_jtag_protect} \

-pass_key {73F09973E792EC9F462AE5A446FB6C77} \

-efm_content {location:0;source:pdb} \

-efm_block

{location:0;config_file:{./eNVM_client_JTAG_protection_A2F500/allClients_Read_ON_Write_O

N.efc}}

-pdb_file {./fpro_jtag/fpro_jtag_30.pdb} \

-enable_m3debugger {no}

188 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Loopback Test

Troubleshooting

Loopback Test

The console software supports all JTAG functions and a diagnostic loopback test. Note that loopback is not supported on all boards.

To perform the diagnostic test

1. Connect the loopback test board to the FlashPro.

2. Connect the FlashPro to the parallel/USB port of the PC.

3. Power-on the FlashPro.

4. From the Start menu, choose Programs > Microsemi FlashPro > Diagnotics. This opens the diagnostics console program.

5. Connect to the FlashPro by entering openport lpt1 or openport usb. The parallel port number depends on the port used to connect the FlashPro.

6. Enter test. The unit runs into self-test mode. Do not interrupt the unit during self-test mode.

Note: To see a complete list of all functions, enter help. To get a more detail description of each function, enter help <command>.

Exit Codes (SmartFusion2, IGLOO2, and RTG4)

Table 24 · Exit Codes (SmartFusion2, IGLOO2, and RTG4)

Error

Code

Exit

Code

Exit Message Possible Cause Possible Solution

0 Passed (no error)

0x8001 -24 Failure to read DSN

Device is in System

Controller Suspend

Mode

Check board connections

TRSTB should be driven High or disable "System Controller Suspend

Mode"

0x8002 5 Failure to configure device programming at 1.2/1.0 VCC voltage

0x8032 5 Device is busy

Unstable voltage level

Signal integrity issues on JTAG pins

Monitor related power supplies that cause the issue during programming; check for transients outside of

Microsemi specifications. See your device datasheet for more information on transient specifications.

Monitor JTAG supply pins during programming; measure JTAG signals for noise or reflection.

Unstable VDDIx voltage level

Monitor related power supplies that cause the issue during programming; check for transients outside of

Microsemi specifications. See your device datasheet for more information on transient specifications.

FlashPro User's Guide 189

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Error

Code

Exit

Code

0x8003 5

Exit Message

Failed to enter programming mode

0x8004 6

0x8005 10

0x8006 10

0x8007 11

Failed to verify IDCODE

Failed to program eNVM

Failed to verify FPGA Array

Possible Cause Possible Solution

Unstable voltage level

Signal integrity issues on JTAG pins

Monitor related power supplies that cause the issue during programming; check for transients outside of

Microsemi specifications. See your device datasheet for more information on transient specifications.

Monitor JTAG supply pins during programming; measure JTAG signals for noise or reflection.

Incorrect programming file

Incorrect device in chain

Signal integrity issues on JTAG pins

Choose the correct programming file and select the correct device in the chain.

Measure JTAG pins and noise for reflection. If TRST is left floating then add pull-up to pin.

Reduce the length of Ground connection.

Unstable voltage level.

Signal integrity issues on JTAG pins.

Monitor related power supplies that cause the issue during programming; check for transients outside of

Microsemi specifications. See your device datasheet for more information on transient specifications.

Monitor JTAG supply pins during programming; measure JTAG signals for noise or reflection.

Unstable voltage level.

Signal integrity issues on JTAG pins.

Monitor related power supplies that cause the issue during programming; check for transients outside of

Microsemi specifications. See your device datasheet for more information on transient specifications.

Monitor JTAG supply pins during programming; measure JTAG signals for noise or reflection.

Device is programmed with a different design.

Unstable voltage level.

Signal integrity issues on JTAG pins.

Verify the device is programmed with the correct data/design

Monitor related power supplies that cause the issue during programming; check for transients outside of

Microsemi specifications. See your device datasheet for more information on transient specifications.

Monitor JTAG supply pins during programming; measure JTAG signals for noise or reflection.

190 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Exit Codes (SmartFusion2, IGLOO2, and RTG4)

Error

Code

Exit

Code

0x8008 11

Exit Message

Failed to verify eNVM

0x8009 11 Failed to verify eNVM

Possible Cause Possible Solution

Device is programmed with a different design.

Unstable voltage level.

Signal integrity issues on JTAG pins.

Verify the device is programmed with the correct data/design

Monitor related power supplies that cause the issue during programming; check for transients outside of

Microsemi specifications. See your device datasheet for more information on transient specifications.

Monitor JTAG supply pins during programming; measure JTAG signals for noise or reflection.

Device is programmed with a different design.

Unstable voltage level.

Signal integrity issues on JTAG pins.

Verify the device is programmed with the correct data/design

Monitor related power supplies that cause the issue during programming; check for transients outside of

Microsemi specifications. See your device datasheet for more information on transient specifications.

Monitor JTAG supply pins during programming; measure JTAG signals for noise or reflection.

0x8010 -35 Failed to unlock User Pass Key

Pass key in file does not match device

Provide a programming file with a pass key that matches pass key programmed into the device

0x8011 -35

0x8012 -35

Failed to unlock User Pass Key

Pass key in file does not match device

Failed to unlock debug pass key Pass key in file does not match device

Provide a programming file with a pass key that matches pass key programmed into the device

0x8013 -18 Digest request from SPI/JTAG is protected by user pass key 1

Digest request from

SPI/JTAG is protected by user pass key 1.

Lock bit has been configured in the Debug

Policy within SPM

(Security Policy

Manager)

Provide a programming file with a pass key that matches pass key programmed into the device

0x8014 -19 Failed to verify digest Unstable voltage level Monitor related power supplies that cause the issue during programming; check for transients outside of

Microsemi specifications. See your device datasheet for more information on transient specifications.

Signal integrity issues Monitor JTAG supply pins during

FlashPro User's Guide 191

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Error

Code

Exit

Code

Exit Message Possible Cause Possible Solution on JTAG pins programming; measure JTAG signals for noise or reflection

0x8015 -20 FPGA Fabric digest verification:

FAIL

Programming bitstream components do not match components programmed

FPGA Fabric is either erased or the data has been corrupted or tampered with

Use the same programming file that was used to program the device.

0x8016 -20 eNVM_0 digest verification:

FAIL

0x8017 -20 eNVM_1 digest verification:

FAIL

Programming bitstream components do not match components programmed eNVM_0 data has been corrupted or tampered with

Use the same programming file that was used to program the device

Programming bitstream components do not match components programmed eNVM_1 data has been corrupted or tampered with

Use the same programming file that was used to program the device

0x8018 -20 User security policies segment digest verification: FAIL

Programming bitstream components do not match components programmed

User security policy segment data has been corrupted or tampered with

Use the same programming file that was used to program the device.

0x8019 -20 User key set 1 segment digest verification: FAIL

Programming bitstream components do not match components programmed

User key set 1 segment data has been corrupted or tampered with

Use the same programming file that was used to program the device.

0x801A -20 User key set 2 segment digest verification: FAIL

Programming bitstream components do not match components programmed

User key set 2 segment data has been

Use the same programming file that was used to program the device.

192 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Exit Codes (SmartFusion2, IGLOO2, and RTG4)

Error

Code

Exit

Code

Exit Message Possible Cause Possible Solution

0x801B -20

0x801C -20

0x801D -21

0x801E -21

Factory row and factory key segment digest verification:

FAIL

Fabric configuration segment digest verification: FAIL

Device security prevented operation

Device security prevented operation corrupted or tampered with

Programming bitstream components do not match components programmed

Factory row and factory key segment data has been corrupted or tampered with

Use the same programming file that was used to program the device.

Programming bitstream components do not match components programmed.

Fabric configuration segment data has been corrupted or tampered with

Use the same programming file that was used to program the device.

The device is protected with user pass key 1 and the bitstream file does not contain user pass key 1.

User pass key 1 in the bitstream file does not match the device.

Run DEVICE_INFO to view security features that are protected.

Provide a bitstream file with a user pass key 1 that matches the user pass key 1 programmed into the device.

The device is protected with user pass key 1 and the bitstream file does not contain user pass key 1.

User pass key 1 in the bitstream file does not match the device.

Run DEVICE_INFO to view security features that are protected.

Provide a bitstream file with a user pass key 1 that matches the user pass key 1 programmed into the device.

0x801F -22 Authentication Error

Invalid/Corrupted programming file

Bitstream file has been corrupted

Bitstream was incorrected generated

Regenerate bitstream file

0x8020 -22 Authentication Error

Invalid/Corrupted programming file

Bitstream file has been corrupted

Bitstream was incorrected generated

Regenerate bitstream file

0x8021 -23 Authentication Error

Invalid/Corrupted encryption key

File contains an encrypted key that does

Provide a programming file with an encryption key that matches that on the

FlashPro User's Guide 193

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Error

Code

Exit

Code

Exit Message Possible Cause Possible Solution not match the device device

File contains user encryption key, but device has not been programmed with the user encryption key

First program security with master programming file, then program with user encryption 1/2 field update programming files

Device has user encryption key 1/2 enforced and you are attempting to reprogram security settings

You must first ERASE security with the master security file, then you can reprogram new security settings

0x8022 -23 Authentication Error

Invalid/Corrupted encryption key

File contains an encrypted key that does not match the device

Provide a programming file with an encryption key that matches that on the device

File contains user encryption key, but device has not been programmed with the user encryption key

First program security with master programming file, then program with user encryption 1/2 field update programming files

Device has user encryption key 1/2 enforced and you are attempting to reprogram security settings

You must first ERASE security with the master security file, then you can reprogram new security settings

0x8023 -24 Authentication

Error

Back level not satisfied

Design version is not higher than the backlevel programmed device

Generate a programming file with a design version higher than the back level version

0x8024 -24 Authentication

Error

Back level not satisfied

Design version is not higher than the backlevel programmed device

Generate a programming file with a design version higher than the back level version

0x8025 -25

0x8026 -25

Authentication Error

DSN binding mismatch

Authentication Error

DSN binding mismatch

0x8027 -26 Authentication Error

Insufficient device capabilities

0x8028 -26 Authentication Error

DSN specified in programming file does not match the device being programmed

Use the correct programming file with a

DSN that matches the DSN of the target device being programmed

DSN specified in programming file does not match the device being programmed

Use the correct programming file with a

DSN that matches the DSN of the target device being programmed

Device does not support the capabilities specified in programming file

Generate a programming file with the correct capabilities for the target device

Device does not Generate a programming file with the

194 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Exit Codes (SmartFusion2, IGLOO2, and RTG4)

Error

Code

Exit

Code

Exit Message Possible Cause Possible Solution

Insufficient device capabilities support the capabilities specified in programming file correct capabilities for the target device

0x8029 -27 Authentication Error

Incorrect DEVICEID

Incorrect programming file

Incorrect device in chain

Signal integrity issues on JTAG pins

Choose the correct programming file and select the correct device in chain

Measure JTAG pins and noise or reflection. If TRST is left floating, then add pull-up to pin

Reduce the length of ground connection

0x802A -27 AuthenticationError

Incorrect DEVICEID

Incorrect programming file

Incorrect device in chain

Signal integrity issues on JTAG pins

Choose the correct programming file and select the correct device in chain

Measure JTAG pins and noise or reflection

If TRST is left floating, then add pull-up to pin Reduce the length of ground connection

Generate programming file with latest version of Libero SoC

0x802B -28 Authentication Error

Unsupported bitstream protocol version

Old programming file

0x802C -28 Authentication Error

Unsupported bitstream protocol version

Old programming file Generate programming file with latest version of Libero SoC

0x802F -30 JTAG interface is protected by

UPK1

0x8030 -31 Authentication Error

Invalid or inaccessible Device

Certificate

Invalid or no UPK1 is provided

User needs to provide correct UPK1 to unlock device.

M2S090 Rev. A or

M2S150 Rev. A: Either certificate is corrupted or the user hasn't provided the application code in the eNVM or provided invalid application code

FAB_RESET_N is tied to ground

User can program a valid application code. This can be done with

SoftConsole.

FAB_RESET_N should be tied to HIGH

0x8031 -31 Authentication Error

Invalid or inaccessible Device

Certificate

M2S090 Rev. A or

M2S150 Rev. A: Either certificate is corrupted or the user hasn't provided the application code in the eNVM or provided invalid application code

FAB_RESET_N is tied

User can program a valid application code. This can be done with

SoftConsole

AB_RESET_N should be tied to HIGH

FlashPro User's Guide 195

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Error

Code

Exit

Code

Exit Message Possible Cause to ground

Possible Solution

SmartFusion, IGLOO, ProASIC3 and Fusion Device Exit Codes for

Software v8.6 and Above

The table below lists exit codes for SmartFusion, IGLOO, ProASIC3 and Fusion devices in software v8.6

and ABOVE only. See the Device Exit Codes for pre-v8.6 Software help topic for exit codes for older

versions.

Note: Exit codes with positive integers are reserved for current and future standard EXIT codes of the STAPL standard. Exit codes with negative integers are reserved for vendor-specific EXIT codes.

Table 25 · Exit Codes for SmartFusion, IGLOO, ProASIC3 and Fusion Family Devices in Software v8.6 and Above

ERROR_CODE Exit

Code

Exit

Message

Possible Cause Possible Solution

Passed

(no error)

A physical chain does not match the expected set up from the STAPL file.

Also known as

Checking

Chain

Error.

Physical chain configuration has been altered. Something has become disconnected in the chain.

The specific IR length of non-

Microsemi devices may be incorrect.

The order of the specified chain may be incorrect.

0x8052

0x801D

0x8053

Failed to enter programmin g mode.

Unstable VPUMP voltage level.

Unstable VCC

Signal integrity issues on JTAG pins.

Device is in FlashFreeze mode

(ProASICL or IGLOO devices)

Older software or programming file used.

Failed to verify

Incorrect programming file

Monitor related power supplies that cause the issue during programming; check for transients outside of Microsemi specifications. See your device datasheet for more information on transient specifications.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

Disble the FlashFreeze pin (ProASICL or

IGLOO devices)

Generate STAPL file with the latest version of Designer/FlashPro.

Use latest version of FlashPro software.

Choose the correct programming file and select the correct device in chain.

196 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

SmartFusion, IGLOO, ProASIC3 and Fusion Device Exit Codes for Software v8.6 and Above

ERROR_CODE

0x8005

0x8009

0x800B

0x8008

0x800A

0x800C

0x800D

0x800E

Exit

Code

Exit

Message

IDCODE

Possible Cause

Incorrect device in chain

Signal integrity issues on JTAG pins

Possible Solution

Measure JTAG pins and noise or reflection. If TRST is left floating then add pull-up to pin.

Reduce the length of ground connection.

Failed to verify AES

Sec.

Programming file generated with an older version of software

Generate STAPL file with the latest version of Designer/FlashPro. Use latest version of FlashPro software.

Try again at a slower TCK.

Contact Microsemi Technical Support.

Failed to verify

IDCODE.

Target is an

M7 device

File is not for M7, but target device is M7

Signal integrity issues on JTAG pins.

Check that the target device is M7 enabled.

Make sure that the programming file you generated is for an M7-enabled device.

Measure JTAG pins, noise and reflection.

Failed to verify

IDCODE

Target is an

M1 device

Files not for M1, but target device is M1.

Signal integrity issues on JTAG pins

Check that the target device is M1 enabled.

Make sure the programming file generated is for an M1-enabled device.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

Failed to verify

IDCODE.

Core enabled device detected

File is not for target device.

Signal integrity issues on JTAG pins

Check the target device; make sure the programming file generated is matches the target device.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

Failed to verify

IDCODE.

The target is not M7 device

File is for M7 but target device is not M7.

Signal integrity issues on JTAG pins.

Check that the target device is not M7 enabled.

Make sure that the programming file generated is for non-M7 enabled device.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

Failed to verify

IDCODE.

File is for M1, but target device is not M1.

Check that the target device is not M1 enabled.

FlashPro User's Guide 197

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

ERROR_CODE

0x8006

0x801E

0x8057

0x8058

0x805D

Exit

Code

Exit

Message

Target is not an M1 device

Possible Cause

Signal integrity issues on JTAG pins

Possible Solution

Make sure that the generated programming file is for non-M1 enabled device.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

Failed to verify

IDCODE.

Target is not a P1 device

File is not for P1, but target device is a P1 device.

Signal integrity issues on JTAG pins

Check that the target device is P1 enabled.

Make sure programming file generated is for M1 enabled device.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

6 A3PE600

Engineering

Sample

Device

Detected.

This device is supported with pre-v8.3

SP1 STAPL files only

Contact Microsemi Technical Support

8 Failed Erase

Operation.

Unstable VPUMP voltage level.

Unstable VCC

Unstable VCC_OSC (Fusion only)

Unstable VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

10 Failed to program

FPGA array at row <row number>.

Unstable VPUMP voltage level.

Unstable VCC

Unstable VCC_OSC (Fusion only)

Unstable VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

10 Failed to Unstable VPUMP voltage level. Monitor related power supplies that cause

198 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

SmartFusion, IGLOO, ProASIC3 and Fusion Device Exit Codes for Software v8.6 and Above

ERROR_CODE

0x805E

0x807B

Exit

Code

Exit

Message

Possible Cause Possible Solution enable

FPGA Array. Unstable VCC

Unstable VCC_OSC (Fusion only)

Unstable VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins. the issue during programming; check for transients outside of Microsemi specifications. See your device datasheet for more information on transient specifications.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

0x80

10 Failed to disable

FPGA Array.

Unstable VPUMP voltage level.

Unstable VCC

Unstable VCC_OSC (Fusion only)

Unstable VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

0x8061

0x8062

0x801B

0x801C

0x806C

0x806D

0x806E

10 Failed to program

FlashROM.

Unstable VPUMP voltage level.

Unstable VCC

Unstable VCC_OSC (Fusion only)

Unstable VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

10 Error programmin g Embedded

Flash

Memory

Block

(EFMB)

Unstable VCC_NVM/VCC_OSC voltage level (Fusion only)

Unstable

VCC_ENVM/VCC_RCOSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins

NVM corruption is possible when writing from your design; check the NVM status for confirmation.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

Reset signal is not properly tied off in your design.

0x807D

0x807E

10 Error programmin g system init

Unstable VCC

Unstable VCC_OSC (Fusion only)

Monitor related power supplies that cause the issue during programming; check for transients outside of Microsemi

FlashPro User's Guide 199

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

ERROR_CODE

0x8069

0x806A

0x806B

0x808E

0x808F

0x8090

0x8091

0x807F

0x8080

0x8059

0x805B

0x8060

Exit

Code

Exit

Message and boot clients

Possible Cause

Unstable VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins

Possible Solution specifications. See your device datasheet for more information on transient specifications.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

10 Error programmin g Embedded

Flash

Memory

Block

(EMFB)

Programming file generated with an older version of software

Generate STAPL file with the latest version of Designer/FlashPro; use the latest version of FlashPro software

Try again at a slower TCK

Contact Microsemi Technical Support

10 Error programmin g Embedded

Flash

Memory

Block

(EFMB)

Try reprogramming

Contact Microsemi Technical Support

10 Error programmin g system init and boot clients

Programming file generated with an older version of software

Generate STAPL file with the latest version of Designer/FlashPro; use the latest version of FlashPro software

Try again at a slower TCK

Contact Microsemi Technical Support

11 Verify 0 failed at row

Verify 1 failed at row

<row number>.

Unstable VPUMP voltage level.

Unstable VCC

Unstable VCC_OSC (Fusion only)

Unstable VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

Failed to verify

FlashROM at row

Device is programmed with a different design.

Unstable VPUMP voltage level.

Run VERIFY_DEVICE_INFO to verify the device is programmed with the correct data/design.

Monitor related power supplies that cause

200 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

SmartFusion, IGLOO, ProASIC3 and Fusion Device Exit Codes for Software v8.6 and Above

ERROR_CODE

0x8075

0x8076

0x8077

0x8085

0x8086

Exit

Code

Exit

Message

Possible Cause Possible Solution

<FlashROM row number>.

Unstable VCC

Unstable VCC_OSC (Fusion only)

Unstable VCC_ROSC voltage level (SmartFusion only)

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

11 Failed to verify

Embedded

Flash

Memory

Block

(EFMB)

Device is programmed with a different design.

Unstable VCC

Unstable VCC_NVM/VCC_OSC

(Fusion only)

Unstable

VCC_ENVM/VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins.

The EFMB data was modified in your FPGA design after programming. This could have occurred during standalone verify.

The target EFMB is locked with

FlashLock when running ACTION

PROGRAM_NVM_ACTIVE_ARR

AY or

VERIFY_NVM_ACTIVE_ARRAY.

Verify the device is programmed with the correct data/design.

Measure JTAG pins, and noise or reflection.

Run DEVICE_INFO to confirm if the target EFMB block is locked with

FlashLock (pass key). If the target EFMB block is locked, then you must unlock it by erasing the security and then reprogramming with the desired security settings. After unlocking the target EFMB block attempt to rerun the target ACTION.

11 Failed to verify system init and boot clients

Device is programmed with a different design.

Unstable VCC

Unstable VCC_NVM/VCC_OSC

(Fusion only)

Unstable

VCC_ENVM/VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins.

The EFMB data was modified in your FPGA design after programming. This could have occurred during standalone verify.

Verify the device is programmed with the correct data/design.

Measure JTAG pins, and noise or reflection.

Run DEVICE_INFO to confirm if the target EFMB block is locked with

FlashLock (pass key). If the target EFMB block is locked, then you must unlock it by erasing the security and then reprogramming with the desired security

FlashPro User's Guide 201

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

ERROR_CODE

0x8072

0x8073

0x8074

0x8083

0x8084

0x8014

0x8015

0x805A

0x805C

Exit

Code

Exit

Message

Possible Cause Possible Solution

The target EFMB is locked with

FlashLock when running ACTION

PROGRAM_NVM_ACTIVE_ARR

AY or

VERIFY_NVM_ACTIVE_ARRAY. settings. After unlocking the target EFMB block attempt to rerun the target ACTION.

11 Failed to verify

Embedded

Flash

Memory

Block

(EFMB)

Programming file generated with an older version of software

Generate STAPL file with the latest version of Designer/FlashPro; use the latest version of FlashPro software

Try again at a slower TCK

Contact Microsemi Technical Support

11 Failed to verify system init and boot clients

Programming file generated with an older version of software

Generate STAPL file with the latest version of Designer/FlashPro; use the latest version of FlashPro software

Try again at a slower TCK

Workaround: Disable optional procedure

Contact Microsemi Technical Support

11 Failed to verify calibration data

Unstable VCC

Unstable VCC_NVM/VCC_OSC

(Fusion only)

Unstable

VCC_ENVM/VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

Try reprogramming.

Workaround: Disable optional procedure

CHECK_AND_BACKUP_CALIB

11 Verify 0 failed at row

<row number> .

Verify 1 failed at row

Device is programmed with a different design

Unstable VPUMP voltage level.

Unstable VCC

Unstable VCC_OSC (Fusion only)

Unstable VCC_ROSC voltage level (SmartFusion only)

Run VERIFY_DEVICE_INFO to verify the device is programmed with the correct data/design.

Monitor VJTAG during programming;

202 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

SmartFusion, IGLOO, ProASIC3 and Fusion Device Exit Codes for Software v8.6 and Above

ERROR_CODE

0x8063

0x8068

0x805F

0x8065

0x8066

Exit

Code

Exit

Message

14 Failed to program

Silicon

Signature.

Failed to program security lock settings.

Possible Cause

Signal integrity issues on JTAG pins

Signal integrity issues on JTAG pins.

Possible Solution measure JTAG signals for noise or reflection.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

-18 Failed to authenticate the encrypted data.

Incorrect AES key.

Signal integrity issues on JTAG pins.

Generate a programming file with the correct AES key.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

-20 Failed to verify

FlashROM at row

<FlashROM row number>.

Programming file generated with an older version of software

Device is programmed with a different design.

Unstable VPUMP voltage level.

Unstable VCC

Unstable VCC_OSC (Fusion only)

Unstable VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins.

Generate STAPL file with the latest version of Designer/FlashPro; use the latest version of FlashPro software.

Program with the correct data/design.

Measure JTAG pins and noise or reflection.

-22 Failed to program pass key.

Unstable VPUMP voltage level.

Unstable VCC

Unstable VCC_OSC (Fusion only)

Unstable VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

-23 Failed to program

AES key.

Unstable VPUMP voltage level.

Unstable VCC

Monitor related power supplies that cause the issue during programming; check for transients outside of Microsemi specifications. See your device datasheet

FlashPro User's Guide 203

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

ERROR_CODE

0x8055

0x8056

0x802A

0x8025

0x802B

0x802D

0x8024

0x8026

Exit

Code

Exit

Message

Possible Cause Possible Solution

-24 Failed to program

UROW.

Unstable VCC_OSC (Fusion only)

Unstable VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins. for more information on transient specifications.

Measure JTAG pins and noise or reflection.

Unstable VPUMP voltage level.

Unstable VCC

Unstable VCC_OSC (Fusion only)

Unstable VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

Make sure you mounted 0.01

µF and

0.33

µF caps on Vpump (close to the pin).

-27 FlashROM

Write/Erase is protected by the passkey.

A valid passkey needs to be provided.

File contains no passkey and device is secured with a passkey.

Passkey in the file does not match device.

Provide a programming file with a passkey that matches the passkey programmed into the device.

-28 FPGA Array

Write/Erase is protected by the passkey.

A valid pass key needs to be provided.

File contains no passkey and device is secured with a passkey.

Passkey in the file does not match device.

Provide a programming file with a passkey that matches the passkey programmed into the device.

-29 FlashROM

Read is protected by passkey.

A valid passkey needs to be provided.

File contains no passkey and device is secured with a passkey.

Passkey in the file does not match device.

Provide a programming file with a pass key that matches the passkey programmed into the device

-30 FPGA Array verification is protected by a passkey.

A valid

File contains no passkey and device is secured with a passkey.

Passkey in the file does not match device.

Provide a programming file with a passkey that matches the passkey programmed into the device.

204 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

SmartFusion, IGLOO, ProASIC3 and Fusion Device Exit Codes for Software v8.6 and Above

ERROR_CODE

0x804B

0x8001

0x8007

0x8000

0x8020

0x8022

0x8028

0x802C

0x802F

0x801F

0x804A

0x802E

0x8030

Exit

Code

Exit

Message passkey needs to be provided.

-31 Failed to verify AES key.

Possible Cause Possible Solution

AES key in the file does not match the device.

Unstable VCC

Unstable VCC_OSC (Fusion only)

Unstable VCC_ROSC voltage level (SmartFusion only)

Unstable JTAG/VPUMP voltage level.

Provide a programming file with an AES key that matches the AES key programmed into the device.

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

-31 Failed to verify AES key.

Programming file generated with an older version of software

Generate STAPL file with the latest version of Designer/FlashPro; use the latest version of FlashPro software.

Try again at a slower TCK

Contact Microsemi Technical Support

-33 FPGA Array encryption is enforced. A programmin g file with encrypted

FPGA array data needs to be provided.

File contains unencrypted array data, but device contains AES key.

-34 FlashROM encryption is enforced. A programmin g file with encrypted

FlashROM data needs to be provided.

File contains unencrypted

FlashROM data, but the device contains an AES key.

-35 Failed to match pass key.

Pass key in file does not match pass key in device.

Provide a programming file with an encrypted FPGA Array data.

Provide a programming file with an encrypted FlashROM data.

Provide a programming file with a pass key that matches the pass key programmed into the device.

-36 FlashROM

Encryption is

File contains encrypted

FlashROM, but device encryption

Regenerate security programming file with proper AES key.

FlashPro User's Guide 205

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

ERROR_CODE

0x8021

0x8023

0x8027

0x8029

0x8067

0x806F

0x8070

0x8071

0x8081

0x8082

0x8089

Exit

Code

Exit

Message

Possible Cause not enforced.

Cannot is not enforced for FlashROM guarantee valid AES key present in target device.

Unable to proceed with

Encrypted

FlashROM programmin g.

Possible Solution

Program device security.

Retry programming FlashROM with encrypted programming file.

-37 FPGA Array

Encryption is not enforced.

Cannot guarantee valid AES

File contains encrypted FPGA

Array, but the device encryption is not enforced for FPGA Array. key present in target device.

Unable to proceed with

Encrypted

FPGA Array verification.

Regenerate security programming file with proper AES key.

Program device security.

Retry programming FPGA Array with encrypted programming file.

-38 Failed to program pass key.

-39 ERROR: 2 or more errors found on this page

Unstable VPUMP voltage level.

Unstable VCC

Unstable VCC_OSC (Fusion only)

Unstable VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins.

Bad device.

Measure JTAG pins and noise or reflection.

Unstable VCC_NVM/VCC_OSC voltage (Fusion only)

Unstable

VCC_ENVM/VCC_ROSC

(SmartFusion only)

NVM reset signal is floating in user design

Bias NVM reset to a logic state in user design.

206 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

SmartFusion, IGLOO, ProASIC3 and Fusion Device Exit Codes for Software v8.6 and Above

ERROR_CODE

0x8010

0x8013

0x8078

0x8079

0x807A

0x8087

0x8088

0x8002

0x8003

0x8093

0x8004

0x8049

0x8054

0x8033

0x8038

Exit

Code

Exit

Message

Possible Cause Possible Solution

2 or more ECC errors found when reading the eNVM

Try reprogramming.

-39 ERROR: 2 or more errors found on this page.

2 or more ECC errors found when reading the master calibration data

The master calibration data has been corrupted. Try restoring master calibration from backup, if it exists, by running RECOVER_CALIB.

CHECK_AND_BACKUP_CALIB

-39 ERROR: 2 or more errors found on this page.

2 or more ECC errors found when verifying the backup calibration

Rerun action to attempt to write backup calibration again.

Workaround: Disable optional procedure

CHECK_AND_BACKUP_CALIB

-40 Embedded

Flash

Memory

Block MAC

Failure.

-42 Failed to verify security settings.

Data in the file is encrypted with a different AES key than the device.

Verify the programming file is generated from the latest version of

Designer/FlashPro.

File security settings do not match device.

Provide a programming file with security setting that match the security settings programmed into the device.

-42 Failed to verify eNVM/EFMB client JTAG protection settings

Device eNVM/EFMB client JTAG protection settings are not programmed or are programmed with different settings

Verify the device is programmed with the correct eNVM/EFMB client JTAG protection settings

-43 Failed to verify design information.

File checksum and design name do not match the device.

Verify the device is programmed with the correct data and design.

-44 Failed to verify AES key.

The AES key in the file does not match the AES key in the device.

File does not contain an AES key and the device is secured with an

AES key.

Provide a programming file with an AES key that matches the AES key programmed into the device.

-45 Device package does not match the programmin g file.

Programming file was generated with an older version of software

Generate STAPL file with the latest version of Designer/FlashPro; use the latest version of FlashPro software.

-46 Embedded

Flash

File contains no pass key or incorrect pass key but EFMB read

Provide a programming file with the correct pass key.

FlashPro User's Guide 207

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

ERROR_CODE

0x803D

0x8042

0x8045

0x8046

0x8047

0x8048

0x8034

0x8039

0x803E

0x8043

0x8032

0x8037

0x803C

0x8041

0x8031

0x8036

0x803B

0x8040

Exit

Code

Exit

Message

Possible Cause

Memory

Block X

Read is protected by pass key. A valid pass key needs to be provided. is secured with a pass key.

Possible Solution

-46 Embedded

Flash

Memory

Block

(EFMB) block X

Read is not protected by pass key.

EFMB content is not secure after encrypted programmin g.

Unable to proceed with encrypted

NVM programmin g.

File contains encrypted EFMB for block X but the device encryption is not enforced for EFMB block X.

Regenerate security programming file with the proper AES key.

Program device security. Retry programming with EFMB block X with encrypted programming file.

-47 Embedded

Flash

Memory

Block

(EFMB) block X encryption is enforced. A programmin g file with encrypted

EFMB data needs to be provided.

The programming EFMB data is not encrypted, but the device contains an AES key with encryption enforced.

-48 Embedded

Flash

Memory

Block

(EFMB) block X

File contains no pass key or incorrect pass key, but device is secured with a pass key.

Provide a programming file with encrypted EFMB data.

Provide a programming file with a passkey that matches the passkey programmed into the device.

208 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

SmartFusion, IGLOO, ProASIC3 and Fusion Device Exit Codes for Software v8.6 and Above

ERROR_CODE

0x8035

0x803A

0x803F

0x8044

0x801A

8x804E

0x804F

Exit

Code

Exit

Message

Write is protected by pass key.

A valid pass key needs to be provided.

Possible Cause Possible Solution

-49 Embedded

Flash

Memory

Block

(EFMB) block X

Encryption is not enforced.

Cannot guarantee valid AES key present in target device.

Unable to proceed with

Encrypted

EFMB programmin g.

File contains encrypted EFMB for block X, but the device encryption is not enforced for EFMB block X.

Regenerate security programming file with proper AES key.

Program device security. Retry programming EFMB block X with encrypted programming file.

No backup calibration copy has been made or the backup copy has been corrupted

If master copy is still intact, rerun Action to create backup calibration copy.

Workaround: Disable optional procedure

CHECK_AND_BACKUP_CALIB

-50 No backup calibration data found or backup calibration data has been corrupted

-51 Failed to access

Embedded

Flash

Memory.

(AFS600 only)

This version of the silicon does not support programming of the

Embedded Flash Memory Block while the FPGA Array is active.

If programming the EFMB while the

FPGA is active is not required, then use actions PROGRAM_NVM or

VERIFY_NVM. Otherwise, use latest revision of silicon.

-52 Failed to access

Embedded

Flash

Memory.

(AFS1500 only)

This version of the silicon does not support programming of the

Embedded Flash Memory Block while the FPGA Array is active.

If programming the EFMB while the

FPGA is active is not required, then use actions PROGRAM_NVM or

VERIFY_NVM. Otherwise, use latest revision of silicon.

FlashPro User's Guide 209

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

ERROR_CODE

0x8050

0x8051

0x808A

0x8094

0x808B

Exit

Code

Exit

Message

-53 Failed to access

Embedded

Flash

Memory.

(AFS1500 only)

-54 Failed to access

Embedded

Flash

Memory.

Possible Cause Possible Solution

This version of the silicon does not support programming block 3 of the EFMBs while the FPGA

Array is active.

If programming the EFMB while the

FPGA is active is not required, then use actions PROGRAM_NVM or

VERIFY_NVM. Otherwise, use EFMB blocks 0, 1, or 2, but do not use block 3.

FPGA Array is accessing the target EFMB block while attempting programming.

NVM reset signal is stuck in design.

Unstable VCC

MSS Clock is disabled during programming.

MSS Clock is not properly routed to the correct pin.

If programming the EFMB while the

FPGA is active is not required, then use actions PROGRAM_NVM or

VERIFY_NVM. Otherwise, check the

FPGA design or use a different EFMB block that is not being accessed. Check if target EFMB block logic is tied to reset.

Verify that the NVM reset signal in the design is not stuck.

Verify the MSS clock is enabled during programming.

If the MSS clock is defined as an external

I/O, then verify that it is properly routed to the correct pin.

-55 Failed to read

Embedded

Flash

Memory

Block

(EFMB)

-55 Failed to read

Embedded

Flash

Memory

Block

(EFMB)

Programming file generated with an older version of software

Generate STAPL file with the latest version of Designer/FlashPro; use the latest version of FlashPro software

Try again at a slower TCK

Inspect device using Device Debug

Contact Microsemi Technical Support

Unstable VPUMP voltage level.

Unstable VCC

Unstable VCC_OSC (Fusion only)

Unstable VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins

Monitor VJTAG during programming; measure JTAG signals for noise or reflection.

210 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

SmartFusion, IGLOO, ProASIC3 and Fusion Device Exit Codes for pre-v8.6 Software

ERROR_CODE

0x808C

0x8011

0x8012

0x808D

0x8092

Exit

Code

Exit

Message

-55 Failed to read

Embedded

Flash

Memory

Block

(EFMB)

-56 Failed to read calibration data

Possible Cause

Internal errror

Unstable VCC

Unstable VCC_NVM/VCC_OSC

(Fusion only)

Unstable

VCC_ENVM/VCC_ROSC voltage level (SmartFusion only)

Signal integrity issues on JTAG pins

Possible Solution

Contact Microsemi Technical Support

Try reprogramming.

Workaround: Disable optional procedure

CHECK_AND_BACKUP_CALIB

Monitor related power supplies that cause the issue during programming; check for transients outside of

Microsemi specifications. See your device datasheet for more information on transient specifications.

Measure

JTAG voltages, noise, and reflection.

Try reprogramming.

Workaround: Disable optional backup procedure

CHECK_BACKUP_CA

LIB

-57 eNVM/EFMB is protected by a Pass

Key; you must provide a valid Pass

Key

File contains no Pass Key and device is secured with a Pass Key

Pass Key in the file does not match device

Provide a programming file with a Pass

Key that matches the Pass Key programmed into the device

SmartFusion, IGLOO, ProASIC3 and Fusion Device Exit Codes for pre-v8.6 Software

The table below lists exit codes for SmartFusion, IGLOO, ProASIC3 and Fusion devices in pre-v8.6 software

only. This includes v8.5 SP2, v8.5 SP1, v8.5, etc. See the Device Exit Codes for Software v8.6 and Above

help topic for exit codes for older versions.

Note: Exit codes with positive integers are reserved for current and future standard EXIT codes of the STAPL standard. Exit codes with negative integers are reserved for vendor-specific EXIT codes.

FlashPro User's Guide 211

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Exit Message

Table 26 · Exit Codes for SmartFusion, IGLOO, ProASIC3 and Fusion Family Devices in pre-v8.6

Software

Possible Cause Possible Solution Exit

Code

Passed (no error).

A physical chain does not match the expected set up from the STAPL file.

Also known as

Checking Chain

Error.

Physical chain configuration has been altered. Something has become disconnected in the chain.

The specific IR length of non-

Microsemi devices may be incorrect.

The order of the specified chain may be incorrect.

Failed to enter programming mode.

Unstable VPUMP voltage level.

Signal integrity issues on JTAG pins.

Older software or programming file used.

Monitor VPUMP voltage during programming

Measure JTAG voltages, noise, and reflection.

Generate STAPL file with the latest version of

Designer/FlashPro.

Use latest version of

FlashPro software.

Failed to verify

IDCODE. Signal integrity issues on JTAG pins.

Measure JTAG pins, noise and reflection.

8 Failed Erase

Operation.

Signal integrity issues on JTAG pins.

Failed to program

FPGA array at row

", rowNumber,"."

Failed to enable

FPGA Array.

Failed to program

FlashROM.

Signal integrity issues on JTAG pins.

Monitor VPUMP voltage during programming.

Measure JTAG voltages, noise, and reflection.

Monitor VPUMP voltage during programming.

Measure JTAG voltages, noise, or reflection.

Monitor VPUMP voltage during programming.

Measure JTAG voltages, noise, or reflection.

Monitor VPUMP voltage during programming.

Measure JTAG voltages, noise, and reflection.

212 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

SmartFusion, IGLOO, ProASIC3 and Fusion Device Exit Codes for pre-v8.6 Software

Exit

Code

Exit Message

FlashROM at row",from rowNumber-1.

Possible Cause

Verify 0 failed at row",rowNumber,"." different design.

Verify 1 failed at

Device is programmed with a row",rowNumber,"." Signal integrity issues on JTAG

Failed to verify pins.

Failed to program

Silicon Signature.

Failed to program security lock settings.

Signal integrity issues on JTAG pins.

-18 Failed to authenticate the encrypted data.

Incorrect AES key.

Signal integrity issues on JTAG pins.

Possible Solution

-20

-22

-23 Failed to program

AES key.

Unstable VPUMP voltage level.

Signal integrity issues on JTAG pins.

-24

Failed to verify

FlashROM at row

FRomRowNumber-

Failed to program pass key.

Failed to program

UROW.

Device is programmed with a different design.

Signal integrity issues on JTAG pins.

Unstable VPUMP voltage level.

Signal integrity issues on JTAG pins.

Unstable VPUMP voltage level.

Signal integrity issues on JTAG pins.

Run

VERIFY_DEVICE_INFO to verify the device is programmed with the correct data/design.

Monitor VPUMP voltage during programming.

Measure JTAG voltages, noise and reflection .

Monitor VPUMP voltage during programming.

Measure JTAG voltages, noise, and reflection.

Generate a programming file with the correct AES key.

Measure JTAG voltages, noise and reflection

Program with the correct data/design.

Monitor VPUMP level during programming.

Measure JTAG pins and noise or reflection.

Monitor VPUMP voltage during programming.

Measure JTAG voltages, noise, and reflection.

Monitor VPUMP voltage during programming.

Measure JTAG pins and noise or reflection.

Monitor VPUMP voltage during programming.

Measure JTAG voltages, noise, and reflection.

Make sure you mounted

FlashPro User's Guide 213

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Exit

Code

Exit Message Possible Cause Possible Solution

-25 Failed to enter programming mode

Signal integrity issues on JTAG pins.

0.01ìF and 0.33ìF caps on Vpump (close to the pin).

Measure JTAG voltages, noise, and reflection.

-26 Failed to enter programming mode

-27 FlashROM

Write/Erase is protected by the passkey.

A valid passkey needs to be provided.

-28 FPGA Array

Write/Erase is protected by the passkey.

A valid pass key needs to be provided.

Signal integrity issues on JTAG pins.

File contains no passkey and device is secured with a passkey.

Passkey in the file does not match device.

Provide a programming file with a passkey that matches the passkey programmed into the device.

File contains no passkey and device is secured with a passkey.

Passkey in the file does not match device.

Measure JTAG voltages, noise, and reflection.

Provide a programming file with a passkey that matches the passkey programmed into the device.

-29 FlashROM Read is protected by passkey.

A valid passkey needs to be provided.

File contains no passkey and device is secured with a passkey.

Passkey in the file does not match device.

Provide a programming file with a pass key that matches the passkey programmed into the device

-30 FPGA Array verification is protected by a passkey.

A valid passkey needs to be provided.

-31 Failed to verify

AES key.

File contains no passkey and device is secured with a passkey.

Passkey in the file does not match device.

Provide a programming file with a passkey that matches the passkey programmed into the device.

AES key in the file does not match the device.

Unstable JTAG/VPUMP voltage level.

Provide a programming file with an AES key that matches the AES key programmed into the device.

Monitor

VPUMP/VJTAG voltage during programming.

Measure JTAG voltages, noise, and

214 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

SmartFusion, IGLOO, ProASIC3 and Fusion Device Exit Codes for pre-v8.6 Software

Exit

Code

Exit Message Possible Cause Possible Solution

-32 Failed to verify

IDCODE.

Target is an M7 device reflection.

File is not for M7, but target device is an M7.

Signal integrity issues on JTAG pins.

Check that the target device is M7 enabled.

Make sure programming file generated is for M7 enabled device.

Measure JTAG pins , noise, and reflection.

-32 Failed to verify

IDCODE.

Target is an M1 device

File is not for M1, but target device is an M1 device.

Signal integrity issues on JTAG pins.

Check that the target device is M1 enabled.

Make sure programming file generated is for M1 enabled device.

Measure JTAG pins, noise, and reflection.

-32

Failed to verify

IDCODE.

Core enabled device detected

Failed to verify

IDCODE.

The target is not an M7 device

-32 Failed to verify

IDCODE.

The target is not an

M1 device

File is not for target device.

Signal integrity issues on JTAG pins

Check the target device.

Make sure programming file generated for target device.

Measure JTAG voltages, noise, and reflection.

File is for M7, but target device is not M7.

Signal integrity issues on JTAG pins.

File is for M1, but target device is not an M1 device.

Signal integrity issues on JTAG pins.

Check that the target device is not M7 enabled.

Make sure programming file generated is for non

M7 enabled device.

Measure JTAG voltages, noise, and reflection.

Check that the target device is not M1 enabled.

Make sure programming file generated is for non M1 enabled device.

Measure JTAG voltages, noise and reflection.

-33 FPGA Array encryption is

File contains unencrypted array data, but device contains AES key.

Provide a programming file with an encrypted

FlashPro User's Guide 215

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Exit

Code

Exit Message enforced. A programming file with encrypted

FPGA array data needs to be provided.

-34 FlashROM encryption is enforced. A programming file with encrypted

FlashROM data needs to be provided.

Possible Cause

File contains unencrypted

FlashROM data, but the device contains an AES key.

Possible Solution

FPGA Array data.

Provide a programming file with an encrypted

FlashROM data.

-35 Failed to match pass key.

Pass key in file does not match pass key in device.

-37 FPGA Array

Encryption is not enforced.

Cannot guarantee valid AES key present in target device.

Unable to proceed with Encrypted

FPGA Array verification.

File contains encrypted FPGA

Array, but the device encryption is not enforced for FPGA Array.

Provide a programming file with a pass key that matches the pass key programmed into the device.

-36 FlashROM

Encryption is not enforced.

Cannot guarantee valid AES key present in target device.

Unable to proceed with Encrypted

FlashROM programming.

File contains encrypted FlashROM, but device encryption is not enforced for FlashROM

Regenerate security programming file with proper AES key.

Program device security.

Retry programming

FlashROM with encrypted programming file.

Regenerate security programming file with proper AES key.

Program device security.

Retry programming

FPGA Array with encrypted programming file.

-38 Failed to program pass key.

Unstable VPUMP voltage level.

Signal integrity issues on JTAG pins.

Bad device.

Monitor VPUMP voltage during programming.

Measure JTAG pins and noise or reflection.

216 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

SmartFusion, IGLOO, ProASIC3 and Fusion Device Exit Codes for pre-v8.6 Software

Exit

Code

Exit Message Possible Cause Possible Solution

-39 Failed to verify

-40

Embedded Flash

Memory Block

(EFMB).

Embedded Flash

Memory Block

MAC Failure.

-41 Error programming

Embedded Flash

Memory Block.

(EFMB)

Device is programmed with a different design.

Signal integrity issues on JTAG pins.

The EFMB data was modified through user FPGA design after programming; this could occur during standalone verify.

Verify the device is programmed with the correct data/design.

Monitor VPUMP voltage during programming.

Measure JTAG pins and noise or reflection.

The target EFMB block is locked with FlashLock when running

Run DEVICE_INFO to confirm if the target

ACTION

PROGRAM_NVM_ACTIVE_ARRAY or VERIFY_NVM_ACTIVE_ARRAY.

EFMB block is locked with FlashLock (pass key). If the target EFMB block is locked, then you must unlock it by erasing the security and then reprogramming with the desired security settings. After unlocking the target EFMB block attempt to rerun the target ACTION.

Data in the file is encrypted with a different AES key than the device.

Signal integrity issues on JTAG pins.

Verify the programming file is generated from the latest version of

Designer/FlashPro.

Measure JTAG pins and noise or reflection.

-42 Failed to verify security settings.

File security settings do not match device.

Provide a programming file with security setting that match the security settings programmed into the device.

-43 Failed to verify design information.

File checksum and design name do not match the device.

Verify the device is programmed with the correct data and design.

-44 Failed to verify

AES key.

-45 Device package does not match the programming file.

The AES key in the file does not match the AES key in the device.

File does not contain an AES key and the device is secured with an

AES key.

Provide a programming file with an AES key that matches the AES key programmed into the device.

FlashPro User's Guide 217

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Exit

Code

Exit Message Possible Cause Possible Solution

-46 Embedded Flash

Memory Block X

Read is protected by pass key. A valid pass key needs to be provided.

File contains no pass key or incorrect pass key but EFMB read is secured with a pass key.

Provide a programming file with the correct pass key.

-47 Embedded Flash

Memory Block, block X encryption is enforced. A programming file with encrypted

EFMB data needs to be provided.

The programming EFMB data is not encrypted, but the device contains an AES key with encryption enforced.

Provide a programming file with encrypted

EFMB data.

-48 Embedded Flash

Memory Block

(EFMB) block X

Write is protected by pass key.

A valid pass key needs to be provided.

File contains no pass key or incorrect pass key, but device is secured with a pass key.

Provide a programming file with a passkey that matches the passkey programmed into the device.

-49 Embedded Flash

Memory Block

(EFMB) block X

Encryption is not enforced.

Cannot guarantee valid AES key present in target device.

Unable to proceed with Encrypted

EFMB programming.

File contains encrypted EFMB for block X, but the device encryption is not enforced for EFMB block X.

Regenerate security programming file with proper AES key.

Program device security. Retry programming EFMB block X with encrypted programming file.

-51 Failed to access

Embedded Flash

Memory.

(AFS600 only)

-52 Failed to access

Embedded Flash

This version of the silicon does not support programming of the

Embedded Flash Memory Block while the FPGA Array is active.

If programming the

EFMB while the FPGA is active is not required, then use actions

PROGRAM_NVM or

VERIFY_NVM.

Otherwise, use latest revision of silicon.

This version of the silicon does not support programming of the

If programming the

EFMB while the FPGA

218 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

ProASICPLUS and ProASIC Exit Codes

Exit

Code

Exit Message Possible Cause Possible Solution

Memory.

(AFS1500 only)

-53 Failed to access

Embedded Flash

Memory.

(AFS1500 only)

-54 Failed to access

Embedded Flash

Memory.

Embedded Flash Memory Block while the FPGA Array is active. is active is not required, then use actions

PROGRAM_NVM or

VERIFY_NVM.

Otherwise, use latest revision of silicon.

This version of the silicon does not support programming block 3 of the

EFMBs while the FPGA Array is active.

If programming the

EFMB while the FPGA is active is not required, then use actions

PROGRAM_NVM or

VERIFY_NVM.

Otherwise, use EFMB blocks 0, 1, or 2, but do not use block 3.

FPGA Array is accessing the target

EFMB block while attempting programming.

NVM reset signal is stuck in design.

If programming the

EFMB while the FPGA is active is not required, then use actions

PROGRAM_NVM or

VERIFY_NVM.

Otherwise, check the

FPGA design or use a different EFMB block that is not being accessed. Check if target EFMB block logic is tied to reset.

Verify that the NVM reset signal in the design is not stuck.

ProASIC

PLUS

and ProASIC Exit Codes

The table below lists the exit codes for ProASIC

PLUS

and ProASIC family devices.

Table 27 · ProASIC PLUS and ProASIC Family Devices Exit Codes

Exit Code Exit Message Possible Cause Possible Solution

This message means passed.

This does not indicate an error.

A physical chain does not match the expected set up from the STAPL file.

Physical chain configuration has been altered. Something has become disconnected in the chain.

FlashPro User's Guide 219

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Exit Code Exit Message

Also known as

Checking Chain

Error.

Possible Cause

The specific IR length of non-Microsemi devices may be incorrect.

The order of the specified chain may be incorrect.

Possible Solution

There is a reading device ID failure.

The device either does not have a valid device

ID or the data cannot be read correctly.

Check the device ID.

This occurs when using ProASIC

PLUS devices.

Connect was set up for a

ProASIC device and the device is actually

ProASIC

PLUS

Set up for a

ProASIC

PLUS

device.

Programming set up problem. Also known as Entering

ISP Failure.

The A500K device senses the VDDL power supply as being on.

Power the VDDL down during programming. Check the device has the correct voltages on

VDDP, VDDL, VPP, and VPN.

The IDCODE of the target device does not match the expected value in the STAPL file.

This is a JEDEC standard message.

The device targeted in the STAPL file does not match the device being programmed.

User selected wrong device.

Device TRST pin is grounded.

Noise or reflections on one or more of the JTAG pins caused by the IR

Bits reading it back incorrectly.

Choose the correct

STAPL file and select the correct device.

Measure JTAG pins and noise or reflection. TRST should be floating or tied high.

Cut down the extra length of ground connection.

Unknown algorithm: alg=x, prev=x Invalid data read from device

This occurs with current

STAPL files when the revision written into the factory row is not rev 1 for ProASICPLUS or rev

2 for ProASIC devices.

The STAPL files from last year may "exit 7" with newer devices or the older revision may cause this failure if the STAPL file used is from latest version.

It can occur if you are using Engineering

Sample parts that are no longer supported, such

Re-generate STAPL file from Designer 6.1

SP1.

Replace A500K ES parts with commercial parts.

Double check VPP and VPN connections.

Make sure VPP and

VPN have correct bypass caps.

Make sure that your power supply can deliver the correct current during programming.

220 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

ProASICPLUS and ProASIC Exit Codes

Exit Code Exit Message Possible Cause as ProASIC Engineering

Sample parts.

This error can also occur if the programmer has trouble reading the factory row due to signal noise, crosstalk, or reflections on the JTAG signal and clock lines.

It can occur if you program an -F

ProASICPLUS device with an old STAPL file.

This error occurs if you connected VPP and VPN the wrong way.

It occurs if there are no bypass Caps on VPP

VPN, which damaged the device.

This error may occur if your power supply cannot source the correct current for programming.

Possible Solution

FPGA failed during the erase operation.

The device is secured, and the corresponding

STAPL file is not loaded.

The device has been permanently secured and cannot be unlocked.

Load the correct

STAPL file.

FPGA failed verify The device is secured and the corresponding

STAPL file is not loaded.

You used the Libero IDE software v2.3 or earlier or the Designer R1-2003 software or earlier to generate the STAPL file.

VPN caps were soldered in the wrong polarity.

Load the correct

STAPL file.

Use later software versions —at least

Libero v2.3 SP1 and

Designer R1-2003

SP1.

Double-check the

VPN bypass caps polarity.

Security is enabled.

The device is secured and the wrong key/STAPL file was entered.

The device is damaged.

The verification was interrupted and therefore fails, causing the software to think the device is secure.

FlashPro User's Guide 221

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

-54

-80

-90

-91

Exit Code Exit Message Possible Cause Possible Solution

Program security failure.

This is a factory

Calibration Data

CRC error.

During program, erase, or verify, you must read back Calibration Data from the FPGA. The data contains a CRC. You use the CRC to ensure the data is not corrupted/wrong.

Device is damaged.

Noise on the FTAL signals causes the programmer to read back wrong data.

The device is secured and the wrong key or

STAPL file was entered.

The device is damaged.

Load the correct

STAPL file.

The device has been secured.

Write-security is enabled.

Failed to access

Embedded Flash

Memory

Analog power supplies

(Vcc15A, Vcc33A,

GNDAQ and GNDA) are not connected.

Connect the analog power supplies

(Vcc15A, Vcc33A,

GNDAQ and GNDA)

Error code results from STAPL files for A500K devices.

An internal calibration

(based on DDP and

VPP) failed.

Check voltages on the device pins.

Check voltages on the VDDP and VPP pins.

Unexpected RCK detected.

Noise on the RCK signal. Disconnect the RCK

You connected a CLK source to the RCK signal. and make sure TCK has a clean signal.

The polarized bypass capacitors on VPP or

VPN are reversed-biased and are affecting the programmer’s VPP or

VPN output voltage. This causes programming to fail. Several FlashPros are programming at the same time and are too close to each other.

Programmer not properly installed by Admin.

Separate FlashPros away from each other while they are programming Internal

ISP.

Connect programmer as an Admin in

FlashPro.

Device is damaged. Replace the device. Calibration data parity error.

Null Several FlashPros are programming at the

222 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

ProASICPLUS and ProASIC Exit Codes

Exit Code Exit Message

Cable to target is not connected properly.

Possible Cause same time and are too close to each other.

FlashPro connects to PC parallel port through a dongle key.

Data length mismatch when performing

DRSCAN on STAPL file.

Possible Solution

When the Analyze command is executed, the FlashPro looks for target devices. If the cable connection is wrong, FlashPro assumes that nothing is connected at all.

Confirm the connection between the header to the device. If the board supplies the power to the device, make sure the voltage level is correct.

Chain integrity test failed: xx

The connection between the FlashPro programmer and the device is broken.

The programmer cable might not be securely inserted into the header.

The header is not connected to the JTAG pins of the FPGA correctly.

The configuration setting

(ProASIC/ProASICPLUS) does not match the target device.

Noise or reflections on the JTAG pins has caused communication between the programmer and the device to fail.

A dongle is plugged in between the PC parallel port and the FlashPro parallel port cable.

Secure the connections.

Check the JTAG pins for signal activity.

Check for broken

TDO, TMS, and TCK pins.

After checking all type of connections if the failure exists, you may need to replace the first device (the devices closest to the

TDO of the programming header) in the chain.

Remove the dongle.

Could not connect to programmer on port lp1 or parallel port device does not support IEEE-

1284 negotiation protocol

The remote device does not respond to the negotiation protocol, for a variety of reasons.

Make sure the port is connected.

Make sure the connected device is a

FlashPro/Lite programmer.

Turn the programmer on.

Check parallel port setting in BIOS.

FlashPro User's Guide 223

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Exit Code Exit Message

External voltage detected on

Possible Cause Possible Solution

Make sure that there are no dongles in between the parallel port and the FlashPro connection.

Try another parallel cable, the parallel cable might be defective.

Check to see if the programmer is damaged.

Make sure the

FlashPro Lite has power. The FlashPro

Lite is powered from the target board through the Vdd pin of the programming header.

Make sure the Vdd pin is connected and the target board is powered up.

Secure the connection between the cable connector and the programming header.

Before you program any devices, you should run the selfdiagnostic test. The diagnostic software can be found on the

Microsemi web site. If the test fails, please contact Microsemi

Customer Technical

Support at [email protected] for credit and replacement.

Note: The Self-test is only available for

FlashPro, not

FlashPro Lite.

The voltage supply for the FPGA is driven by another source (board, external power-supply), but the user forgot to turn off the supply in the

Connect menu.

Set appropriate options in the

Connect menu.

224 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

ProASICPLUS and ProASIC Exit Codes

Exit Code Exit Message Possible Cause Possible Solution

VDPP

Disconnected.

There is no Vddp voltage supply to the FPGA.

You accidentally turned off the Vddp supply in the

Connect menu.

The Vddp supply on the board is not functioning.

Check the Vddp supply on the board for appropriate voltages and correct the Connect menu.

More than one unidentified device.

If you want to perform an operation on the

ProASIC device, the rest of the devices in the chain must be in bypass mode.

To put devices in bypass mode, select

Configuration >

Chain Parameter

(or click the Chain

Parameter button in the Single

STAPL

Configuration window), then set the Pre IR, Pre DR,

Post IR or Post

DR.

STAPL settings of Pre

IR, Pre DR, Post IR, and

Post DR do not match the chain configuration.

One or more of the devices in the chain is damaged and the ID

CODE cannot be read back.

Make sure you have set Pre IR, Pre DR,

Post IR, and Post DR to match the chain configuration. If you are still experiencing the failure, it is likely that the device's ID

CODE cannot be read and you need to replace the device.

Cannot find the programmer with

ID xxx

The programmer is removed from the PC.

Delete programmer

(or reconnect programmer) and select the Refresh

Programmer button.

See Connecting

Programmers for more information.

Fatal Error: Please check programmer set up.

Software cannot resolve the error encountered in the programmer.

Save the project file, restart the software, and power cycle the programmer.

External voltage xxx mV is detected on xxx.

You have specified the programmer to drive the xxx but external xxx is detected.

Deselect the xxx in the programmer

setting.

Executing action xxx failed.

The STAPL runtime failed.

FlashPro User's Guide 225

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Exit Code Exit Message

Executing action xxx with serial index/action xx failed.

Possible Cause

The STAPL runtime failed.

Possible Solution

No Vpump voltage source is detected.

Vpump short detected.

Select the Vpump in the Programmer setting. Make sure the external Vpump is properly turned on.

Use a different programmer. If the problem persists, check the board layout.

xxx Mhz TCK frequency in this

STAPL file is not supported by the

FlashPro Lite detected. It supports only 4

MHz TCK frequency.

xxx Mhz TCK frequency in this

STAPL file is not supported by the

FlashPro Lite

RevC detected. It supports only 1, 2 or 4 Mhz TCK frequency.

Check FlashPro Lite version being used.

Use FlashPro Lite

Rev C or modify the

STAPL file to 4 MHz.

Modify STAPL file to

1, 2, or 4 MHz.

Cannot find the serial Index/Action xxx in STAPL file.

Duplicated serial

Index/Action xxx was removed.

Mismatch between

STAPL file and the

Index/Action selection.

Mismatch between

STAPL file and the

Index/Action selection.

Make sure the

STAPL file was not overwritten. Save the project with updated serial/action selection.

Make sure the

STAPL file was not overwritten. Save the project with updated serial/action selection.

Using local backup copy xxx

Cannot find original copy. Check for available space on the disk.

Check that write permissions are

226 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

ProASICPLUS and ProASIC Exit Codes

Exit Code Exit Message Possible Cause Possible Solution enabled.

FlashPro cannot rename the programmer/device with an existing name.

Name is already in use. Create a new name.

FlashPro cannot rename the programmer/device with an invalid character.

Invalid character used in programmer/device name.

Do not use invalid characters.

Automatic check for updates.

FlashPro can check the Microsemi website to find if an updated version of the software is available. If you would like to have

FlashPro automatically check for software updates, choose Preferences from the File menu.

From the Updates tab, you can choose your automatic software update settings. You can also select Software

Updates from the

Help menu for updates to the

FlashPro software.

FlashPro parse error.

FlashPro software failed to parse the file.

FlashPro does not support STAPL files for xxx.

STAPL file not allowed. Use a STAPL file for your device that is supported by

FlashPro.

FlashPro User's Guide 227

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Electrical Parameters

DC Characteristics for FlashPro5/4/3/3X

Note: The target board must provide the VCC, VCCI, VPUMP, and VJTAG during programming. However, if there is only one ProASIC3 device on the target board, the FlashPro5/4/3/3X can provide the VPUMP power supply via the USB port.

The VJTAG signal is driven from the target/DUT board. The VJTAG pin is sensed by the FP4 to configure the internal input and output buffers to the same IO Voltage levels. The VJTAG pin is only an input pin to the programmer.

Table 28 · DC Characteristic for FlashPro5/4/3/3X

Description Symbol Min Max Unit

Input low voltage, TDO VIL -0.5 0.35*VJTAG V

Input high voltage, TDO

Input current, TDO

Input capacitance, TDO

VIH 0.65*VJTAG 3.6

+20 IIL, IIH -20

V mA pF

Output voltage, VPUMP, operating

VPP

Output current, VPUMP

VJTAG = 1.5V

IPP

Output low voltage, TCK, TMS,

TDI, 100µA load

VOL

Output low voltage, TCK, TMS,

TDI, 4mA load

VOL

Output high voltage, TCK, TMS,

TDI, 100µA load

Output high voltage, TCK, TMS,

TDI, 4mA load

VOH

Output current, TCK, TMS, TDI IOL,

IOH

VJTAG = 1.8V

Output low voltage, TCK, TMS,

TDI, 100µA load

VOL

Output low voltage, TCK, TMS,

TDI, 6mA load

VOL

+3.0

0.0

+3.6

250

0.2

V mA

0.30*VJTAG V

VJTAG-0.2 VJTAG

0.70*VJTAG VJTAG

-4

0.0

0.2

0.3

V mA

228 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Description Symbol Min Max

VJTAG-0.2 VJTAG Output high voltage, TCK, TMS,

TDI, 100µA load

VOH

Output high voltage, TCK, TMS,

TDI, 6mA load

VOH 1.25 VJTAG

-6 +6 Output current, TCK, TMS, TDI IOL,

IOH

VJTAG = 2.5V

Output low voltage, TCK, TMS,

TDI, 100µA load

VOL 0.0 0.2

0.0 0.6 Output low voltage, TCK, TMS,

TDI, 8mA load

VOL

Output high voltage, TCK, TMS,

TDI, 100µA load

VOH

Output high voltage, TCK, TMS,

TDI, 8mA load

VOH

Output current, TCK, TMS, TDI IOL,

IOH

VJTAG = 3.3V

VJTAG-0.2 VJTAG

1.8

-8

VJTAG

Output low voltage, TCK, TMS,

TDI, 100µA load

VOL

Output low voltage, TCK, TMS,

TDI, 8mA load

VOL

Output high voltage, TCK, TMS,

TDI, 100µA load

VOH

Output high voltage, TCK, TMS,

TDI, 8mA load

VOH

Output current, TCK, TMS, TDI IOL,

IOH

0.0

0.6

0.2

VJTAG-0.2 VJTAG

2.4

-8

VJTAG

V mA

Unit

DC Characteristics for FlashPro Lite

Table 29 · DC Characteristic for FlashPro Lite

Description Symbol Min Max Unit

Input low voltage, TDO

Input high voltage, TDO

VIL

VIH

-0.5 0.7

1.7 5.0

DC Characteristics for FlashPro Lite

FlashPro User's Guide 229

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Description

Input current, TDO

Input capacitance, TDO

Input voltage, VDD, operating (see note)

Input voltage, VDD, power off

Input current, VDD

Output voltage, VPP, operating

Output voltage, VPN, operating

Symbol Min Max Unit

IIL, IIH -10 +10 uA

40 pF

IVDD

VPP

VPN

+2.3 +3.5

-1.0 +1.0

500 mA

+15.9 +16.5 V

-13.8 -13.4 V

Output current, IPP

Output current, IPN

IPP

IPN

Output low voltage, TCK, TMS, TDI, 100uA load VOL

Output low voltage, TCK, TMS, TDI, 1mA load

Output low voltage, TCK, TMS, TDI, 2mA load

VOL

Output high voltage, TCK, TMS, TDI, 100uA load VOH

-15

0.0 0.2 V

0.0 0.5 V

0.0 0.8 V

2.1 2.5 V

Output high voltage, TCK, TMS, TDI, 1mA load

Output high voltage, TCK, TMS, TDI, 2mA load

VOH

1.9

1.6

2.5

Output current, TCK, TMS, TDI, nTRST IOL, IOH -2 +2 mA

Note: Up to 3.5 V can be supplied to the FlashPro Lite on the VDD pin. However, if the VDD supply for the

FlashPro is also connected to the APA VDD supply, the voltage for the VDD pin cannot exceed 2.7 V.

DC Characteristics for FlashPro

Table 30 · DC Characteristic for FlashPro

Description Symbol Min

Input low voltage, TDO

Input high voltage, TDO

VIL

VIH

-0.5

0.70 *

VDDP

Max

0.30 *

VDDP

5.5

Input current, TDO

Input voltage, VDDP, VDDL

Input voltage, VPP

Input voltage, VPN

IIL, IIH -10

-21.0

+10

5.25

21.0

Unit

V uA

230 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

DC Characteristics for FlashPro

Description

Input current, VDDP, VDDL, VPN, VP

Output voltage range, VDDP

Symbol

IVCC

VDDP 1.5

Min

5.0

3.3

Max Unit mA

Output voltage range, VPP

Output voltage range, VPN

VPP

VPN

15.0

-16.0

18.0

-12.0

Output voltage resolution / Acccuracy

Output current, IDDP

Output current, IDDL

IDDP

IDDL

-135

-2701

100 / ±50

+135

+135 mV mA mA

Output current, IPP

Output current, IPN

IPP

IPN

+270

1 mA mA -270

0.0 Output low voltage, TCK, TMS, TDI, OUT0, nTRST

VOL

Output high voltage, TCK, TMS, TDI, OUT0, nTRST

VOH 0.85 *

VDDP

0.4

+ 0.3

VDDP

Output current, TCK, TMS, TDI, OUT0, nTRST

IOL,

IOH

-12 +12 mA

Note (1): When power supply mode is set to ABI_GROUND.

* - If you want to power-up the device from the board power supply, clear the checkboxes for VDDL and VDDP.

VPP and VPN are required during programming only and are supplied by the FlashPro programmer.

(2) Microsemi does not have operating temperature information for the FlashPro programmer. FlashPro is intended to be used as lab or production equipment and not tested at extreme temperatures. All devices in the unit are commercial temp. FlashPro4 went through a burn-in cycle operating at 100C for 250 hours during quality testing. This involved repeatedly powering the programmers and then programming after the burn in; they are not actively programming during the burn in.

FlashPro User's Guide 231

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Electrical Specifications

FlashPro5

The FlashPro5 is a JTAG and a SPI based programmer for flash based Microsemi devices.

The FlashPro5 output is supplied via a connector to which a detachable 10-pin cable is fitted. The connector on the FlashPro5 unit is a 2x5, RA male Header connector, which is manufactured by AMP and has a manufacturer’s part number of 103310-1. This is a standard 2x5, 0.1 pitch connector which is keyed. Use the 10 pin right-angle header, AMP P/N 103310-1 (DigiKey P/N A26285-ND) for FlashPro4 and use the 10 pin straight header, AMP P/N 103308-1 (DigiKey P/N A26267-ND) for the straight version.

The signals on the pins of the FlashPro5 10-pin connector are shown in the figure below.

Figure 152 · FlashPro5 10-Pin Connector

Signal

VPUMP

GND

TCK/SCK

Note: All ground pins must be connected. The rectangular shape shows connections on the programmer itself. Arrows show current flow towards or from the rectangular programmer.

The table below shows a description of the signals.

Table 31 · FlashPro5 Signal Description

Description

3.3V Programming voltage

Signal reference

JTAG clock; SPI clock

TDI/SDI

TDO/SDO

TMS/SS#

JTAG data input to device; SPI MOSI

JTAG data output from device; SPI MOSI

JTAG mode select; SPI Chip Select nTRST

VJTAG

Programmable output pin may be set to off, toggle, low, or high level

Reference voltage from the target board

PROG_MODE IGLOO v2 family - Used for switching from VCC 1.2V to 1.5V during programming

232 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

FlashPro4

Some designers of high-integrity boards (military and avionic) may arrange their boards so that TRST is tied to ground via a weak pull-down resistor. The purpose of this is to hold the JTAG state-machine in a reset state by default, so that even with TCK oscillating, some sudden ion bombardment or other electrical even will not suddenly throw the JTAG state-machine into an unknown state. If your design also uses a weak pulldown resistor on TRST on your board, then enabling the “Drive TRST” flag will be required to force the

JTAG state-machine out of reset to permit programming to take place. With most boards, there is no need to select this flag.

FlashPro4

The FlashPro4 output is supplied via a connector to which a detachable 10-pin cable is fitted. The connector on the FlashPro4 unit is a 2x5, RA male Header connector, which is manufactured by AMP and has a manufacturer’s part number of 103310-1. This is a standard 2x5, 0.1 pitch connector which is keyed. Use the 10 pin right-angle header, AMP P/N 103310-1 (DigiKey P/N A26285-ND) for FlashPro4 and use the 10 pin straight header, AMP P/N 103308-1 (DigiKey P/N A26267-ND) for the straight version..

The signals on the pins of the FlashPro4 10-pin connector are shown in the figure below (extracted from

FlashPro4 product specification):

Signal

VPUMP

Figure 153 · FlashPro4 10-Pin Connector

Note: All ground pins must be connected. The rectangular shape shows connections on the programmer itself. Arrows show current flow towards or from the rectangular programmer.

The table below shows a description of the signals.

Table 32 · FlashPro4 Signal Description

Description

3.3V Programming voltage

GND

TCK

TDI

TDO

TMS nTRST

Signal reference

JTAG clock

JTAG data input to device

JTAG data output from device

JTAG mode select

Programmable output pin may be set to off, toggle, low, or high level

VJTAG Reference voltage from the target board

PROG_MODE IGLOO v2 family - Used for switching from VCC 1.2V to 1.5V during programming

FlashPro User's Guide 233

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

JTAG state-machine out of reset to permit programming to take place. With most boards, there is no need to select this flag.

FlashPro3

The FlashPro3 output is supplied via a connector to which a detachable 10-pin cable is fitted. The connector on the FlashPro3 unit is a 2x5, RA male Header connector, which is manufactured by AMP and has a manufacturer’s part number of 103310-1. This is a standard 2x5, 0.1 pitch connector which is keyed. Use the 10 pin right-angle header, AMP P/N 103310-1 (DigiKey P/N A26285-ND) for FlashPro5/4/3/3X and use the 10 pin straight header, AMP P/N 103308-1 (DigiKey P/N A26267-ND) for the straight version.

The signals on the pins of the FlashPro3 10-pin connector are shown in the figure below (extracted from

FlashPro3 product specification):

Figure 154 · FlashPro3 10-Pin Connector

Note: All ground pins must be connected. The rectangular shape shows connections on the programmer itself.

Arrows show current flow towards or from the rectangular programmer.

The table below shows a description of the signals.

Table 33 · FlashPro3 Signal Description

Description Signal

VPUMP 3.3V Programming voltage

GND

TCK

TDI

Signal reference

JTAG clock

JTAG data input to device

TDO

TMS

JTAG data output from device

JTAG mode select nTRST Programmable output pin may be set to off, toggle, low, or high level

VJTAG Reference voltage from the target board

N/C Programmer does not connect to this pin

234 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

FlashPro Lite

JTAG state-machine out of reset to permit programming to take place. With most boards, there is no need to select this flag.

FlashPro Lite

For FlashPro Lite, the existing 26-pin connector is shown in the figure below.

Signal

Figure 155 · 26-pin Connector for FlashPro Lite

Note: All ground pins must be connected. The rectangular shape shows connections on the programmer itself.

Arrows show current flow towards or from the rectangular programmer.

The appropriate SAMTEC micro connector target cable for this is:

Samtec FFSD-13-D-12.00-01-N.

The 12 inch cable is specified. This is likely to be more than enough to connect to the board and reducing the inductance will help compared with 18 inches, which is supplied by the default with FlashPro Lite.

See the table below for a description of the signals.

Table 34 · FlashPro Lite Signal Description

Description

VDDP

VDDL

VPP

VDD supply for logic I/O pads

VDD supply for core

Positive programming supply (+16.5V)

VPN

GND

SENSE

TCK

Negative programming supply(-13.8V)

Signal reference

Input from target board to programmer to indicate connection to ground

JTAG clock

FlashPro User's Guide 235

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Signal

TDI

TDO

Description

JTAG data input to device

JTAG data output from device

TMS nTRST

JTAG mode select

Programmable output pin may be set to off, toggle, low, or high level

RCK/OUT0 Programmable output pin may be set to off, toggle, low, or high level

N/C Programmer does not connect to this pin

JTAG state-machine out of reset to permit programming to take place. With most boards, there is no need to select this flag.

FlashPro

For FlashPro, you can use the same 26-pin target cable you used for FlashPro Lite, but the connections are shown in the figure below.

VDDP

VDDL

Signal

Figure 156 · 26-pin connections for FlashPro

Note: All ground pins must be connected. The rectangular shape shows connections on the programmer itself.

Arrows show current flow towards or from the rectangular programmer.

The table below shows the signal pin descriptions for FlashPro.

Table 35 · FlashPro Signal Description

Description

VDD supply for logic I/O pads

VDD supply for core

236 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

FlashPro 5/4/3/3X Characteristics

VPP

VPN

GND

Signal

SENSE

TCK

TDI

Description

Positive programming supply (+16.5 V)

Negative programming supply (-13.8 V)

Signal reference

Input from target board to programmer to indicate connection to ground

JTAG clock

JTAG data input to device

TDO

TMS nTRST

RCK/OUT0

JTAG data output from device

JTAG mode select

Programmable output pin may be set to off, toggle, low, or high level

2.5V, 2.5V/3.3V,

N/C

Programmer does not connect to these pins

JTAG state-machine out of reset to permit programming to take place. With most boards, there is no need to select this flag.

FlashPro 5/4/3/3X Characteristics

Table 36 · JTAG Switching Characteristics for FlashPro5/4/3/3X

Description Symbol Min Max Unit

Output delay from TCK to TDI, TMS

TDO setup time before TCK rising, VJTAG=3.3

TDO setup time before TCK rising, VJTAG=1.5

TDO hold time after TCK rising

TCK period

TTCKTDI -2

TTDOTCK 12

TTDOTCK 14.5

TTCKTDO 0

TTCK ns

41.7 10667 ns ns ns ns

FlashPro User's Guide 237

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

FlashPro and FlashPro Lite Characteristics

The table below shows the JTAG switching characteristics for FlashPro and FlashPro Lite measured at the programmer end of the JTAG cable.

Table 37 · JTAG Switching Characteristics for FlashPro and FlashPro Lite

Description Symbol Min Max Unit

-2 2 ns Output delay from TCK falling to TDI,

TMS

TTCKTDI

TTDOTCK TDO setup time before TCK rising

TDO hold time after TCK rising

5.0

TTCKTDO 0 ns ns

TCK period TTCK 40 10240 ns

Illustration of the JTAG Switching Characteristics

The figure below is an illustration of the JTAG switching characteristics.

Figure 157 · JTAG Switching Characteristics

Device Debug

Device Debug / SmartDebug enables you to use JTAG to interrogate and view embedded silicon features and device status (FlashROM, Security Settings, Embedded Flash Memory (NVM) and Analog System).

It provides tools to help troubleshoot some of the common issues related to the Embedded Flash Memory and Analog System.

Device Debug supports IGLOO, ProASIC3, SmartFusion and Fusion devices. SmartDebug supports

SmartFusion2 and ProASIC3 devices.

The user support is separated into two sections:

• Using Device Debug to Find Solutions to Common Issues - Contains common issues and troubleshooting instructions that will enable you to solve your problems as quickly as possible.

• Frequently Asked Questions - Answers to the most frequently asked questions about the tools and silicon features related to your solution.

238 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Getting Started with Device Debug

If you are unfamiliar with Device Debug, you may find it helpful to review the Getting Started with Device

Debug topic

. You can view descriptions of the Device Debug interface in the Reference section of the help.

Getting Started with Device Debug

This topic introduces the basic elements and features of Device Debug. If you are already familiar with the user interface then proceed to Solutions to Common Problems or Frequently Asked Questions sections.

Device Debug (SmartDebug for some families) enables you to use JTAG to interrogate and view embedded silicon features and device status (FlashROM, Security Settings, Embedded Flash Memory (NVM) and

Analog System). Device Debug is available as a part of the FlashPro programming tool.

See the Using Device Debug topic for an overview of the use flow.

You can use the debugger to:

•

Get device status and view diagnostics

•

Use the FlashROM debug GUI to read out and compare content

•

Use the Embedded Flash Memory Debug GUI to read out and compare your content with your original files

•

Use the Analog System Debug to read out and compare your analog block configuration with your original file

Using Device Debug

The most common flow for Device Debug is:

Start FlashPro

. If necessary, create a new project .

2. Set up your FlashPro Project with or without a PDB file. If you are in single-device mode you will need a PDB file. You can create a PDB file in both Single Device and Chain mode.

With a PDB, you will get additional information such as FlashROM and Embedded Flash Memory partitions when debugging the silicon features. Best practice is to use a PDB with a valid-use design to start a debug session.

3. Select the target device from your chain and click Inspect Device.

4. Click Device Status to get device status and check for issues

5. Examine individual silicon features (FlashROM, Embedded Flash Memory Block and Analog System) on the device.

FlashPro User's Guide 239

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Solutions to Common Issues Using Device

Debug

Embedded Flash Memory (NVM) - Failure when

Programming/Verifying

If the Embedded Flash Memory failed verification when executing the PROGRAM_NVM, VERIFY_NVM or

PROGRAM_NVM_ACTIVE_ARRAY action, the failing page may be corrupted . To confirm and address this

issue:

1. In the Inspect Device window click View Flash Memory Content.

2. Select the Flash Memory block and client (or page range) to retrieve from the device.

3. Click Read from Device; the retrieved data appears in the lower part of the window.

4. Click View Detailed Status to check the NVM Status .

Note: You can use the check_flash_memory and read_flash_memory Tcl commands to perform diagnostics similar to the commands outlined above.

5. If the NVM is corrupted you must reset the affected NVM pages.

To reset the affected NVM pages, either re-program the pages with your original data or ‘zero-out’ the

pages by using the Tcl command recover_flash_memory .

If the Embedded Flash Memory failed verification when executing a VERIFY_NVM or

VERIFY_NVM_ACTIVE_ARRAY action, the failure may be due to the change of content in your design. To confirm this, repeat steps 1-3 above.

NOTE: NVM corruption is still possible when writing from user design. Check NVM status for confirmation.

Analog System Not Working as Expected

If the Analog System is not working correctly, it may be due the following:

1. System supply issue. To troubleshoot:

• Physically verify that all the supplies are properly connected to the device and they are at the proper level. Then confirm by running the Device Status.

• Physically verify that the relevant channels are correctly connected to the device.

2. Analog system is not properly configured. You can confirm this by examining the Analog System .

ADC Not Sampling the Correct Value

If the ADC is sampling all zero values then the wrong analog pin may be connected to the system, or the analog pin is disconnected. If that is not the case and the ADC is not sampling the correct value, it may be due to the following:

1. System supply issues - Run the device status to confirm.

2. Analog system is not configured at all - To confirm, read out the ACM configuration and verify if the

ACM content is all zero.

3. Analog system is not configured correctly - To confirm, read out the ACM configuration and verify that

the configuration is as expected .

Once analog block configuration has been confirmed, you can use the sample_analog_channel Tcl

command for debug sampling of the analog channel with user-supplied sampling parameters.

240 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

ADC Not Sampling the Correct Value

If you have access to your Analog System Builder settings project (<Libero IDE

project>/Smartgen/AnalogBlock), you may use the compare function provided by the tool .

FlashPro User's Guide 241

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Frequently Asked Questions

How do I unlock the device security so I can debug?

You must provide the PDB file with a User Pass Key in order to unlock the device and continue debugging.

If you do not have a PDB with User Pass Key, you can create a PDB file in FlashPro (if you know the Pass

Key value).

How do I export a report?

You can export three reports from the Device Debug GUI: Device Status, Client Detailed Status from the

NVM, or the Compare Client Content report from the NVM. Each of those reports can be saved and printed.

If using a Tcl command, you can use the –file <filename> option for the following commands:

read_device_status

read_analog_block_config

compare_flashrom_client compare_analog_config

For example, you can use the following command to export the content of the client 'datastore1' in NVM block 0 to the report file datastore1_content.txt: read_flash_memory –client “datastore1” –file {C:\temp\datastore1_content.txt}

How do I generate diagnostic reports for my target device?

A set of diagnostic reports can be generated for your target device depending on which silicon feature you are debugging. A set of Tcl commands are available to export those reports. The following is a summary of those Tcl commands based on the silicon features.

When using the –file parameter, ensure that you use a different file name for each command so you do not overwrite the report content. If you do not specify the –file option in the Tcl, the output results will be directed to the FlashPro log window.

For the overall device:

read_device_status

read_id_code

For FlashROM:

compare_flashrom_client

For Embedded Flash Memory (NVM):

For Analog Block:

read_analog_block_config

242 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Where can I find files to compare my contents/settings?

compare_analog_config

To examine the NVM content, see the FlashROM Memory Content Dialog Box .

To execute the Tcl command, from the File menu choose Run Script.

Where can I find files to compare my contents/settings?

FlashROM

You can compare the FlashROM content in the device with the data in the PDB file. You can find the PDB in the <Libero IDE project>/Designer/Impl directory.

Embedded Flash Memory (NVM)

You can compare the Embedded Flash Memory content in the device with the data in the PDB file. You can find the PDB in the <Libero IDE project>/Designer/Impl directory.

Analog System

You can compare the Analog System configuration in the device with the data in the loaded PDB file or in the Analog System folder. Go to:

• Fusion devices - <Libero IDE project>/Smartgen/AnalogBlock

• SmartFusion devices - <Libero IDE Project>/component/<SmartDesign Project>/MSS_ACE_0

The tool automatically identifies the necessary files in the selected folder for comparison.

What is a UFC file? What is an EFC file?

UFC is the User FlashROM Configuration file, generated by the FlashROM configurator; it contains the partition information set by the user. It also contains the user-selected data for region types with static data.

However, for AUTO_INC and READ_FROM_FILE, regions the UFC file contains only:

• Start value, end value, and step size for AUTO_INC regions, and

• File directory for READ_FROM_FILE regions

EFC is the Embedded Flash Configuration file, generated by the Flash Memory Builder in the Project

Manager Catalog ; it contains the partition information and data set by the user.

Both UFC and EFC information is embedded in the PDB when you generate the PDB file.

Is my FPGA fabric enabled?

When your FPGA fabric is programmed, you will see the following statement under Device State in the

Device Status report:

FPGA Array Status: Programmed and Enabled

If the FPGA fabric is not programmed, the Device State shows:

FPGA Array Status: Not Enabled

FlashPro User's Guide 243

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Embedded Flash Memory (NVM) Frequently

Asked Questions

Is my Embedded Flash Memory (NVM) programmed?

To figure out if your NVM is programmed, read out and view the NVM content or perform verification with the

PDB file.

To verify the NVM with the PDB select the VERIFY or VERIFY_NVM action in FlashPro.

How do I display Embedded Flash Memory (NVM) content in the

Client partition?

You must load your PDB into your FlashPro project in order to view the Embedded Flash Memory content in the Client partition. To view NVM content in the client partition:

1. Load your PDB into your FlashPro project.

2. Click Inspect Device.

3. Click View Flash Memory Content.

4. Choose a block from the drop-down menu.

5. Select a client.

6. Click Read from Device. The Embedded Flash Memory content from the device appears in the Flash

Memory dialog box.

See the Flash Memory Dialog Box topic for more description on viewing the NVM content.

How do I know if I have Embedded Flash Memory (NVM) corruption?

When Embedded Flash Memory is corrupted ,

checking Embedded Flash Memory may return with any or all

of the following page status:

• ECC1/ECC2 failure

• Page write count exceeds the 10-year retention threshold

• Page write count is invalid

• Page protection is set illegally (set when it should not be)

See the How do I interpret data in the Flash Memory (NVM) Status Report?

topic for details.

If your Embedded Flash Memory is corrupted, you can recover by reprogramming with original design data.

Alternatively, you can ‘zero-out’ the pages by using the Tcl command recover_flash_memory .

Why does Embedded Flash Memory (NVM) corruption happen?

Embedded Flash Memory corruption occurs when Embedded Flash Memory programming is interrupted due to:

• Supply brownout; monitor power supplies for brownout conditions. For SmartFusion monitor the

VCC_ENVM/VCC_ROSC voltage levels; for Fusion, monitor VCC_NVM/VCC_OSC.

• Reset signal is not properly tied off in your design. Check the Embedded Memory reset signal.

244 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

How do I recover from Embedded Flash Memory corruption?

How do I recover from Embedded Flash Memory corruption?

Reprogram with original design data or ‘zero-out’ the pages by using the Tcl command

recover_flash_memory .

What is a JTAG IR-Capture value?

JTAG IR-Capture value contains private and public device status values. The public status value in the value read is ISC_DONE, which indicates if the FPGA Array is programmed and enabled.

The ISC_DONE signal is implemented as part of IEEE 1532 specification.

What does the ECC1/ECC2 error mean?

ECC is the Error Correction Code embedded in each Flash Memory page.

ECC1 – One bit error and correctable.

ECC2 – Two or more errors found, and not correctable.

How can I tell if my FlashROM is programmed?

To verify that your FlashROM is programmed, read out and view the FlashROM content or perform

verification with the PDB file by selecting the VERIFY or VERIFY_FROM action in FlashPro.

Can I compare serialization data?

To compare the serialization data, you can read out the FlashROM content and visually check data in the serialization region. Note that a serialization region can be an AUTO_INC or READ_FROM_FILE region.

For serialization data in the AUTO_INC region, check to make sure that the data is within the specified range for that region.

For READ_FROM_FILE region, you can search for a match in the source data file.

Can I tell what security options are programmed in my device?

To determine the programmed security settings, run the Device Status option from the Inspect Device dialog and examine the Security Section in the report.

This section lists the security status of the FlashROM, FPGA Array and Flash Memory blocks.

Is my analog system configured?

To determine if the analog block is configured, run the Device Status option from the Inspect Device dialog and examine the Analog Block Section in the report. For example, the excerpt from the Device Status report below shows that the analog block status is operational:

Analog Block:

OABTR Register (HEX): 0dbe37b

3.3V (vdd33): PASS

1.5V (vdd15): PASS

Bandgap: PASS

-3.3V (vddn33): PASS

ADC Reference: PASS

FPGA_Good: PASS

Status: Analog Block is operational

If you read out an all zero value when examining the Analog System Configuration , then it is possible that

the Analog System is not configured.

FlashPro User's Guide 245

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

You need to compare your analog system configuration with the design configuration from the Analog

System Builder

The -3.3V (vddn33) voltage is optional.

How do I interpret data in the Device Status report?

The Device Status Report generated from the FlashPro Device Debug Feature contains the following sections:

• IDCode (see below)

•

User Information

•

Device State

•

Analog Block (SmartFusion and Fusion only)

•

Factory Data

•

Security Settings

IDCode

Bit Field (little endian)

The IDCode section shows the raw IDCode read from the device. For example, in the Device Status report for an AFS600 device, you will find the following statement:

IDCode (HEX): 233261cf

The IDCode is compliant to IEEE 1149.1. The following table lists the IDCode bit assignments:

Table 38 · IDCode Bit Assignments

Example Bit Value for

AFS600 (HEX)

Description

Bit [31-28] (4 bits) 2 Silicon Revision

Device ID Bit [27-12] (16 bits)

3326

Bit [11-0] (12 bits) 1cf IEEE 1149.1 Manufacturer ID for

Microsemi

Device Status Report: User Info

The User Information section reports the information read from the User ROW (UROW) of IGLOO,

ProASIC3, SmartFusion and Fusion devices. The User Row includes user design information as well as troubleshooting information, including:

• Design name (10 characters max)

• Design check sum (16-bit CRC)

• Last programming setup used to program/erase any of the silicon features.

• FPGA Array / Fabric programming cycle count

For example:

User Information:

UROW data (HEX): 603a04e0a1c2860e59384af926fe389f

Programming Method: STAPL

Programmer: FlashPro3

Programmer Software: FlashPro vX.X

Design Name: ABCBASICTO

Design Check Sum: 603A

246 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Device Status Report: Device State

Category

Algorithm Version: 19

Array Prog. Cycle Count: 19

Table 39 · Device Status Report User Info Description

Field Description

User Row Data (Example)

UROW data (HEX):

603a04e0a1c2860e59384af926fe389f

Raw data from User Row

(UROW)

Programming

Troubleshooting

Info

(Example)

Programming Method: STAPL

Programmer: FlashPro3

Programmer Software: FlashPro v8.6

Algorithm Version: 19

Known programming setup used. This includes:

Programming method/file, programmer and software. It also includes programming

Algorithm version used.

Design Info (Example)

Design Name: ABCASICTO

Design Check Sum: 603A

Design name (limited to 10 characters) and check sum.

Design check sum is a 16bit CRC calculated from the fabric (FPGA Array) datastream generated for programming. If encrypted datastream is generated selected, the encrypted datastream is used for calculating the check sum.

Device Status Report: Device State

The device state section contains:.

• IR-Capture register value, and

• The FPGA status

The IR-Capture is the value captured by the IEEE1149.1 instruction register when going through the IR-

Capture state of the IEEE 1149.1 state machine. It contains information reflecting some of the states of the devices that is useful for troubleshooting.

One of the bits in the value captured is the ISC_DONE value, specified by IEEE 1532 standard. When the value is ‘1’ it means that the FPGA array/fabric is programmed and enabled. This is available for IGLOO,

ProASIC3, SmartFusion and Fusion devices.

For example:

Device State:

IRCapture Register (HEX): 55

FPGA Array Status: Programmed and enabled

For a blank device:

Device State:

IRCapture Register (HEX): 51

FPGA Array Status: Not enabled

FlashPro User's Guide 247

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Device Status Report: Analog Block

The Analog block of the SmartFusion and Fusion devices monitors some of the key power supplies needed by the device to function. These power supply status is captured in the OABTR test register in the Analog block.

For example, if you run Device Status when the Fabric and Analog configuration is programmed and powered up successfully the report indicates:

Analog Block:

OABTR Register (HEX): 0dbe3bb

3.3V (vdd33): PASS

1.5V (vdd15): PASS

Bandgap: PASS

-3.3V (vddn33): PASS

ADC Reference: PASS

FPGA_Good: PASS

Status: Analog Block is operational

Table 40 · Device Status Report - Analog Block Description

Analog Block Status Description

OABTR Register

3.3V (vdd33)

1.5V (vdd15)

RAW data captured from the device

Vcc33a supply status

Vccnvm supply status

Bandgap

ADC Reference

Internal bandgap supply status

ADC reference voltage status

-3.3V (vddn33)

FPGA Good

Vddn33 supply status (optional voltage)

FPGA array or Fabric status

If the Fusion device is erased, the report indicates:

Analog Block:

OABTR Register (HEX): 188e3ba

3.3V (vdd33): PASS

1.5V (vdd15): PASS

Bandgap: PASS

-3.3V (vddn33): FAIL

ADC Reference: FAIL

FPGA_Good: FAIL

Status: Analog Block is non-operational

Analog Block is not programmed

Device Status Report: Factory Data

The Factory Data section lists the Factory Serial Number (FSN).

Each of the IGLOO, ProASIC3, SmartFusion and Fusion devices has a unique 48-bit FSN.

248 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Device Status Report: Security

Device Status Report: Security

The security section shows the security options for the FPGA Array, FlashROM and Flash Memory (NVM) block that you programmed into the device.

For example, using a Fusion AFS600 device:

Security:

Security Register (HEX): 0000000088c01b

FlashROM

Write/Erase protection: Off

Read protection: Off

Encrypted programming: Off

FPGA Array

Write/Erase protection: Off

Verify protection: Off

Encrypted programming: Off

FlashMemory Block 0

Write protection: On

Read protection: On

Encrypted programming: Off

FlashMemory Block 1

Write protection: On

Read protection: On

Encrypted programming: Off

Table 41 · Device Status Report - Security Description

Security

Status Info

Description

Security

Raw data captured from the device's security status register

Write/Erase

Protection

Read

Protection

Write protection is applicable to FlashROM, FPGA Array (Fabric)and

Flash Memory (NVM) blocks. When On, the Silicon feature is write/erase protected by user passkey.

Read protection is applicable to FlashROM and Flash Memory (NVM) blocks. When On, the Silicon feature is read protected by user passkey.

Verify

Protection

Encrypted

Programming

Verify Protection is only applicable to FPGA Array (Fabric) only. When

On, the FPGA Array require user passkey for verification.

Reading back from the FPGA Array (Fabric) is not supported.

Verification is accomplished by sending in the expected data for verification.

Encrypted Programming is supported for FlashROM, FPGA Array

(Fabric) and Flash Memory (NVM) blocks. When On, the silicon feature is enable for encrypted programmed. This allows field design update with encrypted datastream so the user design is protected.

FlashPro User's Guide 249

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Encrypted Programming

To allow encrypted programming of the features, the target feature cannot be Write/Erase protected by user passkey.

The security settings of each silicon feature when they are enabled for encrypted programming are listed below.

FPGA Array (Fabric)

Write/Erase protection: Off

Verify protection: Off

Encrypted programming: On

Set automatically by Designer or FlashPro when you select to enable encrypted programming of the FPGA

Array (Fabric). This setting allows the FPGA Array (Fabric) to be programmed and verified with an encrypted datastream.

FlashROM

Write/Erase protection: Off

Read protection: On

Encrypted programming: On

Set automatically by Designer or FlashPro when you select to enable encrypted programming of the

FlashROM. This setting allows the FlashROM to be programmed and verified with an encrypted datastream.

FlashROM always allows verification. If encrypted programming is set, verification has to be performed with encrypted datastream.

Designer and FlashPro automatically set the FlashROM to be read protected by user passkey when encrypted programming is enabled. This protects the content from being read out of the JTAG port after encrypted programming.

Flash Memory (NVM) Block

Write/Erase protection: Off

Read protection: On

Encrypted programming: On

The above setting is set automatically set by Designer or FlashPro when you select to enable encrypted programming of the Flash Memory (NVM) block. This setting allows the Flash Memory (NVM) block to be programmed with an encrypted datastream.

The Flash Memory (NVM) block does not support verification with encrypted datastream.

Designer and FlashPro automatically set the Flash Memory (NVM) block to be read protected by user passkey when encrypted programming is enabled. This protects the content from being read out of the

JTAG port after encrypted programming.

How do I interpret data in the Flash Memory (NVM) Status Report?

The Embedded Flash Memory (NVM) Status Report generated from the FlashPro Device Debug Feature consists of the page status of each NVM page. For example:

Flash Memory Content [ Page 34 to 34 ]

FlashMemory Page #34:

Status Register(HEX): 00090000

Status ECC2 check: Pass

Data ECC2 Check: Pass

Write Count: Pass (2304 writes)

Total number of pages with status ECC2 errors: 0

Total number of pages with data ECC2 errors: 0

Total number of pages with write count out of range: 0

FlashMemory Check PASSED for [ Page 34 to 34 ]

The 'check_flash_memory' command succeeded.

250 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Probe Insertion (Post-Layout) - SmartFusion2, IGLOO2, and RTG4

The Execute Script command succeeded.

Table 42 · Embedded Flash Memory Status Report Description

Description Flash

Memory

Status Info

Status

(HEX)

Raw page status register captured from device

Status

ECC2

Check

Check for ECC2 issue in the page status

Data ECC2

Check

Check for ECC2 issue in the page data

Write Count Check if the page-write count is within the expected range.

The expected write count is greater than or equal to:

6,384 - SmartFusion devices

2,288 - Fusion devices

Note: Write count, if corrupted, cannot be reset to a valid value within the customer flow;invalid write count will not prevent device from being programmed with the FlashPro tool.

The write count on all good eNVM pages is set to be 2288 instead of 0 in the manufacturing flow. The starting count of the eNVM is 2288. Each time the page is programmed or erased the count increments by one.

There is a Threshold that is set to 12288, which equals to 3 * 4096.

Since the threshold can only be set in multiples of 4096 (2^12), to set a

10,000 limit, the Threshold is set to 12288 and the start count is set to

2288; and thus the eNVM has a 10k write cycle limit. After the write count exceeds the threshold, the STATUS bit goes to 11 when attempting to erase/program the page.

Probe Insertion (Post-Layout) - SmartFusion2, IGLOO2, and RTG4

Introduction

Probe insertion is a post-layout debug process that enables internal nets in the FPGA design to be routed to unused I/Os, as shown. Nets are selected and assigned to probes using the Probe Insertion window in the

SmartDebug tools. The re-routed design can then be programmed into the FPGA, where an external logic analyzer or oscilloscope can be used to view the activity of the probed signal.

FlashPro User's Guide 251

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Probe Insertion in the Design Process

The Probe Insertion debug feature is complementary to the Live Probes and Active Probes. In the case of

Live Probes and Active Probes, a special dedicated probe circuitry is used.

Probe Insertion

1. Double-click SmartDebug Design in the Design Flow window to open the SmartDebug window.

Note: FlashPro Programmer must be connected for SmartDebug to open.

2. Select Debug FPGA Array and then select the Probe Insertion tab.

252

3. Click Add Probe.

Figure 158 · Probe Insertion Tab

FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Probe Insertion (Post-Layout) - SmartFusion2, IGLOO2, and RTG4

The Add Probe dialog box displays the nets available to be probed on the right side. Each entry has a

Net and Driver name which identifies that probe point. The left (filter) pane allows filtering of the probe points by net names or instance names.

To add filtering for Cell Types, enter the Cell Type Name in the Cell Type field. Enter, for example,

SEQ in the Cell Type field and all SEQ (Sequential) cell types will be displayed. If you enter COMB in the Cell Type field, all COMB (Combinational Cells) will be displayed.

Figure 159 · Add Probe(s) Dialog Box

4. Select one or more nets to probe and click OK.

The selected net(s) will appear in the Probes table in the Probe Insertion tab, as shown in the figure below. SmartDebug automatically generates the Port Name for the probe. You can change the Port

Name from the default if desired.

5. Assign a package pin to the probe using the drop-down list in the Package Pin column. You can assign the probe to any unused package pin (spare I/O).

Figure 160 · Debug FPGA Array > Probe Insertion > Add Probe

6. Click Run.

FlashPro User's Guide 253

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

This triggers Place and Route in the incremental mode, and the selected probe nets are routed to the selected package pin. After incremental Place and Route, Libero automatically reprograms the device

(with the added probes).

The log window shows the status of the Probe Insertion run.

Edit Probes

To edit/change a probe, select the probe and click Edit Probe. The Edit Net for Probe dialog box appears.

Figure 161 · Edit Net for Probe Dialog Box

Click and select a net to replace the original net for the Probe.

Probe Deletion

To delete a probe, select the probe and click Delete. To delete all the probes, click Delete All.

Note: Deleting probes from the probes list without Run does not automatically remove the probes from the design.

Reverting to the Original Design

To revert to the original design after you have finished debugging:

1. In SmartDebug, click Delete All to delete all probes.

2. Click Run.

3. Wait until the action has completed by monitoring the activity indicator (spinning blue circle). Action is completed when the activity indicator disappears.

4. Close SmartDebug.

See Also

Debug FPGA Array

254 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Probe Insertion (Post-Layout) - SmartFusion2, IGLOO2, and RTG4

Active Probes (SmartFusion2, IGLOO2, and RTG4)

On the Active Probes tab a table of Probe Names is shown with the Name, Type (which is the physical location of the flip-flop) and Value.

Click the Select Active Probes button to open a window that lists all the Available Probe Points and

Selected Probe Points. Both lists can be filtered using the inline Filter box. Between the two lists of Probe points are buttons for adding and removing probe points from either list.

Figure 162 · Active Probes Tab in SmartDebug FPGA Array Dialog Box

Once you have selected the desired probe, points appear in the Active Probe Data chart and you can read and write multiple probes at the same time (as shown in the figure below).

The Value column fields are editable for each of the probe points. Clicking the circle shaped icon changes the value, and clicking the back-arrow resets the value. Fields that have been changed are indicated by red text. After the probes have been written, the values return to black text.

FlashPro User's Guide

Figure 163 · Active Probes Tab - Select Active Probe Points

255

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Live Probes (SmartFusion2, IGLOO2, and RTG4)

The Live Probes tab shows a table with the probe name and pin type.

Note: SmartFusion2 and IGLOO2 support two probe channels, and RTG4 supports one probe channel.

SmartFusion2 and IGLOO2

Two Probe Channels (ChannelA and ChannelB) are available. Once a Probe Name is selected, it can be assigned to either ChannelA or ChannelB.

Note: At least one channel must be set; if you intend to use both probes, they must be set at the same time.

The Active Probes READ/WRITE will overwrite the settings of Live Probe channels (if any).

RTG4

After the channels have been set, SmartDebug configures the ChannelA and ChannelB IO’s to monitor the desired probe points. The maximum number of simultaneous probes is two internal signals. There is also a

Filter box to filter through the Probe Names. As you begin typing in the Filter box, the Probe Name table only shows results for the queried names.

One Probe Channel (Probe Read Data Pin) is available for RTG4 for debug. Once a Probe Name is selected, it can be assigned to the Probe Channel (Probe Read Data Pin).

The Active Probes READ/WRITE will overwrite the settings of Live Probe channels (if any).

256 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Probe Insertion (Post-Layout) - SmartFusion2, IGLOO2, and RTG4

FlashPro User's Guide 257

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Device Debug User Interface

Inspect Device Dialog Box

Inspect Device is available as a part of the FlashPro programming tool. Refer to Using Device Debug for

information on how to configure the FlashPro to get access to this feature.

The Inspect Device dialog box enables you to access all the Device Debug features, such as the FlashROM,

Embedded Flash Memory (NVM) and Analog Block. If you have multiple devices and programmers connected, choose your target device/programmer from the dropdown menu and use the ID code to verify that you are inspecting the correct device.

View Device Status - Displays the Device Status Report . The Device Status Report is a complete summary

of your device state, analog block test values, user information, factory data and security information. Use this dialog box to save or print your information for future reference.

View Analog Block Configuration - Opens the Analog Block Configuration dialog box . Enables you to view

the channel configuration for your analog block and compare the channel configuration with any other analog block file.

View Flash Memory Content - Opens the Flash Memory dialog box . This dialog box enables you to view

the details for each flash memory block in your device.

View FlashROM Content - Opens the FlashROM data dialog box , enables you to view a list of the physical

blocks in your FlashROM and the client partitions in FlashROM configuration files.

Figure 164 · Inspect Device Dialog Box

Device Status Report

This dialog box displays the Device Information report. The Device Information report is a complete summary of your device state, analog block test values, user information, factory serial number and security

information. Use this dialog box to save or print your information for future reference. See the Interpreting the Device Status Report topic for information on the report contents.

258 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Analog Block Configuration Dialog Box (SmartFusion and Fusion Only)

Figure 165 · Device Status Report

Analog Block Configuration Dialog Box (SmartFusion and Fusion

Only)

Enables you to:

• View the channel configuration on your analog system, identify if/how the channels are configured.

• Compare with the design configuration from the Analog System Builder for Fusion and SmartDesign

MSS Configurator for SmartFusion

The values displayed for each channel vary depending on the device family and channel you select; the

Channel configuration register read from the ACM is shown for each analog channel. Individual, decoded bit fields of the register are listed immediately beneath (as described in Fusion and SmartFusion handbook).

The dialog box may display the following values:

Fusion Device

• Analog MUX select

• Internal chip T monitor

FlashPro User's Guide 259

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

• Scaling factor control

• Current monitor switch

• Current monitor drive control

• Direct analog input switch

• Pad polarity - G, T, V, C pad polarity, positive or negative

• Select low/high drive

• Prescaler op amp mode

SmartFusion Device

• Gain select

• Channel state

• Direct Input state

• Current Monitor state

• Current monitor strobe state

• Comparator state

• Hysteresis select

• Analog MUX select

• DAC input select

• Temperature monitor state

• Temperature monitor strobe state

• Vref switch state

To use the compare feature, select the Compare with checkbox. If the loaded PDB file contains Analog

Block configuration information the comparison appear automatically.

To use a specific Project File, click Browse and navigate to the Analog System Builder directory for for

Fusion or SmartDesign for SmartFusion. In a typical IDE project, this directory is located at:

• Fusion - <project_root>/smartgen/<analog_block_core_name>

• SmartFusion - <project root>/component/work/<SmartDesign project>/MSS_ACE_0

After specifying the compare directory the differences (if any) are indicated in red on a channel by channel basis, as shown in the figure below.

260 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Embedded Flash Memory (NVM) Content

Figure 166 · Analog Block Configuration Dialog Box for a Fusion Device (Differences in Red)

Embedded Flash Memory (NVM) Content

The NVM content dialog is divided into two sections. The top section shows the data that is retrieved from the PDB that you specified. The bottom section shows the data that is retrieved from the actual device. The

View Flash Memory Content diagnostic enables you to:

•

View content of Flash Memory pages (as shown in the figure below)

•

Compare device content with original design content (requires a PDB that contains your EFC data)

• Check page status and identify if a page is corrupted or if the write count limit has exceeded the 10-

year retention threshold

Fusion Devices: Choose your block from the From block dropdown list This action populates the Select dropdown list with the names of the clients in the selected block that is configured in the Flash Memory

System Builder.

SmartFusion Devices: Block selection is unused and unavailable.

Choose a client name from the Select dropdown list and click Read from Device to view the values. You can also view a specific page range by selecting the <Page Range> option in the Select dropdown list and then specifying the start page and the end page.

You must click Read from device each time you specify a new page range to update the view.

If you do not have your original design programming database (PDB) file, then you can also examine and retrieve a range of pages. Specify a page range if you wish to examine a specific set of pages.

FlashPro User's Guide 261

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Figure 167 · Flash Memory Dialog Box for a SmartFusion Device (Device Debug)

Embedded Flash Memory: Browse Retrieved Data

The retrieved data table displays the content of the selected client or the page range selection. Corrupted pages content is displayed in red. Read-only page content, corresponding to clients defined with the Prevent read option in Flash Memory System Builder, is displayed on gray background. If content cannot be read

(e.g. pages are read-protected, but security has been erased), it is displayed as XX. The mouse tooltip summarizes abnormal content status (as shown in the figure below).

The corresponding page number and address (relative to the current block) are displayed in the left column.

The client size specified in the Flash Memory System Builder is shown at the top of the content table.

In the Retrieved Data View you can enter an Address value (such as 0010) in the Go to Address field and click the corresponding button to go directly to that address.

Click View Detailed Status for a detailed report on the page range you have selected.

For example, if you want to view a report on pages 1-3, set the Start Page to 1, End Page to 3 and click

Read from Device, then click View Detailed Status; the figure below is an example of the data for a specific page range.

262 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Embedded Flash Memory: Browse Retrieved Data

Figure 168 · Flash Memory Details Dialog Box (Device Debug)

FlashPro User's Guide

Figure 169 · Flash Memory Browse Retrieved Data

263

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Embedded Flash Memory: Compare Memory Client

After you retrieve the data from the device, the Compare Client Content button enables you to compare the content of the selected client from the device with the original programming database (PDB) file. The differences are shown in the Compare Memory Client dialog (as shown in the figure below).

NOTE: This option is not available when you select to retrieve the data based on a page range.

Figure 170 · Compare Memory Client Dialog Box

FlashROM Content Dialog Box

Enables you to view the physical blocks in your FlashROM and the client partitions specified in the original design content (requires a PDB that contains your UFC data). If the project’s PDB does not contain UFC data, only the physical blocks are displayed.

Scroll through the table to view the Words and Pages for your physical blocks.

The Client Partitions section lists the names and configuration details of the clients set up in the FlashROM

Builder. It automatically finds all mismatched client regions. To view the differences between a client and the device content, select a region row in the Client Partitions table. This action will highlight the corresponding device content in the Physical Blocks table. The mismatch details are displayed below the Client Partitions table.

To copy to clipboard the content of the Physical Blocks table, select one or more cells in the table and type

Ctrl+C.

264 FlashPro User's Guide

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Device Debug Tcl Commands

Figure 171 · FlashROM Content Dialog Box

Device Debug Tcl Commands

The following table lists the Tcl commands related to Device Debug. Click the command to view more information.

Table 43 · Device Debug Tcl Commands

Command Action Type

Performs diagnostics of the page status and data information

Embedded

Flash

Memory

(NVM)

compare_analog_config

Compares the content of the analog block Analog Block

FlashPro User's Guide 265

NOTE: Links and cross-references in this PDF file may point to external files and generate an error when clicked. View the online help included with software to enable all linked content.

Command Action configurations in your design against the actual values in the device.

compare_flashrom_client

Compares the content of the FlashROM configurations in your design against the actual values in the selected device.

read_analog_block_config

Type

FlashROM

Compares the memory client in a specific device and block

Embedded

Flash

Memory

(NVM)

Reads each channel configuration on your analog system, enabling you to identify if/how each channel is configured.

Analog Block

read_device_status

read_id_code recover_flash_memory

Displays a summary of the selected device

Reads the content of the FlashROM from the selected device

FlashROM

Reads information from the NVM modules

(page status and page data)

Embedded

Flash

Memory

(NVM)

Reads IDCode from the device without masking any IDCode fields

Removes ECC2 errors due to memory corruption by reprogramming specified flash memory (NVM) pages and initializing all pages to zeros.

Embedded

Flash

Memory

(NVM)