Environment
- Original Creality CFS (G32), connected through CH340/RS485
- Creality K1C, host firmware 2.3.5.34
- Upstream
cfstool.py from this repository
Observed behavior
After a successful flash transfer, the CFS application did not answer any immediate follow-up commands. APP-mode queries and diagnostics were not
usable immediately after flashing, which made the update appear unsuccessful.
What made it work
After the flash process had fully completed, I physically powered off the CFS, powered it back on, and then started Klipper again. The CFS then worked
normally.
Documentation suggestion
For at least some original G32 CFS units, a physical CFS power-cycle may be required after a completed flash before judging the result from APP-mode
commands or starting Klipper.
Important: this is not a recommendation to power-cycle during a flash. The power-cycle was done only after the transfer/process had completed.
Environment
cfstool.pyfrom this repositoryObserved behavior
After a successful flash transfer, the CFS application did not answer any immediate follow-up commands. APP-mode queries and diagnostics were not
usable immediately after flashing, which made the update appear unsuccessful.
What made it work
After the flash process had fully completed, I physically powered off the CFS, powered it back on, and then started Klipper again. The CFS then worked
normally.
Documentation suggestion
For at least some original G32 CFS units, a physical CFS power-cycle may be required after a completed flash before judging the result from APP-mode
commands or starting Klipper.
Important: this is not a recommendation to power-cycle during a flash. The power-cycle was done only after the transfer/process had completed.