Bitporter-to-target-device connectivity test, Handling multiple pods connected to the same pc – Achronix Bitporter User Manual
Page 25
Connecting the Bitporter Pod
Handling Multiple Pods Connected to the Same PC
Bitporter User Guide
PAGE 19
contains elements of Jam STAPL Player Version 2.5 (20040526)
Copyright (C) 1997-2004 Altera Corporation
******************************************
* Attempting to find all reachable pods: *
******************************************
Attempting to auto-detect 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++ |
|==========|======================================|
Refer to
“Connecting to Specific Pods by Name (‐p option)”
for complete details.
Bitporter-to-Target-Device Connectivity Test
To verify the connection to the target device via the Bitporter pod:
1.
Open a 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 dev kit CD in the /Software directory. If
that file is unavailable, the READ_IDCODE action is also present in every STAPL bitstream
(*.jam) file generated by ACE.
After successfully connecting to the Bitporter Pod, the program returns the device ID
code of the target device (example below shows a SPD60 ID code):
Entering JTAG programming mode...
Reading Device ID code...
IDCODE=0011000 00000000 00001011 001000001
Exiting JTAG 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 with a single local Bitporter
pod. 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.
Important!
When multiple pods are auto‐detected, but a 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. (Automated selection of pods would be error‐prone, since it
would likely interrupt already‐running tests.)