The main difference if have seen is the size of the firmware
firmware v0.11 28kB
firmware v0.13 42kB (but i think this is because off more feature)
Has enybody an idea what’s wrong ?
my MCU is a STM32F070CBT6
I wonder if there is a bootloader programming issue when the flash size is in a particular range. It might be worth reducing code size to see if it resolves the issue.
Check the Only 6KiB of RAM box. Note that I haven’t changed any other configuration in the screenshot below, make sure you set the correct bootloader offset, clock reference, etc.
Scroll down to Support Trinamic stepper motor driver UART communication and deselect it and everything below it. Save and build. This should get the code size down below 28 KiB.
i could not belive, but this did it.
Have done as you suggested. now my firmware file is 18 KiB.
And its working.
I was suprised because the stock firmware is 80KiB. But anyway. It’s working.
And if i can stripe down my firmware on a minimal size, double good.
I didn’t test my hole printig because no task at the moment. But the printer become responsive with the actual firmware and homeing is working. Also temperature data is visible.
I have extra GPIO Pin’s set and these are also working.
I don’t expect any issues. On weekend i will print something.
Format a small ssd-card with fat32.
Copy klipper.bin to firmware.bin in the root directory.
Copy the a file fcupdate.flg in the root directory.
This file has to be at least 1KiB. Content doesn’t matter.
I picked the file from the page below.
Sick in the ssd-card into the printer.
Switch off then on. The upgrade process started automatically.
After upgrade the printer reboots. That’s it.
I found the information here:
Monoprice MP Select Mini Pro Motion Controller Firmware Update Instructions at:
The most likely explanation for the original problem is that the stock bootloader is doing something weird.
You can continue to run with the stm32f070x6 compile if you wish. It’ll only be able to utilize 6KiB of ram, but that’s probably not a huge issue.
An alternate solution may be to replace the bootloader with Katapult ( GitHub - Arksine/katapult: Configurable bootloader for Klipper ). Replacing the bootloader takes some work and has some risks though (if the bootloader is not flashed correctly it can be very difficult to repair). So it’s understandable if one wishes to stay with the stm32f070x6 image.
as long as the minimal klipper firmware is working i will stay at the original bootloader.
If i run in issues later i will sell my printer and buy a new bigger one with a board that is better supported by klipper. It makes no sense to waste time and money on it.
I think you are rigth regarding stock bootloader is doing something weird. The stock firmware is really stupid but has some silly thinks like webinterface and wifi stuff and also a useless touchsceen that waste a lot of flash and is maybe splitt in partitions.
Maybe i will investigate the original firmware with binwalk. But not yet.
Interesting. My initial thought was a bug in the stock bootloader, however I wonder if the board ships with write protection enabled on some sectors where assets are stored for the UI.
