How to Flash DMA Firmware: Universal Guide for 35T, 75T & 100T in One Tool

The complete firmware flashing guide for every DMA card — 35T, 75T, and 100T — using both CH347 (JTAG) and RS232 (UART) interfaces. One tool, one page, every method.

What You Need Before You Start

Hardware

• Two-PC setup: main PC has the DMA card in a PCIe slot (x1 / x4 / x16, bracket flush) — if you haven't physically built the rig yet, follow our DMA card & rig setup guide first; second PC runs the tool.
• USB 3.0 data cable (not charging-only) — the most common failure cause. USB 3.0 ports are blue, red, or teal; never use a black USB 2.0 port.

Identify Your Ports: DMA Flash Port vs DMA Speed Port

• Flash port (JTAG / CFG / Update) — USB-C closest to the gold fingers. Use only for flashing + DNA.
• Speed port (DATA) — the other USB-C. Use for normal operation + speed test.

BIOS Settings for DMA Cards (Intel and AMD)

Before touching BIOS: open Settings → Windows Security → Device Security → Core Isolation Details and disable Memory Integrity. Restart if prompted. This is on the main PC, not the second PC. These are the same protections a DMA cheat has to get around — and the ones kernel-level anti-cheat leans on — which is why this setup disables them.

If the card is not detected after flashing, also enable CSM in the Boot tab. Setting paths by brand: ASUS → Advanced → PCI Subsystem Settings; MSI → Settings → Advanced → PCI Subsystem Settings; Gigabyte → Settings → Miscellaneous or IO Ports; ASRock → Advanced → Chipset Configuration.

Download and Set Up the BurgerCheats DMA Flash Tool

Download DMAFlashLite.exe. Extract anywhere on the second PC.

Requires: Windows 10 / 11 64-bit · WebView2 Runtime (pre-installed on most Win10 / 11) · USB 3.0 port.

The UI: left panel = DNA Extraction (status dots, chip dropdown, Extract DNA button, driver buttons). Right panel = Firmware Flash & Speed Test. Bottom = log (green = success, red = error, white = info). Globe icon top-right toggles English / Chinese UI.

One-Click Drivers (Install All Three on First Setup)

• CH347 Driver — installs CH341PAR (sourced from wch-ic.com, the upstream package). DMA347 Flash Port dot turns green.
• RS232 Driver — opens Zadig 2.5+. In Zadig: Options → List All Devices, then select each Quad RS232-HS Interface 0 through Interface 3 and click Replace Driver — all four. DMA232 Flash Port turns green.
• FT601 Driver — installs FTDI D3XX (FTD3XX.dll). Required for the speed test. Speed Driver turns green.

If any install fails, run DMAFlashLite.exe as Administrator. If a device still does not appear, try a different USB 3.0 port — front-panel ports often route through hubs that break driver enumeration.

CH347 vs RS232 — Which DMA Flash Method Do You Need?

This trips up more first-time users than any other step. You do not have to guess.

Plug the card into its flash port and look at the status dots: DMA347 Flash Port green → your card uses CH347 (JTAG). DMA232 Flash Port green → your card uses RS232 (UART). Both red → driver not installed.

The chip model dropdown offers all six combinations: CH347_35T, CH347_75T, CH347_100T, RS232_35T, RS232_75T, RS232_100T. By default the tool auto-filters this list based on the connected card. Toggle Manual Flash Mode at the bottom of the DNA panel to see all six — useful when recovering a card whose driver is misbehaving. The flashing workflow downstream is identical regardless of interface; the tool absorbs the JTAG vs UART protocol differences internally.

DMA DNA Extraction — Read Your Board’s Hardware ID

The DNA value is a 96-bit hardware serial burned into the Xilinx Artix-7 FPGA. Firmware is locked to one DNA — any firmware built for one card will not run on another.

