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
  • Requirements
  • Step 1 - Wire up your probe
  • If using Windows follow the next steps, if you are using Linux (Pi) click here
  • Step 3 - Check the Settings
  • Flash and Confirm Firmware
  • Flashing via Linux (Pi)
  • Reconnect your probe to your printer
  1. Cartographer Probe
  2. Firmware
  3. Manual Methods

Update or Re-Flash via ST-Link

PreviousFirmwareNextSwitching between CAN and USB Operation (v3 only)

Last updated 8 months ago

pdating via the ST-Link provides a reliable and easy way to flash any STM based MCU's especially if you have issues entering DFU mode, the only time where it becomes problematic is when older/fake ST-Links are used, please see the notes and ways of identifying below.

Requirements

  • ST-Link v2 (Below is a table of the most common ST-Link v2s. There are obviously more available on the market.

STLink
ST-Link V2 Mini (Fake MCU)
ST-Link V2 Mini
ST-Link V2

Image

Note

Uses fake STM Chip, Pin order is different and isnt always recognised via STM Cube Programmer.

Occasional Issues, depending on age / firmware.

Most Reliable

STMCubeProg Compatible

❌

May not work

✅

  • STM Cube Programmer - (recommended version v2.15.0) - if using Windows or MacOS

  • 4x DuPont M-M or M-F Cables

  • Cartographer V3 Probe

Step 1 - Wire up your probe

Connect the following pins based upon the different ST-Links.

Hardware
Pinout
Connections (STLink - Probe)

ST-Link V2

SWDIO - SWD SWCLK - SCL GND - GND VCC - 5V

ST-Link V2 Mini (Fake Chip)

SWDIO - SWD SWCLK - SCL GND - GND 3.3V*- 5V * 5v may also work , but on some mini's it can cause stability issues.

ST-Link V2 Mini

SWDIO - SWD SWCLK - SCL GND - GND 3.3V*- 5V * 5v may also work , but on some mini's it can cause stability issues.

Connect your probe to the STLink connectors to the left and the right of the JST connector.

You do NOT need to solder in the connector, pressure fit is fine.

Open STM32CubeProg

Select Open File and select the file you want to open. For this, I recommend flashing the FULL complete firmware files, which include both bootloader and Cartographer firmware.

Step 3 - Check the Settings

Ensure that you are writing to the correct memory location

If your firmware is from the combined-firmware folder or starts with the words Katapult, ensure that the address is set to 0x08000000

Ensure that you have ST-LINK slelected on the right (this can default to DFU mode if you havnt used this before)

Now press Connect and the screen should indicate that the probe is Connected

Flash and Confirm Firmware

Press download to Download the firmware to your Cartographer

The output should look something like this

Press Disconnect and unplug the probe.

Flashing via Linux (Pi)

  1. SSH into your 3D Printer using your client of choice

  2. Run the following command (this may take a little while)

sudo apt-get update
sudo apt-get upgrade
sudo apt-get -y install stlink-tools
  1. Navigate to the folder where your firmware is stored, usually

cd ~/cartographer-klipper/firmware/v2-v3/combined-firmware
  1. Check if the ST-Link has been detected using lsusb if it is not visable, unplug and re-plug it back in.

  1. run the following command replacing firmware.bin and the memory address with the correct address for the firmware that you are using.

st-flash write firmware.bin 0x080000000

For example to flash the Survey CAN firmware

st-flash write Full_Survey_Cartographer_CAN_1M_5_0_0.bin 0x08000000

Upon completion, you should see something like this

Reconnect your probe to your printer

Reconnect your probe to your 3D Printer, and it should work perfectly :)

If using Windows follow the next steps, if you are using Linux (Pi)

🗺️
♻️
click here
LogoSTM32CubeProg - STMicroelectronicsSTMicroelectronics
Pinout on Cartgorapher V2 and V3
Connected on ST-Link V2
Connected to a ST-Link v2 Mini (with a Genuine STM Chip)
Select the file you need
Original lsusb not being able to see the ST-Link, second one able to see it.
Successful Flash