-
-
Notifications
You must be signed in to change notification settings - Fork 7k
Code uploading on DUE is not working in UBUNTU #3923
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
Why dont you switch to the 16u2 usb port? |
@Fede85 is having the same issue with his ubuntu 14.04, while I'm not with mine. My only guess so far it's that it's hardware related. Can you spare a 14.04 on a different pc and retest? |
Hi ffissore, Executing the same command with the PC where bossac fails, we get: No LSB modules are available. Main difference is that the first one is Ubuntu 14.04.1 LTS while the second one is Ubuntu 14.04.3 LTS 'uname -a' returns: 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux for Ubuntu 14.04.1 LTS, and 3.13.0-65-generic #105-Ubuntu SMP Mon Sep 21 18:50:58 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux for Ubuntu 14.04.3 LTS I'm attaching also a couple of log files detailing the modules loaded in both cases. ------- For the PC where bossac works --------------------------------------------------------------------------- Script terminado (mié 07 oct 2015 12:25:59 WEST ------- For the PC where bossac DOES NOT work --------------------------------------------------------------- |
Hi, We have tested this booting the system through the "Advanced options for Ubuntu" in the grub booting screen and selecting the adequate kernel image. This is also an EMERGENCY shortcut to deal with this problem. This issue is clearly related to reading data from a USB device. While dealing with these tests, we found also an unexpected problem with a USB XBee adapter where outgoing messages were sent without problem but incoming messages were not received (in esence the same problem with bossac). This problem was solved also if a 3.13.0-63-generic (or previous) kernel was used. Regards |
What usb port are you using? The one connected to the DUE or the one connected to the 16u2. |
Hi, |
You mean on the DUE USB port and the 16u2 USB Port? (you know your arduino has 2 usb plugs). |
Yes, we found this problem with the two DUE's ports (the programming port and the native port). However, we haven't tested other boards yet. |
Other boards would be nice to test. I only have AVR boards, but I programmed/modified a lot of the bootloaders. So I could play with this under my linux (where everything runs fine though). |
The changelog between 3.13.0-63 and 3.13.0-64 (https://launchpad.net/ubuntu/+source/linux/3.13.0-64.104) shows that a bunch of modifications has been made for both the tty and the usb subsystems.
However we can only report this issue to Ubuntu maintainers as a generic bug until we are able to bisect the offending commit |
We are not alone 😄 https://bugreports.qt.io/browse/QTBUG-48499 |
Reported here |
I'm running a Debian machine with kernel 4.0.2, which can upload to the Due (both ports) just fine (just tested with Arduino IDE 1.6.5). Perhaps this is a kernel bug that has since been fixed and we shouldn't spend to much time on this? Perhaps the original reporter can try a newer kernel version (from a newer Ubuntu version?) and see if that helps? |
@matthijskooijman , I'm running kernel 4.2 on Arch so I should be even less concerned 😄 |
I am running kernel: I have no due, but all other avr devices work. Using Elementary OS based on Ubuntu 14 LTS |
Hi, |
👍 👍
|
Hi,
We're facing exactly the problem declared in this link.
http://askubuntu.com/questions/681555/ubuntu-14-04-arduino-due-upload-firmware-issue
This problem is serious as it renders the DUE board useless under UBUNTU.
The text was updated successfully, but these errors were encountered: