Skip to content

Added STM32H750 with 32kb offset#7219

Open
wildBill83 wants to merge 4 commits intoKlipper3d:masterfrom
wildBill83:master
Open

Added STM32H750 with 32kb offset#7219
wildBill83 wants to merge 4 commits intoKlipper3d:masterfrom
wildBill83:master

Conversation

@wildBill83
Copy link

@wildBill83 wildBill83 commented Mar 3, 2026

STM32H750 only has 128kb of storage so the STM32H7 typical offset of 128kb would be too large, I added it to the 32kb bootloader selections.

Signed-off-by: Bill Horan whoran83@gmail.com

STM32H750 only has 128kb of storage so the STM32H7 typical offset of 128kb would be too large, I added it to the 32kb bootloader selections.
@wildBill83 wildBill83 changed the title Addted STM32H750 with 32kb offset Added STM32H750 with 32kb offset Mar 3, 2026
@asnajder
Copy link

asnajder commented Mar 3, 2026

Tested and working on my Sovol Zero, which uses STM32H750

@nefelim4ag
Copy link
Collaborator

nefelim4ag commented Mar 3, 2026

Just for cross-linking:
Arksine/katapult#177

Because they depend on each other, I think.

Also, you want to add a sign-off, at least in the message (https://www.klipper3d.org/CONTRIBUTING.html).
(same for the katapult)

Thanks,
-Timofey


Ah, just a suggestion, you can also check the 400 -> 480MHz, it should probably work.

Co-authored-by: asnajder <andrew.snajder@gmail.com>
@wildBill83
Copy link
Author

Thanks for the help and testing guys!

-wildBill83

@wildBill83
Copy link
Author

Just for cross-linking: Arksine/katapult#177

Because they depend on each other, I think.

Also, you want to add a sign-off, at least in the message (https://www.klipper3d.org/CONTRIBUTING.html). (same for the katapult)

Thanks, -Timofey

Ah, just a suggestion, you can also check the 400 -> 480MHz, it should probably work.

I have added my signoff in the initial post. Sorry for missing that.

bool "16KiB bootloader" if MACH_STM32F207 || MACH_STM32F401 || MACH_STM32F4x5 || MACH_STM32F103 || MACH_STM32F072
config STM32_FLASH_START_20000
bool "128KiB bootloader" if MACH_STM32H743 || MACH_STM32H723 || MACH_STM32F7
bool "128KiB bootloader" if MACH_STM32H743 || MACH_STM32H723 || MACH_STM32F7 || MACH_STM32H750
Copy link
Collaborator

@nefelim4ag nefelim4ag Mar 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You explicitly said that 128Kb is an invalid offset, because 128kb is a whole flash memory size.
So, why are you adding H750 here?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can add my two cents regarding that.

There is a scenario where 128KiB is actually preferred - if you are using a Sovol Zero mainboard, it ships with a 128KiB offset and what we believe to be a QSPI flash chip.

STM32H750-QSPI

Myself and many others have flashed Klipper with the 128KiB offset using Sovol's shipped Katapult successfully. (In fact, if you flash Klipper with the "correct" offset of 32KiB on top of Sovol's Katapult, it bricks the chip and you need to get your st-link out).

The stock board's Katapult reports 128, and there are mentions of quadspi in the sovol repo.

So in summary, there are two scenarios at play here:

  1. For those "mainlining" off of Sovol's stock version of Klipper, flashing with a 128KiB offset "just works" and you do not need to re-do Katapult with 32KiB and then flash Klipper with 32KiB.
  2. For those not using a Sovol Zero mainboard, but their board has an STM32H750, you can do it with 32KiB.

Therefore, it would be advantageous to have 128KiB as an option to flash Klipper with on the STM32H750.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants