> 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/dna-id.md).

# DNA ID

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

{% stepper %}
{% step %}

### Download the DNA ID Tool

<a href="https://mega.nz/file/u65DGLBD#RuutSPcUPxvF_ixb8U0CMc97Ov-HrKvE2p9JruM-mZc" class="button primary" data-icon="arrow-down-to-bracket">DNA ID Tool</a>
{% endstep %}

{% step %}

### Connect Your DMA Card via JTAG

* Plug your **DMA card** into your PC.
* Connect to the **JTAG port** on the card using the included USB cable.
  {% endstep %}

{% step %}

### Install JTAG Drivers

* Once the files are downloaded, run and install the included drivers.
  {% endstep %}

{% step %}

### Run the Tool

* Locate the `.bat` file inside the downloaded folder that corresponds to your **specific DMA card model** (e.g., 35t, 75t, 100t, etc.).
* Double-click the `.bat` file to run it.
* Wait a few seconds for the script to complete.
  {% endstep %}

{% step %}

### Find the DNA Line

* Once the tool runs successfully, it will output a line like this:

```
DNA = XXXXX (XXXXXXXXXXXXXX)
```

{% endstep %}

{% step %}

### Send Us Your DNA

* Copy the **entire DNA ID line** and send it along with your firmware order # in a DMA ticket.

{% hint style="info" %}
This value is required to generate your **DNA-locked firmware**. If anything looks off or you get an error, reach out to support with a screenshot.
{% endhint %}
{% 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.ducks-services.com/dma/dma-fimware/dna-id.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.