Hi Sruk,
Thank you for confirming that you are using the adapter and the legacy 2.54 mm pinout.
The known USB-Blaster III Product ID issue affects Active Serial programming only. It should not prevent normal JTAG device detection.
Related KDB: Why Can't I Program Using Active Serial Programming with my USB Blaster III?
For this JTAG error, please check the target voltage reference at the connector. USB-Blaster III uses the target board VREF to set its JTAG signal levels. Measure VREF at the adapter/header while the board is powered. It must be within the supported range and match the FPGA JTAG I/O voltage.
Try Lowering the JTAG Clock Speed. You can try reducing the JTAG clock speed using:
jtagconfig --setparam <cable_number> JtagClock 6M
Also, please confirm:
- The target board is fully powered before scanning.
- TDO is not held high by another device or circuit.
- No other JTAG source is connected to the chain.
- The cable LED state and the output from jtagconfig.
Since the same boards work with an older cable, if VREF and TDO are correct, this may indicate a cable issue. The "Engineering Sample" marking on the box is unusual for a production unit purchased through DigiKey. It would be worth confirming with DigiKey whether this is expected for your order.
Thanks,
Fakhrul