Failed to flash 1.0.6  

RE: Failed to flash 1.0.6

Check my post just before yours, you need to follow the 2nd part of the guide

https://forum.prusa3d.com/forum/original-prusa-i3-mmu2s-mmu2-hardware-firmware-and-software-help/fixing-your-bricked-mmu2-guide/

RE: Failed to flash 1.0.6

Thanks, I'll try that. I retried to flash it to 1.0.5 (although it is already running 1.0.5) and got the exact same error.

I'll cannot retry tonight but will keep you posted tomorrow.

RE: Failed to flash 1.0.6

folllowing that guide - now i'm bricked.

one thing i found is that the /dev/ttyacm0 device used by the MMU2 is not writable outside of root. I've been having to sudo the PrusaSlicer to get past that.

when doing that, i can do the printer reboot, and then hit the flash. but it blocked on some fuse problem and now its NA.

Connecting to programmer: Found programmer: Id = "CATERIN"; type = S
Software Version = 1.0; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=128 bytes.

Programmer supports the following devices:
Device code: 0x44

avrdude-slic3r: devcode selected: 0x44
avrdude-slic3r: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude-slic3r: Device signature = 0x1e9587 (probably m32u4)
avrdude-slic3r: safemode: hfuse reads as D8
avrdude-slic3r: safemode: efuse reads as CB
avrdude-slic3r: reading input file "/home/rgordon/Downloads/prusa3d_fw_3_8_1_MK3S_1_0_6_MMU2S/prusa3d_fw_MMU2board_1_0_6.hex"
avrdude-slic3r: writing flash (20844 bytes):

Writing | #######avrdude-slic3r: error: programmer did not respond to command: write block
# ***failed;
########################################## | 100% 0.55s

avrdude-slic3r: failed to write flash memory, rc=-1

avrdude-slic3r: safemode: Verify error - unable to read lfuse properly. Programmer may not be reliable.
avrdude-slic3r: safemode: Verify error - unable to read hfuse properly. Programmer may not be reliable.
avrdude-slic3r: safemode: Sorry, reading back fuses was unreliable. I have given up and exited programming mode
avrdude-slic3r: error: programmer did not respond to command: leave prog mode
avrdude-slic3r: error: programmer did not respond to command: exit bootloader

avrdude-slic3r done. Thank you.

RE: Failed to flash 1.0.6

and attempting to get back to 1.0.5 leaves me with this:

vrdude-slic3r: Device signature = 0x0d3f0d
avrdude-slic3r: Expected signature for ATmega32U4 is 1E 95 87
Double check chip, or use -F to override this check.

avrdude-slic3r done. Thank you.

crap.

RE: Failed to flash 1.0.6

I was getting the same output as Louis-s4 using MacOS coming from 1-05-300.  Tried the quick reboot flash and that didn't work at all.  Ended up using Windows 10 laptop and it flashed no problem.  Just seems to be with the MMU2, the MK3s flashes fine from MAC.  

RE: Failed to flash 1.0.6

Indeed, the update of the MK3S went fine. The update of the mmu2s is the problematic one. I’m running a Mac.

RE: Failed to flash 1.0.6

@louis-s4

I would try it from windows if you can, the Mac one does not work properly at all.  

RE: Failed to flash 1.0.6

for me, it failed using a Ubuntu-Based laptop. every time it created the device file when connecting, I could not write to it. Given that this file was owned by user:root and group:dialout, and my user was a member of that group, it should have been allowed.

Anyway, tonight - I tried it using a Mac laptop that I had available - it required an MMU2 reset to get a device file created, and a printer reset to successfully write it. so - now I'm no longer bricked - printer shows its running 1.0.6-372.

RE: Failed to flash 1.0.6

@rgordon0

So a factory reset of the MMU2? I'll try that.

RE: Failed to flash 1.0.6

There seems to be a known issue updating the firmware of the MMU with certain Linux and Mac systems:

https://github.com/prusa3d/MM-control-01/issues/154 and at the bottom of this page https://github.com/prusa3d/MM-control-01

I'm running Debian and had to use their blacklist method to make the update to 1.0.6 work. No doubt a Mac will be different, despite being Unix'y under the hood.

