OctoPrint - Firmware update stuck?
This is mildly terrifying... OctoPrint is displaying "Starting Flash" but is stuck there. I am first and foremost furious that this stupid thing doesn't have a TIMEOUT function, but that is an Octoprint problem and not a Prusa problem.
I have a Prusa i3 MK3. I am trying to load 3.3.1 and this is my first attempt at updating the firmware since I received the printer.
First off: Is it safe for me to turn anything off to troubleshoot? It does not appear to be flashing... the printer LCD screen has not changed and the log file does not appear to have connected/started loading.
Second off: What is going wrong here? Some config/log info below:
FirmwareUpdate Config:
Path to avrdude: /usr/bin/avrdude
AVR MCU Type: ATmega2560
AVR Programmer Type: wiring
(I also set the baud rate to 115200 which seems to be the normal setting that works for Octoprint... Auto would fail)
Octoprint Log:
2018-09-02 03:26:27,134 - octoprint.plugins.firmwareupdater - INFO - Got CONNECTED event
2018-09-02 03:26:27,136 - octoprint.plugins.firmwareupdater - INFO - Run postflash flag is not set
2018-09-02 03:26:27,155 - octoprint.util.comm - INFO - Printer reports firmware name "Marlin V1.0.2; Sprinter/grbl mashup for gen6"
2018-09-02 03:27:00,008 - octoprint.plugins.firmwareupdater - INFO - Firmware update started
2018-09-02 03:27:00,010 - octoprint.plugins.firmwareupdater - INFO - Disconnecting from printer
2018-09-02 03:27:00,051 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Offline"
2018-09-02 03:27:00,084 - octoprint.plugins.firmwareupdater - INFO - Running u'usr/bin/avrdude -v -q -p m2560 -c wiring -P /dev/ttyACM0 -D -b 115200 -U flash:w:/tmp/tmpJkcTB8:i' in usr/bin
2018-09-02 03:30:51,278 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.11
2018-09-02 03:30:51,475 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.1.11
2018-09-02 03:31:02,358 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.11
2018-09-02 03:31:02,589 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.1.11
2018-09-02 03:33:01,296 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.11
2018-09-02 03:33:01,445 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.1.11
2018-09-02 03:35:06,480 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.11
2018-09-02 03:35:06,581 - octoprint.server.util.sockjs - INFO - New connection from client: ::ffff:192.168.1.11
2018-09-02 03:38:41,755 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.1.11
So in my novice experience here... It looks like it keeps trying to connect, timing out, and repeating the process? My normal Octoprint IP address is 192.168.1.5 so I don't quite understand why it is using .11 for the firmware or if that is an issue or not.
Any ideas how to fix this? Thanks for any help.
Re: OctoPrint - Firmware update stuck?
I have the same behaviour!
Printer i3MK3 Firmware version 3.4.0
Octopi 0.14.0 on RPI Zero W
Octoprint 1.3.9
avrdude is installed
frech apt-get update, apt-get upgrade
Printing with this configuration is no problem
verified configuration of plug in firmware updater several time, it's as described in many documents on the web
the octoprint log shows:
2018-10-26 21:25:59,595 - octoprint.plugins.firmwareupdater - INFO - Firmware update started
2018-10-26 21:25:59,612 - octoprint.plugins.firmwareupdater - INFO - Disconnecting from printer
2018-10-26 21:25:59,697 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Offline"
2018-10-26 21:25:59,777 - octoprint.plugins.firmwareupdater - INFO - Running u'usr/bin/avrdude -v -q -p m2560 -c wiring -P /dev/ttyAMA0 -D -U flash:w:/tmp/tmpWixeox:i' in usr/bin
2018-10-26 21:26:02,676 - octoprint.server.preemptive_cache - INFO - ... done in 64.17s
but nothing happens. There is also no message on the printer display.
Any idea, what could be wrong.
Thank's Wolfgang
Re: OctoPrint - Firmware update stuck?
I have the same problem I guess. Mine hangs when trying to update firmware.
It’s one of the main reasons I got all the hardware and installed OctoPrint, to be able to update firmware...so disappointing : /
It seems like it used to work in the past based on forum posts, but I guess not anymore.
Re: OctoPrint - Firmware update stuck?
Have you tried disconnecting in OctoPrint first?
I was having a similar issue, found this thread - then attempted to do it manually and that seems to have worked
randall@imac: scp prusa3d_fw_MK3_3_4_1.hex [email protected]:
...
pi@octopi:~ $ avrdude -v -q -p m2560 -c wiring -P /dev/ttyACM0 -D -b 115200 -U flash:w:prusa3d_fw_MK3_3_4_1.hex
avrdude: Version 6.3-20171130
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch
System wide configuration file is "/etc/avrdude.conf"
User configuration file is "/home/pi/.avrduderc"
User configuration file does not exist or is not a regular file, skipping
Using Port : /dev/ttyACM0
Using Programmer : wiring
Overriding Baud Rate : 115200
AVR Part : ATmega2560
Chip Erase delay : 9000 us
PAGEL : PD7
BS2 : PA0
RESET disposition : dedicated
RETRY pulse : SCK
serial program mode : yes
parallel program mode : yes
Timeout : 200
StabDelay : 100
CmdexeDelay : 25
SyncLoops : 32
ByteDelay : 0
PollIndex : 3
PollValue : 0x53
Memory Detail :
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
eeprom 65 10 8 0 no 4096 8 0 9000 9000 0x00 0x00
flash 65 10 256 0 yes 262144 256 1024 4500 4500 0x00 0x00
lfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
hfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
efuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
lock 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
calibration 0 0 0 0 no 1 0 0 0 0 0x00 0x00
signature 0 0 0 0 no 3 0 0 0 0 0x00 0x00
Programmer Type : Wiring
Description : Wiring
Programmer Model: AVRISP
Hardware Version: 15
Firmware Version Master : 2.10
Vtarget : 0.0 V
SCK period : 0.1 us
avrdude: AVR device initialized and ready to accept instructions
avrdude: Device signature = 0x1e9801 (probably m2560)
avrdude: safemode: lfuse reads as FF
avrdude: safemode: hfuse reads as D0
avrdude: safemode: efuse reads as FD
avrdude: reading input file "prusa3d_fw_MK3_3_4_1.hex"
avrdude: input file prusa3d_fw_MK3_3_4_1.hex auto detected as Intel Hex
avrdude: writing flash (253186 bytes):
avrdude: 253186 bytes of flash written
avrdude: verifying flash memory against prusa3d_fw_MK3_3_4_1.hex:
avrdude: load data flash data from input file prusa3d_fw_MK3_3_4_1.hex:
avrdude: input file prusa3d_fw_MK3_3_4_1.hex auto detected as Intel Hex
avrdude: input file prusa3d_fw_MK3_3_4_1.hex contains 253186 bytes
avrdude: reading on-chip flash data:
avrdude: verifying ...
avrdude: 253186 bytes of flash verified
avrdude: safemode: lfuse reads as FF
avrdude: safemode: hfuse reads as D0
avrdude: safemode: efuse reads as FD
avrdude: safemode: Fuses OK (E:FD, H:D0, L:FF)
avrdude done. Thank you.
will have to wait for the next firmware to see if i can do it natively via the UI.