> For the complete documentation index, see [llms.txt](https://docs.dexa.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dexa.im/2pc-dma-guides/getting-started/getting-started/dma-card-guides/installing-firmware.md).

# Installing Firmware

Installation guide for DEXAIMDMA custom firmware. Not applicable to all firmware.

{% embed url="<https://dexaimdma.com/products/akqmx9d>" %}
Shop our custom 1:1 fully emulated firmware for EAC, BE, ACE, VGK and more.
{% endembed %}

## On the **GAMING PC**

{% stepper %}
{% step %}

### Power OFF the GAMING PC

* Perform a [Troubleshooting](/2pc-dma-guides/getting-started/getting-started/troubleshooting.md#flea-power-drain-cold-boot)
  {% endstep %}

{% step %}

### Move the USB cable

* move the USB-C data cable to the `JTAG` port on the DMA card

{% hint style="info" %}
If the DMA card is not labeled, the `JTAG` port is the port closest to the PCB pins (bottom port).
{% endhint %}
{% endstep %}

{% step %}

### Power ON the GAMING PC

{% endstep %}
{% endstepper %}

## On the DMA PC

{% stepper %}
{% step %}

### Flash the firmware

* Download the [firmware .bin file from your order](https://account.dexaimdma.com/orders/)

{% hint style="info" %}
**Firmware is always delivered as a `.bin` file.** If Windows renames it to an audio file like `.mp3`, rename the file extension to `.bin` or re-download the firmware.
{% endhint %}

* Use Kilmu's [DMA Tool](https://github.com/kilmu1337/DMA-Tool/releases/) to flash firmware to the DMA card

{% hint style="warning" %}
**If you experience issues flashing firmware, note:** some DMA card manufacturers do not work well with Kilmu's DMA Tool. In this case, reach out to your DMA card's manufacturer and verify if you need to use their specific DMA flashing software/tool.
{% endhint %}

<figure><img src="https://604738803-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA5lofRaOTEWCi5oCwOuw%2Fuploads%2FjLGgE9BDB9Bpliyeoz5A%2Fkilmu%201.png?alt=media&amp;token=d4e58256-7a35-4816-bf30-c3ff5e4ebe5a" alt="" width="563"><figcaption></figcaption></figure>

* click `Select File`
* choose your firmware `.bin` file
* from the drop-down, select your DMA card type (T-Rating):
  * for 35T cards: `XC7A35T`
  * for 75T cards: `XC7A75T`
  * for 100T cards: `XC7A100T`
* click `Flash`

<figure><img src="https://604738803-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA5lofRaOTEWCi5oCwOuw%2Fuploads%2FNjfAHqM8Yyebj6AqL3vl%2F1745335858664.jpg?alt=media&amp;token=cf4c070a-77a9-42bf-818e-768c78226b1e" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="success" %}
Success! Your DMA card is flashed and ready to test.
{% endhint %}
{% endstep %}

{% step %}

### Move the USB cable

* Move the USB-C data cable to the `DATA` port on the DMA card

{% hint style="info" %}
If the DMA card is not labeled, the `DATA` port is the port furthest from the PCB pins (top port).
{% endhint %}

* Perform a [Troubleshooting](/2pc-dma-guides/getting-started/getting-started/troubleshooting.md#flea-power-drain-cold-boot) on BOTH PCs
  * verify once more using a DMA test tool that the DMA card is connected and passes speed/throughput tests
    {% endstep %}

{% step %}

### Perform a speed test

* Using Kilmu's Speed Test option within the tool or using Lone's DMA [test tool](https://github.com/lone-dma/Lone-DMA-Test/releases/download/v3.2.21/github.lonedma.dmatest-win-Setup.exe), perform a speed test on the DMA card

{% hint style="success" %}
Success! You've validated the DMA card is installed, configured, and flashed correctly.
{% endhint %}
{% endstep %}
{% endstepper %}

## On the **GAMING PC**

{% stepper %}
{% step %}

### Adjust power options

* Press the <kbd>Windows Key</kbd> -> type `power plan` -> click `edit power plan` -> click `Change advanced power settings` -> set Hard Disk, Turn off hard disk, `Setting (Minutes): 0`

<figure><img src="https://604738803-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA5lofRaOTEWCi5oCwOuw%2Fuploads%2FjOMDXLiTKg0cHQZhhBJW%2Frundll32_z7xi51Bh4E.png?alt=media&amp;token=15c720ed-7024-4c2f-acf1-e0ad1ebeccbf" alt="" width="303"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Install drivers

* If drivers are included in [your order](https://account.dexaimdma.com/orders/), download and install them.

<details>

<summary>Installing drivers using Windows Explorer</summary>

Some drivers do not have an executable to install them easily; we can use native Windows Explorer functionality to install.

#### Method to Install Drivers via Windows Exporer

1. **If your driver is in an archive (.zip), extract it:**
   * Right click on the `.zip` file and select **Extract All...**
2. **Find the driver file:**
   * Open the newly extracted folder.
   * Find the `.inf` file
     * If you are unsure about which file, in the Windows Explorer menu, click **View** and check the box for **File name extensions**.
   * Once you've located the `.inf`, right click on the file and select **Install**.

<figure><img src="https://604738803-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA5lofRaOTEWCi5oCwOuw%2Fuploads%2F7cF6mGnnatNVLQ8gMQ1N%2FCapture.PNG?alt=media&amp;token=adf143e6-3202-4bdc-921a-07dde6af1987" alt=""><figcaption><p>Right click on the .inf file and select Install</p></figcaption></figure>

</details>

<details>

<summary>Installing drivers using command prompt</summary>

Some drivers do not have an executable to install them easily; we can use command prompt or Windows PowerShell to install via commands.

#### Methods to Force Install Drivers via CMD

1. **Open Command Prompt as Administrator:**
   * Press **Win + S**, type `cmd`, right-click **Command Prompt**, and select **Run as administrator**.
2. **Using `pnputil` (Recommended):**
   * **Force Install/Update:** `pnputil /add-driver "C:\Path\To\Driver.inf" /install`.
   * **Force Override/Replace:** If a driver is already present, use: `pnputil /add-driver "C:\Path\To\Driver.inf" /install /force`.
   * **Install all drivers in a folder:** `pnputil /add-driver "C:\Path\To\Folder\*.inf" /subdirs /install`.
3. **Using `drvload` (For Windows Recovery/BMR):**
   * To load a driver during boot-time (BMR), use: `drvload C:\path\to\driver.inf`.
4. **Using PowerShell (Alternative to CMD):**
   * To force install all `.inf` files in a folder:powershell

     ```
     $Drivers = Get-ChildItem "C:\mydrivers\" -Recurse -Filter "*.inf"
     ForEach ($Driver in $Drivers) {
         PNPUtil.exe /add-driver $Driver.FullName /install
     }
     ```

</details>
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dexa.im/2pc-dma-guides/getting-started/getting-started/dma-card-guides/installing-firmware.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.