> For the complete documentation index, see [llms.txt](https://docs.cartographer3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cartographer3d.com/cartographer-probe/archive/broken-katapult-bootloader.md).

# Broken Katapult Bootloader

There are some Cartographer V3 ADXL probes that were shipped with a broken version of katapult. Unfortunately this means that when you go to update firmware via Katapult, the device wont be able to enter katapult mode for flashing.\
\
Fixing it is quite simple.

## Step 1. [Visit Here for the DFU flashing guide.](/original-plugin/firmware-archive/firmware-updating/via-dfu.md)

## Step 2. Once Flashed

If you chose FULL CANBUS, unplug the cable and plug Cartographer into your CANBUS cable.

If you chose FULL USB, unplug and re-plug into USB cable.

## Step 3. All Done

## Optional Step: Survey Touch

If you want to use **Survey Touch you will need to do some extra steps.**

* For USB, [Check out this guide on updating firmware to Survey Touch mode.](/original-plugin/firmware-archive/firmware-updating/via-katapult/usb-flash.md)
* For CANBUS, [Check out this guide on updating firmware to Survey Touch mode.](/original-plugin/firmware-archive/firmware-updating/via-katapult/canbus-flash.md)

### Katapult Bootloader will now be fixed for future flashing and DFU will not be required unless another issue arises with Katapult.


---

# 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.cartographer3d.com/cartographer-probe/archive/broken-katapult-bootloader.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.