How to Flash DMA Firmware: Universal Guide for CH347 & RS232

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.

Flashing firmware onto a DMA card should not require three different guides, four browser tabs, and a prayer. Most existing tutorials cover only one chip, one interface, or one brand — and the moment your card does not match the screenshots, you are stuck hunting forums for answers.

This guide eliminates that problem. Whether you are flashing a 35T board via RS232, a 75T via CH347, or a 100T through either method, the entire process is documented here. We built BurgerCheatsDMAflash — a universal flashing tool that handles all three FPGA chip sizes, both interface types, driver installation, DNA extraction, and speed testing in a single application. This page walks you through every step from BIOS configuration to post-flash verification to recovering a card that will not boot.

If you are looking for an explanation of what DMA firmware does and how device emulation works at a technical level, our DMA Firmware deep-dive covers PCIe config space, TLP compliance, and anti-cheat interaction in detail. This page focuses purely on getting firmware onto your card correctly.

What You Need Before Flashing DMA Firmware

Every failed flash starts with a skipped prerequisite. Before you open BurgerCheatsDMAflash, confirm you have the right hardware, cables, and system configuration in place. Missing any of these will waste your time and could leave your card in a non-functional state.

Required Hardware and Cables

Flashing requires a two-PC setup. Your main PC (the one with the DMA card physically installed in a PCIe slot) provides power to the card. Your second PC runs BurgerCheatsDMAflash and communicates with the card over USB.

You need a USB 3.0 data cable — not a charging-only cable. This is the single most common source of flashing failures and slow speed tests. Most DMA cards use a USB-C connector on the card side and USB-A on the PC side. USB 3.0 ports are typically colored blue, red, or teal on your motherboard I/O panel.

Your DMA card must be seated firmly in a PCIe slot (x1, x4, or x16) on the main PC motherboard. The card bracket should sit flush against the case — if it is angled or partially inserted, the card may receive power but fail to communicate. If your card has a physical power switch, ensure it is in the ON position.

Identify Your Ports: Flash Port vs Speed Port

Every DMA card has at least two USB ports, and getting them confused is one of the fastest ways to waste an hour.

The flash port (also called JTAG port) is the TypeC port closest to the PCIe edge connector — the gold fingers that slot into your motherboard. This port is used exclusively for flashing firmware and extracting DNA. Some manufacturers label it "JTAG," "Update," or "Flash."

The speed port (also called DATA port) is the other TypeC port, typically furthest from the motherboard. This port is used for normal operation — memory reading, software communication, and speed testing after flashing is complete.

During flashing, your USB cable must be connected to the flash port. BurgerCheatsDMAflash will show a green dot next to "DMA347 Flash Port" or "DMA232 Flash Port" when connected correctly. If all status dots are red, you are either on the wrong port or the driver is not installed.

BIOS Settings for DMA Cards

Your main PC's BIOS must be configured to allow the DMA card to operate correctly after flashing. Most guides skip this section or link to a separate page — but if these settings are wrong, your freshly flashed card will fail to initialize regardless of firmware quality.

Windows Security — disable Memory Integrity first. Before touching BIOS, open Windows Settings → Windows Security → Device Security → Core Isolation Details and disable Memory Integrity. Restart if prompted. This must be done on the main PC. You can also check your Kernel DMA Protection status by pressing Win+R, typing msinfo32, and looking for "Kernel DMA Protection" — if you are using BurgerCheats firmware with IOMMU enabled, this can remain on without affecting DMA card operation.

Intel motherboards: Enter BIOS and disable Secure Boot. Disable Fast Boot. Disable NX Bit (may be listed as XD Bit or Execute Disable Bit — skip if not present in your BIOS). Set the PCIe slot containing your DMA card to Gen1 first for maximum compatibility — you can increase to Gen2 or Gen3 later once everything is confirmed working. Artix-7 FPGAs natively support PCIe Gen2 x1, so Gen4 or Auto may cause link negotiation failures.

AMD motherboards: Disable Secure Boot. Disable Fast Boot. Disable NX Bit (if available). Set the PCIe slot to Gen1. On some ASUS AMD boards, these settings are found under Advanced → PCI Subsystem Settings.

