Bricked Printer Woes
I went to update my MK2S to the latest firmware but accidentally used the MK2.5S firmware (from octoprint). After the update completed, I received a fan error but the fan was spinning. I realized what I had done and downloaded the correct firmware. During the flashing of the firmware (Again from octoprint) I received a communication error. Now the printer just shows solid blocks for each character on the LCD. Octoprint can no longer communicate to the printer. So, I plugged my mac laptop directly into the printer and attempted to flash the firmware with Prusa Slicer. The printer was detected on the USB connection but upon beginning the flash I immediately get a communications error. So, I ran a longer USB cable to my Son's Windows 10 desktop and have the same behavior there. Prusa Slicer detects the printer on the COM port, but when I attempt to flash the firmware, it fails communicating again. The avrdude error is "Timeout communicating with programmer" "Could not open port COM4". Which is the correct COM port.
Any suggestions?
Thanks in advance!
~ted
RE: Bricked Printer Woes
did you download the hex file or build from source?
RE: Bricked Printer Woes
Did you disconnect Octoprint and the raspberry pi before flashing from PrusaSlicer?
Bill
Tagaytay City, Philippines
Founder member of Philippines Prusa Printer Owners FB Group
Sponsor Pillars of God Academy in Bacoor
RE: Bricked Printer Woes
Did you disconnect Octoprint and the raspberry pi before flashing from PrusaSlicer?
Yes. Since there is a single USB port, I don't think there is another option.
RE: Bricked Printer Woes
did you download the hex file or build from source?
I downloaded the hex file from the Prusa site.