- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 598
- Reaction score
- 7
Anyone else running into JTAG issues with a fresh DMA build?
Getting the card recognized in the PCIe slot is one thing—speedtests might even pass—but as soon as you try to flash custom gateware to keep your setup UD, OpenOCD throws a fit. This is a classic wall when the JTAG debugger isn't talking properly to the Artix-7 chip on your board.
The Error Log:
Technical Breakdown — What "All Ones" Really Means
When OpenOCD reports "all ones" (0xffffff), it means the TDO (Test Data Out) line is stuck high. The software is shouting into the void, and the FPGA isn't responding. Since the speedtest is running fine, the FPGA is clearly powered via the PCIe slot, so we can likely rule out a dead chip.
Anyone else seen this specific ID 0xffffff error on the newer boards? Drop your hardware rev and config below.
Getting the card recognized in the PCIe slot is one thing—speedtests might even pass—but as soon as you try to flash custom gateware to keep your setup UD, OpenOCD throws a fit. This is a classic wall when the JTAG debugger isn't talking properly to the Artix-7 chip on your board.
The Error Log:
Code:
Open On-Chip Debugger 0.11.0+dev
Info : clock speed 10000 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: xc7.tap: IR capture error; saw 0x3f not 0x01
Error: Unknown flash device (ID 0xffffff)
Technical Breakdown — What "All Ones" Really Means
When OpenOCD reports "all ones" (0xffffff), it means the TDO (Test Data Out) line is stuck high. The software is shouting into the void, and the FPGA isn't responding. Since the speedtest is running fine, the FPGA is clearly powered via the PCIe slot, so we can likely rule out a dead chip.
- Signal Integrity & Speed: The log shows an adapter speed of 10000 kHz (10 MHz). This is often way too aggressive for cheap JTAG programmers or unshielded cables. Try dropping your clock speed to 1000 kHz or even 500 kHz in your config to see if the chain initializes.
- Wiring Pinout: Check your JTAG header. If you aren't using the standard ribbon cable, double-check that TMS, TCK, TDI, and TDO aren't crossed. A single loose jumper is enough to return 0xff.
- Driver Issues: If you're on Windows, ensure the JTAG interface is correctly bound to WinUSB via Zadig. If OpenOCD can't talk to the programmer properly, it won't be able to cycle the TAP controller on the FPGA.
- VREF/VCC Sense: Some debuggers require the VREF pin on the JTAG header to be connected to the FPGA's IO voltage to sense the logic level. If this isn't connected, the programmer might not drive the lines correctly.
- Ensure the PC hosting the JTAG is sharing a common ground with the DMA card PC (if they are different).
- Try a different USB port for the JTAG debugger; front panel ports are notoriously noisy for flashing.
- Reseat the JTAG connector on the actual DMA board—some of these Chinese clones have poorly soldered headers.
- Try a different USB port for the JTAG debugger; front panel ports are notoriously noisy for flashing.
- Reseat the JTAG connector on the actual DMA board—some of these Chinese clones have poorly soldered headers.
Anyone else seen this specific ID 0xffffff error on the newer boards? Drop your hardware rev and config below.