Cartographer 3D
  • Welcome
  • 🗺️Cartographer Probe
    • Scan vs Touch Modes
    • 🏗️Installation and Setup
      • Before You Begin
      • Hardware Setup
        • CAN Termination
        • Stealthburner CW2 Mount
        • Wiring Diagrams
      • Software Configuration
        • Klipper Setup
        • Klipper Configuation
        • Calibration
        • Print Start Macro
        • First Print
        • Migrating from Cartographer to Scanner
      • Creality K1 & K1 Max Specific
      • Qidi Specific Installation Instructions
    • 📐Fine Tuning
      • Cartographer Models
      • Temperature Differential Calibration
      • Useful Macros
      • Extras
    • ♻️Firmware
      • Broken Katapult Bootloader
      • CANBUS Bitrate Switching
      • Firmware Switching
        • CANBUS to USB
        • USB to CANBUS
      • Firmware Updating
        • via Katapult
          • USB Flash
          • CANBUS Flash
        • via DFU
      • Manual Methods
        • ⬆️Firmware
        • Update or Re-Flash via ST-Link
        • Switching between CAN and USB Operation (v3 only)
        • Cartographer with Input Shaper
          • Update via Katapult (recommended)
          • Update via DFU Mode
        • Archive
          • Katapult
          • Re-Flashing Firmware
          • Cartographer (rp2040)
            • DFU / U2F Bootloader Mode
          • Which Firmware?
            • Cartographer v1 (RP2040 based probe)
            • Cartographer v2 or v3 w/ Input Shaper (USB/CAN)
              • Old Firmware
          • Update via STLink
    • ⚙️Settings & Commands
    • 😭Troubleshooting
    • 🆘Need Assistance?
    • 🔗Useful Links
    • ⁉️FAQ
    • 🔧Assembly
      • Standard
      • Low Profile
      • Right Angle
    • Archive
      • v1 (RP2040 Based Probes)
        • Klipper Configuration
        • Calibration
      • Classic Installation
        • Klipper Setup
        • Klipper Configuration
        • Calibration
      • Scan Based Calibration
  • 🚠Cartographer CNC Mount
    • 🚧Installation
  • 🌪️Linear Motor
    • 🗓️Coming Soon
Powered by GitBook
On this page
  • Equipment / Parts Required
  • Method 1
  • Method 2
  • Firmware
  • Entering DFU Mode
  • Flashing via STM32CubeProgrammer (Windows & MacOS)
  • Flashing via DFU Util (Linux Terminal).
  1. Cartographer Probe
  2. Firmware
  3. Manual Methods
  4. Archive

Re-Flashing Firmware

PreviousKatapultNextCartographer (rp2040)

Last updated 1 year ago

A number of probes unfortunatly shipped miss-flashed with the incorrect firmware, this guide will go through how to re-flash them with the correct firmware.

Equipment / Parts Required

For this, you will need the following items / tools, though it does vary depending on the configuration you recieved, or if you have any existing equipment.

If you recieved a USB Cable with your order, OR have a USB Cable terminated with a JST-PH connector then continue from here

If you happen to have a ST-Link Flasher (), the process is a bit simpler, to find out more information click

There are two solutions;

  • Method 1 - Modifying a USB cable to connect with the CAN cable

  • Method 2 - Create a USB Cable with a JST-PH Connector

Method 1 Equipment

  • A old USB cable, any old USB2 cable which does data (not a charge only USB-C Cable)

  • Your fastener pack that came with your probe

  • Your CAN cable

  • Some cutters / strippers.

  • 1 or 2 Tweezers (or something to bridge the BT0 and RESET pad)

Method 2 Equipment

  • A old USB cable, any old USB2 cable which does data (not a charge only USB-C Cable)

  • Your fastener pack that came with your probe

  • Some cutters / strippers.

  • A crimp tool for JST-PH

  • 1 or 2 Tweezers (or something to bridge the BT0 and RESET pad)

Method 1

Step 1 - Cut the end off your donor USB cable

Step 2 - Remove the outer plastic, revealing the 4 pairs of cables

Remove any outer sheilding

Use your snippers / strippers to expose about 6 - 8 mm at the end of your wires

Step 3 - Feed the exposed wires into the DuPont connectors, and use the right angle DuPont male connectors to plug the cable in and force contact

Typically the following cables will be matched with each other

USB Cable
CAN Cable

Red - 5v

Red - 5v

Black - GND

Black - GND

Green (D+)

Yellow (Can H)

White (D-)

White (Can L)

You should be able to connect your USB Cable to your computer now, as the probe will have accidently been flashed with USB Firmware rather than CAN, so if you plug into a Windows PC, you should hear that new device connected chime.

If you plug it into your Pi, or a linux PC it shouild appear under lsusb as OpenMoko, and if you recieved your probe in mid-march, and it has the USB firmware on it, if you do:

ls /dev/serial/by-id/

It should appear as a serial device there. Any issues, please join our Discord and ping me (RichardTHF) for help and support.

Method 2

Crimping your own JST-PH - USB cable, this is a useful cable to have, and can be done with the crimps and connector incldued with the probe.

Step 1

Cut the end off your donor USB cable. This needs to be a cable which works for data, there seem to be a lot of USB cables which are power only, these will not work.

Step 2

Strip the cable back to reveal the internal cables.

Step 3

Crimp the JST PH connectors onto the cable.

I found this video for how to crimp JST connectors, check it out its very well done.

Step 4 - Rehouse the connector

Notice the order - of the cable and connector.

You should be able to connect your USB Cable to your computer now, as the probe will have accidently been flashed with USB Firmware rather than CAN, so if you plug into a Windows PC, you should hear that new device connected chime.

If you plug it into your Pi, or a linux PC it shouild appear under lsusb as OpenMoko, and if you recieved your probe in mid-march, and it has the USB firmware on it, if you do:

ls /dev/serial/by-id/

It should appear as a serial device there. Any issues, please join our Discord and ping me (RichardTHF) for help and support.

The following method is compatible with MOST Cartographer probes, please check the compatibility chart listed below.

Firmware

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.

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

  • Mac - TBC

Flashing via STM32CubeProgrammer (Windows & MacOS)

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.

Open the application, and on the RIGHT side, select the following options and press Connect.

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.

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.

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).

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 v3 run the following command.

cd ~/cartographer-klipper/firmware/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 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_Cartographer_USB_v3.bin

Once compelete, it should exit out of DFU mode, and you should be able to find your probe using either CAN or USB.

The best place to get the probes firmware is from our . 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 .

You can also build your own firmware, our GitHub organisation has both a custom build of and that you can build yourself.

You should see STM32 BOOTLOADER as an option

Download and Install STM32CubeProgrammer from , I warn you it requires you to sign up for an account.

If in doubt about what address to use, please check the relevent tables

🗺️
♻️
like this
here
GitHub
here
Klipper
Katapult
here
here
Remove the end of the USB Cable
Remove the outer plastic
Notice the DuPont 2.54mm RA connectors plugging the cable in.
Notice the order of the cables.
STM32CubeProgrammer Settings
Firmwares Loaded
How to change the address in STM32CubeProgrammer