About VT-d / IOMMU: IOMMU does not affect the flashing process itself — flashing runs over the USB-JTAG connection and works regardless of this setting. IOMMU matters after flashing, during normal DMA card operation. Basic or bridge-type firmware from most providers requires IOMMU to be disabled, which creates a problem: major anti-cheat systems — including Vanguard (Valorant), FACEIT (CS2), Fortnite (all PC tournaments since February 2026), and Delta Force's DMA Shield — now require IOMMU to be enabled. Disabling it means you cannot launch those games. Our emulated firmware is built to operate with IOMMU enabled, so you do not need to choose between your DMA card and your games.

If the card is not detected after flashing, try enabling CSM (Compatibility Support Module) in BIOS under the Boot tab. Some motherboard and DMA card combinations require legacy compatibility mode to initialize correctly.

Where to find these settings by brand: ASUS boards typically list them under Advanced → PCI Subsystem Settings or Advanced → System Agent Configuration. MSI boards use Settings → Advanced → PCI Subsystem Settings. Gigabyte boards place them under Settings → Miscellaneous or Settings → IO Ports. ASRock boards use Advanced → Chipset Configuration.

Download and Set Up BurgerCheatsDMAflash

BurgerCheatsDMAflash consolidates what typically requires three or four separate downloads into a single application. It handles CH347 and RS232 communication, supports 35T, 75T, and 100T FPGA chips, and includes built-in driver installation, DNA extraction, and DMA speed testing — eliminating the most common setup failure points.

Download BurgerCheatsDMAflash

Download BurgerCheatsDMAflash and extract the archive to your second PC. Launch the executable. The interface is divided into two main panels: the left panel handles DNA Extraction (device connection status, chip model selection, DNA readout, and driver installation), and the right panel handles Firmware Flash & Speed Test (firmware selection, flashing, and post-flash speed verification).

The bottom of the interface shows the Operation Results log panel, which displays real-time feedback during every operation. Green text indicates success, red text indicates errors, and white text provides informational messages. Logs auto-scroll to the latest entry — click "Clear Logs" to reset when needed.

Install Drivers from Within the Tool

BurgerCheatsDMAflash includes one-click driver installation so you never need to hunt down separate driver packages. Three driver buttons sit at the bottom of the DNA Extraction panel:

CH347 Driver — click this button to auto-install the CH347/CH341PAR driver for JTAG-based flashing. Wait for the completion message in the log panel. After installation, the status dot next to "DMA347 Flash Port" should turn green if your card uses this interface.

RS232 Driver — click this button to open the Zadig utility for RS232 driver replacement. In Zadig, go to Options → List All Devices, select each RS232 interface that appears in the dropdown (e.g., "Quad RS232-HS Interface 0" through Interface 3), and click Replace Driver for each one. After completion, the "DMA232 Flash Port" status dot should turn green.

FT601 Driver — this driver is required for DMA speed testing after flashing. Install it now so it is ready when you reach the verification step. The "Speed Driver" status dot will turn green once installed.

If any driver installation fails, run BurgerCheatsDMAflash as Administrator and retry. If the device still does not appear, try a different USB 3.0 port on your second PC.

CH347 vs RS232 — Which Flashing Method Do You Need?

This is the question that trips up first-time users more than any other. Your DMA card's onboard interface chip determines which method works — using the wrong one produces driver errors or simply nothing.

BurgerCheatsDMAflash makes this easy. Connect your card to the flash port and look at the status indicators in the tool. Whichever flash port shows a green dot is your interface: if "DMA347 Flash Port" lights up green, you use CH347. If "DMA232 Flash Port" lights up green, you use RS232. If neither lights up, the driver for your interface is not installed — install both CH347 and RS232 drivers and reconnect.

General Patterns by Chip Type

While exceptions exist across DMA card brands, the typical patterns are: 35T cards more commonly use RS232, though some newer 35T boards support CH347. 75T cards predominantly use CH347 (JTAG), but a few older boards use RS232. 100T cards almost exclusively use CH347.

Regardless of your card's interface, the flashing process within BurgerCheatsDMAflash follows the same workflow. The chip model dropdown offers all combinations — CH347_35T, CH347_75T, CH347_100T, RS232_35T, RS232_75T, RS232_100T — and the tool auto-filters based on your connected device. If you want to see all chip models (for example, when using Manual Flash Mode), enable it via the button at the bottom of the DNA panel.

