FPGA Engineer Development Tools

Many Digilent development boards include onboard USB-JTAG circuitry, eliminating the need for a separate programming cable. The hardware design itself is created using software such as AMD Vivado.

Projects often require additional hardware beyond the development board. Depending on the application, that may include Pmods or Zmods for expansion, along with power supplies, cables, adapters, level shifters, and enclosures.

Programmers, Debug Modules, and JTAG Cables

Some FPGA boards do not include built-in programming hardware. These boards require an external programmer to connect the host computer to the target device.

Digilent’s JTAG programmers provide programming and debugging access for compatible AMD devices. Digilent offers external programming cables as well as surface-mount modules that engineers can integrate directly into custom PCBs.

• JTAG-HS3: A high-speed USB programming and debugging cable for compatible AMD FPGAs and SoCs. It connects to an appropriate JTAG header on the target board and supports JTAG daisy-chaining.
• JTAG-SMT3-NC: A surface-mount programming module designed for integration into a custom PCB. Digilent’s SMT modules provide a direct programming and debugging interface without requiring a separate external programmer for normal use.
• JTAG cables and adapters: Ribbon cables and adapters can accommodate different headers, pin arrangements, and physical board layouts.
• USB cables and extensions: The correct cable depends on the USB connector used by the board or programmer. An extension cable may also be helpful when the computer and target system are separated on the bench.

Many Digilent development boards already include onboard USB-JTAG circuitry. Before purchasing a programmer, consult the board’s product page or reference manual to determine whether one is required.

If the board already has onboard programming hardware, a standalone JTAG programmer is usually unnecessary. External programmers are more commonly used with custom PCBs, boards without onboard USB-JTAG, and production or debugging setups that require a dedicated connection.

Expansion Modules: Pmods and Zmods

Digilent’s expansion modules support projects ranging from basic digital I/O to high-speed data acquisition.

Pmods and Zmods serve different purposes. Pmods provide compact peripheral expansion for sensors, communications, displays, converters, and control hardware. Zmods use the SYZYGY standard to provide a higher-bandwidth interface for measurement, control, signal generation, and software-defined radio applications.

Pmods: Peripheral and General-Purpose I/O Expansion

Pmods are small peripheral modules designed to extend FPGA, microcontroller, and embedded-control boards. They make it possible to add application-specific hardware without designing a custom daughterboard.

Available Pmod categories include:

• Sensors: Temperature, humidity, distance, motion, acceleration, orientation, and ambient-light sensing
• Analog conversion: Analog-to-digital and digital-to-analog conversion
• Wireless communications: Wi-Fi, Bluetooth, Bluetooth Low Energy, and other radio interfaces
• Wired communications: CAN, RS-485, UART, and related interfaces
• Storage: microSD and nonvolatile memory
• Displays and user interfaces: OLED displays, LEDs, switches, buttons, keypads, and seven-segment displays
• Motor and actuator control: H-bridges, relays, and control interfaces
• Audio: Audio input, output, and amplification modules

The current selection includes products such as Pmod BLE, Pmod ToF, Pmod MicroSD, Pmod RS485, Pmod CAN, Pmod VGA, and Pmod I2S2. Browse the complete Pmod collection to compare available interfaces and applications.

Although Pmods use a standardized physical format, always verify the required interface, supply voltage, pin assignment, and available host libraries or IP before connecting a module.

Zmods: High-Speed Measurement and Signal Expansion

Zmods are SYZYGY-compliant expansion modules intended for higher-speed applications.

The SYZYGY standard provides greater bandwidth than the Pmod interface while using a smaller form factor than FMC. Zmods support applications involving instrumentation, high-speed control, data acquisition, signal generation, and software-defined radio.

The current Zmod lineup includes:

• Zmod Scope 1410-105: Two channels, 14-bit resolution, and a sample rate of 105 MS/s
• Zmod Scope 1410-125: Two channels, 12-bit resolution, and a sample rate of 125 MS/s
• Zmod AWG 1411: Two-channel arbitrary waveform generation with 14-bit resolution and a sample rate of 100 MS/s
• Zmod Digitizer 1430-125: Two-channel digitizer with 14-bit resolution and a sample rate of 125 MS/s
• Zmod SDR 1450-122: Two-channel, 14-bit software-defined radio digitizer with a maximum sample rate of 122.88 MS/s

 

Zmods require a carrier board with a compatible SYZYGY interface. Compatible Digilent platforms include the Eclypse Z7 and Genesys ZU.

The Eclypse Z7 includes two SYZYGY-compatible Zmod ports and is designed for modular embedded measurement systems. Available configurations include oscilloscope, SDR, digitizer, and other Zmod-based bundles.

Before selecting a Zmod, confirm:

• Carrier-board compatibility
• Required power configuration
• Available IP and example designs
• Required analog bandwidth and resolution
• Sample-rate requirements
• Host software support

Cables, Headers, Power Supplies, and Enclosures

