> For the complete documentation index, see [llms.txt](https://docs.ducks-services.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ducks-services.com/dma/dma-fimware/75t-100t-firmware-flashing.md).

# 75t / 100t Firmware Flashing

{% embed url="<https://youtu.be/wVi4NgpvDq0?t=391>" %}

***

{% stepper %}
{% step %}

### Connect to JTAG Port

* Plug the **USB cable** into the **JTAG port** on your DMA card.
  {% endstep %}

{% step %}

### Install JTAG Driver

* Ensure the [**JTAG Driver**](https://ducks-services.gitbook.io/dma/~/revisions/JpVzONbaEFULHqa0sxde/dma-card/jtag-driver-setup-2nd-pc) is installed on your second PC.
  {% endstep %}

{% step %}

### Download 75T Flashing Tool

<a href="https://mega.nz/file/X6oTGZIQ#C95km-IdJWGiFbINd0i-hMTX6w0m_Am--lN1wllAS3k" class="button primary" data-icon="arrow-down-to-bracket">75t / 100t Flashing Tool</a>
{% endstep %}

{% step %}

### Configure Tool Settings

In the tool, set the fields as follows:

* **If 75t - Field 1:** `xc7a75t`
* **If 100t - Field 1:** `xc7a100t`
* **Field 2:** `BIN`
* **Field 3:** `10000000`
  {% endstep %}

{% step %}

### Select Firmware File

* Click the button below the **"FPGA"** label and select your `.bin` firmware file.
  {% endstep %}

{% step %}

### Flash the Firmware

* Press the **Flash** button (located directly beneath the firmware selection).
  {% endstep %}

{% step %}

### Confirm Success

* Once the process completes and the progress bar reached 100%, the flash was successful.
  {% endstep %}
  {% endstepper %}

***

### ✅ You're Done

You have now successfully flashed your 75t / 100t DMA Card.

{% hint style="info" %}
It is now recommended to run a [**Speed Test (2nd PC)**](https://docs.ducks-services.com/dma/dma-card/speed-test-2nd-pc) to ensure everything was flashed correctly.
{% endhint %}


---

# 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.ducks-services.com/dma/dma-fimware/75t-100t-firmware-flashing.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.