Extract Your DMA Board's DNA Value

Before flashing custom firmware, most firmware providers require your DMA board's unique DNA identifier. This hardware-level serial number is burned into the FPGA chip at manufacturing and cannot be changed. BurgerCheatsDMAflash reads it directly from the board.

Step 1: Ensure your flash port is connected (green status dot) and the correct driver is installed.

Step 2: Select your chip model from the "Chip Model" dropdown in the DNA Extraction panel. The tool auto-detects available models based on your connection, but you can enable Manual Flash Mode to see all options.

Step 3: Click "Extract DNA." The log panel will show extraction progress. After a few seconds, your DNA value appears in the DNA Value field.

Step 4: Click the copy button next to the DNA Value field to copy it to your clipboard. Send this value to your firmware provider — they use it to generate firmware locked to your specific board.

If extraction fails with "Please select a chip model," confirm you have chosen a model from the dropdown. If it fails with "Please connect the flash port," check your USB connection and verify the driver is installed. If extraction fails repeatedly, try a different USB port and ensure the main PC is powered on to supply electricity to the DMA card.

Flash DMA Firmware — Step by Step

With your drivers installed, chip model selected, and DNA extracted, you are ready to flash. The process is identical regardless of whether you are using CH347 or RS232 — BurgerCheatsDMAflash handles the interface differences internally.

Select Your Firmware File

In the right panel under "Firmware Flash & Speed Test," confirm that your Target Chip is correctly shown (it inherits from the chip model you selected in the DNA panel). Then click the "Select Firmware" area and browse to your firmware file.

BurgerCheatsDMAflash supports two firmware formats:

.bin files write firmware to the DMA card's SPI Flash memory. This is a permanent installation — the firmware persists through power cycles and the FPGA automatically resets after writing. This is the standard method for production firmware. Flash duration is approximately 2-3 minutes.

.bit files load firmware directly into the FPGA's RAM. This is temporary — the firmware is lost when the card loses power. Flash duration is only a few seconds. Use .bit files for testing new firmware before committing to a permanent .bin flash.

If the tool rejects your file with "Only .bin or .bit firmware supported," you have selected the wrong file format. Firmware files from your provider should always be in one of these two formats.

Start Flashing

Click "Start Flashing." The log panel at the bottom of the interface begins showing real-time progress as each sector is written to the FPGA. The UI remains responsive during flashing — you can monitor logs and status, but do not disconnect the USB cable or power off either PC during the flash.

Timing validation: During a .bin flash, the log panel shows sector-by-sector write progress. Each sector should take tens to hundreds of milliseconds. If you see sectors completing in single-digit milliseconds or 0ms, the flash is not writing correctly — the data is not reaching the chip. Stop the process, re-seat the USB cable, verify the driver is installed, and try again.

A successful flash ends with a green completion message in the log panel. For .bin files, the FPGA resets automatically after the write completes. For .bit files, the firmware loads immediately.

After Flashing — Critical Cold Boot Procedure

Do not simply restart your main PC after flashing. You must perform a full cold boot to ensure the PCIe bus re-enumerates the DMA card with its new firmware identity:

1. Shut down the main PC completely (Start → Shut Down, not Restart).

2. Unplug the power cable from the main PC.

3. Hold the power button for 10-15 seconds to discharge residual voltage from the motherboard capacitors.

4. Switch the USB cable from the flash port to the speed port (the other TypeC port on the DMA card, further from the motherboard).

5. Reconnect the power cable and boot the main PC normally.

Skipping this procedure — especially the power discharge step — is one of the most common causes of "firmware flash succeeded but card doesn't work" problems.

Verify Your Flash with the DMA Speed Test

BurgerCheatsDMAflash includes a built-in DMA speed test so you do not need a separate tool. This test verifies that your freshly flashed firmware is operational and reading memory at acceptable speeds.

Run the Speed Test

Before testing: Confirm your USB cable is now connected to the speed port (DATA port), not the flash port. Confirm both PCs are booted into Windows. Check that the "DMA Speed Port" and "Speed Driver" status indicators show green dots — if "Speed Driver" is red, click the FT601 Driver button to install it.

