-
Notifications
You must be signed in to change notification settings - Fork 132
Beta 4.4: No such file or directory avrdude error on Ubuntu 20.04 #1301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I see 2 possible reasons:
Is the path (with the .../Sloeber/Sloeber/... ) correct? |
And thanks for testing :-) |
The avrdude binary is located here /home/rmueller/Sloeber/Sloeber/arduinoPlugin/packages/arduino/tools/avrdude/6.3.0-arduino17/bin The following command "/home/rmueller/Sloeber/Sloeber/arduinoPlugin/packages/arduino/tools/avrdude/6.3.0-arduino17/bin/avrdude"
"-C/home/rmueller/Sloeber/Sloeber/arduinoPlugin/packages/arduino/tools/avrdude/6.3.0-arduino17/etc/avrdude.conf"
-patmega4809 -cjtag2updi -P/dev/ttyACM0 -b115200 -e
-D "-Uflash:w:/home/rmueller/Sloeber/sloeber-repository/NanoEveryTest/Release/NanoEveryTest.hex:i"
"-Ufuse2:w:0x01:m" "-Ufuse5:w:0xC9:m" "-Ufuse8:w:0x00:m" works in the command line and I also checked the folder manually, avrdude is installed. If I do it in command line, I still have to run the Sloeber upload before each upload because Sloeber it is also forcing some required reset (see console output in the screenshot above). This is really odd, the command does not seem to depend on paths being set or using relativ paths, so if it works in the command line, it should also work in the IDE.. Here is also the command line error: |
After some thinking I assume this change causes the problem |
I can confirm adding back those lines solved the issue for me. |
great :-) |
This problem occurs when I tested the new beta release of Ubuntu 20.04.
I was able to build an application in Sloeber, but I am not able to flash the board on Ubuntu because there is a "No such file or directory error" when launching avrdude. This was not an issue on Windows 10.
Here is a screenshot:

I ran the command displayed in the Sloeber console in the command line and that worked without issues..
The text was updated successfully, but these errors were encountered: