artisan Achronix Bitporter User manual
Artisan Technology Group is your source for quality
new and certied-used/pre-owned equipment
• FAST SHIPPING AND
DELIVERY
• TENS OF THOUSANDS OF
IN-STOCK ITEMS
• EQUIPMENT DEMOS
• HUNDREDS OF
MANUFACTURERS
SUPPORTED
• LEASING/MONTHLY
RENTALS
• ITAR CERTIFIED
SECURE ASSET SOLUTIONS
SERVICE CENTER REPAIRS
Experienced engineers and technicians on staff
at our full-service, in-house repair center
WE BUY USED EQUIPMENT
Sell your excess, underutilized, and idle used equipment
We also offer credit for buy-backs and trade-ins
www.artisantg.com/WeBuyEquipment
REMOTE INSPECTION
Remotely inspect equipment before purchasing with
our interactive website at www.instraview.com
LOOKING FOR MORE INFORMATION?
Visit us on the web at www.artisantg.com for more
information on price quotations, drivers, technical
specications, manuals, and documentation
Contact us: (888) 88-SOURCE | sales@artisantg.com | www.artisantg.com
SM
View
Instra
PAGE i www.achronix.com Bitporter User Guide
Copyright Info
Copyright © 2008–2009 Achronix Semiconductor Corporation. All rights reserved. Achronix,
Speedster, and picoPIPE are trademarks of Achronix Semiconductor Corporation. All other
trademarks are the property of their prospective owners. All specifications subject to change
without notice.
NOTICE of DISCLAIMER: The information given in this document is believed to be accurate
and reliable. However, Achronix Semiconductor Corporation does not give any repre-
sentations or warranties as to the completeness or accuracy of such information and shall have
no liability for the use of the information contained herein. Achronix Semiconductor
Corporation reserves the right to make changes to this document and the information
contained herein at any time and without notice. All Achronix trademarks, registered
trademarks, disclaimers and patents are listed at http://www.achronix.com/legal.
Achronix Semiconductor Corporation
333 West San Carlos Street, Suite 1050
San Jose, CA, 95110
USA
Phone : 877.GHZ.FPGA (877.449.3742)
Fax : 408.286.3645
Bitporter User Guide www.achronix.com PAGE ii
Table of Contents
Preface - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - iv
About this Guide - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - iv
Reference Documents - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - iv
Conventions Used in this Guide - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - iv
Chapter 1 – Configuration Overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1
Introduction - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -1
JTAG Configuration using the Bitporter Pod - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2
Supported Operating Systems - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2
Minimum Hardware Requirements - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3
Board-Level Device Connections - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3
Chapter 2 – Software and Driver Install - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5
Introduction - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -5
Standalone STAPL Player and USB Driver Install - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5
Windows - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5
Linux - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 8
Chapter 3 – Connecting the Bitporter Pod- - - - - - - - - - - - - - - - - - - - - - - - - - - - 9
Introduction - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -9
Choosing a Connection Type — USB versus Ethernet - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 9
Connecting the Bitporter Pod - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 9
Connecting the Bitporter Pod via Ethernet (Windows and Linux) - - - - - - - - - - - - - - - - - - - - - 13
Disconnecting the Bitporter Pod - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 14
Bitporter Connection Errors - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 14
“Attempting to auto-detect Bitporter pods (USB pods and Ethernet pods on this sub net)...
found 0 pods.” - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 14
“PROGRAM ERROR: Bitporter driver library not found - unable to program device.” - - - - - - 14
“Port has not been opened” - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 15
“Unable to retrieve pathname for USB device” - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 15
“USB communication error” - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 15
“USB communication timeout” - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 15
“Unable to load hid.dll. One or more exported functions missing”- - - - - - - - - - - - - - - - - - - - - 15
“Can't open setupapi.dll: <reason>” - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 15
“Can't open hid.dll: <reason>“ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 15
PAGE iii www.achronix.com Bitporter User Guide
“USB read error. <reason>” - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 15
“USB write error. <reason>” - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 15
"No available Achronix Bitporter products with matching serial number found on USB port." 15
Ethernet Connection Errors: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 16
"No available Achronix Bitporter products with matching serial number found on local
subnet." - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 16
"No available Achronix Bitporter product found at supplied network address." - - - - - - - - - - - 16
"Network device is not an Achronix Bitporter pod."- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 16
Verifying the Setup - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 16
Bitporter Connectivity Self Test- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 16
Bitporter-to-Target-Device Connectivity Test- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17
Handling Multiple Pods Connected to the Same PC - - - - - - - - - - - - - - - - - - - - - - - - - - - - 17
Chapter 4 – Using the Achronix STAPL Player - - - - - - - - - - - - - - - - - - - - - - - 19
Introduction - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 19
Command Syntax - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 19
Bitporter Pod Naming Conventions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 20
Picking a STAPL Action (-a option) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 20
Procedures - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 21
The Action read_idcode - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22
The Action program - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 22
The Action verify - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 23
The Action read - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 23
The Action read_state - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 25
The Action erase - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 27
Querying the Availability of Connected Pods (-q option) - - - - - - - - - - - - - - - - - - - - - - - - 28
Connecting to Specific Pods by Name (-p option) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 29
Configuring the Bitporter Pod's IP address (-i Option) - - - - - - - - - - - - - - - - - - - - - - - - - - 30
Bitporter Pod MAC Addresses - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 30
Checking the Bitporter Pod's Current Ethernet IP Configuration - - - - - - - - - - - - - - - - - - - - - - 30
Configuration the Pod for DHCP (Dynamic IP Address) - - - - - - - - - - - - - - - - - - - - - - - - - - - - 31
Configuring the Pod to Use a Static IP Address - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 32
Programming a Device - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 33
Revision History- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 35
Bitporter User Guide www.achronix.com PAGE iv
Preface
About this Guide
This guide provides details about device programming within the Achronix CAD
Environment (ACE), starting with an existing bitstream through to downloading and device
configuration.
This guide consists of the following chapters:
Chapter 1 – “Configuration Overview” provides an overview of configuring Achronix
FPGAs.
Chapter 2 – “Software and Driver Install” details the installation of the Bitporter USB drivers
and the Achronix STAPL player.
Chapter 3 – “Connecting the Bitporter Pod” covers connecting the pod to a target device and
host PC.
Chapter 4 – “Using the Achronix STAPL Player” covers the syntax and usage of the STAPL
player.
Reference Documents
ACE User Guide (UG001)
ACE Installation and Licensing Guide (UG002)
ACE Quick Start Guide (UG003)
EIA/JEDEC Standard 71 (JESD71), Standard Test and Programming Language (STAPL)
Conventions Used in this Guide
Item Format Examples
Command-line entries Formatted with the Courier bold
font face.
$ Open top_level_name.log
File Names Formatted with the Courier font
face.
filename.ext
GUI buttons, menus
and radio buttons
Formatted with the Helvetica bold
font face.
Click OK to continue.
File →Open
Variables Formatted with italic emphasis. design_dir/output.log
Window and dialog
box headings and
sub-headings
Heading formatted in quotation
marks.
Under “Output Files,” select ...
Window and dialog
box names
Initial caps. From the Add Files dialog box, ...
Bitporter User Guide www.achronix.com PAGE 1
Chapter 1 – Configuration Overview
Introduction
Achronix Semiconductor delivers the world’s fastest commercially available FPGAs. Using CMOS
process technology and conventional SRAM-based device configuration, Speedster™ FPGAs are
capable of operating at 1.5 GHz of system throughput by using unique picoPIPE™ technology.
The embedded programming and configuration logic in the FPGA is designed to support a
variety of programming options. Figure 1-1 outlines the basic block diagram of the
programming and configuration logic, including additional logic to implement security
features. The configuration management unit controls the startup and shutdown sequence
from configuration mode to the user mode and back. The configuration management unit
includes the provisions for configuring the device with a secure bitstream using a 256-bit
Advanced Encryption Standard (AES) algorithm in Cipher Block Chaining (CBC) mode. The
device contains a small non-volatile memory for the storage of the required AES key.
This guide covers configuration via the JTAG port using the Achronix Bitporter pod.
Figure 1-1: Speedster Configuration Options
Configuration Logic
FPGA
User Logic
JTAG
USB
Bitporter
Pod
JTAG
Interface
External CPU
CPU Slave
Controller
Serial (SPI)
Flash
SPI Flash
Controller
Serial
Data
ug004_c01_01_v04
••
FPGA
Configuration
Management
Unit
SRAM Scan
Chain
AES
Decode
AES NV
Key
Storage
Mode and Status Pins
Ethernet
JTAG Configuration using the Bitporter Pod Configuration Overview
PAGE 2 www.achronix.com Bitporter User Guide
JTAG Configuration using the Bitporter Pod
The Bitporter pod (Figure 1-2) connects between a host PC via either a 10/100 Ethernet or
USB 2.0 connection and an EJTAG-compliant connector on the target system. When
connected, the Bitporter pod supports device configuration and debug, along with flash
memory programming.
Note: USB 1.0 and 1.1 are also supported, but discouraged for performance reasons.
The JTAG configuration flow is as follows:
• Generate a design_name.jam file from a placed-and-routed design within ACE.
• Connect the Bitporter pod to either the USB or Ethernet port of the host PC and to the
JTAG port of the target Speedster device.
•Play the STAPL file to the FPGA using acx_stapl_player.exe, executed from
the command line, or via the Download view within ACE (see “Playing a STAPL File”
in ACE User Guide (UG001) for details).
Supported Operating Systems
JTAG programming is currently supported under the following operating systems:
•Foracx_stapl_player with USB-connected Bitporter pods:
♦Red Hat Enterprise Linux Release 5, 32-bit
♦CentOS 5, 32-bit
♦Microsoft Windows XP Professional SP2 32-bit (other versions may work, but are
untested)
Figure 1-2: Bitporter Pod
ug004_c01_02_v01
Configuration Overview Minimum Hardware Requirements
Bitporter User Guide www.achronix.com PAGE 3
•Foracx_stapl_player with Ethernet-connected Bitporter pods:
♦Red Hat Enterprise Linux Release 5, 32-bit
♦Red Hat Enterprise Linux WS Release 4, 32-bit
♦CentOS 5, 32-bit
♦Microsoft Windows XP Professional SP2 32-bit (other versions may work, but are
untested)
Note: Other 32-bit versions of Linux may work, but are unsupported. No 64-bit operating systems are
supported at this time.
Minimum Hardware Requirements
• Pentium-class PC with a minimum of 128 MB of memory (512 MB for Windows Vista)
• Either a USB 2.0 port and/or an Ethernet connection for the Bitporter pod
Note: USB 1.0 and 1.1 may be used but USB 2.0 is strongly recommended for performance
reasons. In addition, a USB port connection is required to change the Ethernet configuration of a
Bitporter pod (Bitporter pods are configured for DHCP by default — if this configuration is
acceptable, no USB connection is needed).
Board-Level Device Connections
Figure 1-3 details the board-level electrical connections to the JTAG header, and Figure 1-4
provides the mechanical specifications.
Figure 1-3: JTAG Header Electrical Connections
ug004_c01_03_v02
1
TRST
TDI
TDO
TMS
TCK
NC
NC
FPGA
1 KΩ
10 KΩ
10 KΩ
10 KΩ
VDDO_JTAG VDDO_JTAG
Bitporter User Guide www.achronix.com PAGE 5
Chapter 2 – Software and Driver Install
Introduction
Prior to device configuration, both the STAPL player (acx_stapl_player) and, if required,
the USB drivers for the Bitporter pod must be installed on the host system. Currently, the USB
drivers and STAPL player are installed concurrently with the Achronix CAD Environment
(ACE) software; however, they can be installed separately if desired.
Note: No license file is needed when running the STAPL player from the command line.
Standalone STAPL Player and USB Driver Install
For users wishing to install only the player, for example when using a separate host PC in a
lab environment, the player and USB drivers can be installed separately. Users wishing to
install the entire ACE software should refer to ACE Installation and Licensing Guide (UG002).
Important! Disconnect any attached Bitporter pods from the host PC before installing the player and
drivers.
Windows
After locating the standalone STAPL player installer (standalone_acx_stapl_player_
installer.exe) on the SDK60 CD, install the software to the desired installation directory.
Important! It is not recommended to install both ACE and the standalone STAPL player on the same
machine. Be sure to uninstall any previous installation of ACE before running the standalone STAPL
player installer.
1. Locate the standalone STAPL player installer standalone_acx_stapl_player_
installer.exe) on the SDK60 CD. Double-click the install file to begin the process.
2. Select the desired language from the pull-down menu of the Installer Language
dialog box (Figure 2-1).and click OK to open the Achronix STAPL Player Setup
wizard.
Figure 2-1: Installer Language Dialog Box
UG004_c02_01_v01
Standalone STAPL Player and USB Driver Install Software and Driver Install
PAGE 6 www.achronix.com Bitporter User Guide
3. From the wizard, click Next > to open the License Acceptance dialog box. Click
IAgreeto continue.
4. From the License Agreement dialog box (Figure 2-3), click I Agree after reviewing the
license.
Figure 2-2: Achronix CAD Environment Setup Wizard
Figure 2-3: License Agreement Dialog Box
UG004_c02_02_v01
UG004_c02_03_v01
Software and Driver Install Standalone STAPL Player and USB Driver Install
Bitporter User Guide www.achronix.com PAGE 7
5. From the Choose Components dialog box (Figure 2-4), select the desired components
to install. Click Next > to continue.
6. From the Choose Install Location dialog box (Figure 2-5), set the desired installed
directory by either typing the path under Destination Folder or using the Browse
button to navigate the desired location. Click Next > to continue.
Figure 2-4: Choose Components Dialog Box
Figure 2-5: Choose Install Location Dialog Box
UG004_c02_04_v01
UG004_c02_05_v01
Standalone STAPL Player and USB Driver Install Software and Driver Install
PAGE 8 www.achronix.com Bitporter User Guide
7. From the Choose Start Menu Folder dialog box, select the desired folder and click
Install to start file extraction and begins installation. Once the install completes, click
Close from the final dialog box (Figure 2-6).
Linux
After locating the standalone STAPL player installer (standalone_acx_stapl_player.tgz)
on the SDK60 CD, extract and install the software to the desired installation directory.
Note: The archive contains no directory structure; therefore, the installation directory chosen must be
the final desired location.
1. Extract the software.
% mkdir <install_directory>
% cd <install_directory>
% tar -xzvf standalone_acx_stapl_player.tar
2. (Only necessary when USB Bitporter support is desired.) Run the Perl install script
./install_acx_bitporter_usb.pl
# ./install_acx_bitporter_usb.pl
After the installation completes, the script ends with the following message:
Bitporter USB driver, version 2.4.2, installed.
Note: Linux USB Bitporter connections are currently only supported on 32-bit CentOS 5 and
RHEL 5. Other Linux release may work if they support udev, but are not supported.
Figure 2-6: Completing Install
UG004_c02_06_v01
Bitporter User Guide www.achronix.com PAGE 9
Chapter 3 – Connecting the Bitporter Pod
Introduction
Choosing a Connection Type — USB versus Ethernet
Ethernet
• Ethernet-connected Bitporter pods are visible from multiple PCs at once:
♦However, users can overwrite each other's programs. The Achronix
acx_stapl_player/Bitporter programming system does prevent multiple users
from programming the device simultaneously but does not ensure that the con-
nected hardware is not already mid-test. Such test queueing is left up to the user.
♦Pod autodetect visibility is limited to the pod's local subnet. Beyond the local sub-
net, the pod's IP address must be known before a user can connect to it.
• Bitporter performance may be slower via Ethernet than via High-Speed USB,
depending upon network configuration. On a congested network, programming via
Ethernet can take up to 5x longer than via High-Speed USB.
• Before attempting Ethernet connection to a Bitporter pod, please consult the network
administrator to ensure the Bitporter is allowed to connect to the necessary network.
• A USB connection is required to alter the Bitporter pod's Ethernet configuration, for
example, selecting static IP over DHCP, changing the static IP, etc. (see command-line
options -id, -iq, and -is in Table 4-1, page 19)
USB
• Bitporter performance may be faster than via Ethernet, depending upon network
configuration.
• Only visible from the PC hosting the connection.
Connecting the Bitporter Pod
Important! Never apply power to the target without the pod turned on. The Bitporter pod must always
be powered if the connected target device is powered. Always supply power to the Bitporter pod first
before supplying power to the target hardware. Always power down the target hardware before
powering down the Bitporter pod. When power-cycling the pod, leave it turned off for at least 5 seconds.
Also, the Bitporter pod is sensitive to Electrostatic Discharge (ESD). When operating the pod, ESD
precautions must be observed to ensure proper function.
Connecting the Bitporter Pod via USB
Before connecting the Bitporter pod, please observe the following:
• Do not plug in the Bitporter USB cable until after the software installation (see
Chapter 2 – “Software and Driver Install”).
• When using the USB interface, do not plug in the power cable. The power cable is only
used for the Ethernet interface. When using the USB interface, all power to the device
is provided through the USB cable.
Connecting the Bitporter Pod Connecting the Bitporter Pod
PAGE 10 www.achronix.com Bitporter User Guide
Note: When the power cable is plugged into the Bitporter, the Bitporter ignores the USB
interface and only utilizes the Ethernet interface.
• Be sure to have the USB appropriate drivers installed. See Chapter 2 – “Software and
Driver Install” for details.
Windows
To connect the Bitporter pod to the target hardware:
1. Turn off the power to the target hardware.
2. Connect one end of the JTAG flat ribbon cable to the target EJTAG connector. The red
strip is pin 1.
Note: The key of the JTAG cable should point towards J52 (towards the bottom edge of the board).
3. Connect the other end of the JTAG flat ribbon cable to the Bitporter pod. The plug is
keyed.
4. Connect the USB cable to the host PC.
5. Connect the USB cable to the Bitporter.
6. When prompted by the Found New Hardware Wizard, click Next > (Figure 3-1).
Figure 3-1: Found New Hardware Wizard
ug004_c03_01_v01
Connecting the Bitporter Pod Connecting the Bitporter Pod
Bitporter User Guide www.achronix.com PAGE 11
7. At the next window of the wizard (Figure 3-2), select Install the software automati-
cally (Recommended), followed by Next >.
8. After the wizard has found the Bitporter firmware loader, at the Windows Logo test-
ing warning window, click Continue Anyway.
Figure 3-2: Found New Hardware Wizard
Figure 3-3: Windows Logo Testing Warning Window
ug004_c03_02_v01
ug004_c03_03_v01
Connecting the Bitporter Pod Connecting the Bitporter Pod
PAGE 12 www.achronix.com Bitporter User Guide
9. At the final wizard window (Figure 3-4), click Finish to complete the driver install.
The wizard appears twice during the install: once for the Achronix Bitporter Firm-
ware Loader and then again for the Achronix Bitporter Pod drivers. The first driver
downloads firmware to the Bitporter pod; the second driver connects to the pod for
JTAG operations.
If not prompted to install these drivers the first time the Bitporter is connected to a
USB port, unplug the USB cable, reboot the host PC. Once the system has rebooted,
plug in the USB cable again — at this point driver installation should begin.
Note: During the driver installation, the Bitporter pod’s power LED turns on and the
COMM LED may flash. Once driver installation completes successfully, the power LED
remains lit, and the COMM LED turns off.
10. Turn on the power to the target hardware.
11. Continue to “Verifying the Setup,” on page 16.
Linux
1. Turn off the power to the target hardware.
2. Connect one end of the JTAG flat ribbon cable to the target EJTAG connector. The red
strip is pin 1.
Note: The key of the JTAG cable should point towards J52 (towards the bottom edge of the board).
3. Connect the other end of the JTAG flat ribbon cable to the Bitporter pod. The plug is
keyed.
4. Connect the USB cable to the host PC.
Figure 3-4: Completing the Found New Hardware Wizard
ug004_c03_04_v01
Connecting the Bitporter Pod Connecting the Bitporter Pod
Bitporter User Guide www.achronix.com PAGE 13
5. Connect the USB cable to the Bitporter.
Note: During the pod initialization, the Bitporter pod’s power LED turns on and the COMM
LED may flash. Once pod initialization completes successfully, the power LED remains lit,
and the COMM LED turns off.
6. Turn on the power to the target hardware.
7. Continue to “Verifying the Setup,” on page 16.
Connecting the Bitporter Pod via Ethernet (Windows and Linux)
The Bitporter pod supports Ethernet connectivity to one or more PCs, supporting both static
and dynamic (via DHCP) IP addressing. Before attempting Ethernet connection to a Bitporter
pod, please consult the network administrator to ensure that:
• A DHCP server covers the network segment onto which the pod is attached. If no
such DHCP server is in place, then consult with the system administrator to
determine the static IP addressing settings to be explicitly assigned to the pod.
• The Bitporter pod is allowed to connect to the necessary network.
By default, all Bitporter pods are set up to use DHCP negotiation the first time they are
plugged into an Ethernet network. Since the pod stores its Ethernet configuration in flash
memory, the Ethernet configuration typically only needs to be performed once.
Note: Only pods on the same subnet (without an intervening router) can be automatically detected by
STAPL player (see the -q option, Table 4-1, page 19). Use the -p option to connect to pods on non-
local subnets using the podname containing the IP address of the pod (see Table 4-1). For ease of use, it
is recommend that both the PC used to program the Achronix device and the Bitporter pod are placed on
the same subnet.
To connect to a Bitporter pod via Ethernet:
1. Turn off the power to the target system.
2. If the pod is connected to the PC via USB, disconnect the USB cable from the Bitporter.
3. Connect the JTAG flat ribbon cable to the target JTAG pins. The red strip is pin 1.
4. Connect the JTAG flat ribbon cable to the Bitporter pod. The plug is keyed.
5. Connect the power cable to the power outlet and the pod. The Bitporter pod's POWER
LED should now be on. The pod's COMM LED should start blinking.
6. Connect the Ethernet cable to the Ethernet jack on the wall and the pod. Once the Bit-
porter pod's COMM LED stops blinking, the pod has successfully acquired an IP address.
Note: If the COMM LED does not stop blinking (it should take less than ten seconds), talk to
the network administrator to verify that the device's MAC address has permission to connect
to the local network, and that the device is connected to the proper Ethernet network jack.
7. Turn on the power to the target hardware.
8. Continue to “Verifying the Setup,” on page 16.
The pod is now able to be referred to by name as net<serial_number>or
net<ip_address>. The latter name must be used if pod communication is being attempted
across subnets (see Table 4-1).
Table of contents
Other artisan Controllers manuals