RE: Failed to flash 1.0.6

I had the same problem and bricked mine. I fixed it stooping the daemon temporary while flashing:

sudo service ModemManager stop
... Flash the MMU2S ...
Connect the cable, prepare the software (1.0.6), press the side button and inmediatly after that press the flash button.
...
sudo service ModemManager start

I am running on Ubuntu 16.04
I hope this help.

RE: Failed to flash 1.0.6

I am running Ubuntu 19.10, no ModemManager, but was failing to flash the 1.0.6 firmware using PrusaSlicer.

Errors would be like:

Writing | ##############avrdude-slic3r: error: programmer did not respond to command: set addr
avrdude-slic3r: error: programmer did not respond to command: write block
# ***failed;

I was able to recover and flash from the command line using avrdude.

The mmu will go into boot mode for 5 seconds after the reset on the mmu board is pressed.
During that time first call a chip erase using avrdude from the command line:
avrdude -v -p atmega32u4 -c avr109 -P /dev/ttyACM0 -b 57600 -e

Then repeat the reset and do the actual programming (this is a single line command)
avrdude -v -p atmega32u4 -c avr109 -P /dev/ttyACM0 -b 57600 -U flash:w:/home/tflint/Documents/Prusa/prusa3d_fw_MMU2board_1_0_6.hex:i

Note that my programming command differs from the one sent by PrusaSlicer in that it does NOT contain the -D flag, which disables autoerase.

Here is from the manpage for avrdude:

-D
Disable auto erase for flash. When the -U option with flash memory is specified, avrdude will perform a chip erase before starting any of the programming operations, since it generally is a mistake to program the flash without performing an erase first. This option disables that. Auto erase is not used for ATxmega devices as these devices can use page erase before writing each page so no explicit chip erase is required. Note however that any page not affected by the current operation will retain its previous contents.

-e
Causes a chip erase to be executed. This will reset the contents of the flash ROM and EEPROM to the value ‘0xff’, and clear all lock bits. Except for ATxmega devices which can use page erase, it is basically a prerequisite command before the flash ROM can be reprogrammed again. The only exception would be if the new contents would exclusively cause bits to be programmed from the value ‘1’ to ‘0’. Note that in order to reprogram EERPOM cells, no explicit prior chip erase is required since the MCU provides an auto-erase cycle in that case before programming the cell.

RE: Failed to flash 1.0.6

I have the same issue. Flashing failed: The Original Prusa MMU 2.0 Control device could not have been found

I have two Prusas. I added the MMU to this one when it came out and it was so frustrating to use, I parked it and stuck with the  more reliable MK2.

I took the Mk3 w MMU out of the closet today to give it another try. The first thing I did was upgrade the firmware for the printer to: 3.8.1 but when I tried to upgrade the MMU it said it could not be found. I am running Windows 10 1909.  I feel the problem is the printer and not my system used to upgrade it.

In Support in the LED panel it says the MMU2 is connected and the FW is version 1.0.2-132

RE: Failed to flash 1.0.6

More information..

Error:
Flashing Original Prusa MMU 2.0 Control, looking for VID/PID 0x2c99/3 or 0x2c99/4 ...
The Original Prusa MMU 2.0 Control device was not found.
The Original Prusa MMU 2.0 Control device could not have been found

I've tried:
Resetting the Power to the i3
Pressing the MMU Reset button on the MMU near the MMU USB port
Followed the steps in: prusa3d_manual_mmu2s_eng_1_00.pdf
to rest the board.

MY i3 is on firmware: 3.8.1-2869
MMU is on: 1.0.2-132I bought this printer a while ago and have not used it since the MMU upgrade as it is so user unfriendly. The manuals as well as the slicer could be friendlier as well.
I see many other people on the boards with the same error but I don't see anyone getting help in the process or the procedures.

RE: Failed to flash 1.0.6

I used the "Chat" from the Prusa sales page and got around my firmware issue by changing out my micro USB cable. I have bever had an issue with the first cable and I use it for everything but the Chat tech to try another. Of course I have many so I changed out the Amazon one I was failing with, with a Samsung micro USB cable. It worked flawlessly. MMU firmware upgraded from 1.0.2-132I  to 1.06.

Try it!

Greg