Dead MMU2S?
Heyas,
I just got done assembling my MMU2S, and the first thing I did out of the gate was updated the firmware on my MK3S and MMU2S. The MK3S firmware went just swimmingly, but the MMU2S firmware failed. To make matters worse, after that failed firmware update, I tried installing a second time, and now the system can no longer see the MMU2S unit to flash it?? I then checked in the MK3S LCD, and the MMU2S is at 1.05, so I tried doing a factory reset by hitting the reset button and pressing the middle MMU2S button... nothing. No LED's, nothing.
Next I tried power cycling the MK3S, and I went down to look for the version of the MMU2S, and it now doesn't see the MMU2S at all?? Any idea how to troubleshoot this?
RE: Dead MMU2S?
Have you checked the power connect between MMU2S to PSU? It could be loose. If not, I have no idea.
RE: Dead MMU2S?
I did check the power to the MMU2S, and that is connected. What I didn't notice at first is that there is an LED right below the CPU of the MMU2S board that when the printer is powered on, or the soft reset button is hit, it blinks orange 17 times. I couldn't find any reference to this LED though... ideas?
RE: Dead MMU2S?
Well, it looks like it's not ALL dead, just MOSTLY dead. I am getting some output when I connect it to my Linux box and try flashing from there. When I connect the MMU2 to the linux host I get:
[2581795.662786] usb 1-8: New USB device found, idVendor=2c99, idProduct=0003, bcdDevice= 0.01
[2581795.662788] usb 1-8: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[2581795.662790] usb 1-8: Product: Original Prusa i3 MK3 Multi Material 2.0 upgrade (bootloader)
[2581795.662792] usb 1-8: Manufacturer: Prusa Research (prusa3d.com)
[2581795.662793] usb 1-8: SerialNumber: 57383735313315190E14
When I try to flash the MMU2, it fails at first, indicating that I need to press the soft reset button. I do that, and the flash then shortly fails, with the following log:
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.
Found VID/PID 0x2c99/3 at `/dev/ttyACM0`, flashing ...
avrdude-slic3r -v -p atmega32u4 -c avr109 -P /dev/ttyACM0 -b 57600 -D -U flash:w:0:/home/ken/prusa/firmware/3.8.0/prusa3d_fw_MMU2board_1_0_6.hex:i
avrdude-slic3r: Version 6.3-20160220-prusa3d, compiled on Aug 20 2019 at 21:43:13
Copyright (c) 2000-2005 Brian Dean, http: // www . bdmicro . com/
Copyright (c) 2007-2014 Joerg Wunsch
Using Port : /dev/ttyACM0
Using Programmer : avr109
Overriding Baud Rate : 57600
AVR Part : ATmega32U4
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 20 4 0 no 1024 4 0 9000 9000 0x00 0x00
flash 65 6 128 0 yes 32768 128 256 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 : butterfly
Description : Atmel AppNote AVR109 Boot Loader
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/ken/prusa/firmware/3.8.0/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.86s
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.
So something is unhappy in the MMU2. I also went ahead and checked both 5A fuses, and they are both fine. Just to be paranoid, I ran a selfcheck on the MK3S, and it appears to still be OK. Nothing much happening on the MMU2S
RE: Dead MMU2S?
Please contact live chat support. They will help you to diagnose the issue and provide replacement if needed.
Often linked posts:
Going small with MMU2
Real Multi Material
My prints on Instagram
RE: Dead MMU2S?
Have you tried flashing from different computers? If yes, I second the recommendation to contact support.
RE: Dead MMU2S?
So I contacted support. It turns out that apparently I can flash my MK3S on ubuntu all day and night, but there's something flaky about flashing the MMU2S under Ubuntu. So I went ahead and tried flashing from the windows 10 system -- still got "no MMU unit found", then pressed the soft reset button and it was able to flash successfully.
Sooo from now on I do all my flashing from my Windows system.
RE: Dead MMU2S?
Did you try to blacklist the prusa usb devices as written on https://github.com/prusa3d/MM-control-01?
This helped on my raspian. Will checkout debian/testing later
RE: Dead MMU2S?
Checked with debian/testing (bullseye/sid). Does not work. Using prusa-slicer it seems that the timespan between reset and start of flashing is to short:
Flashing Original Prusa MMU 2.0 Control, looking for VID/PID 0x2c99/3 or 0x2c99/4 ...
Found VID/PID 0x2c99/4 at `/dev/ttyACM0`, rebooting the device ...
Found VID/PID 0x2c99/3 at `/dev/ttyACM0`, flashing ...
avrdude-slic3r -v -p atmega32u4 -c avr109 -P /dev/ttyACM0 -b 57600 -D -U flash:w:0:/home/rowue/Downloads/prusa/fw/prusa3d_fw_MMU2board_1_0_6.hex:iavrdude-slic3r: Version 6.3-20160220-prusa3d, compiled on Sep 16 2019 at 11:26:52
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg WunschUsing Port : /dev/ttyACM0
Using Programmer : avr109
Overriding Baud Rate : 57600
avrdude-slic3r: ser_open(): can't open device "/dev/ttyACM0": Permission denied
avrdude-slic3r: Could not open port: /dev/ttyACM0avrdude-slic3r done. Thank you.
Using avrdude directly leads to "programmer is not responding" error:
rowue@pizzabox:~/Downloads/prusa/fw$ avrdude -v -p atmega32u4 -c avr109 -P /dev/ttyACM0 -b 57600 -D -U flash:w:0:/home/rowue/Downloads/prusa/fw/prusa3d_fw_MMU2board_1_0_6.hex:i
avrdude: Version 6.3-20171130
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg WunschSystem wide configuration file is "/etc/avrdude.conf"
User configuration file is "/home/rowue/.avrduderc"
User configuration file does not exist or is not a regular file, skippingUsing Port : /dev/ttyACM0
Using Programmer : avr109
Overriding Baud Rate : 57600
AVR Part : ATmega32U4
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 20 4 0 no 1024 4 0 9000 9000 0x00 0x00
flash 65 6 128 0 yes 32768 128 256 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 0x00Programmer Type : butterfly
Description : Atmel AppNote AVR109 Boot LoaderConnecting to programmer: .avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
Hope, this gives some information on debugging. Flashing from raspian with debian_version 9.11 works after setting printer to ignore in udev rule.
Best,
rowue
RE: Dead MMU2S?
It seems you never had played on that ubuntu computer with the Arduino IDE to program normal arduinos. May be also you performed an Ubuntu software update that reset the access rights.
I see that at the moment you have not granted the access to the hardware USB ports. It seems more an Ubuntu system matter, than a Prusaslicer or MMU issue. Try to configure the Ubuntu USB access right on that machine.
- Did you success to flash the i3MK3 printer board on that computer ?
Regards