Originally Posted by
Pilot
Have you tried switching the ChromeOS channel to beta?
In the Linux terminal, what is the output of lsusb before and after pressing the Program button?
Does it make a difference if you run the IDE with sudo?
The difference in lsusb seems to be that Teensy invokes the chrome usbhid driver but Uno invokes the chrome cdc-acm driver.
I have not switched to Beta channel. Its my kid's chromebook he uses for homework. I'd like to keep it stable. But if there is a reason beyond a shot in the dark, I'll give it a try.
Linux Beta terminal before Teensy plugged in, after plugged in running blink, and after program button remain unchanged.
Currently, with Version 85.0.4183.133 (Official Build) (32-bit) it looks the same with Uno plugged in also, where previously it showed up.
Code:
user@penguin:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
chrome://system/ lsusb section
before plugging in Teensy
Code:
Bus 002 Device 002: ID 0bda:0416 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:5416 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 04ca:707c Lite-On Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-mtk/1p, 5000M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-mtk/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 1: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/2p, 480M
After plugging in Teensy 3.5 running blink
Code:
Bus 002 Device 002: ID 0bda:0416 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 16c0:0486 Van Ooijen Technische Informatica Teensyduino RawHID
Bus 001 Device 003: ID 0bda:5416 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 04ca:707c Lite-On Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-mtk/1p, 5000M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-mtk/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 1: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/2p, 480M
|__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M
After pressing program button on Teensy 3.5
Code:
Bus 002 Device 002: ID 0bda:0416 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 16c0:0478 Van Ooijen Technische Informatica Teensy Halfkay Bootloader
Bus 001 Device 003: ID 0bda:5416 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 04ca:707c Lite-On Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-mtk/1p, 5000M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-mtk/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 1: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/2p, 480M
|__ Port 1: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M
For comparison, this is Uno
Code:
Bus 002 Device 002: ID 0bda:0416 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 2341:0043 Arduino SA Uno R3 (CDC ACM)
Bus 001 Device 003: ID 0bda:5416 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 04ca:707c Lite-On Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-mtk/1p, 5000M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-mtk/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 1: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/2p, 480M
|__ Port 1: Dev 6, If 0, Class=Communications, Driver=cdc_acm, 12M
|__ Port 1: Dev 6, If 1, Class=CDC Data, Driver=cdc_acm, 12M
Launching Arduino with sudo from command line fails. Graphically launching from Chrome launcher works fine.
Code:
user@penguin:~/arduino/arduino-1.8.13$ sudo ./arduino ~/Arduino/blink.ino
No protocol specified
Picked up JAVA_TOOL_OPTIONS:
Set log4j store directory /root/.arduino15
No protocol specified
java.awt.AWTError: Can't connect to X11 window server using ':0' as the value of the DISPLAY variable.
at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
at sun.awt.X11GraphicsEnvironment.access$200(X11GraphicsEnvironment.java:65)
at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:115)
at java.security.AccessController.doPrivileged(Native Method)
at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:74)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at java.awt.GraphicsEnvironment.createGE(GraphicsEnvironment.java:103)
at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:82)
at sun.awt.X11.XToolkit.<clinit>(XToolkit.java:126)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at java.awt.Toolkit$2.run(Toolkit.java:860)
at java.awt.Toolkit$2.run(Toolkit.java:855)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:854)
at java.awt.SystemColor.updateSystemColors(SystemColor.java:473)
at java.awt.SystemColor.<clinit>(SystemColor.java:465)
at processing.app.Theme.init(Theme.java:343)
at processing.app.Base.<init>(Base.java:250)
at processing.app.Base.main(Base.java:150)
Reply With Quote