> For the complete documentation index, see [llms.txt](https://docs.mclimate.eu/mclimate-lorawan-devices/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mclimate.eu/mclimate-lorawan-devices/other/device-firmware-upgrade-via-a-field-programming-kit-fpk.md).

# Device Firmware upgrade via a Field Programming Kit (FPK)

All MClimate devices now support [Firmware Upgrade Over The Air (FUOTA)](/mclimate-lorawan-devices/firmware-upgrade-over-the-air-fuota.md).

However,, certain older firmware versions can only be upgraded to the latest firmware via a manual upgrade procedure that requires a set of special adapter tools directly be connected to the PCB in a certain way. Once updated to a more recent version, the device will support FUOTA, so the FPK wouldn't be required.

A proprietary MClimate software tool needs to be used to facilitate the process, which we call Field Programming Kit or FPK for short. MClimate can provide both the hardware and software tools (in the form of a pre-installed Laptop kit) in order to perform the upgrade in the field.

Take note the procedure differs depending on which MClimate device you want to upgrade. Please navigate to one of the next sections that matches yours.


---

# 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.mclimate.eu/mclimate-lorawan-devices/other/device-firmware-upgrade-via-a-field-programming-kit-fpk.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.
