Achronix ACE Version 5.0 User Manual
Page 187
Views
Chapter 3. Concepts
Download View Options
Option
Description
STAPL design file
Default File from Current Design/Impl
The STAPL design file will correspond to the
bitstream file of the currently active
implementation (
design name.jam
).
Manual Selection and Browse
Allow the user to choose/enter any STAPL design
file from the file system. The textfield showing the
filename is also a drop-down combobox of the last
15
*.jam
files selected.
STAPL Actions and Procedures
Refresh lists from STAPL file selected above
Button to refresh the lists of actions and
procedures to match those found in the selected
STAPL file.
Action Name
Lists the Actions contained in the selected STAPL
file.
Description
Lists the description for each Action found in the
file.
Run
Allows the Procedure to be run or bypassed. Icons
indicate:
= Required;
= Deselected;
=
Selected
Procedure Name
Displays the names of the Procedures comprising
the selected Action, in execution order.
Execution State
Displays the execution state of a Procedure. Values
include: blank (required), optional, recommended
Bitporter Probes
Autodetect
Selects an attached Bitporter.
12
Manually Specify by Name
When selected, allows a Bitporter pod to be
specified by name, for example, ”
usb12345
”, or
”
net10234
”.
13
Pick from List
When selected, allows a Bitporter pod to be
selected from a list of detected pods.
Refresh list
Button to refresh the list of detected Bitporter
pods. Equivalent to Tcl command
Run Selected Action
Run ’Selected Action’ on the Connected Device
Plays the selected Action with the active
Procedures to the connected Achronix FPGA.
Equivalent to TCL command
See also:
12
If a STAPL Action is played while autodetection is selected and more than one pod is detected, an error is written to the TCL
console. The option remains active.
13
Bitporter pod names consist of a three-letter suffix, (”usb” for USB-connected pods, ”net” for Ethernet-connected pods,)
followed by either the five-digit serial number, or optionally for Ethernet-connected pods, their IP address.
For example:
”
net192.168.100.101
”.
175
UG001 Rev. 5.0 - 5th December 2012