Closed blondsign closed 1 year ago
You are the first person I know with a 4.5.2 board on which to test this theory, so I hope this works flawlessly.
The regular Klipper installation instructions call for precisely the same Make Menuconfig settings for all three of the Creality motherboards (4.5.2, 4.5.3 and 1.1.0.3 ERA).
Those settings are slightly different from what you have pasted above:
If that commonality of configuration holds true, here, you should be able to flash the precompiled bin file in this folder to your motherboard:
If you prefer to make your own bin file, these would be the Make Menuconfig settings to try:
The "usual rules" about having to rename the bin file each time you try again will apply, if the first flash does not work.
Remember that you will also have to change the serial interface id in the [mcu] section of your printer.cfg file, to get past that unknown ping command. (See |Where's my serial port?| in https://www.klipper3d.org/FAQ.html)
Hi @Thinkersbluff, I was able to solve the Issue. Unfortunately the firmware was not flashed, because I didn't changed the name of the file (not the same name as last flash is allowed). Now I am very happy with a running screen. Thanks a lot for the quick help and reply.
For the sake of others who have the 4.5.2 board, please confirm what make menuconfig worked for you?
Both ways.. Pre-compiled, as well as STM32F03 -> 28kiB Bootloader -> USART1 PA10/PA9 -> Screen -> USART3 (PB11/PB10)
Oh good! So I can safely update the documentation here to say that the same klipper.bin file works on all 3 Creality boards. Thank you!
Yes should be fine. Thank you for creating this nice thing!
Discussed in https://github.com/Thinkersbluff/DGUS-Reloaded_for_CR6-DWIN-SET_Component/discussions/15