Autodetection mode – Achronix Bitporter User Manual
Page 39
Using the Achronix STAPL Player
Querying the Availability of Connected Pods (-q option)
Bitporter User Guide
PAGE 33
Autodetection Mode
To see a list of the pods currently autodetected by acx_stapl_player, run the following at the
command‐line:
acx_stapl_player -q
This command returns to the command‐line a table of the currently detected pods, using the
following criteria:
•
USB‐connected Bitporter pods: Pods connected to the host are listed by name in the
first column only if they are currently not in use by another instance of
acx_stapl_player. Pods connected to the host via USB which are already in use are not
listed. Pods connected to other hosts via USB are not listed, regardless of usage state.
•
Ethernet‐connected Bitporter pods: All Bitporter pods connected on the same subnet
as the host are listed by name in the first column. The second column contains the
availability status of each pod found. A listing of ++AVAILABLE++ means the pod
currently has no owner (and is available for immediate use). A listing displaying an IP
address means the pod is currently in use by a host located at that IP address.
Note:
Bitporter pods on different Ethernet subnets from the host are not autodetected. To
query the availability state of these pods, the pods must be queried by name with the ‐q and ‐p
options used in conjunction. See
“Querying the Availability of Named Pods”
below.
For example, if two pods with serial numbers 12345 and 12346 are connected to the same host
via USB, and two additional pods with serial numbers 12347 and 12348 are connected via
Ethernet on the same subnet, then when the acx_stapl_player is run in autodetection query
mode:
acx_stapl_player -q
The command returns:
Achronix STAPL Player (acx_stapl_player)
(c) Copyright Achronix Semiconductor Corp. All rights reserved.
contains elements of Jam STAPL Player Version 2.5 (20040526)
Copyright (C) 1997-2004 Altera Corporation
******************************************
* Attempting to find all reachable pods: *
******************************************
Attempting to autodetect availability of local Bitporter pods (USB pods
and Ethernet pods on this subnet)...
...autodetection found 3 pods.
|==========|======================================|
| Pod | Detected |
| Name | Availability |
|==========|======================================|
| usb12345 | ++AVAILABLE++ |
| net12346 | --in use, owner is 192.168.100.123-- |
| net12347 | ++AVAILABLE++ |
|==========|======================================|
In this example, pod 12345 is connected via USB, and is currently not in use. Pod 12346 is visible
via Ethernet, but is already in use by a host at IP address 192.168.100.123. Pod 12347 is also
visible via Ethernet, currently has no owner, and is thus available for use. Pod 12348 is not listed,
which means it must also be connected via USB, but it is in use. (USB probes in use are not
autodetected, and are thus not listed.)