Click "DMA Speed Test" in the right panel. The test runs for approximately 20-30 seconds and displays results in a popup window.

Reading Your Results

Green popup with speed in MB/s — your firmware is flashed correctly and operating at the displayed transfer rate. As a general benchmark, speeds above 100 MB/s indicate a healthy connection and above 150 MB/s is excellent — though actual results vary by card model, firmware, and USB cable quality. If you get a red popup with a failure reason, see the troubleshooting section below for specific error messages and fixes.

If your speed is below 60 MB/s, the issue is almost always the USB connection — not the firmware. Try a different data-rated USB 3.0 cable, switch USB ports, re-seat the DMA card, and set the PCIe slot to Gen2 or Gen3 in BIOS (not Auto). Set the second PC's power plan to High Performance.

Once your speed test passes, your DMA card is fully operational. To understand how firmware emulation protects against anti-cheat detection at the PCIe level, read our DMA Firmware technical breakdown. For game-specific DMA setup guides, see our pages for Valorant, Fortnite, Delta Force, and Rust.

DMA Firmware Flashing Troubleshooting

Connection & Driver Issues

All status dots red: Confirm cable is in the flash port (not speed port), main PC is powered on, card switch is ON. Try a different USB 3.0 port and cable. Install both CH347 and RS232 drivers, then reconnect. Run BurgerCheatsDMAflash as Administrator.

Driver installation fails: Run as Administrator. Ensure no pending Windows updates. For RS232, manually select the device in Zadig under Options → List All Devices. Temporarily disable antivirus if needed.

Flashing Errors

"Flashing Failed": USB cable loosened, .bin file corrupted (re-download), wrong chip model selected, or driver conflict. Progress bar stuck for 5+ minutes with no log activity = connection dropped — reconnect and retry.

Flash succeeds but card does not work: Perform a cold boot (shutdown → unplug power → hold power button 15 seconds → reconnect → boot). Confirm you switched to the speed port. Install FT601 driver. Try a different PCIe slot.

Speed Test Errors

"FT601 device not found": install FT601 driver and switch to speed port. "FPGA device initialization failed": still on flash port — switch and cold boot. "Failed to open device": reinstall FT601 driver. "Timed out": check USB cable, try different port, ensure main PC is fully booted.

Firmware & Software Errors

"TINY PCIe TLP Algorithm": firmware config space issue — not a flashing problem. Contact your firmware provider.

"CORE Initialization Failed — Unable to Locate Valid DTB": verify all BIOS settings from the prerequisites section — Secure Boot off, Memory Integrity off in Windows. If using non-emulated firmware, VT-d/IOMMU may also need to be disabled. Confirm you are on the speed port.

Recovering a Bricked Card

If the main PC still powers on, reconnect to the flash port and re-flash. If it will not boot, use a PCIe riser cable to power the card independently while flashing from the second PC. Alternative: unplug main PC, hold power 15 seconds, remove card, boot without it, reinstall card, and flash immediately before the system enumerates the device. No LED activity in any system = hardware failure — contact manufacturer.

DMA Firmware Flashing FAQ

What is the difference between the flash port and the speed port?

Flash port (JTAG, closest to gold fingers) = flashing and DNA extraction. Speed port (DATA) = normal operation and speed testing. Flash first, then switch.

What is the difference between .bin and .bit firmware files?

.bin writes to SPI Flash permanently (2-3 min). .bit loads to FPGA RAM temporarily, lost on power off (seconds). Use .bin for production, .bit for testing.

Do I need to flash firmware on a brand new DMA card?

Yes, unless your seller pre-flashed custom firmware. Stock firmware lacks device emulation.

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

No. Firmware is chip-specific. BurgerCheatsDMAflash auto-filters models to prevent mismatches.

What happens if the flash is interrupted?

Card will not function but is almost always recoverable by re-flashing via the flash port. See recovery steps above if the main PC will not boot.

This guide covers everything you need to flash, verify, and troubleshoot DMA firmware on any card. For a deeper look at how firmware emulation works under the hood — PCIe config space, TLP compliance, donor device cloning, and anti-cheat detection methods — read our DMA Firmware technical breakdown. If you are ready to set up a complete DMA system, the DMA hardware page covers card selection, fuser setup, and bundle options.