Firmware 3.10.0 not flashing  

RE: Firmware 3.10.0 not flashing

Have you followed these steps? https://help.prusa3d.com/en/article/firmware-updating-mk3s-mk3s-mk3_2227

I don't see a COM port in the text you posted.

RE: Firmware 3.10.0 not flashing

Posted by: @bryan-2

Just tried to upgrade my i3 Mk3S and was greeted with this wall of text... I don't know what to do.

 

avrdude-slic3r -v -p atmega2560 -c wiring -P /dev/cu.usbmodemFA141 -b 115200 -D -U flash:w:0:/Users/eric/Downloads/prusa3d_fw_3_10_0_MK3S/prusa3d_fw_MK3S_3_10_0_4481.hex:i

avrdude-slic3r: Version 6.3-20160220-prusa3d, compiled on Mar 21 2020 at 12:32:49
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch

Using Port : /dev/cu.usbmodemFA141
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-slic3r: AVR device initialized and ready to accept instructions

Reading | avrdude-slic3r: stk500v2_recv(): timeout
avrdude-slic3r: stk500v2_recv(): timeout
avrdude-slic3r: stk500v2_getsync(): timeout communicating with programmer
avrdude-slic3r: stk500v2_command(): failed miserably to execute command 0x1b
avrdude-slic3r: stk500isp_read_byte(): timeout/error communicating with programmer
avr_read(): error reading address 0x0001
read operation not supported for memory "signature"
avrdude-slic3r: error reading signature data for part "ATmega2560", rc=-2
avrdude-slic3r: error reading signature data, rc=-1

avrdude-slic3r done. Thank you.

Flashing works very well on a Windows or Linux machine with the latest version of PrusaSlicer. It is important that the printer is recognized at the COM port and that no other devices, e.g. activated Bluetooth, blocks the flash process.

wbr,

Karl

RE: Firmware 3.10.0 not flashing

@baklin

Thanks. I'll give it a go.

RE: Firmware 3.10.0 not flashing

@karl-herbert

The printer has always flashed correctly in the past using this MacBook. What I haven't done is upgraded prusa slicer... it's still at 2.2.0

I'll let you know how I get on.

RE: Firmware 3.10.0 not flashing

@bryan-2

It might be helpful to uninstall the 2.2.0 with all folders and reinstall the latest version of PrusaSlicer including all drivers.

good luck!

Karl

RE: Firmware 3.10.0 not flashing

Well, that was fun. I upgraded Prusa slicer to 2.3.1 and flashed the printer. It failed. I checked the log and it was empty! I swapped USB ports... SUCCESS! Spoke too soon. Stalled at 12%. It was still stalled at 12% 30 minutes later. I rebooted the printer and the LCD showed, er... see image attached. I changed the cable to my 3rd and final USB port and flashed the printer. It's writing the firmware. Stalls at 19%. Reaches 28% and stalls again. Reaches 100% and starts verifying. Firmware upgraded!

Can't wait for the next upgrade, Joseph!

RE: Firmware 3.10.0 not flashing

@bryan-2

If you have problems with Prusaslicer, flashing should also work with Arduino 1.8.5 (without multilanguage option) - according to this procedure:

http://theprusamk3clone.blogspot.com/2019/02/change-and-compile-original-prusa-mk3.html

For me PS works without problems both with W10, and with Linux Ubuntu 20.04.  I use a high quality and short USB cable (1.5m) on the USB2 port.

wbr,

Karl