Microsemi FlashPro Express User Manual

FlashPro Express for Software v11.6
User’s Guide
NOTE: PDF files are intended to be viewed on the printed page; 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: 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 Express User's Guide
Table of Contents
FlashPro Express ..........................................................................................5
Getting Started ...............................................................................................9
FlashPro Express Interface......................................................................... 10
Programming Settings and Operations ..................................................... 17
Programmer Settings ............................................................................................................... 18
Scanning and Checking a Chain.............................................................................................. 21
Chain Programming..................................................................................... 22
Chain Order .............................................................................................................................. 23
Selecting an Action .................................................................................................................. 24
Tcl Commands - FlashPro Express ............................................................ 25
Electrical Parameters .................................................................................. 78
Electrical Specifications.............................................................................. 82
FlashPro Express Reference ...................................................................... 89
Product Support .......................................................................................... 92
3
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 Express
FlashPro Express is Microsemi’s programming tool designed to address secured programming assurance in
production programming house environments. FlashPro Express supports SmartFusion2, IGLOO2, RTG4,
SmartFusion, IGLOO, ProASIC3, Fusion, and ProASICPLUS devices in the Windows OS environments and
supports SmartFusion2, IGLOO2, and RTG4 in the Linux OS environments.
You can install FlashPro Express two ways:
•
Integrated with Libero - FlashPro Express is installed automatically when Libero is installed.
FlashPro express is used by Libero to perform the programming tasks, for SmartFusion2, IGLOO2,
and RTG4, as part of the design flow.
•
Stand-Alone - FlashPro Express is also available as a stand alone installation. This mode is primarily
used for production programming or lab programming on machines in which a full version of Libero is
not required. When installed using the stand alone installation, FlashPro Express is joined by the
predecessor product FlashPro.
View the detailed Install Instructions and System Requirements at the Flashpro Express software page:
http://www.microsemi.com/products/fpga-soc/design-resources/programming/flashproexpress#overview
Secure Job Programming
Job programming is the concept of using a single file to program a Microsemi device or chain of Microsemi
devices using encrypted bitstreams.
The single job file contains all of the information necessary to setup FlashPro Express as well as the
encrypted bitstream images for the devices in the job. Once a job file is created it can be handed off
securely to production programming houses or contract engineering facilities to load the Microsemi images
during manufacturing. Job projects can be exported from Libero and imported into stand alone FlashPro
Express providing a clean delineation between design flow and production programming.
Migrating FlashPro Projects to FlashPro Express
Existing FlashPro projects (*.pro) files are now called Job Project files in FlashPro Express. These Job
Projects can be opened with FlashPro Express to take advantage of Linux programming support and the
simplified tool targeted for operators in a production floor environment.
FlashPro projects that were created in single mode will not be supported with this tool. Microsemi
recommends that you convert these projects to chain mode projects. To convert the project to a chain
project, do the following steps:
1.
2.
Open the FlashPro project (*.pro) in FlashPro.
Locate the loaded STAPL file by one of two methods:
The log will print “STAPL file ‘<stapl_path>’ has been loaded successfully.” <stapl_path> is the
location of the STAPL file loaded.
Within the Single Device Configuration Window there is a field STAPL_FILE_NAME, which displays the
location of the STAPL file loaded.
FlashPro Express User's Guide
5
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.
3.
4.
5.
6.
Switch the project to chain mode by one of the two methods:
a.
Press the chain button from the toolbar.
b.
From the Tools menu, select Mode->Chain Programming.
Load the STAPL file in chain mode by adding a Microsemi device in the chain.
a.
From the File menu, select Configuration->Add Microsemi Devices from Files.
b.
Browse to the location of the STAPL file and click Open.
To save the project, from the File menu, select Save Project.
You can now open the project using FlashPro Express.
When moving FlashPro project (*.pro) files to another machine, Microsemi recommends that you archive the
entire project folder, copy it to the new machine, extract it locally, then load the job project within FlashPro
Express. FlashPro Express will only open a job project if a programmer is connected to the machine, at least
one Microsemi device has programmed enabled, and all enabled Microsemi devices have a bitstream file
loaded.
Supported Families - FlashPro Express
FlashPro Express programs all the devices from all the following device families:
6
•
SmartFusion2 FPGAs
•
IGLOO2 FPGAs
•
RTG4 FPGAs
•
SmartFusion FPGAs
•
IGLOO FPGAs
•
ProASIC3 FPGAs
•
Fusion FPGAs
•
ProASIC PLUS FPGAs - FlashPro Express ONLY; not supported in Libero SOC.
FlashPro Express 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.
Supported Families - FlashPro Express
When we specify a family name, we refer to the device family and all its derivatives, unless otherwise
specified. See the table below for a list of supported device families and their derivatives:
Table 1 · Product Families and Derivatives
Device
Family
Family
Derivatives
Description
SmartFusion2 N/A
Address fundamental requirements for advanced
security, high reliability and low power in critical
industrial, military, aviation, communications and
medical applications.
IGLOO2
N/A
Low-power mixed-signal programmable solution
RTG4
N/A
Radiation-tolerant programmable solution
SmartFusion
SmartFusion
SmartFusion intelligent mixed-signal FPGAs are the
only devices that integrate an FPGA, ARM Cortex-M3,
and programmable analog, offering full customization
and IP protection.
Fusion
N/A
Mixed-signal FPGA integrating ProASIC3 FPGA
fabric, programmable analog block, support for ARM®
TM
Cortex -M1 soft processors, and flash memory into a
monolithic device.
IGLOO
IGLOO
The ultra-low-power, programmable solution
IGLOOe
Higher density IGLOO FPGAs with six PLLs and
additional I/O standards
IGLOO nano
The industry’s lowest power, smallest size solution
IGLOO PLUS
The low-power FPGA with enhanced I/O capabilities
ProASIC3
The low-power, low-cost, FPGA solution
ProASIC3E
Higher density ProASIC3 FPGAs with six PLLs and
additional I/O standards
ProASIC3
nano
Lowest cost solution with enhanced I/O capabilities
ProASIC3L
The FPGA that balances low power, performance,
and low cost
Automotive
ProASIC3
ProASIC3 FPGAs qualified for automotive
applications
Military
ProASIC3/EL
Military temperature A3PE600L, A3P1000, and
A3PE3000L
RT ProASIC3
Radiation-tolerant RT3PE600L and RT3PE3000L
N/A
Supported by FlashPro Express ONLY- not supported
by Libero SoC.
ProASIC3
ProASIC
PLUS
FlashPro Express User's Guide
7
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.
Installing FlashPro Express Software and Hardware
See the FlashPro Express Installation Instructions on the Microsemi website for information on supported
platforms, how to install FlashPro Express software/hardware and relevant system requirements.
View the detailed Install Instructions and System Requirements at the FlashPro Express software page:
http://www.microsemi.com/products/fpga-soc/design-resources/programming/FlashPro#overview
8
FlashPro Express 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.
Starting FlashPro Express
Getting Started
Starting FlashPro Express
You can start the FlashPro Express software from Programs > Microsemi FlashPro Express vx.x >
FlashPro Express. If you installed the program in a folder other than FlashPro Express, choose that folder
from the Programs menu.
FlashPro Express User's Guide
9
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 Express Interface
The main FlashPro Express UI consists of a list of programmers and a chain table, as shown in the figure
below. This view displays the programmers connected to the machine, and the devices within the JTAG
chain specified in the job project file (PRO) file, as shown in the figure below.
•
Hover over the programmer Info icon to display more information about a programmer.
•
Click the Name field to change a programmer name.
•
Click the checkbox to enable or disable a programmer.
•
Right-click a programmer to Ping, Self-Test, Scan, Check Chain or Remove it from the list.
•
Additional information about a device and programming file, if loaded, can be viewed by hovering over
the info icon of that device.
•
Devices specified as disabled in the job project (*.pro) file are shown disabled and their HighZ value is
displayed in the column header.
•
Device/Programmer States:
•
IDLE: The devices/programmers are idle and not executing any programming action.
•
DISABLED: Devices that are not enabled for programming
•
PASSED: The last programming operation passed
•
FAILED: The last programming operation failed
Figure 1 · FlashPro Express Programmers and Chain Table
10
FlashPro Express 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.
Load a Job Project
Load a Job Project
To get started in FlashPro Express you must load a job project (*.pro file). To do so, from the Project menu
choose Open Job Project. A job project will open if:
•
At least 1 programmer is connected
•
At least 1 Microsemi device is enabled for programming
•
Any enabled Microsemi device for programming must have a bitstream file loaded
Note: FlashPro projects (*.pro) created in single chain mode are not supported with this tool. You must
create a chain mode project with the existing programming files within FlashPro prior to using
FlashPro Express.
To open a project:
1.
2.
3.
From the Project menu, choose Open Job Project. The Open Project dialog box appears.
Find your project file or type in your project file name in the File name field.
Click Open.
Figure 2 · FlashPro Express Launch Screen
Saving a Job Project
Click the Save button on the toolbar, or from the Project menu choose Save Job Project to save your
project.
Parallel Programming with FlashPro5/4/3/3X
Parallel programming enables you to program multiple Microsemi devices in parallel with multiple
programmers. In parallel programming, all targeted devices are programmed with the same programming
file (STAPL). The targeted device or chain configuration that is connected to each programmer must be
identical.
FlashPro Express User's Guide
11
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.
The FlashPro Express software together with the FlashPro5/4/3/3X programmers supports parallel
programming via a USB port. You can connect up to sixteen FlashPro5/4/3/3X's to a PC via a USB v1.1 or a
USB v2.0 port. FlashPro5/4/3/3X requires a self-powered hub.
Connecting FlashPro5/4/3/3X (a USB v2.0 enabled programmer) to USB v1.1 port increases device
programming time due to a slow data transfer rate on the USB v1.1 port in comparison to a USB v2.0 port.
Note: FlashPro (USB/LPT1) or FlashPro Lite programmers do not support parallel programming.
The following figure illustrates how you can connect a FlashPro5/4/3/3X programmer for parallel
programming.
Figure 3 · Connecting a FlashPro5/4/3/3X Programmer
An independent thread processes the STAPL file during parallel programming. In an Microsemi test, parallel
programming is approximately five times faster than programming 16 devices sequentially.
Note: Microsemi has tested Belkin PCI-USB cards and hubs. We have found that parallel programming
works best with the vendor's latest driver installed and with the matching hubs.
Chain Programming Tutorial
This tutorial demonstrates how to use FlashPro Express to program a multi-device, multi-programmer chain.
This tutorial uses the production programming flow that exports a programming job from Libero SoC, which
includes chain configuration, programmer settings, and bitstream files for programming, and creates a job
project from a programming job.
The figure below shows the chain used in this tutorial. M2S050T is device 1 and A3P250 is device 3. Device
1 is the first device to be programmed in the chain and device 2 is the last; device 3 is disabled and will not
be programmed.
Figure 4 · Chain Programming Devices
12
FlashPro Express 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.
Chain Programming Tutorial
To program a chain:
1.
2.
From the Project menu, choose Create Job Project from Programming Job.
Click Browse to load a Programming Job File, and specify your FlashPro Express job project
location. Click OK to continue, as shown in the figure below.
Figure 5 · Create Job Project from Programming Job
FlashPro Express displays your Job Project and programmers, as shown in the figure below. The
Device/Programmer states are:
•
IDLE: The devices/programmers are idle and not executing any programming action
•
DISABLED: Devices that are not enabled for programming
•
PASSED: The last programming operation passed
•
FAILED: The last programming operation failed
FlashPro Express User's Guide
13
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 6 · FlashPro Express with Loaded Job Project
See the Export Programming Job topic for information on how to generate a Programming Job file.
3.
Click the Refresh/Rescan button if your programmer is not listed. Hover your mouse over the Info
icon to view device info. If a device is Disabled for programming the HighZ status appears in the GUI,
as shown in the figure above.
4.
Set the Programming Action in the dropdown menu to PROGRAM, as shown in the figure below.
Figure 7 · Programming Action Set to PROGRAM
14
5.
Click RUN. Detailed individual programmer and device status information appears in the Programmer
List. Your programmer status (PASSED or FAILED) appears in the Programmer Status Bar, as shown
in the figure below.
•
Hover your mouse over the Programmer Status Bar to display information on the programmers.
•
Hover over the FAILED status to list all programmers that failed programming.
•
Hover over the PASSED status to list all the programmers that programmed successfully.
FlashPro Express 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.
Creating a Job Project from a Programming Job
Figure 8 · Chain Programming Complete
View the Log for Messages, Errors, Warnings and Info generated during programming.
Creating a Job Project from a Programming Job
Once you are ready to hand off your design for production you can create a job project. To do so:
1.
In Libero SoC run Export Programming Job to create a container that will be used to transfer
programming configuration information, including programming files, to the production programming
tool FlashPro Express.
FlashPro Express User's Guide
15
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 9 · Export Programming Job
1.
In FlashPro Express, from the Project menu choose Create Job Project From a Programming Job.
You will be prompted to specify the Programming Job File location that you just exported from Libero
and the location of where to store the FlashPro Express Job Project. The Job Project name
automatically uses the programming job name and cannot be changed. Click OK and a new Job
Project will be created and opened for production programming.
Figure 10 · Create Job Project Dialog Box
16
FlashPro Express 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.
Introduction
Programming Settings and Operations
Introduction
The FlashPro Express software enables you to connect multiple programmers to your computer. With each
programmer you select, you can connect the programmer, perform a self-test, customize, add, and remove
and analyze the JTAG chain, as shown in the figure below.
Figure 11 · FlashPro Express Right-Click Menu
FlashPro Express User's Guide
17
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.
Programmer Settings
The Programmer Settings dialog box includes setting options for FlashPro5/4/3/3X, FlashPro Lite and
FlashPro.
Note: You can set the TCK setting in the PDB/STAPL file by selecting the TCK frequency in the
Programmer Settings dialog box.
Limitation of the TCK frequency for the selected programmer:
•
FlashPro supports 1-4 MHz
•
FlashPro Lite is limited to 1, 2, or 4 MHz only.
•
FlashPro 4/3/3X supports 1-64 MHz.
•
FlashPro5 supports 1-10 MHz
Limitation of the TCK frequency for the target device:
•
IGLOO, ProASIC3, and Fusion – 10MHz to 20MHz
•
ProASICPLUS and ProASIC – 10 MHz.
During execution, the frequency set by the FREQUENCY statement in the PDB/STAPL file will override the
TCK frequency setting selected by you in the Programmer Settings dialog box unless the Force TCK
Frequency checkbox is selected.
To set your programmer settings:
1.
From the Tools menu, choose Programmer Settings.The Programmer Settings dialog box appears
(as shown in the figure below).
2.
Click a programmer tab and check the appropriate settings for your programmer.
Figure 12 · Programmer Settings Dialog Box for FlashPro Express
3.
18
Click OK.
FlashPro Express 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.
Introduction
FlashPro Programmer Settings
Choose your programmer settings for FlashPro (see figure above). If you choose to add the Force TCK
Frequency, select the appropriate MHz frequency. After you have made your selection(s), click OK.
Default Settings
•
The Vpp, Vpn, Vdd(l), and Vddp options are checked (Vddp is set to 2.5V) to instruct the FlashPro
Express programmer(s) to supply Vpp, Vpn, Vdd(l) and Vddp.
•
The Drive TRST option is unchecked to instruct the FlashPro Express programmer(s) NOT to drive the
TRST pin.
•
The Force TCK Frequency option is unchecked to instruct FlashPro Express to use the TCK frequency
specified by the Frequency statement in the STAPL file(s).
FlashPro Lite Programmer Settings
If you choose to add the Force TCK Frequency, select the appropriate MHz frequency. After you have made
your selection(s), click OK.
Default Settings
•
The Vpp and Vpn options are checked to instruct the FlashPro Express Lite programmer(s) to supply
Vpp and Vpn.
•
The Drive TRST option is unchecked to instruct the FlashPro Express Lite programmer(s) NOT to
drive the TRST pin.
•
The Force TCK Frequency option is unchecked to instruct the FlashPro Express Lite to use the TCK
frequency specified by the Frequency statement in the STAPL file(s).
FlashPro5/4/3/3X Programmer Settings
For FlashPro5/4/3/3X, you have the option of choosing the Set Vpump setting or the Force TCK Frequency.
If you choose the Force TCK Frequency, select the appropriate MHz frequency. For FlashPro4/3X settings,
you have the option of switching the TCK mode between Free running clock and Discrete clocking. After you
have made your selections(s), click OK.
Default Settings
•
The Vpump option is checked to instruct the FlashPro5/4/3/3X programmer(s) to supply Vpump to the
device.
•
The Force TCK Frequency option is unchecked to instruct the FlashPro5/4/3/3X to use the TCK
frequency specified by the Frequency statement in the PDB/STAPL file(s).
•
FlashPro5/4/3/3X default TCK mode setting is Free running clock
TCK Setting (ForceTCK Frequency)
If Force TCK Frequency is checked (in the Programmer Setting) then the selected TCK value is set for
the programmer and the Frequency statement in the PDB/STAPL file is ignored.
Note: FlashPro Lite RevA supports only 4MHz on TCK.
Default TCK frequency
When the PDB/STAPL file or Chain does not exist, the default TCK frequency is set to 4MHz. In the Single
Device File Programming mode, FlashPro Express will parse through the file and search for the "freq"
keyword and the "MAX_FREQ" Note field, which are expected in all Microsemi flash device files. The
FlashPro Express software uses the lesser value of the two as the default TCK frequency.
In Chain Programming mode, when more than one Microsemi flash device is targeted in the chain, the
FlashPro Express software passes through all of the files and searches for the "freq" keyword and the
"MAX_FREQ" Note field. The FlashPro Express software uses the lesser value of all the TCK frequency
settings and the "MAX_FREQ" Note field values.
FlashPro Express User's Guide
19
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 Programmers
To ping a programmer(s):
Right-click a programmer and choose Ping.
Note: You can click the Refresh/Rescan for Programmers button to quickly ping new programmers.
Performing a Self-Test
To perform a self-test:
Right-click the programmer you want to self-test and choose Self Test.
Note: You must connect the programmer to the self-test board that comes with your programmer before
performing a self-test.
Note: Self-test is not supported with FlashPro5/4 or FlashPro Lite programmers. These programmers are
rigorously tested at the factory during production.
20
FlashPro Express 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.
Enabling and Disabling Programmers
Scanning and Checking a Chain
The scan chain operation scans and analyzes the JTAG chain connected to programmer(s) you have
selected and checks that chain scanned matches the chain configured in FlashPro Express.
To scan a chain:
Right-click the programmer you want to scan and choose Scan and check chain.
Enabling and Disabling Programmers
After loading a job project, you can enable/disable or remove a programmer and can also ping, self-test, run
scan and check chain on any of the connected programmers. These actions are available in the shortcut
menu (right-click) for each of the programmers listed in the programmer column.
Click the checkbox next to a programmer in the Programmer column to enable or disable it. The
programmer is enabled when there is a tick mark in the checkbox and disabled when the checkbox is empty.
Renaming a Programmer
Enter the new programmer name in the Programmer window to rename the programmer. By default, the
programmer name is the same as the programmer ID.
Removing a Programmer
To remove a programmer:
Right-click the programmer and choose Remove.
FlashPro Express User's Guide
21
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.
Chain Programming
22
FlashPro Express 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.
Multiple Device Chain Programming
Chain Order
Chain Programming enables you to program several devices at one time. The order of devices in the chain
imported from Job Project must match the physical chain to be programmed.
The TDO for the first device connects to the programmer, and the last device's TDI connects to the
programmer. The devices in the chain go in order from a device's TDI into the next device's TDO, as shown
in the figure below.
Figure 13 · Chain Order
Multiple Device Chain Programming
The FlashPro Express software enables direct chain programming without generating a chain STAPL file.
Each device will be programmed in sequential order starting from device 1 to device N. See example below.
For more information about chain order, see the Chain Order help topic.
TDI > Device N > Device N-1 >… > Device 2 > Device 1 > TDO
Device Programming Compatibility
SmartFusion2, IGLOO2, RTG4, SmartFusion, IGLOO, ProASIC3, Fusion families can be programmed in the
same chain.
Programmer Support
FlashPro5/4/3/3X supports the SmartFusion2, IGLOO2, RTG4, SmartFusion, IGLOO, ProASIC3, Fusion
family devices. The Vpump on FlashPro5/4/3/3X is designed to support the programming of only one device.
Please make sure that Vpump, Vcc and Vjtag are provided on board for chain programming. Connect the
Vpump to the header as the Flashpro Express software will attempt to check for all external supplies,
including Vpump, to ensure successful programming. There is no limitation to the chain length; however,
ensure that the JTAG signal integrity and the timing are preserved.
FlashPro Express User's Guide
23
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.
Selecting an Action
FlashPro Express supports the following programming actions:
•
DEVICE_INFO
•
ENC_DATA_AUTHENTICATION - encrypted bitstream files for SmartFusion, IGLOO, ProASIC3/E and
Fusion; bitstream files for SmartFusion2, IGLOO2, and RTG4. If an enabled device for programming
does not contain this action in the chain, then the action will error out.
•
ERASE
•
PROGRAM
•
READ_IDCODE
•
VERIFY
To configure a programming action:
Select an action from the Programming Action dropdown menu in FlashPro Express, as shown in the figure
below.
Figure 14 · FlashPro Express Programming Actions
24
FlashPro Express 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 Express Tcl Command Reference
Tcl Commands - FlashPro Express
About TCL Commands - FlashPro Express Tcl Command
Reference
A Tcl (Tool Command Language) file contains scripts for simple or complex tasks. You can run scripts from
the Windows command line or store and run a series of Tcl commands in a *.tcl batch file. The Tcl
commands supported by FlashPro Express are listed in the table below.
Note: Tcl commands are case sensitive. However, their arguments are not.
Command
Action
close_project
Closes the FlashPro project
configure_flashpro_prg
Changes FlashPro programmer settings
configure_flashpro3_prg
Changes FlashPro3 programmer settings
configure_flashpro4_prg
Changes FlashPro 4 programmer settings
configure_flashpro5_prg
Changes FlashPro 5 programmer settings
configure_flashproLite_prg Changes FlashPro Lite programmer settings
create_job
Create a job in FlashPro Express
dump_tcl_support
Unloads the list of supported FlashPro Tcl commands
enable_serialization
Enables or disables serialization programming.
open_project
Opens a FlashPro project
ping_prg
Pings one or more programmers
refresh_prg_list
Refreshes the programmer list
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_log
Saves the log file
save_project
Saves the FlashPro project
scan_chain_prg
Runs scan chain on a programmer
select_serial_range
Selects the range of indexes to program.
self_test_prg
Runs Self-Test on a programmer
set_prg_name
Changes the user name of a programmer
FlashPro Express User's Guide
25
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
set_programming_action
Selects the action for a device
set_serialization_log_file
Sets the path and name of the serialization log file.
Running Tcl Scripts from within FlashPro Express
Instead of running scripts from the command line, you can use FlashPro Express's Execute Script dialog box
to run a script.
To execute a Tcl script file within FlashPro Express:
1.
From the File menu, choose Execute Script to display the Run Script dialog box.
Figure 15 · Run Script Dialog Box
2.
Click the Browse button 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 Express enters the full path and
script filename into the Run 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 or Linux command line.
To execute a Tcl script file in the FlashPro Express 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/FPExpress.exe SCRIPT:<filename>
The example below executes in batch mode the script foo.tcl:
<location of Microsemi software>/bin/FPExpress.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/FPExpress.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/FPExpress.exe script:foo.tcl console_mode:brief
logfile:foo.txt
26
FlashPro Express 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.
Exporting Tcl Scripts from within FlashPro Express
If you leave console_mode unspecified or set it to 'hide' FlashPro Express 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/FPExpress.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/FPExpress.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
}
Note: Script names can contain spaces if the script name is protected with double quotes:
FPExpress script:"FPExpress tcl/foo 1.tcl"
Exporting Tcl Scripts from within FlashPro Express
To export a set of Tcl commands from the FlashPro Express history:
1.
2.
From the File menu, choose Export Script File.
Enter the filename and click Save. The Export Script Options dialog appears (as shown in the figure
below).
Figure 16 · Script Export Options Dialog Box
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.
FlashPro Express User's Guide
27
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.
close_project
Closes the FlashPro or FlashPro Express project.
close_project
Arguments
None
Supported Families
All
Exceptions
None
Example
close_project
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
PLUS
ProASIC
, ProASIC
Exceptions
None
28
FlashPro Express 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.
configure_flashpro3_prg
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}]
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}
FlashPro Express User's Guide
29
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 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 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
30
FlashPro Express 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.
configure_flashproLite_prg
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.
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
PLUS
ProASIC
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}
create_job_project
Creates a Flashpro Express job using the programming job exported from Libero.
create_job_project –job_project_location location –job_file path –overwrite 0|1
Arguments
-job_project_location location
FlashPro Express User's Guide
31
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 location for your FlashPro Express job project.
-job_file path
Path to the Libero job file that is used as input to create the Flashpro Express job project.
-overwrite 0|1
Set value to 1 to overwrite your existing job project. .
Supported Families
SmartFusion2, IGLOO2, RTG4
Exceptions
None
Example
The following example creates a job project named test.job in the \fpexpress directory. It does not
overwrite the existing job project.
create_job_project \
-job_project_location {D:\fpexpress} \
-job_file {D:\test\designer\test\export\test.job} –overwrite 0\
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_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.
32
FlashPro Express 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.
open_project
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
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}
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'.
FlashPro Express User's Guide
33
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 –name {FP300085} –name {FP300086}
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
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
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})*]
34
FlashPro Express 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.
save_log
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}
save_log
Saves the log file.
save_log -file {file}
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
FlashPro Express User's Guide
35
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
save_project
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_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.
-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.
36
FlashPro Express 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.
self_test_prg
Exceptions
Must be a Microsemi Device
Example
select_serial_range -name M2S/M2GL050{T|S|TS} -from_data 3 -to_data 5
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
Exceptions
None
Example
The following examples runs the self test on the programmer '30175':
self_test_prg (-name {30175})*
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}
FlashPro Express User's Guide
37
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_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.
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}
38
FlashPro Express 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_serialization_log_file
In chain programming mode:
set_programming_file –name {MyDevice2} –file {e:/design/pdb/TopA3P250.pdb}
set_programming_file –name {MyDevice1} –no_file
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}
Exit Codes (SmartFusion2, IGLOO2, and RTG4)
Table 2 · Exit Codes (SmartFusion2, IGLOO2, and RTG4)
Error
Code
0x8001
Exit
Code
Exit Message
Possible Cause
Possible Solution
0
Passed (no error)
-
-
-24
Failure to read DSN
Device is in System
Controller Suspend
Mode
TRSTB should be driven High or disable
"System Controller Suspend Mode"
Check board
connections
0x8002
5
Failure to configure device
programming at 1.2/1.0 VCC
voltage
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.
0x8032
5
Device is busy
FlashPro Express User's Guide
Unstable VDDIx
voltage level
Monitor related power supplies that
cause the issue during programming;
check for transients outside of Microsemi
39
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
specifications. See your device
datasheet for more information on
transient specifications.
0x8003
5
Failed to enter programming
mode
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.
0x8004
6
Failed to verify IDCODE
Incorrect programming Choose the correct programming file and
select the correct device in the chain.
file
Incorrect device in
chain
Signal integrity issues
on JTAG pins
0x8005
10
Failed to program eNVM
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. Monitor related power supplies that
Signal integrity issues cause the issue during programming;
check for transients outside of Microsemi
on JTAG pins.
specifications. See your device
datasheet for more information on
transient specifications.
Monitor JTAG supply pins during
programming; measure JTAG signals for
noise or reflection.
0x8006
10
Failed to program eNVM
Unstable voltage level. Monitor related power supplies that
Signal integrity issues cause the issue during programming;
check for transients outside of Microsemi
on JTAG pins.
specifications. See your device
datasheet for more information on
transient specifications.
Monitor JTAG supply pins during
programming; measure JTAG signals for
noise or reflection.
0x8007
11
Failed to verify FPGA Array
Device is programmed
with a different design.
Verify the device is programmed with the
correct data/design
Unstable voltage level. Monitor related power supplies that
Signal integrity issues cause the issue during programming;
check for transients outside of Microsemi
on JTAG pins.
specifications. See your device
datasheet for more information on
transient specifications.
Monitor JTAG supply pins during
40
FlashPro Express 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
programming; measure JTAG signals for
noise or reflection.
0x8008
11
Failed to verify eNVM
Device is programmed
with a different design.
Verify the device is programmed with the
correct data/design
Unstable voltage level. Monitor related power supplies that
Signal integrity issues cause the issue during programming;
check for transients outside of Microsemi
on JTAG pins.
specifications. See your device
datasheet for more information on
transient specifications.
Monitor JTAG supply pins during
programming; measure JTAG signals for
noise or reflection.
0x8009
11
Failed to verify eNVM
Device is programmed
with a different design.
Verify the device is programmed with the
correct data/design
Unstable voltage level. Monitor related power supplies that
Signal integrity issues cause the issue during programming;
check for transients outside of Microsemi
on JTAG pins.
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
1
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
Failed to unlock User Pass Key
2
Pass key in file does
not match device
Provide a programming file with a pass
key that matches pass key programmed
into the device
0x8012
-35
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
FlashPro Express User's Guide
41
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
transient specifications.
0x8015
-20
FPGA Fabric digest verification:
FAIL
Signal integrity issues
on JTAG pins
Monitor JTAG supply pins during
programming; measure JTAG signals for
noise or reflection
Programming
bitstream components
do not match
components
programmed
Use the same programming file that was
used to program the device.
FPGA Fabric is either
erased or the data has
been corrupted or
tampered with
0x8016
-20
eNVM_0 digest verification:
FAIL
Programming
bitstream components
do not match
components
programmed
Use the same programming file that
was used to program the device
eNVM_0 data has
been corrupted or
tampered with
0x8017
-20
eNVM_1 digest verification:
FAIL
Programming
bitstream components
do not match
components
programmed
Use the same programming file that was
used to program the device
eNVM_1 data has
been corrupted or
tampered with
0x8018
-20
User security policies segment
digest verification: FAIL
Programming
bitstream components
do not match
components
programmed
Use the same programming file that was
used to program the device.
User security policy
segment data has
been corrupted or
tampered with
0x8019
-20
User key set 1 segment digest
verification: FAIL
Programming
bitstream components
do not match
components
programmed
Use the same programming file that was
used to program the device.
User key set 1
segment data has
been corrupted or
42
FlashPro Express 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
tampered with
0x801A -20
User key set 2 segment digest
verification: FAIL
Programming
bitstream components
do not match
components
programmed
Use the same programming file that was
used to program the device.
User key set 2
segment data has
been corrupted or
tampered with
0x801B -20
Factory row and factory key
segment digest verification:
FAIL
Programming
bitstream components
do not match
components
programmed
Use the same programming file that was
used to program the device.
Factory row and
factory key segment
data has been
corrupted or tampered
with
0x801C -20
Fabric configuration segment
digest verification: FAIL
Programming
bitstream components
do not match
components
programmed.
Use the same programming file that was
used to program the device.
Fabric configuration
segment data has
been corrupted or
tampered with
0x801D -21
Device security prevented
operation
The device is
protected with user
pass key 1 and the
bitstream file does not
contain user pass key
1.
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.
User pass key 1 in the
bitstream file does not
match the device.
0x801E -21
Device security prevented
operation
The device is
protected with user
pass key 1 and the
bitstream file does not
contain user pass key
1.
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.
User pass key 1 in the
bitstream file does not
match the device.
FlashPro Express User's Guide
43
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
0x801F -22
Exit Message
Authentication Error
Invalid/Corrupted programming
file
0x8020
-22
Authentication Error
Invalid/Corrupted programming
file
0x8021
-23
Possible Cause
Bitstream file has been Regenerate bitstream file
corrupted
Bitstream was
incorrected generated
Bitstream file has been Regenerate bitstream file
corrupted
Bitstream was
incorrected generated
Authentication Error
File contains an
Invalid/Corrupted encryption key encrypted key that
does not match the
device
File contains user
encryption key, but
device has not been
programmed with the
user encryption key
Device has user
encryption key 1/2
enforced and you are
attempting to
reprogram security
settings
0x8022
-23
Possible Solution
Authentication Error
File contains an
Invalid/Corrupted encryption key encrypted key that
does not match the
device
File contains user
encryption key, but
device has not been
programmed with the
user encryption key
Device has user
encryption key 1/2
enforced and you are
attempting to
reprogram security
settings
Provide a programming file with an
encryption key that matches that on the
device
First program security with master
programming file, then program with
user encryption 1/2 field update
programming files
You must first ERASE security with the
master security file, then you can
reprogram new security settings
Provide a programming file with an
encryption key that matches that on the
device
First program security with master
programming file, then program with
user encryption 1/2 field update
programming files
You must first ERASE security with the
master security file, then you can
reprogram new security settings
0x8023
-24
Authentication Design version is not
Error
higher than the backBack level not level programmed
device
satisfied
Generate a programming file with a
design version higher than the back level
version
0x8024
-24
Authentication Design version is not
Error
higher than the backBack level not level programmed
device
satisfied
Generate a programming file with a
design version higher than the back level
version
44
FlashPro Express 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
0x8025
Exit
Code
-25
Exit Message
Authentication Error
DSN binding mismatch
0x8026
-25
Authentication Error
DSN binding mismatch
0x8027
-26
Authentication Error
Insufficient device capabilities
0x8028
-26
Authentication Error
Insufficient device capabilities
0x8029
-27
Authentication Error
Incorrect DEVICEID
Possible Cause
Possible Solution
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
support the
capabilities specified
in programming file
Generate a programming file with the
correct capabilities for the target device
Incorrect programming Choose the correct programming file and
select the correct device in chain
file
Incorrect device in
chain
Signal integrity issues
on JTAG pins
0x802A -27
AuthenticationError
Incorrect DEVICEID
0x802B -28
Incorrect device in
chain
Measure JTAG pins and noise or
reflection
Signal integrity issues
on JTAG pins
If TRST is left floating, then add pull-up
to pin Reduce the length of ground
connection
Old programming file
Generate programming file with latest
version of Libero SoC
Old programming file
Generate programming file with latest
version of Libero SoC
JTAG interface is protected by
UPK1
Invalid or no UPK1 is
provided
User needs to provide correct UPK1 to
unlock device.
Authentication Error
M2S090 Rev. A or
M2S150 Rev. A: Either
certificate is corrupted
or the user hasn't
provided the
application code in the
User can program a valid application
code. This can be done with
SoftConsole.
Authentication Error
Authentication Error
Unsupported bitstream protocol
version
0x802F -30
0x8030
-31
Reduce the length of ground connection
Incorrect programming Choose the correct programming file and
select the correct device in chain
file
Unsupported bitstream protocol
version
0x802C -28
Measure JTAG pins and noise or
reflection. If TRST is left floating, then
add pull-up to pin
Invalid or inaccessible Device
Certificate
FlashPro Express User's Guide
FAB_RESET_N should be tied to HIGH
45
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
eNVM or provided
invalid application
code
FAB_RESET_N is tied
to ground
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
User can program a valid application
code. This can be done with
SoftConsole
AB_RESET_N should be tied to HIGH
FAB_RESET_N is tied
to ground
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 3 · Exit Codes for SmartFusion, IGLOO, ProASIC3 and Fusion Family Devices in Software v8.6 and Above
ERROR_CODE
0x8052
Exit
Code
Exit
Message
Possible Cause
0
Passed (no
error)
1
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 nonMicrosemi devices may be
incorrect.
The order of the specified chain
may be incorrect.
5
Failed to
enter
programming
mode.
Unstable VPUMP voltage level.
Unstable VCC
Signal integrity issues on JTAG
46
Possible Solution
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
FlashPro Express 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
Exit
Code
Exit
Message
Possible Cause
Possible Solution
pins.
specifications.
Device is in FlashFreeze mode
(ProASICL or IGLOO devices)
Monitor VJTAG during programming;
measure JTAG signals for noise or
reflection.
Older software or programming file
used.
Disble the FlashFreeze pin (ProASICL or
IGLOO devices)
Generate STAPL file with the latest version
of Designer/FlashPro.
Use latest version of FlashPro software.
0x801D
0x8053
6
Failed to
verify
IDCODE
Incorrect programming file
Choose the correct programming file and
select the correct device in chain.
Incorrect device in chain
Measure JTAG pins and noise or reflection.
Signal integrity issues on JTAG pins If TRST is left floating then add pull-up to
pin.
Reduce the length of ground connection.
0x8005
0x8009
0x800B
6
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.
0x8008
6
Failed to
verify
IDCODE.
Target is an
M7 device
0x800A
6
Failed to
verify
IDCODE
File is not for M7, but target device
is M7
Signal integrity issues on JTAG
pins.
6
Failed to
verify
IDCODE.
Core enabled
device
detected
0x800D
6
Failed to
FlashPro Express User's Guide
Make sure that the programming file you
generated is for an M7-enabled device.
Measure JTAG pins, noise and reflection.
Files not for M1, but target device is
M1.
Check that the target device is M1 enabled.
Make sure the programming file generated
Signal integrity issues on JTAG pins is for an M1-enabled device.
Target is an
M1 device
0x800C
Check that the target device is M7 enabled.
Monitor VJTAG during programming;
measure JTAG signals for noise or
reflection.
File is not for target device.
Check the target device; make sure the
programming file generated is matches the
Signal integrity issues on JTAG pins target device.
Monitor VJTAG during programming;
measure JTAG signals for noise or
reflection.
File is for M7 but target device is not Check that the target device is not M7
47
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
verify
IDCODE.
The target is
not M7
device
0x800E
6
Failed to
verify
IDCODE.
Target is not
an M1 device
Possible Cause
Possible Solution
M7.
enabled.
Signal integrity issues on JTAG
pins.
Make sure that the programming file
generated is for non-M7 enabled device.
Monitor VJTAG during programming;
measure JTAG signals for noise or
reflection.
File is for M1, but target device is
not M1.
Check that the target device is not M1
enabled.
Signal integrity issues on JTAG pins Make sure that the generated programming
file is for non-M1 enabled device.
Monitor VJTAG during programming;
measure JTAG signals for noise or
reflection.
0x8006
6
Failed to
verify
IDCODE.
File is not for P1, but target device
is a P1 device.
Make sure programming file generated is
Signal integrity issues on JTAG pins for M1 enabled device.
Target is not
a P1 device
0x801E
6
A3PE600
Engineering
Sample
Device
Detected.
This device is
supported
with pre-v8.3
SP1 STAPL
files only
0x8057
8
Failed Erase
Operation.
Monitor VJTAG during programming;
measure JTAG signals for noise or
reflection.
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.
0x8058
48
10
Failed to
program
FPGA array
at row <row
Check that the target device is P1 enabled.
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
for more information on transient
specifications.
Monitor VJTAG during programming;
measure JTAG signals for noise or
reflection.
Monitor related power supplies that cause
the issue during programming; check for
transients outside of Microsemi
specifications. See your device datasheet
FlashPro Express 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
Exit
Code
Exit
Message
Possible Cause
number>.
Unstable VCC_OSC (Fusion only)
Unstable VCC_ROSC voltage level
(SmartFusion only)
Possible Solution
for more information on transient
specifications.
Monitor VJTAG during programming;
measure JTAG signals for noise or
reflection.
Signal integrity issues on JTAG
pins.
0x805D
0x805E
0x807B
10
Failed to
Unstable VPUMP voltage level.
enable FPGA
Array.
Unstable VCC
Unstable VCC_OSC (Fusion only)
Unstable VCC_ROSC voltage level
(SmartFusion only)
Signal integrity issues on JTAG
pins.
0x8095
10
0x8096
0x8097
Failed to
disable FPGA Unstable VPUMP voltage level.
Array.
Unstable VCC
Unstable VCC_OSC (Fusion only)
Unstable VCC_ROSC voltage level
(SmartFusion only)
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.
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.
Signal integrity issues on JTAG
pins.
0x8061
0x8062
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.
0x801B
0x801C
0x806C
0x806D
0x806E
10
Error
programming
Embedded
Flash
Memory
Block (EFMB)
Unstable VCC_NVM/VCC_OSC
voltage level (Fusion only)
Unstable
VCC_ENVM/VCC_RCOSC voltage
level (SmartFusion only)
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.
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 on JTAG pins Monitor VJTAG during programming;
measure JTAG signals for noise or
FlashPro Express User's Guide
49
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
NVM corruption is possible when
writing from your design; check the
NVM status for confirmation.
Possible Solution
reflection.
Reset signal is not properly tied off in your
design.
Inspect device using Device Debug.
0x807D
0x807E
10
Error
programming
system init
and boot
clients
Unstable VCC
Unstable VCC_OSC (Fusion only)
Unstable VCC_ROSC voltage level
(SmartFusion only)
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 on JTAG pins Monitor VJTAG during programming;
measure JTAG signals for noise or
reflection.
Inspect device using Device Debug.
0x8069
0x806A
0x806B
10
Error
Programming file generated with an
programming older version of software
Embedded
Flash
Memory
Block (EMFB)
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
0x808E
0x808F
0x8090
0x8091
10
0x807F
0x8080
10
Error
programming
Embedded
Flash
Memory
Block (EFMB)
Error
programming
system init
and boot
clients
Try reprogramming
Contact Microsemi Technical Support
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
0x8059
0x805B
11
Verify 0 failed Unstable VPUMP voltage level.
at row <row
number>
Unstable VCC
Verify 1
failed at row
<row
number>.
50
Unstable VCC_OSC (Fusion only)
Unstable VCC_ROSC voltage level
(SmartFusion only)
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;
FlashPro Express 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
Exit
Code
Exit
Message
Possible Cause
Signal integrity issues on JTAG
pins.
0x8060
11
Device is programmed with a
Failed to
different design.
verify
FlashROM at Unstable VPUMP voltage level.
row
<FlashROM
Unstable VCC
row number>.
Unstable VCC_OSC (Fusion only)
Unstable VCC_ROSC voltage level
(SmartFusion only)
0x8075
0x8076
0x8077
11
Failed to
verify
Embedded
Flash
Memory
Block (EFMB)
Possible Solution
measure JTAG signals for noise or
reflection.
Run VERIFY_DEVICE_INFO to 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.
Signal integrity issues on JTAG
pins.
Monitor VJTAG during programming;
measure JTAG signals for noise or
reflection.
Device is programmed with a
different design.
Verify the device is programmed with the
correct data/design.
Unstable VCC
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.
Unstable VCC_NVM/VCC_OSC
(Fusion only)
Unstable VCC_ENVM/VCC_ROSC
voltage level (SmartFusion only)
Measure JTAG pins, and noise or reflection.
Signal integrity issues on JTAG
pins.
The EFMB data was modified in
your FPGA design after
programming. This could have
occurred during standalone verify.
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.
The target EFMB is locked with
FlashLock when running ACTION
PROGRAM_NVM_ACTIVE_ARRAY Inspect device using Device Debug.
or VERIFY_NVM_ACTIVE_ARRAY.
0x8085
0x8086
11
Failed to
verify system
init and boot
clients
Device is programmed with a
different design.
Verify the device is programmed with the
correct data/design.
Unstable VCC
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.
Unstable VCC_NVM/VCC_OSC
(Fusion only)
Unstable VCC_ENVM/VCC_ROSC
voltage level (SmartFusion only)
Measure JTAG pins, and noise or reflection.
Signal integrity issues on JTAG
FlashPro Express User's Guide
51
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
pins.
The EFMB data was modified in
your FPGA design after
programming. This could have
occurred during standalone verify.
Possible Solution
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.
The target EFMB is locked with
FlashLock when running ACTION
PROGRAM_NVM_ACTIVE_ARRAY Inspect device using Device Debug.
or VERIFY_NVM_ACTIVE_ARRAY.
0x8072
0x8073
0x8074
11
Failed to
Programming file generated with an
verify
older version of software
Embedded
Flash
Memory
Block (EFMB)
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
0x8083
0x8084
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
Inspect device using Device Debug.
Contact Microsemi Technical Support
0x8014
0x8015
11
Failed to
verify
calibration
data
Unstable VCC
Unstable VCC_NVM/VCC_OSC
(Fusion only)
Unstable VCC_ENVM/VCC_ROSC
voltage level (SmartFusion only)
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;
Signal integrity issues on JTAG pins measure JTAG signals for noise or
reflection.
Try reprogramming.
Workaround: Disable optional procedure
CHECK_AND_BACKUP_CALIB
0x805A
0x805C
52
11
Verify 0 failed Device is programmed with a
at row <row
different design
number> .
Unstable VPUMP voltage level.
Verify 1 failed
at row <row
Unstable VCC
number>
Run VERIFY_DEVICE_INFO to 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
FlashPro Express 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
Exit
Code
Exit
Message
Possible Cause
Unstable VCC_OSC (Fusion only)
Unstable VCC_ROSC voltage level
(SmartFusion only)
Possible Solution
specifications. See your device datasheet
for more information on transient
specifications.
Monitor VJTAG during programming;
Signal integrity issues on JTAG pins measure JTAG signals for noise or
reflection.
0x8063
0x8068
0x805F
14
-18
-20
Failed to
program
Silicon
Signature.
Failed to
program
security lock
settings.
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 VJTAG during programming;
measure JTAG signals for noise or
reflection.
Failed to
Incorrect AES key.
authenticate
the encrypted Signal integrity issues on JTAG
data.
pins.
Generate a programming file with the
correct AES key.
Failed to
verify
FlashROM at
row
<FlashROM
row number>.
Generate STAPL file with the latest version
of Designer/FlashPro; use the latest version
of FlashPro software.
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)
Monitor VJTAG during programming;
measure JTAG signals for noise or
reflection.
Program 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.
Measure JTAG pins and noise or reflection.
Signal integrity issues on JTAG
pins.
0x8065
-22
Failed to
Unstable VPUMP voltage level.
program pass
key.
Unstable VCC
Unstable VCC_OSC (Fusion only)
Unstable VCC_ROSC voltage level
(SmartFusion only)
Signal integrity issues on JTAG
pins.
FlashPro Express User's Guide
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.
53
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
0x8066
-23
Exit
Message
Failed to
program AES
key.
Possible Cause
Unstable VPUMP voltage level.
Unstable VCC
Unstable VCC_OSC (Fusion only)
Unstable VCC_ROSC voltage level
(SmartFusion only)
Possible Solution
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 pins and noise or reflection.
Signal integrity issues on JTAG
pins.
0x8055
0x8056
-24
Failed to
program
UROW.
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 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.
Make sure you mounted 0.01µF and
0.33µF caps on Vpump (close to the pin).
0x802A
-27
FlashROM
Write/Erase
is protected
by the
passkey.
A valid
passkey
needs to be
provided.
File contains no passkey and device Provide a programming file with a passkey
that matches the passkey programmed into
is secured with a passkey.
the device.
Passkey in the file does not match
device.
0x8025
-28
FPGA Array
Write/Erase
is protected
by the
passkey.
A valid pass
key needs to
be provided.
File contains no passkey and device Provide a programming file with a passkey
is secured with a passkey.
that matches the passkey programmed into
Passkey in the file does not match the device.
device.
0x802B
0x802D
-29
FlashROM
Read is
protected by
passkey.
A valid
passkey
needs to be
provided.
File contains no passkey and device Provide a programming file with a pass key
is secured with a passkey.
that matches the passkey programmed into
Passkey in the file does not match
the device
device.
54
FlashPro Express 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
Exit
Code
0x8024
0x8026
-30
FPGA Array
verification is
protected by
a passkey.
A valid
passkey
needs to be
provided.
File contains no passkey and device Provide a programming file with a passkey
that matches the passkey programmed into
is secured with a passkey.
Passkey in the file does not match the device.
device.
-31
Failed to
verify AES
key.
AES key in the file does not match
the device.
0x804B
0x8001
0x8007
Exit
Message
Possible Cause
Provide a programming file with an AES key
that matches the AES key programmed into
the device.
Unstable VCC
Unstable VCC_OSC (Fusion only)
Unstable VCC_ROSC voltage level
(SmartFusion only)
Unstable JTAG/VPUMP voltage
level.
0x8000
Possible Solution
-31
Failed to
verify AES
key.
Programming file generated with an
older version of software
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.
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
0x8020
0x8022
0x8028
-33
FPGA Array
File contains unencrypted array
encryption is data, but device contains AES key.
enforced. A
programming
file with
encrypted
FPGA array
data needs to
be provided.
Provide a programming file with an
encrypted FPGA Array data.
0x802C
0x802F
-34
FlashROM
File contains unencrypted
encryption is FlashROM data, but the device
enforced. A
contains an AES key.
programming
file with
encrypted
FlashROM
data needs to
be provided.
Provide a programming file with an
encrypted FlashROM data.
0x801F
0x804A
-35
Failed to
match pass
Provide a programming file with a pass key
that matches the pass key programmed into
FlashPro Express User's Guide
Pass key in file does not match
pass key in device.
55
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
key.
0x802E
0x8030
-36
FlashROM
Encryption is
not enforced.
Possible Solution
the device.
File contains encrypted FlashROM,
but device encryption is not
enforced for FlashROM
Regenerate security programming file with
proper AES key.
Program device security.
Cannot
guarantee
valid AES key
present in
target device.
Retry programming FlashROM with
encrypted programming file.
Unable to
proceed with
Encrypted
FlashROM
programming.
0x8021
0x8023
0x8027
0x8029
-37
FPGA Array
Encryption is
not enforced.
File contains encrypted FPGA
Array, but the device encryption is
not enforced for FPGA Array.
Regenerate security programming file with
proper AES key.
Program device security.
Cannot
guarantee
valid AES key
present in
target device.
Retry programming FPGA Array with
encrypted programming file.
Unable to
proceed with
Encrypted
FPGA Array
verification.
0x8067
-38
Failed to
Unstable VPUMP voltage level.
program pass
key.
Unstable VCC
Unstable VCC_OSC (Fusion only)
Unstable VCC_ROSC voltage level
(SmartFusion only)
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 pins and noise or reflection.
Signal integrity issues on JTAG
pins.
Bad device.
0x806F
0x8070
0x8071
0x8081
0x8082
0x8089
-39
ERROR: 2 or
more errors
found on this
page
Unstable VCC_NVM/VCC_OSC
voltage (Fusion only)
Unstable VCC_ENVM/VCC_ROSC
(SmartFusion only)
NVM reset signal is floating in user
design
56
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.
Bias NVM reset to a logic state in user
FlashPro Express 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
Exit
Code
Exit
Message
Possible Cause
Possible Solution
design.
2 or more ECC errors found when
reading the eNVM
0x8010
-39
ERROR: 2 or
more errors
found on this
page.
2 or more ECC errors found when
reading the master calibration data
Try reprogramming.
The master calibration data has been
corrupted. Try restoring master calibration
from backup, if it exists, by running
RECOVER_CALIB.
Workaround: Disable optional procedure
CHECK_AND_BACKUP_CALIB
0x8013
-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
0x8078
0x8079
0x807A
0x8087
0x8088
-40
Embedded
Flash
Memory
Block MAC
Failure.
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.
0x8002
0x8003
-42
Failed to
File security settings do not match
verify security device.
settings.
Provide a programming file with security
setting that match the security settings
programmed into the device.
0x8093
-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
0x8004
-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.
0x8049
-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.
0x8054
-45
Device
package
does not
match the
programming
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.
0x8033
0x8038
0x803D
-46
Embedded
Flash
Memory
File contains no pass key or
Provide a programming file with the correct
incorrect pass key but EFMB read is pass key.
secured with a pass key.
FlashPro Express User's Guide
57
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
0x8042
0x8045
0x8046
0x8047
0x8048
0x8034
0x8039
0x803E
0x8043
Exit
Message
Possible Cause
Possible Solution
Block X Read
is protected
by pass key.
A valid pass
key needs to
be provided.
-46
Embedded
File contains encrypted EFMB for
Flash
block X but the device encryption is
Memory
not enforced for EFMB block X.
Block (EFMB)
block X Read
is not
protected by
pass key.
Regenerate security programming file with
the proper AES key.
Program device security. Retry
programming with EFMB block X with
encrypted programming file.
EFMB
content is not
secure after
encrypted
programming.
Unable to
proceed with
encrypted
NVM
programming.
0x8032
0x8037
0x803C
0x8041
-47
Embedded
Flash
Memory
Block (EFMB)
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.
0x8031
0x8036
0x803B
0x8040
-48
Embedded
File contains no pass key or
Flash
incorrect pass key, but device is
Memory
secured with a pass key.
Block (EFMB)
block X Write
is protected
by 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.
A valid pass
key needs to
be provided.
0x8035
58
-49
Embedded
File contains encrypted EFMB for
Regenerate security programming file with
FlashPro Express 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
Exit
Code
0x803A
0x803F
0x8044
Exit
Message
Possible Cause
Flash
block X, but the device encryption is
Memory
not enforced for EFMB block X.
Block (EFMB)
block X
Encryption is
not enforced.
Possible Solution
proper AES key.
Program device security. Retry
programming EFMB block X with encrypted
programming file.
Cannot
guarantee
valid AES key
present in
target device.
Unable to
proceed with
Encrypted
EFMB
programming.
0x801A
-50
No backup
calibration
data found or
backup
calibration
data has
been
corrupted
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
8x804E
-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.
0x804F
-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.
0x8050
-53
Failed to
access
Embedded
Flash
Memory.
(AFS1500
only)
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.
0x8051
-54
Failed to
access
Embedded
FPGA Array is accessing the target
EFMB block while attempting
programming.
If programming the EFMB while the FPGA
is active is not required, then use actions
PROGRAM_NVM or VERIFY_NVM.
FlashPro Express User's Guide
59
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
Flash
Memory.
Possible Cause
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.
Possible Solution
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.
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.
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.
0x808A
0x8094
-55
Failed to read Programming file generated with an
Embedded
older version of software
Flash
Memory
Block (EFMB)
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
0x808B
-55
Failed to read Unstable VPUMP voltage level.
Embedded
Flash
Unstable VCC
Memory
Block (EFMB) Unstable VCC_OSC (Fusion only)
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.
Unstable VCC_ROSC voltage level
(SmartFusion only)
Monitor VJTAG during programming;
measure JTAG signals for noise or
Signal integrity issues on JTAG pins reflection.
0x808C
-55
Failed to read Internal errror
Embedded
Flash
Memory
Block (EFMB)
Contact Microsemi Technical Support
0x8011
-56
Failed to read
calibration
data
Try reprogramming.
0x8012
60
-56
Failed to read Unstable VCC
Workaround: Disable optional procedure
CHECK_AND_BACKUP_CALIB
Monitor related power
FlashPro Express 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
Exit
Code
Exit
Message
calibration
data
Possible Cause
Possible Solution
supplies that cause the
issue during
programming; check for
transients outside of
Microsemi specifications.
See your device
datasheet for more
information on transient
specifications.
Unstable VCC_NVM/VCC_OSC
(Fusion only)
Unstable VCC_ENVM/VCC_ROSC
voltage level (SmartFusion only)
Signal integrity issues on JTAG pins
Measure JTAG voltages,
noise, and reflection.
Try reprogramming.
Workaround: Disable
optional backup
procedure
CHECK_BACKUP_CALIB
0x808D
0x8092
-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
Provide a programming file with a Pass Key
that matches the Pass Key programmed
into the device
Pass Key in the file does not match
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.
Table 4 · Exit Codes for SmartFusion, IGLOO, ProASIC3 and Fusion Family Devices in pre-v8.6 Software
Exit
Code
Exit Message
0
Passed (no error).
1
A physical chain
does not match the
expected set up
from the STAPL
file.
Also known as
Checking Chain
Error.
Possible Cause
Possible Solution
Physical chain configuration has
been altered. Something has
become disconnected in the chain.
The specific IR length of nonMicrosemi devices may be
incorrect.
The order of the specified chain
may be incorrect.
FlashPro Express User's Guide
61
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
5
Exit Message
Failed to enter
programming
mode.
Possible Cause
Unstable VPUMP voltage level.
Signal integrity issues on JTAG
pins.
Older software or programming file
used.
6
Failed to verify
IDCODE.
Signal integrity issues on JTAG
pins.
Possible Solution
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.
Measure JTAG pins,
noise and reflection.
8
Failed Erase
Operation.
Signal integrity issues on JTAG
pins.
Monitor VPUMP voltage
during programming.
Measure JTAG
voltages, noise, and
reflection.
10
Failed to program
FPGA array at row
", rowNumber,"."
Signal integrity issues on JTAG
pins.
Monitor VPUMP voltage
during programming.
Measure JTAG
voltages, noise, or
reflection.
10
Failed to enable
FPGA Array.
Signal integrity issues on JTAG
pins.
Monitor VPUMP voltage
during programming.
Measure JTAG
voltages, noise, or
reflection.
10
Failed to program
FlashROM.
Signal integrity issues on JTAG
pins.
Monitor VPUMP voltage
during programming.
Measure JTAG
voltages, noise, and
reflection.
11
Verify 0 failed at
row",rowNumber,"."
Verify 1 failed at
row",rowNumber,"."
Failed to verify
FlashROM at
row",from
rowNumber-1.
Device is programmed with a
different design.
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 .
Failed to program
Silicon Signature.
Signal integrity issues on JTAG
pins.
14
62
Signal integrity issues on JTAG
pins.
Monitor VPUMP voltage
during programming.
FlashPro Express 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
Failed to program
security lock
settings.
-18
Failed to
authenticate the
encrypted data.
Possible Solution
Measure JTAG
voltages, noise, and
reflection.
Incorrect AES key.
Signal integrity issues on JTAG
pins.
Generate a
programming file with
the correct AES key.
Measure JTAG
voltages, noise and
reflection
-20
-22
Failed to verify
FlashROM at row
",
FRomRowNumber1.
Device is programmed with a
different design.
Program with the
correct data/design.
Signal integrity issues on JTAG
pins.
Monitor VPUMP level
during programming.
Measure JTAG pins and
noise or reflection.
Failed to program
pass key.
Unstable VPUMP voltage level.
Monitor VPUMP voltage
during programming.
Signal integrity issues on JTAG
pins.
-23
Failed to program
AES key.
Unstable VPUMP voltage level.
Signal integrity issues on JTAG
pins.
Measure JTAG
voltages, noise, and
reflection.
Monitor VPUMP
voltage during
programming.
Measure JTAG pins
and noise or reflection.
-24
Failed to program
UROW.
Unstable VPUMP voltage level.
Signal integrity issues on JTAG
pins.
Monitor VPUMP voltage
during programming.
Measure JTAG
voltages, noise, and
reflection.
Make sure you mounted
0.01ìF and 0.33ìF caps
on Vpump (close to the
pin).
-25
Failed to enter
Signal integrity issues on JTAG
programming mode pins.
Measure JTAG
voltages, noise, and
reflection.
-26
Failed to enter
Signal integrity issues on JTAG
programming mode pins.
Measure JTAG
voltages, noise, and
reflection.
-27
FlashROM
Write/Erase is
File contains no passkey and device Provide a programming
is secured with a passkey.
file with a passkey that
FlashPro Express User's Guide
63
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
protected by the
passkey.
A valid passkey
needs to be
provided.
Passkey in the file does not match
device.
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 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.
-31
Failed to verify
AES key.
AES key in the file does not match
the device.
Provide a programming
file with an AES key that
matches the AES key
programmed into the
device.
Unstable JTAG/VPUMP voltage
level.
Monitor
VPUMP/VJTAG voltage
during programming.
Measure JTAG
voltages, noise, and
reflection.
-32
Failed to verify
IDCODE.
Target is an M7
device
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
64
Failed to verify
IDCODE.
File is not for M1, but target device
is an M1 device.
Check that the target
device is M1 enabled.
FlashPro Express 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
Target is an M1
device
Possible Cause
Signal integrity issues on JTAG
pins.
Possible Solution
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
File is not for target device.
Check the target device.
Make sure programming
Signal integrity issues on JTAG pins file generated for target
device.
Measure JTAG
voltages, noise, and
reflection.
-32
Failed to verify
IDCODE.
The target is not
an 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 programming
file generated is for non
M7 enabled device.
Measure JTAG
voltages, noise, and
reflection.
-32
Failed to verify
File is for M1, but target device is
IDCODE.
not an M1 device.
The target is not an
M1 device
Signal integrity issues on JTAG
pins.
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
enforced. A
programming file
with encrypted
FPGA array data
needs to be
provided.
File contains unencrypted array
data, but device contains AES key.
Provide a programming
file with an encrypted
FPGA Array data.
-34
FlashROM
encryption is
enforced. A
programming file
with encrypted
FlashROM data
needs to be
File contains unencrypted
FlashROM data, but the device
contains an AES key.
Provide a programming
file with an encrypted
FlashROM data.
FlashPro Express User's Guide
65
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
provided.
-35
Failed to match
pass key.
Pass key in file does not match
pass key in device.
Provide a programming
file with a pass key that
matches the pass key
programmed into the
device.
-36
FlashROM
Encryption is not
enforced.
File contains encrypted FlashROM,
but device encryption is not
enforced for FlashROM
Regenerate security
programming file with
proper AES key.
Cannot guarantee
valid AES key
present in target
device.
Program device
security.
Retry programming
FlashROM with
encrypted programming
file.
Unable to proceed
with Encrypted
FlashROM
programming.
-37
FPGA Array
Encryption is not
enforced.
File contains encrypted FPGA
Array, but the device encryption is
not enforced for FPGA Array.
Cannot guarantee
valid AES key
present in target
device.
Program device
security.
Retry programming
FPGA Array with
encrypted programming
file.
Unable to proceed
with Encrypted
FPGA Array
verification.
-38
Failed to program
pass key.
Unstable VPUMP voltage level.
Signal integrity issues on JTAG
pins.
Bad device.
-39
66
Failed to verify
Embedded Flash
Memory Block
(EFMB).
Regenerate security
programming file with
proper AES key.
Device is programmed with a
different design.
Signal integrity issues on JTAG
pins.
Monitor VPUMP voltage
during programming.
Measure JTAG pins
and noise or reflection.
Verify the device is
programmed with the
correct data/design.
The EFMB data was modified
through user FPGA design after
programming; this could occur
during standalone verify.
Monitor VPUMP
voltage during
programming.
Measure JTAG pins
and noise or reflection.
The target EFMB block is locked
with FlashLock when running
ACTION
Run DEVICE_INFO to
confirm if the target
EFMB block is locked
FlashPro Express 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
PROGRAM_NVM_ACTIVE_ARRAY with FlashLock (pass
or VERIFY_NVM_ACTIVE_ARRAY. 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.
-40
Embedded Flash
Memory Block
MAC Failure.
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.
-41
Error programming
Embedded Flash
Memory Block.
(EFMB)
Signal integrity issues on JTAG
pins.
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.
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
programming file.
-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
Provide a programming
incorrect pass key but EFMB read is file with the correct pass
secured with a pass key.
key.
-47
Embedded Flash
Memory Block,
block X encryption
is enforced. A
programming file
The programming EFMB data is not
encrypted, but the device contains
an AES key with encryption
enforced.
FlashPro Express User's Guide
Provide a programming
file with encrypted
EFMB data.
67
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
with encrypted
EFMB data needs
to be provided.
-48
Embedded Flash
Memory Block
(EFMB) block X
Write is protected
by pass key.
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.
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.
A valid pass key
needs to be
provided.
-49
Embedded Flash
Memory Block
(EFMB) block X
Encryption is not
enforced.
Program device
security. Retry
programming EFMB
block X with encrypted
programming file.
Cannot guarantee
valid AES key
present in target
device.
Unable to proceed
with Encrypted
EFMB
programming.
-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.
-53
Failed to access
Embedded Flash
Memory.
(AFS1500 only)
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
68
FlashPro Express 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 Exit Codes
Exit
Code
Exit Message
Possible Cause
Possible Solution
blocks 0, 1, or 2, but do
not use block 3.
-54
Failed to access
Embedded Flash
Memory.
FPGA Array is accessing the target
EFMB block while attempting
programming.
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.
NVM reset signal is stuck in design.
Verify that the NVM
reset signal in the
design is not stuck.
ProASICPLUS Exit Codes
PLUS
The table below lists the exit codes for ProASIC
Table 5 · ProASIC
Exit Code
Exit Message
PLUS
devices.
Family Devices Exit Codes
Possible Cause
Possible Solution
0
This message
means passed.
This does not
indicate an error.
1
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.
2
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.
3
This occurs when
PLUS
using ProASIC
Connect was set up for a
ProASIC device and the
Set up for a
PLUS
ProASIC
device.
FlashPro Express User's Guide
69
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
devices.
device is actually
PLUS
ProASIC
.
5
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.
6
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.
7
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
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.
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.
Re-generate STAPL
file from Designer 6.1
SP1.
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.
70
FlashPro Express 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 Exit Codes
Exit Code
Exit Message
Possible Cause
Possible Solution
This error may occur if
your power supply
cannot source the correct
current for programming.
8
FPGA failed during The device is secured,
Load the correct
the erase
and the corresponding
STAPL file.
operation.
STAPL file is not loaded.
The device has been
permanently secured and
cannot be unlocked.
11
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.
12
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.
14
Program security
failure.
15
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.
17
The device has
been secured.
Write-security is
enabled.
The device is secured
and the wrong key or
STAPL file was entered.
The device is damaged.
FlashPro Express User's Guide
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.
Load the correct
STAPL file.
71
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
-54
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)
-90
Unexpected RCK
detected.
Noise on the RCK signal.
You connected a CLK
source to the RCK 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.
Disconnect the RCK
and make sure TCK
has a clean signal.
Separate FlashPros
away from each other
while they are
programming Internal
ISP.
Connect programmer
as an Admin in
FlashPro.
-91
Calibration data
parity error.
Device is damaged.
Replace the device.
Null
Several FlashPros are
programming at the
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.
Cable to target is
not connected
properly.
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
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
72
FlashPro Express 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 Exit Codes
Exit Code
Exit Message
Could not connect
to programmer on
port lp1 or parallel
port device does
not support IEEE1284 negotiation
protocol
FlashPro Express User's Guide
Possible Cause
Possible Solution
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.
may need to replace
the first device (the
devices closest to the
TDO of the
programming header)
in the chain.
Remove the dongle.
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.
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
73
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
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.
External voltage
detected on
<Supply>
The voltage supply for
Set appropriate
the FPGA is driven by
options in the
another source (board,
Connect menu.
external power-supply),
but the user forgot to turn
off the supply in the
Connect menu.
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,
74
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.
FlashPro Express 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 Exit Codes
Exit Code
Exit Message
Possible Cause
Possible Solution
Post IR or Post
DR.
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.
Executing action
xxx with serial
index/action xx
failed.
The STAPL runtime
failed.
No Vpump voltage
source is detected.
Select the Vpump in
the Programmer
setting. Make sure
the external Vpump
is properly turned on.
Vpump short
detected.
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.
Check FlashPro Lite
version being used.
Use FlashPro Lite
Rev C or modify the
STAPL file to 4 MHz.
xxx Mhz TCK
frequency in this
STAPL file is not
supported by the
Modify STAPL file to
1, 2, or 4 MHz.
FlashPro Express User's Guide
75
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
FlashPro Lite
RevC detected. It
supports only 1, 2
or 4 Mhz TCK
frequency.
76
Cannot find the
serial Index/Action
xxx in STAPL file.
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.
Duplicated serial
Index/Action xxx
was removed.
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.
Using local backup
copy xxx
Cannot find original copy. Check for available
space on the disk.
Check that write
permissions are
enabled.
FlashPro cannot
Name is already in use.
rename the
programmer/device
with an existing
name.
Create a new name.
FlashPro cannot
Invalid character used in
rename the
programmer/device
programmer/device name.
with an invalid
character.
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
FlashPro Express 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 Exit Codes
Exit Code
Exit Message
Possible Cause
Possible Solution
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.
FlashPro Express User's Guide
Use a STAPL file for
your device that is
supported by
FlashPro.
77
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.
Note: 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 6 · DC Characteristic for FlashPro5/4/3/3X
Description
Symbol
Min
Max
Unit
Input low voltage, TDO
VIL
-0.5
Input high voltage, TDO
VIH
0.65*VJTAG 3.6
V
Input current, TDO
IIL, IIH
-20
+20
mA
40
pF
+3.6
V
250
mA
V
Input capacitance, TDO
Output voltage, VPUMP,
operating
VPP
Output current, VPUMP
IPP
+3.0
0.35*VJTAG V
VJTAG = 1.5V
Output low voltage, TCK, TMS,
TDI, 100µA load
VOL
0.0
0.2
Output low voltage, TCK, TMS,
TDI, 4mA load
VOL
0.0
0.30*VJTAG V
Output high voltage, TCK, TMS,
TDI, 100µA load
V
VJTAG-0.2
VJTAG
V
Output high voltage, TCK, TMS,
TDI, 4mA load
VOH
0.70*VJTAG VJTAG
V
Output current, TCK, TMS, TDI
IOL,
IOH
-4
+4
mA
Output low voltage, TCK, TMS,
TDI, 100µA load
VOL
0.0
0.2
V
Output low voltage, TCK, TMS,
TDI, 6mA load
VOL
0.0
0.3
V
VJTAG = 1.8V
78
FlashPro Express 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 Lite
Description
Symbol
Min
Max
Unit
Output high voltage, TCK, TMS,
TDI, 100µA load
VOH
VJTAG-0.2
VJTAG
V
Output high voltage, TCK, TMS,
TDI, 6mA load
VOH
1.25
VJTAG
V
Output current, TCK, TMS, TDI
IOL,
IOH
-6
+6
mA
Output low voltage, TCK, TMS,
TDI, 100µA load
VOL
0.0
0.2
V
Output low voltage, TCK, TMS,
TDI, 8mA load
VOL
0.0
0.6
V
Output high voltage, TCK, TMS,
TDI, 100µA load
VOH
VJTAG-0.2
VJTAG
V
Output high voltage, TCK, TMS,
TDI, 8mA load
VOH
1.8
VJTAG
V
Output current, TCK, TMS, TDI
IOL,
IOH
-8
+8
mA
Output low voltage, TCK, TMS,
TDI, 100µA load
VOL
0.0
0.2
V
Output low voltage, TCK, TMS,
TDI, 8mA load
VOL
0.6
V
Output high voltage, TCK, TMS,
TDI, 100µA load
VOH
VJTAG-0.2
VJTAG
V
Output high voltage, TCK, TMS,
TDI, 8mA load
VOH
2.4
VJTAG
V
Output current, TCK, TMS, TDI
IOL,
IOH
-8
+8
mA
VJTAG = 2.5V
VJTAG = 3.3V
DC Characteristics for FlashPro Lite
Table 7 · DC Characteristic for FlashPro Lite
Description
Symbol
Min
Max
Unit
Input low voltage, TDO
VIL
-0.5
0.7
V
Input high voltage, TDO
VIH
1.7
5.0
V
FlashPro Express User's Guide
79
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
Input current, TDO
IIL, IIH
Min
Max
-10
Unit
+10
uA
40
pF
Input capacitance, TDO
Input voltage, VDD, operating (see note)
+2.3
+3.5
V
Input voltage, VDD, power off
-1.0
+1.0
V
500
mA
Input current, VDD
IVDD
Output voltage, VPP, operating
VPP
+15.9
+16.5
V
Output voltage, VPN, operating
VPN
-13.8
-13.4
V
Output current, IPP
IPP
0
35
mA
Output current, IPN
IPN
0
-15
mA
Output low voltage, TCK, TMS, TDI, 100uA load
VOL
0.0
0.2
V
Output low voltage, TCK, TMS, TDI, 1mA load
VOL
0.0
0.5
V
Output low voltage, TCK, TMS, TDI, 2mA load
VOL
0.0
0.8
V
Output high voltage, TCK, TMS, TDI, 100uA load
VOH
2.1
2.5
V
Output high voltage, TCK, TMS, TDI, 1mA load
VOH
1.9
2.5
V
Output high voltage, TCK, TMS, TDI, 2mA load
VOH
1.6
2.5
V
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 8 · DC Characteristic for FlashPro
Description
Symbol
Min
Max
Unit
Input low voltage, TDO
VIL
-0.5
0.30 *
VDDP
V
Input high voltage, TDO
VIH
0.70 *
VDDP
5.5
V
Input current, TDO
IIL, IIH
-10
+10
uA
Input voltage, VDDP, VDDL
0
5.25
V
Input voltage, VPP
0
21.0
V
Input voltage, VPN
-21.0
80
V
FlashPro Express 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
Symbol
Input current, VDDP, VDDL, VPN, VP
IVCC
Output voltage range, VDDP
VDDP
Output voltage range, VPP
Output voltage range, VPN
Min
Max
Unit
5.0
mA
1.5
3.3
V
VPP
15.0
18.0
V
VPN
-16.0
-12.0
V
100 / ±50
mV
Output voltage resolution / Acccuracy
Output current, IDDP
IDDP
-135
1
+135
mA
Output current, IDDL
IDDL
-135
1
+135
mA
Output current, IPP
IPP
-2701
+270
mA
Output current, IPN
IPN
-270
+270
Output low voltage, TCK, TMS, TDI, OUT0,
nTRST
VOL
0.0
0.4
V
Output high voltage, TCK, TMS, TDI, OUT0, VOH
nTRST
0.85 *
VDDP
+ 0.3
VDDP
V
Output current, TCK, TMS, TDI, OUT0,
nTRST
-12
+12
mA
IOL,
IOH
1
1
mA
Note: (1): When power supply mode is set to ABI_GROUND.
Note: * - 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.
Note: (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 Express User's Guide
81
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 17 · FlashPro5 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 9 · FlashPro5 Signal Description
Signal
Description
VPUMP
3.3V Programming voltage
GND
Signal reference
TCK/SCK
JTAG clock; SPI clock
TDI/SDI
JTAG data input to device; SPI MOSI
TDO/SDO
JTAG data output from device; SPI MOSI
TMS/SS#
JTAG mode select; SPI Chip Select
nTRST
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
82
FlashPro Express 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):
Figure 18 · 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 10 · FlashPro4 Signal Description
Signal
Description
VPUMP
3.3V Programming voltage
GND
Signal reference
TCK
JTAG clock
TDI
JTAG data input to device
TDO
JTAG data output from device
TMS
JTAG mode select
nTRST
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 Express User's Guide
83
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.
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.
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 19 · 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 11 · FlashPro3 Signal Description
Signal
Description
VPUMP
3.3V Programming voltage
GND
Signal reference
TCK
JTAG clock
TDI
JTAG data input to device
TDO
JTAG data output from device
TMS
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
84
FlashPro Express 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
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.
FlashPro Lite
For FlashPro Lite, the existing 26-pin connector is shown in the figure below.
Figure 20 · 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 12 · FlashPro Lite Signal Description
Signal
Description
VDDP
VDD supply for logic I/O pads
VDDL
VDD supply for core
VPP
Positive programming supply (+16.5V)
VPN
Negative programming supply(-13.8V)
GND
Signal reference
SENSE
Input from target board to programmer to indicate connection to ground
TCK
JTAG clock
FlashPro Express User's Guide
85
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
Description
TDI
JTAG data input to device
TDO
JTAG data output from device
TMS
JTAG mode select
nTRST
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
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.
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.
Figure 21 · 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 13 · FlashPro Signal Description
Signal
Description
VDDP
VDD supply for logic I/O pads
VDDL
VDD supply for core
86
FlashPro Express 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
Signal
Description
VPP
Positive programming supply (+16.5 V)
VPN
Negative programming supply (-13.8 V)
GND
Signal reference
SENSE
Input from target board to programmer to indicate connection to
ground
TCK
JTAG clock
TDI
JTAG data input to device
TDO
JTAG data output from device
TMS
JTAG mode select
nTRST
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
2.5V, 2.5V/3.3V,
N/C
Programmer does not connect to these pins
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.
FlashPro 5/4/3/3X Characteristics
Table 14 · JTAG Switching Characteristics for FlashPro5/4/3/3X
Description
Symbol
Min
Max
Output delay from TCK to TDI, TMS
TTCKTDI
-2
TDO setup time before TCK rising, VJTAG=3.3
TTDOTCK
12
ns
TDO setup time before TCK rising, VJTAG=1.5
TTDOTCK
14.5
ns
TDO hold time after TCK rising
TTCKTDO
0
ns
TCK period
TTCK
41.7
FlashPro Express User's Guide
2
Unit
10667
ns
ns
87
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 15 · JTAG Switching Characteristics for FlashPro and FlashPro Lite
Description
Symbol
Min
Output delay from TCK falling to TDI, TTCKTDI
TMS
-2
TDO setup time before TCK rising
5.0
TTDOTCK
TDO hold time after TCK rising
TCK period
TTCKTDO 0
TTCK
40
Max
2
Unit
ns
ns
ns
10240 ns
Illustration of the JTAG Switching Characteristics
The figure below is an illustration of the JTAG switching characteristics.
Figure 22 · JTAG Switching Characteristics
.
88
FlashPro Express 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 Express Start Page
FlashPro Express Reference
FlashPro Express Start Page
The FlashPro Express Start Page is the first page to show when the tool starts up. This page provides the
interface for loading a project into the tool by either navigating to the project location, or clicking on one of
the recently opened projects.
Figure 23 · FlashPro Express Start Page
FlashPro Express Project Menu
Command
Function
Create Job Project from
Programming Job
New job project folder with programming job name will
be created at the specified location.
Open Job Project
Loads a job project into the tool by reading the
FlashPro Express User's Guide
89
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
Function
information in user specified .pro file.
Close Job Project
Closes the current job project
Save Job Project
Saves the current job project
Set Log File
Sets the location of the Log file to your specified
location.
Export Log File
Exports the Log file to your specified location.
Execute Script
Runs your specified Tcl script.
Export Script File
Exports all commands run in this session to your
specified path as a Tcl script
Exit
Exits FlashPro Express
FlashPro Express Edit Menu
Command
Clear Log Window
Function
Clears the Log window
FlashPro Express View Menu
The View menu shows or hides the FlashPro Express GUI elements.
Command
Log Window
Function
Shows/hides the Log window
FlashPro Express Tools Menu
Command
Function
Programmer
Settings
Opens the Programmer Settings dialog box; enables you to set
options for all types of supported Microsemi programmers
Run
Runs the current Programming Action.
90
FlashPro Express 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 Express Help Menu
FlashPro Express Help Menu
Command
Function
Help Topics
Opens the help
Microsemi Technical
Support
Opens the Microsemi technical support site.
Microsemi Web Site
Opens the Microsemi website in your default browser
User Guide
Opens the FlashPro Express User Guide.
Check for Software
Updates
Checks for software updates (works only if you are
connected to the internet)
About FlashPro Express
Lists the FlashPro Express release information
FlashPro Express Log Window and Status Bar
FlashProExpress Log Window
The FlashPro Express log window shows status messages for user activity. Click on the appropriate tab
(Messages, Errors, Warning, Info) to filter messages by type.
•
Use the right-click menu to copy text, clear the log, and scroll the log.
•
Use the def variable LOG_WINDOW_BUFFER_SIZE to set the buffer size.
•
Use the View menu to show or hide the Log window.
FlashProExpress Status Bar
The Status Bar at the bottom displays the status of the load project action.
FlashPro Express User's Guide
91
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.
Product Support
The Microsemi SoC Products Group backs its products with various support services including a Customer
Technical Support Center and Non-Technical Customer Service. This appendix contains information about
contacting the SoC Products Group and using these support services.
Contacting the Customer Technical Support Center
Microsemi staffs its Customer Technical Support Center with highly skilled engineers who can help answer
your hardware, software, and design questions. The Customer Technical Support Center spends a great
deal of time creating application notes and answers to FAQs. So, before you contact us, please visit our
online resources. It is very likely we have already answered your questions.
Technical Support
Microsemi customers can receive technical support on Microsemi SoC products by calling Technical
Support Hotline anytime Monday through Friday. Customers also have the option to interactively submit and
track cases online at My Cases or submit questions through email anytime during the week.
Web: www.actel.com/mycases
Phone (North America): 1.800.262.1060
Phone (International): +1 650.318.4460
Email: [email protected]
ITAR Technical Support
Microsemi customers can receive ITAR technical support on Microsemi SoC products by calling ITAR
Technical Support Hotline: Monday through Friday, from 9 AM to 6 PM Pacific Time. Customers also have
the option to interactively submit and track cases online at My Cases or submit questions through email
anytime during the week.
Web: www.actel.com/mycases
Phone (North America): 1.888.988.ITAR
Phone (International): +1 650.318.4900
Email: [email protected]
Non-Technical Customer Service
Contact Customer Service for non-technical product support, such as product pricing, product upgrades,
update information, order status, and authorization.
Microsemi’s customer service representatives are available Monday through Friday, from 8 AM to 5 PM
Pacific Time, to answer non-technical questions.
Phone: +1 650.318.2470
92
FlashPro Express User's Guide
Microsemi Corporate Headquarters
One Enterprise, Aliso Viejo,
CA 92656 USA
Within the USA: +1 (800) 713-4113
Outside the USA: +1 (949) 380-6100
Sales: +1 (949) 380-6136
Fax: +1 (949) 215-4996
E-mail: [email protected]
©2015 Microsemi Corporation. All
rights reserved. Microsemi and the
Microsemi logo are trademarks of
Microsemi Corporation. All other
trademarks and service marks are the
property of their respective owners.
Microsemi Corporation (Nasdaq: MSCC) offers a comprehensive portfolio of semiconductor
and system solutions for communications, defense & security, aerospace and industrial
markets. Products include high-performance and radiation-hardened analog mixed-signal
integrated circuits, FPGAs, SoCs and ASICs; power management products; timing and
synchronization devices and precise time solutions, setting the world’s standard for time;
voice processing devices; RF solutions; discrete components; security technologies and
scalable anti-tamper products; Power-over-Ethernet ICs and midspans; as well as custom
design capabilities and services. Microsemi is headquartered in Aliso Viejo, Calif., and has
approximately 3,400 employees globally. Learn more at www.microsemi.com.
Microsemi makes no warranty, representation, or guarantee regarding the information contained herein
or the suitability of its products and services for any particular purpose, nor does Microsemi assume
any liability whatsoever arising out of the application or use of any product or circuit. The products sold
hereunder and any other products sold by Microsemi have been subject to limited testing and should
not be used in conjunction with mission-critical equipment or applications. Any performance
specifications are believed to be reliable but are not verified, and Buyer must conduct and complete all
performance and other testing of the products, alone and together with, or installed in, any endproducts. Buyer shall not rely on any data and performance specifications or parameters provided by
Microsemi. It is the Buyer’s responsibility to independently determine suitability of any products and to
test and verify the same. The information provided by Microsemi hereunder is provided “as is, where is”
and with all faults, and the entire risk associated with such information is entirely with the Buyer.
Microsemi does not grant, explicitly or implicitly, to any party any patent rights, licenses, or any other IP
rights, whether with regard to such information itself or anything described by such information.
Information provided in this document is proprietary to Microsemi, and Microsemi reserves the right to
make any changes to the information in this document or to any products and services at any time
without notice.
5-02-00560-2/07.15
">