Octopus pro stm32h723

General Discussion
1

Basic Information:

Printer Model: Core xy Home Brew
MCU / Printerboard: Octopus Pro tcm32h723
Host / SBC Raspberry Pi
klippy.log
klippy-5.log (129.8 KB)

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

… I have spent days looking how to update the file.

Pulled all my hair out.

The answer will be simple as usual.

Need to update Klipper make menuconfig

Any help would be greatly appreciated.

Bootloader offset (128KiB bootloader (SKR SE BX v2.0))

Thanks

Byron

Klipper make menuconfig

(Top)
Klipper Firmware Configuration
[*] Enable extra low-level configuration options
Micro-controller Architecture (STMicroelectronics STM32) —>
Processor model (STM32H723) —>
Bootloader offset (128KiB bootloader) —>
Clock Reference (25 MHz crystal) —>
Communication interface (USB to CAN bus bridge (USB on PA11/PA12)) —>
CAN bus interface (CAN bus (on PD0/PD1)) —>
USB ids —>
(1000000) CAN bus speed
() GP
printer.cfg (15.4 KB)
IO pins to set at micro-controller startup

image
image718×225 7.71 KB

2025-03-04T13:00:00Z

2

This is from my Octopus pro with STM32H723.

[*] Enable extra low-level configuration options
    Micro-controller Architecture (STMicroelectronics STM32)  --->
    Processor model (STM32H723)  --->
    Bootloader offset (128KiB bootloader)  --->
    Clock Reference (25 MHz crystal)  --->
    Communication interface (USB (on PA11/PA12))  --->
    USB ids  --->
(PD15) GPIO pins to set at micro-controller startup

And your serial will looks like: /dev/serial/by-id/usb-Klipper_stm32h723xx_0C0024001951313434373135-if00

In case of CAN:

[*] Enable extra low-level configuration options
    Micro-controller Architecture (STMicroelectronics STM32)  --->
    Processor model (STM32H723)  --->
    Bootloader offset (128KiB bootloader)  --->
    Clock Reference (25 MHz crystal)  --->
    Communication interface (USB to CAN bus bridge (USB on PA11/PA12))  --->
    CAN bus interface (CAN bus (on PD0/PD1))  --->
    USB ids  --->
(1000000) CAN bus speed
(PD15) GPIO pins to set at micro-controller startup

There will be a can0 network device and no serial.

Hope it helps.

3

I have tried this config and get the this klippy log
I have been following the Esoterical github the only thing that
that is different is the bootloader offset
Klipper reports: STARTUP

Printer is not ready
The klippy host software is attempting to connect. Please
retry in a few moments.

4

you are trying to connect to a katapult id not a klipper one mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/usb-katapult_stm32h723xx_1E0003000751313339373836-if00: [Errno 2] No such file or directory: '/dev/serial/usb-katapult_stm32h723xx_1E0003000751313339373836-if00' seems you have a katpult flash but no klipper one. workflow to flash klipper over katapult would be

cd ~/klipper
make clean
make menuconfig
make
cd ~/katapult/scripts
sudo apt install python3-serial
python3 flashtool.py -d /dev/serial/usb-katapult_stm32h723xx_1E0003000751313339373836-if00

then you would query for your canbus_uuid, as usb can bridge klipper flashes dont show a by-id.

flashtool.py -i can0 -q

you would then add the found uuid into config with

[mcu]
canbus_uuid: xxxxxxxxxxxx
5

I tried this in usb and then in dfu mode and get the same result

Flashing Serial Device /dev/serial/usb-katapult_stm32h723xx_1E0003000751313339373836-if00, baud 250000
ERROR:root:Flash Error
Traceback (most recent call last):
File “/home/byron/katapult/scripts/flashtool.py”, line 875, in main
await sock.run(args.device, args.baud, fpath, req_only)
File “/home/byron/katapult/scripts/flashtool.py”, line 786, in run
await self.validate_device(intf)
File “/home/byron/katapult/scripts/flashtool.py”, line 695, in validate_device
raise FlashError(f"No Serial Device found at {dev_path}")
FlashError: No Serial Device found at /dev/serial/usb-katapult_stm32h723xx_1E0003000751313339373836-if00

6

maybe you have already flashed it properly, run

lsusb

do you see an openmoko can adapter?

7

byron@hevort:~/klipper $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 036: ID 1d50:6177 OpenMoko, Inc. stm32h723xx
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

byron@hevort:~/klipper lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 037: ID 0483:df11 STMicroelectronics STM Device in DFU Mode Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub byron@hevort:~/klipper

8

Hi Timofey

All my settings appear to be working. I am getting this error

Klipper reports: STARTUP

Printer is not ready
The klippy host software is attempting to connect.  Please
retry in a few moments.


The only make menuconfig settings that does not appear in 


in the klipper config is 


Bootloader offset ((128KiB bootloader)SKR SE BX v2.0))


This Bootloader offset appears in the katapult config.


It seems to me that I need to upgrade the klipper make menuconfig file.


I have followed the Esoterical install at least 15 times and this is the only discrepancy I have been able to find.
9

I have just looked at rolling back the katapult make menuconfig bu there is no option to do this

Cheers

Byron