
Querying the Availability of Connected Pods (-q option) Using the Achronix STAPL Player
PAGE 32
www.achronix.com Bitporter User Guide
acx_stapl_player -pusb12348,usb12345,net12347 -aREAD_IDCODE quickstart.jam
Thecommandreturns:
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 connect to user-specified pod(s):
WARNING: User-specified pod "usb12348" not found/not connected.
Successfully opened Bitporter pod usb12345.
Entering JTAG programming mode...
Reading Device ID code...
IDCODE=00100000 00000000 00010110 01000001
Exiting JTAG programming mode...
Exit code = 0... Success
Note: ThereportedIDCODEwould,ofcourse,varyaccordingtothetargetdevice.
TheSTAPLPlayerattemptstoconnecttothepodsintheorderlisted,thenplaysthespecified
Action using the first successful connection. Once a connection is successful, no subsequent
connectionsareattempted.UnsuccessfulconnectionattemptsarereportedasWARNINGS.
Bitporter Pod Naming Conventions
Each Bitporter pod has a unique name which includes a prefix to indicate the kind of
connectionused to communicate with the pod (forexample,“usb”for USB‐connected pods
and“net”forEthernet‐connectedpods)plusasuffixindicatingeitherthepodʹsserialnumber
orIPaddress.
Forexample,ifa
podhastheserialnumber12345(theserialnumberisonastickerlocatedon
theBitporter),thepodcanbenamed:
• usb12345–ifconnectedviaUSB.
• net12345–ifconnectedviaEthernet,connectedonthesubnet.
• net192.168.1.123 –ifconnectedviaEthernet,whetheronthelocalsubnetornot
(ifthe
pod’sIPaddresswas192.168.1.123).
Querying the Availability of Connected Pods (-q option)
TheBitporter pod query modeistypically used when multiple Bitporterpodsarevisible to
thehostrunningacx_stapl_player,orwhenmultipleusersneedtoshareaccesstoacommon
poolofBitporterpods.Thisquerymodereturnsthecurrentavailabilitystateofautodetected
orexplicitlynamedpods.
Theusermaychooseto
explicitlystatewhichpods’availabilityshouldbequ eried(byusing
the‐poptionwithacomma‐separatedlistofpodnames).Alternately,ifnopodsareexplicitly
named,theSTAPLPlayerwillautodetectthestateoflocalpods.
Important! Itisrecommendedthatthisquerymodenotbetheonlymeansused
tosynchronizemultiple
usersʹattemptstousemultiplepods—usersstillneedtoensurethatagiventargetboardisnot being
usedthroughanothernon‐BitporterinterfacebeforeaccessingtheBitporterattachedtothattar getboard.
Comentários a estes Manuais