RussNelson
Member
I'm running Ubuntu 12.04 (important, because it works on 10.04), and I can't program a Teensy -- neither 2.0 nor 3.0. I'm running Teensyduino 1.15 against Arduino 1.05.
The teensy is programmed with sensor code that writes output to Serial(). When I plug it in, it creates /dev/ttyACM0, and I can read the output with 'cat </dev/ttyACM0'.
When I compile a new version of the code, it emits the usual "Please press the RESET BUTTON on your Teensy to upload your sketch. Auto-reboot only works if the Teensy is running a previous sketch." even though it's already running a previous sketch. That would be okay if pressing the PROGRAM BUTTON worked. I have the Verbose output window open, and it prints nothing when I press the program button. It also doesn't create /dev/ttyACM0, presumably because it's stuck in raw hid mode for programming.
There's no "device came online" message in the Teensy loader window. I ran strace against the 'teensy' executable, and while it can see the USB device when it gets created by the kernel, it can't access it.
open("/dev/bus/usb/002/039", O_RDWR|O_LARGEFILE) = -1 EACCES (Permission denied)
However, I see the exact same thing on 10.04 where it *does* work. So this may be a red herring.
Help?
The teensy is programmed with sensor code that writes output to Serial(). When I plug it in, it creates /dev/ttyACM0, and I can read the output with 'cat </dev/ttyACM0'.
When I compile a new version of the code, it emits the usual "Please press the RESET BUTTON on your Teensy to upload your sketch. Auto-reboot only works if the Teensy is running a previous sketch." even though it's already running a previous sketch. That would be okay if pressing the PROGRAM BUTTON worked. I have the Verbose output window open, and it prints nothing when I press the program button. It also doesn't create /dev/ttyACM0, presumably because it's stuck in raw hid mode for programming.
There's no "device came online" message in the Teensy loader window. I ran strace against the 'teensy' executable, and while it can see the USB device when it gets created by the kernel, it can't access it.
open("/dev/bus/usb/002/039", O_RDWR|O_LARGEFILE) = -1 EACCES (Permission denied)
However, I see the exact same thing on 10.04 where it *does* work. So this may be a red herring.
Help?