Printer Model: Ender-3 S1 Plus
MCU / Printerboard: STM32F401
Host / SBC: Pi 4 Mainsail OS
klippy.log
Describe your issue:
It seems I have tried every kilpper.bin/firmware.bin combination and the printer still will not flash klipper. One of two things happens:
the screen is frozen with only small parts of the CREALITY logo visible
the boots appears to run smoothly as if the bin file was ignored and the stock firmware runs as usual
I have noticed though that the bash command file returns two different results for the following:
$ file firmware.bin
firmware.bin: data
$ file Ender-3S1_Plus_HWv24S1_301_SWV2.0.8.28F4_F401_FDM_LASER.bin
Ender-3S1_Plus_HWv24S1_301_SWV2.0.8.28F4_F401_FDM_LASER.bin: ARM Cortex-M firmware, initial SP at 0x20010000, reset at 0x08011e2c, NMI at 0x08011e7c, HardFault at 0x08011e7c, SVCall at 0x08011e7c, PendSV at 0x08011e7c
..which leads me to believe one is of course valid and the other is clearly missing headers.
Hi - I have a STM32F401, as I’ve removed the bottom cover and checked.
I was wondering if anybody with the same model could give me a working set of settings, I followed a few guides and AI and rarely were they all consistent, and none of the solutions worked so far.
Will Bootloader size and other details for a Pro work with a Plus? Thanks for the link, I will look at it.
Typically the bootloader on boards that update via SD card is left alone as updating it requires a STlink or similar. AFAIK you could but Catapult (bootloader) on the chip with a programmer. Then flash firmware updates over USB with KIAUH. I’ve never done it so do your own research before proceeding. @mykepredko is a good resource if you want to go this route.
Note: the in video I sent he is using stock Marlin files. I do note that the .bin file is in a folder not the root directory. See the header in the .cfg file above for details.