1. Cable on flash port (green dot), driver installed.
2. Pick chip model from the dropdown. Toggle Manual Flash Mode if auto-detect will not show your option.
3. Click Extract DNA → value appears in seconds.
4. Copy the value → send to firmware provider.

DNA Extraction Failed — Common Causes

• Please select a chip model → pick from dropdown.
• Please connect the flash port → wrong port or no driver.
• DNA extraction failed with zeros or repeats → Zadig replacement did not stick on all four interfaces; redo it.
• Generic failure → try another USB 3.0 port; confirm the main PC is powered on (the card draws PCIe power).

Flash DMA Firmware — Step by Step

1. Rename the .bin (PCILeech Convention)

This step is missing from most tutorials and causes the most preventable failures.

• 35T (Screamer M2-class) → pcileech_screamer_m2_top.bin
• Other models → pcileech_squirrel_top.bin (verify with your firmware provider)

If your provider did not specify, ask. The FPGA bitstream layer expects exact filenames.

2. Pick Format: .bin vs .bit

• .bin → writes to SPI Flash, permanent, survives power cycles, FPGA auto-resets after write. 2–3 min. Production format.
• .bit → loads to FPGA RAM, temporary, lost on power off. Seconds. Use for testing builds.

If the tool rejects your file with Only .bin or .bit firmware supported, the format is wrong.

3. Start Flashing

Confirm Target Chip matches your DNA selection. Select your renamed .bin and click Start Flashing. Do not disconnect USB, do not power off either PC during the flash.

Timing sanity check: the log shows sector 0xNNNNNN took NNNms. Each sector should take tens to a few hundred ms. Single-digit ms or 0ms means the USB connection has dropped and the chip is not actually being written. No error appears — you must catch this from the log timing. Stop, reseat the cable, verify the green dot, restart from the beginning.

A green completion message in the log = done. .bin flashes auto-reset the FPGA. .bit loads immediately.

4. DMA Cold Boot After Flashing (Why It’s Required)

A restart is not enough — the PCIe bus must re-enumerate the card with its new firmware identity.

1. Full shutdown (Start → Shut Down, not Restart).
2. Unplug power cable from main PC.
3. Hold power button 15 seconds to discharge motherboard capacitors.
4. Switch USB cable from flash port to speed port.
5. Reconnect power → boot.

This single sequence resolves roughly 99% of hung-after-flash cases. Try it before re-flashing or re-checking BIOS.

DMA Speed Test — Verify Your Flash Works

Before clicking the button: cable on speed port, both PCs in Windows, Speed Driver dot green (install FT601 driver if it’s red).

Click DMA Speed Test → 20–30 seconds → result popup.

Below 60 MB/s = USB problem, not firmware, nine times out of ten. Try in order: a different data-rated USB 3.0 cable → a different USB 3.0 port (motherboard rear, not front panel) → re-seat the DMA card → force PCIe Gen2 or Gen3 in BIOS (not Auto) → second PC’s power plan to High Performance.

DMA Firmware Flashing Troubleshooting & FAQ

Card Bricked by Interrupted Flash?

Almost always recoverable. Reconnect to flash port → re-extract DNA → re-flash. If the main PC will not boot at all because of the card, use a PCIe riser cable to power the card from a separate PSU and flash from the second PC. No LED activity anywhere = hardware failure — contact the card manufacturer.

Flash port vs speed port?

Flash port (JTAG, closest to gold fingers) = flashing + DNA. Speed port (DATA) = normal use + speed test. Flash first, cold-boot, then switch.

.bin vs .bit?

.bin writes to SPI Flash, permanent, 2–3 minutes. .bit loads to FPGA RAM, temporary, seconds. Production = .bin.

Why rename the .bin to pcileech_screamer_m2_top.bin?

The FPGA bitstream layer (built on ufrisk/pcileech-fpga) expects exact filenames. Skipping the rename is the #1 silent failure in DMA flashing.

Can I flash 75T firmware onto a 35T card?

No. Firmware is chip-specific; the FPGA itself rejects wrong-chip bitstreams.