I ordered an avrprommer and with that I was able to reflash the bootloader. Problems are gone now. So it seems that the bootloader had become corrupt. I don't know how this happened, but I have a suspicion that it's because it's because I use OctoPrint on a RasberryPi, and the Creality mainboard is drawing power over the USB cable. There may have been a brownout condition which caused the bootloader corruption. I can't know for sure, but it's my best theory. So a word of caution for anyone with a similar setup.
Now I still have the buzzer going constantly even though I changed SERVO0_PIN to 29 in Configuration.h
Is there some other setting that affects the buzzer?
Thank you! I ordered an…
Thank you!
I ordered an avrprommer and with that I was able to reflash the bootloader. Problems are gone now. So it seems that the bootloader had become corrupt. I don't know how this happened, but I have a suspicion that it's because it's because I use OctoPrint on a RasberryPi, and the Creality mainboard is drawing power over the USB cable. There may have been a brownout condition which caused the bootloader corruption. I can't know for sure, but it's my best theory. So a word of caution for anyone with a similar setup.
Now I still have the buzzer going constantly even though I changed SERVO0_PIN to 29 in Configuration.h
Is there some other setting that affects the buzzer?