- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 381
- Reaction score
- 7
Anyone digging into DMA setups knows the drill—the hardware is solid until you start touching the firmware. I've been troubleshooting a recurring issue with an Enigma X1 card that was running fine on factory stock but turned into a brick after trying a custom flash.
The Situation
Initially, I hit a snag flashing the card where OpenOCD was throwing a
error during the process. After getting past the flash, the card is recognized, but the throughput tests are completely tanking.
Tech Details
Troubleshooting Steps
I suspect the firmware image might be mismatched or the CH347 flasher handled the bitstream incorrectly. It's too coincidental that it worked perfectly on the original shipped firmware but dies on any custom build. I've got a fresh USB 3.0 cable on the way to rule out data corruption during the transfer, but I'm leaning toward a botched bitstream compatibility issue with the specific FPGA ID.
Has anyone else seen these massive throughput failures post-flash on an X1? I need to know if there's a more reliable test binary or if I should look into re-flashing the original factory bitstream to verify the card isn't actually hardware-damaged.
While others are out there burning cards by blindly following outdated tutorials, we actually dig into the logs here. Anyone dealt with a similar speed test failure after moving to custom firmware?
The Situation
Initially, I hit a snag flashing the card where OpenOCD was throwing a
Code:
wrong # args: should be "jtagspi_init chain_id proxy_bit"Tech Details
- Device: Enigma X1 (FT601 PCIe)
- Issue: 97.92% failed pages on throughput test
- Current Status: Speed tests fail consistently after flashing alternative firmware (tried Eknod's).
- Vmm Version: 5.8.25.145
- Leechcore Version: 2.16.11.62
Code:
== Throughput Test Results (4kB Reads) ==
Total Read Throughput: 85.78 MB/s
Total Pages: 150000
Failed Pages: 146884 (97.92%)
[i] Test Result: FAILTroubleshooting Steps
I suspect the firmware image might be mismatched or the CH347 flasher handled the bitstream incorrectly. It's too coincidental that it worked perfectly on the original shipped firmware but dies on any custom build. I've got a fresh USB 3.0 cable on the way to rule out data corruption during the transfer, but I'm leaning toward a botched bitstream compatibility issue with the specific FPGA ID.
Has anyone else seen these massive throughput failures post-flash on an X1? I need to know if there's a more reliable test binary or if I should look into re-flashing the original factory bitstream to verify the card isn't actually hardware-damaged.
While others are out there burning cards by blindly following outdated tutorials, we actually dig into the logs here. Anyone dealt with a similar speed test failure after moving to custom firmware?
