> 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/35t-firmware-flashing.md).
# 35t Firmware Flashing
This guide walks you through preparing, identifying, and flashing firmware to your 35T DMA card using LurkerUpdater.
{% hint style="info" %}
**Before you begin:** Your firmware must be built for your card's unique **DNA ID**. Do not flash firmware intended for a different card.
{% endhint %}
***
### 📦 What You'll Need
Before starting, make sure you have:
* **35T DMA card**
* **Windows PC**
* **LurkerUpdater**
* **USB-A data/power cable**
* **USB-C JTAG/Update cable**
* Your card's matching **`.bin` firmware file**
#### 📥 Download LurkerUpdater
[Download LurkerUpdater](https://cdn.discordapp.com/attachments/1491687409736482940/1541144957618753576/LurkerUpdater.key.duck35.zip?ex=6a9c5896\&is=6a9b0716\&hm=62ac358754771c22c794bd20e531f694e08bc9b948a532017e4cc0108b86efb1&) - Password is duck35
***
## 1. 📥 Install the LurkerUpdater Driver (2nd PC)
Extract the downloaded **LurkerUpdater** folder.
1. Open the extracted folder.
2. Open the **`UpdateDriver`** folder.
3. Run **`SETUP.EXE`**.
4. Click **Install**.
5. Click **OK** once installation is complete.
{% hint style="info" %}
The serial driver normally only needs to be installed **once**. You do not need to reinstall it every time you flash the card.
{% endhint %}
***
## 2. 🔌 Connect Both USB Cables
Your 35T card requires **two USB connections** during the flashing process.
#### USB-A — Data / Power
Connect the card's **Data (USB-A)** port to a USB port on the PC.
This connection provides power to the card.
#### USB-C — JTAG / Update
Connect the card's **JTAG/Update (USB-C)** port to another USB port on the **same PC**.
This connection is used to:
* Read the card's DNA
* Communicate with LurkerUpdater
* Flash firmware
Photo: Top Type-C = Flash port
\
Side: USB-A = Power port
{% hint style="warning" %}
**Keep both USB cables connected throughout the flashing process.**
For the most stable power connection, we recommend connecting the USB-A cable directly to a **rear USB 3.0 port** on your motherboard. Avoid USB hubs or extension cables when possible.
{% endhint %}
***
## 3. 🔎 Check the Card & Find the COM Port
Once both cables are connected, check the LEDs on your 35T card.
#### LED Status
**Blinking blue LEDs**
The card is powered and the bootloader is in its flash-ready state. You can continue.
**Solid blue LEDs**
The card is powered. If LurkerUpdater cannot communicate with the card, power-cycle the card once or twice before continuing.
**No LEDs**
The card is not receiving power.
Check the following:
* USB-A power cable
* USB port
* Cable connection
* Try another USB port if necessary
{% hint style="danger" %}
Never disconnect the card or toggle its power while firmware is actively being written.
{% endhint %}
#### Find Your COM Port
On Windows:
1. Open **Device Manager**.
2. Expand **Ports (COM & LPT)**.
3. Locate:
**USB-SERIAL CH343**
4. Note the COM number shown beside it.
For example:
`USB-SERIAL CH343 (COM3)`
You will need this COM number in the next step.
***
## 4. 🧬 Read Your Card's DNA
Each 35T card has a unique **DNA ID** used to generate firmware specifically for that card.
1. Open **`LurkerUpdate_V2.0.0.exe`**.
2. Under **Port**, select the COM port you found in Device Manager.
3. Click **open**.
When successfully connected, the button will change from:
`open`
to:
`close`
Leave the port open.
#### Retrieve the DNA
With the **LurkerUpdater window selected**, type:
`qaqaqa`
You do **not** need to press Enter.
Your card's DNA should appear inside the updater.
It will look similar to:
`DNA = 0123456789AB`
Copy the DNA or take a screenshot of it.
#### Get Your Firmware
Send the DNA to your firmware provider or open a **firmware ticket** with Duck's Services.
Your firmware will be generated specifically for that DNA ID.
{% hint style="warning" %}
Do not flash firmware made for another card. Always verify that the firmware you received matches your card's DNA.
{% endhint %}
***
## 5. ▶️ Flash the Firmware
Once you have received your matching **`.bin` firmware file**, return to LurkerUpdater.
Before proceeding, confirm:
* Both USB cables are connected
* The correct COM port is selected
* The port is **open**
* You have the firmware matching your card's DNA
#### Flashing Steps
1. Set **FileType** to:
`BIN`
2. Click the **`..`** button beside the file path.
3. Select your provided **`.bin` firmware file**.
4. Click **OK** to begin flashing.
5. Wait for the flashing process to completely finish.
The process will normally take approximately **1–3 minutes**.
{% hint style="danger" %}
#### ⚠️ DO NOT interrupt the flashing process.
While the firmware is being written:
* **Do not unplug either USB cable**
* **Do not power off the card**
* **Do not restart or shut down the PC**
* **Do not close LurkerUpdater**
* **Do not toggle any switches on the card**
Wait until LurkerUpdater confirms that flashing has finished.
{% endhint %}
{% hint style="info" %}
For this flashing procedure, select **BIN** as the FileType.
{% endhint %}
***
## 6. 🔄 Restart the Card
After LurkerUpdater confirms that the firmware was successfully flashed:
1. Close LurkerUpdater.
2. Disconnect power from the card.
3. Reconnect the card.
4. Allow the card to fully initialize.
The card should now boot using your newly installed firmware.
***
## 7. 🖥️ Install the Firmware Drivers
Once the card has been successfully flashed, install the drivers provided with your firmware on your **main PC**.
1. Download and unzip the provided driver files.
2. Open the extracted folder.
3. Locate the **Setup Information (`.INF`)** file.
4. Right-click the `.INF` file.
5. Select **Install**.
6. Allow Windows to complete the driver installation.
{% hint style="info" %}
If your firmware provider included multiple files, make sure you are installing the `.INF` file specifically intended for your firmware.
{% endhint %}
***
## 8. ❄️ Cold Boot Both PCs
After installing the firmware drivers, perform a full **cold boot** of both computers.
1. Fully shut down your **main PC**.
2. Fully shut down your **second PC**.
3. Make sure the 35T card is connected correctly.
4. Power both systems back on.
A cold boot ensures the card and newly installed drivers initialize from a completely powered-off state.
***
## 🔧 Troubleshooting
### No COM Port Appears
If **USB-SERIAL CH343** does not appear under Device Manager:
* Reinstall `UpdateDriver\SETUP.EXE`
* Try another USB port
* Try another data-capable USB-C cable
* Avoid USB hubs and extension cables
***
### `Serial not connect!`
If LurkerUpdater displays:
`Error: Serial not connect!`
Check:
* USB-C JTAG/Update cable
* Correct COM port is selected
* You clicked **open**
* The button currently displays **close**
***
### DNA Does Not Appear
If typing `qaqaqa` does nothing:
1. Click inside the LurkerUpdater window.
2. Confirm the correct COM port is selected.
3. Confirm the port is open and the button displays **close**.
4. Type:
`qaqaqa`
Do not press Enter.
***
### LEDs Are Not Blinking
If the card is powered but does not enter its expected flash-ready state:
1. Make sure you are **not currently flashing firmware**.
2. Power-cycle the card.
3. Reconnect it and check the LEDs again.
You may need to repeat the power cycle once or twice.
***
### Flash Fails Partway Through
A flash that stops or fails partway through can be caused by an unstable USB connection or power source.
Try the following:
* Move the USB-A power cable to a **rear motherboard USB 3.0 port**
* Avoid hubs or extensions
* Confirm both USB cables are secure
* Restart the flashing process from the beginning
* Confirm **FileType = BIN**
* Confirm the firmware matches your card's DNA
***
## ✅ Quick Checklist
Before flashing:
* [ ] LurkerUpdater extracted
* [ ] Serial driver installed
* [ ] USB-A Data/Power connected
* [ ] USB-C JTAG/Update connected
* [ ] USB-SERIAL CH343 visible in Device Manager
* [ ] Correct COM port selected
* [ ] Port opened in LurkerUpdater
* [ ] DNA retrieved with `qaqaqa`
* [ ] Firmware matches your DNA
During flashing:
* [ ] FileType set to **BIN**
* [ ] Correct `.bin` firmware selected
* [ ] Both USB cables remain connected
* [ ] Power remains uninterrupted
* [ ] Flash completes without errors
After flashing:
* [ ] Card restarted
* [ ] Firmware `.INF` drivers installed on main PC
* [ ] Both PCs cold booted
* [ ] DMA speed test completed successfully
***
### ✅ You're Done
You have now successfully flashed your 35t 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ducks-services.com/dma/dma-fimware/35t-firmware-flashing.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
