artisan Achronix Bitporter, Руководство пользователя, Страница: 24 / 44

Connecting the Bitporter Pod Handling Multiple Pods Connected to the Same PC
Bitporter User Guide
www.achronix.com
PAGE 17
******************************************
* Attempting to find all reachable pods: *
******************************************
Attempting to auto-detect Bitporter pods (USB pods and Ethernet pods on
this subnet)...
...found 3 pods.
|==========|=================|
| Pod | (Ethernet only) |
| Name | Owner's IP addr |
|==========|=================|
| usb12345 | <not tracked> |
| net12346 | 192.168.1.123 |
| net12347 | <available> |
|==========|=================|
Refer to “Querying the Availability of Connected Pods (-q option)” in Chapter 4 – Using the
Achronix STAPL Player for complete details.
Bitporter-to-Target-Device Connectivity Test
To verify the connection to the target device via the Bitporter pod:
1. Open a Windows command prompt and navigate to the STAPL player installation
directory.
2. At the command prompt, run:
acx_stapl_player -aREAD_IDCODE read_idcode.jam
Note: The file
read_idcode.jam
is on the SDK60 CD in the
/Software
directory.
After successful opening the Bitporter Pod, the program returns the device ID code of
the target device:
Entering ISP programming mode...
Reading Device ID code...
IDCODEVALID=0
IDCODE=0011000 00000000 00001011 001000001
Exiting ISP programming mode...
Exit code = 0... Success
Handling Multiple Pods Connected to the Same PC
By default the Achronix STAPL Player assumes that it is operating in a single Bitporter pod
environment. If this is true, no special actions by the user are necessary — when
acx_stapl_player finds only one pod during the auto-detection phase, it uses that pod.
The Achronix STAPL Player can support multiple users sharing a collection or pool of
Bitporter pods connected to a single PC via USB, and/or Bitporter pods connected to a
collection of PCs via Ethernet. When multiple pods are found, but the desired pod is not
specified with the
-p
command-line option, acx_stapl_player exits with an error, informing
the user that they must specify by name, which pod(s) is/are to be used.
Note: The
-q
command-line option can be used to list the pods detected by acx_stapl_player (see
Table 4-1 , page 19).-