Accessories may seem secondary, but an incorrect cable or power supply can prevent a system from operating correctly.

Cables and Headers

Available cables and headers may include:

• USB cables for programming, communication, or power
• JTAG ribbon cables
• Pmod extension and splitter cables
• Breakout headers
• Breadboard connections
• Logic-level shifting modules
• Board-specific adapters

Check the connector type and electrical requirements in the board’s reference manual before purchasing a cable or adapter.

A physical connection alone does not guarantee electrical compatibility. Pay particular attention to I/O voltage, current limits, pin orientation, and ground connections.

Power Supplies

Use a power supply that meets the voltage, current, polarity, and connector requirements specified for the board.

Some development boards can operate from USB power, while others require an external barrel-jack supply. Higher-performance boards, attached peripherals, motors, and high-speed expansion modules may also increase the system’s power requirements.

Do not assume that a supply from another board is compatible simply because the connector fits.

Enclosures and Mounting Hardware

Enclosures can protect a board from accidental contact, dropped objects, cable strain, and conductive debris.

They are particularly helpful for:

• Classroom laboratories
• Trade-show demonstrations
• Repeated bench use
• Portable prototypes
• Shared equipment
• Systems with attached Zmods or other expansion hardware

Before ordering an enclosure, verify the exact board model and revision, as connector placement and mounting-hole locations may vary.

Small items such as standoffs, screws, microSD cards, cables, level shifters, and spare power supplies are easy to overlook. Browse the available FPGA accessories and compare them with the board’s required and included components before placing an order.

Frequently Asked Questions

What Tools Do I Need to Program an FPGA?

At a minimum, you need:

• A compatible FPGA or SoC development board
• The appropriate design software
• A programming connection
• The correct USB or JTAG cable
• Board-specific documentation and constraints
• A compatible power source

Many Digilent boards include onboard USB-JTAG, so a separate programmer may not be necessary. Boards without onboard programming circuitry need an external cable such as the JTAG-HS3 or an integrated module such as a JTAG-SMT device.

Depending on the board and project, you may also need Digilent board files, an XDC constraints file, embedded-development software, or a boot-storage device.

Do I Need a Separate JTAG Programmer for My Digilent FPGA Board?

Usually not, provided the board includes onboard USB-JTAG.

Check the product page or reference manual before buying a separate programmer. If the board has an onboard programming interface, connect it using the specified USB cable and use the supported AMD or Digilent programming software.

A separate programmer is more likely to be required for:

• A custom FPGA PCB
• A target board without onboard USB-JTAG
• Board bring-up and debugging
• Production programming
• A design requiring direct access to a JTAG chain

The JTAG-HS3 and other external JTAG programmers provide external programming connections. Digilent’s JTAG-SMT modules can instead be incorporated directly into a custom PCB.

Which Tools Do I Need for My Specific Board?

The exact setup depends on the board.

• Basys 3, Nexys A7, Arty A7, and Arty S7: Begin with the board’s onboard programming interface, the required USB cable, AMD Vivado, and the appropriate constraints or board files.
• Zybo Z7 and Cora Z7: In addition to FPGA development tools, projects using the Arm processing system may require AMD Vitis. A microSD card may be useful for projects that boot software or an operating system from removable storage.
• Eclypse Z7: Select compatible Zmods based on the required analog input, output, digitizer, or SDR functionality. The Eclypse Z7 includes two SYZYGY-compatible Zmod ports.
• Custom AMD FPGA boards: Verify the JTAG header, I/O voltage, target-device support, and whether you need an external JTAG cable or integrated SMT programming module.

 

Always use the product’s reference manual and “What’s Included” list as the final purchasing checklist.

What FPGA Design Software Will I Pair With These Tools?

AMD Vivado is the primary hardware-design environment for the AMD FPGA and adaptive SoC devices used on many Digilent boards.

The required Vivado license or tier depends on the target device and the features needed by the project. AMD introduced a new tiered licensing model with Vivado 2026.1, so check current device support and licensing before choosing a version.

For embedded software running on Arm processors or supported soft processors, use AMD Vitis.

For embedded Linux development, AMD states that PetaLinux tools and board support packages are being superseded by the Yocto-based AMD Embedded Development Framework. PetaLinux remains available during this transition, so existing projects may continue to use it while new projects should review AMD’s current Embedded Development Framework guidance.

Are These Development Tools Compatible With Linux?

Many are, but compatibility depends on the specific software release, Linux distribution, target device, and license. AMD provides both Windows and Linux installers for Vivado 2026.1. Check AMD’s installation and operating-system support information before selecting a release.

Before installing an FPGA toolchain on Linux, verify:

• Supported Linux distribution and release
• Required system packages
• Available storage and memory
• License requirements
• USB and JTAG driver support
• Board and target-device support
• Compatibility with the required Vivado, Vitis, PetaLinux, or Embedded Development Framework release

Avoid selecting a development environment based only on general Linux availability. Confirm the exact tool version and operating-system combination required by the project.