Description
So, it appears there is an issue in Debian Buster and Ubuntu 18.04.2 already, and more Linux distros will follow suit due to a change in behaviour in the ModemManager package exposing a bug in the firmware used on ATMEGA32U4 USB bootloaders, so boards like the Arduino Micro and Sparkfun Pro Micro are affected, just to name two... would adding something to the FAQ be more appropriate than to each boards page?
I found it mentioned here after banging my head against errors for a good half hour, and trying to craft udev rules to stop it, to no avail: arduino/Arduino/issues/7690 . If this PR is committed, the underlying issue will be resolved, but that won't fix all the boards already out in the wild. arduino/ArduinoCore-avr/pull/92 And this is the issue to follow to see if a workaround is done on ModemManagers end...
e.g. Something like the below?
error: programmer did not respond to command: set addr
- Newer versions of ModemManager are known to cause this error when trying to upload to your Arduino Micro or Sparkfun Pro Micro (and potentially more ATMEGA32U4 based boards) if trying to use the built in USB bootloader. The upload is prone to failure, corrupting the upload, and may require you to use an In Circuit Serial Programmer in order to re-write the device bootloader.
A temporary fix is to run sudo systemctl stop ModemManager
from a terminal prompt, which will last until you reboot your computer. The more permanent solution is to run sudo systemctl disable ModemManager
. Unless you use mobile broadband you may not even notice it's disabled.