Dataman 448PRO2AP-AU, User Manual, Page: 102 / 160

102
Selecting an action
After successful loading the STAPLE file, select an intending operation action in Device
operation options (Alt+O short key)/STAPL configuration.... (STAPL configuration ...). For
device programming select PROGRAM from action list. List of all the actions for the
programming file with describe can be found in ACTEL FlashPro User’s Guide on
<http://www.actel.com>.
Running an action
Click Play STAPL button to run selected action. Successful operation (e.g. programming) is
terminated with printout “Exit Code = 0... Success” to log window.
Information about converting PDB file to JAM STAPLE for ACTEL
devices
Actel PDB file is a proprietary file format that can be supported by Actel programmers only,
e.g. FlashPro programmer. PG4UW control program can program Actel devices only with Jam
STAPL file. Therefore a file conversion between PDB and STAPL is necessary.
Converting PDB file to Jam STAPL file for ACTEL devices:
 install software tool FlashPro (component of Actel Libero tool suite or can be downloads from
<http://www.actel.com> as a standalone version)

run FlashPro
 click the New Project button or from the File menu choose New Project and type in the name
of your project in the Project Name field. Select desired programming mode – single device
or chain and click OK
 from the Configuration menu, choose Load Programming File and select corresponding
*.pdb file to convert

from the File menu, choose Export/Export Single Device STAPL File... Type in file name
and click Save button for export STAPL file to the directory you specified
 Conversion of PDB file to STAPL has finish and created *.stp file can be used for
programming Actel device.
Frequently asked questions about Actel
Q: How can be identify/verify already programmed Actel device?
A: There are several possible options to get this done. Each option (action) is varying from
each other in method of comparing already programmed Actel device with loaded STAPL
file. There are the following appropriate mentioned actions in a STP file:
DEVICE_INFO: read and among other things display to log window also the checksum of
the programming environment programmed into the device. This value can be manually
compared by user with the value in the header of the STAPL file (can be viewed in
Information window). Caution: Value of the programmed device checksum isn't counting
from existing (maybe corrupted) device data content however this value is stored during
programming to special memory localization and is only reading!
VERIFY_DEVICE_INFO: similar options as previous with difference in automatic
comparison of programmed device checksum and STAPLE file checksum. The result of
comparison can be either success or error window message.
VERIFY: the safest but the slowest (~tens of seconds depends on device capacity against
~1 second in options 1 and 2) option for data compare programmed device content with
content of STAPLE file. Comparison selected family features(FPGA Array, targeted
FlashROM pages, security setting...) is executing bit by bit and verification process can be
early terminated if data mismatch occurs with writing error message to log window.