Added STM32H750 with 32kb offset

[wildBill83]

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

[asnajder]

Tested and working on my Sovol Zero, which uses STM32H750

[nefelim4ag]

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.

[wildBill83]

Thanks for the help and testing guys!

-wildBill83

[wildBill83]

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.

[nefelim4ag]

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

[asnajder]

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.

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.

[KevinOConnor]

Thanks. In general it seems fine and I'm okay with committing these changes. However, it looks to me like there are two separate changes - increase the clock speed of stm32h750 to 480Mhz and support bootloader sizes on stm32h750. Due to the risk of a regression, I'd need those two changes to be in separate commits.

It would help if you can either use git rebase to reformat the commits so there are just two commits and the commit messages follow the guidelines at https://www.klipper3d.org/CONTRIBUTING.html#format-of-commit-messages , or split the changes into two separate PRs. (If you split the changes into two separate PRs I can use github's "squash and merge" to ensure the commit messages follow the guidelines.)

Cheers,
-Kevin

[Chineko-Koizumi]

Sovol zero and Max use STM32H750 so if someone want to use katapul alongside klipper have to build klipper with bootloader offset. I can confirm that this works on SV08 Max

[KevinOConnor]

Thanks. I rebased this branch and committed it (commits 666781a and 43f9219).

-Kevin

[github-actions]

This ticket is being closed because the underlying issue is now thought to be resolved.

Best regards,
~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being.