# Update via DFU Mode ### Compatibility The following method is compatible with MOST Cartographer probes, please check the compatibility chart listed below. | Probe | Interface | Compatible | | ----------------------------------------------------------- | --------- | --------------------------------------------------------------------------------------------------------------------- | | Cartographer V1 (RP2040) | USB | [Click Here](/original-plugin/firmware-archive/manual-methods/archive/cartographer-rp2040/dfu-u2f-bootloader-mode.md) | | Cartographer with Input Shaper (v2) | USB | Yes | | | CAN | No | | Cartographer Probe v3 with Input Shaping (Hybrid USB & CAN) | USB | Yes | | | CAN | Yes | ### Pre-requirements Prior to flashing, you will need to following tools * 2 x Ferrous Tweezers (or any conductive tool to bridge the two pads) * 1 x Compatible Cartographer Probe (see above) * 1 x USB Cable terminated to work w/ Catographer ### Firmware The best place to get the probes firmware is from our [GitHub](https://github.com/Cartographer3D/cartographer-klipper/tree/master/firmware). These have been tested thoroughly, and are known to work perfectly. If you want to find a link to the latest firmware for each of your probes, please check [here](/original-plugin/firmware-archive/manual-methods/firmware-update.md). You can also build your own firmware, our GitHub organisation has both a custom build of [Klipper](/readme.md) and [Katapult](https://github.com/Cartographer3D/katapult) that you can build yourself. {% hint style="danger" %} Untested Firmware could brick your probe - it is advisable if this is the case, you have a STLink handy in order to easily re-flash the probe. {% endhint %} ### Entering DFU Mode To enter DFU Mode, it can be a bit fiddly, but once you get the knack of it, it's fairly simple. Plug your USB cable into the device you will be flashing from and your Cartographer probe, this can be either a seprate Windows PC, Mac, or a Linux machine, or the device you run your 3D Printer off. Using your ferrous tweezers, or similar use one to bridge pads 1 (boot0), once you have a solid contact on those tap pad 2 (reset) with your other ferrous tool.
If you have done this correctly, your device should have entered DFU Mode. To check, * Linux - follow the following steps * SSH in, or load a termanal shell. * type `lsusb` in your bash shell, it should list a device in DFU Mode * One of the options should be `Bus 001 Device 004: ID 0483:df11 STMicroelectronics STM Device in DFU Mode` - This (as long as you don't have any other devices in DFU Mode) should be your Cartographer Probe in DFU Mode. * Windows - follow the following steps * Start Menu * Search and open "Device Manager" * Scroll down to Universal Serial Bus Devices * You should see STM32 BOOTLOADER as an option\ Device Manager view of Cartographer in Bootloader mode. * Mac - TBC ### Flashing via STM32CubeProgrammer (Windows & MacOS) Download and Install STM32CubeProgrammer from [here](https://www.st.com/en/development-tools/stm32cubeprog.html), I warn you it requires you to sign up for an account. {% hint style="warning" %} Version 2.14.0 is recommended due to a known bug in 2.16.0 which causes issues when flashing via STMCubeProgammer - this can be selected from the version 'drop down' on the site. {% endhint %} Open the application, and on the RIGHT side, select the following options and press **Connect**.

STM32CubeProgrammer Settings

Once you have connected, Click Open File - you will need to select both the Katapult Bootloader for your board, and your Cartographer Firmware that you have downloaded.

Firmwares Loaded

For your Cartographer Firmware, you need to set the address to `0x08002000` This provides the 8KiB offset for the firmware. Katapult firmware can be flashed at the default `0x08000000.`

How to change the address in STM32CubeProgrammer

If in doubt about what address to use, please check the relevent tables [here](https://docs.cartographer3d.com/firmware-update) On each of the firmware's press "Download", starting with Katapult, then with Cartographer. \ \ Now press Disconnect in the TOP RIGHT corner. If your BLUE LED is Flashing, you have not fully flashed your Firmware, and you should start again, If you now Power Cycle your probe, or simply hit the RESET (2) pads from earlier, your probe should react when it has anything solid metal put under it. ### Flashing via DFU Util (Linux Terminal). {% embed url="" %} SSH into your linux host MCU, ensuring that your Cartographer is plugged in and in DFU Mode. Navigate into the correct folder, so if you want to update your v2 or v3 run the following command. ``` cd ~/cartographer-klipper/firmware/v2-v3 - Carto with Input Shaper Hybrid ``` Once in the folder, simply check that your probe is still in DFU Mode by running `lsusb`, and if you still get a result stating it is in DFU Mode, run the following command. ``` dfu-util -R -a 0 -s 0x08000000:leave -D firmware.bin ``` NOTE - REPLACE the address (`0x08000000`) with what ever is listed in the [table here](/original-plugin/firmware-archive/manual-methods/firmware-update.md) for the specific firmware you are using, and rename `firmware.bin` to what ever the firmware file you are using is called. Example: ``` dfu-util -R -a 0 -s 0x08000000:leave -D Full_Survey_Cartographer_USB_v3.bin ``` Once compelte, it shoudl exit out of DFU mode, and you should be able to find your probe using either CAN or USB. --- # Agent Instructions: 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: ``` GET https://docs.cartographer3d.com/original-plugin/firmware-archive/manual-methods/cartographer-with-input-shaper/update-via-dfu-mode.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.