> For the complete documentation index, see [llms.txt](https://guides.privatesolution.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.privatesolution.org/firmware/firmware-installation.md).

# Firmware Installation

For most people, this page is a formality: your DMA card ships **pre-flashed**, so there is nothing to install. This page covers the rare case where firmware changes are needed, and what the process looks like.

## For new hardware orders

Nothing to do. The card arrives ready. Connect it and [run the speedtest](/dma-card-setup/speedtest.md).

## If we send you a firmware update

1. **Close any software** that is running on the 2nd PC.
2. **Download the file** from the link in your ticket.
3. **Run the flash tool** we sent with the file, on the 2nd PC.
4. **Pick your card** in the tool and click Flash.
5. **Wait for "Done"** — do not unplug anything while it runs. It takes under a minute.
6. **Power cycle the main PC** (full shut down, then on again).
7. **Run the speedtest** to confirm.

## If something goes wrong

* Flash interrupted? Just run the flash tool again — it is safe to repeat.
* Still stuck? Open your ticket. A real person will walk you through it, or we replace the card if the hardware is at fault.

{% hint style="warning" %}
Never flash a file we did not send you. Wrong firmware can make the card undetectable to the tool until it is re-flashed.
{% 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://guides.privatesolution.org/firmware/firmware-installation.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.