-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flashing over "pure" serial connection (Creality 4.2.7 board)? #100
Comments
To answer your second question, yes, it is possible for Katapult to flash Klipper over Serial, provided you configured Katapult correctly. If you chose If you flashed with the USB option configured you'll need to use a programmer to recover. The schematic shows that the debug pins are available, however it looks like you might need to solder your own headers. With regard to the first question, there is an LED configuration that is intended to notify users when Katapult is running and when it is flashing. I'm not sure if the Creality 4.2.7 has any onboard LEDs, don't see any on the schematic. |
I selected serial as com interface:
But no luck to flash Klipper afterward. About the LEDs ... There are only two LEDs - Rx and Power. No extra Led on any other µC Pin sadly. Any other ideas what I could check / test to get katapult working? |
Unfortunately I don't have much more guidance to give. I would check to make sure the deployer flashed by attempting to flash Klipper via SD. Once you have verified that the stock bootloader is indeed not functional the next step is to attempt to program Katapult directly. One other thing, I presume that this board is a legit STM32F103, and not one of the GD32 clones? I know that Creality has released boards with both on the 4.2.2, but not sure about the 4.2.7. |
Oh, maybe you got me wrong. The stock bootloader works fine. It flashes Katapult over SD without any issue. Even flashing Klipper via SD and stock bootloader is no problem. I will try 2 things later
It looks to me like a normal STM32 and not a clone. I have a SKR Mini V2 Board which has the same controller (same ARM / STM labeling). |
Update Now I will reinstall the preinstalled bootloader + Marlin to check the deployer way. |
We can't erase all flash after Katapult as it would result in the deployer deleting itself. Generally its probably not a good idea to write to the application area while the deployer could be in it. Its possible to add, but I think unnecessary. As you have observed, the double reset is the primary solution when using the deployer. Boards that don't have a reset button can configure the |
Ok using an extra wire for the deployer could be a solution.
Got the point. But maybe Katapult could erase the rest of the flash after the first run? It would just prevent people from having extra hardware / extra wiring to get Katapult running. |
Unfortunately, I have to ask something again. Catapult and Klipper are installed on my board and Klipper is running. When I now start a Klipper update, it cannot reach the bootloader with any of the following commands:
Does it work at all with the STM32 F103 that Klipper starts the bootloader (in this case Katapult) in order to install an update? Or do I have to explicitly double-tap Reset (or an extra GPIO) to activate Catapult for flashing? |
It is possible to request the serial bootloader. You can't use make to do it, but you could write your own small script. Eventually we'll likely come up with a better way to unify all of this in Klipper. |
Ok in this case I think using the SD Method is easier as soon as Klipper is installed. This needs only one reboot and no Reset or button pressing. Would be great if Katapult / Klipper gets a mechanism to update F103 Boards without any user interaction. Anyway. Thx for your help and information on this topic! |
Hi !
Just installed Katapult on a Creality 4.2.7 board with the deployment method.
This worked for me.
I triedy to flash Klipper and I hoped to use this call for that:
~/katapult/scripts/flashtool.py -d /dev/ttyUSB0 -f ~/klipper/out/klipper.bin -b 250000 -v
But I got only this output:
Even if I Reset the board twice very quickly it´s not possible to flash Klipper.
The Creality board uses a CH340 chip as USB/serial bridge.
I hope anyone can help with these questions:
dmesg
. But with a pure serial connection this is not possible because it just reports "CH340 device" ...Dominik
The text was updated successfully, but these errors were encountered: