monkeyfork
Member
I've been working on keyboard/pointer sharing from PC to Chromebook using teensy-LC as a serial->USB bridge for a while. The project is mostly finished with keystrokes and mouse movement working very good. I've been developing on a xubuntu 18.04 machine with arduino 1.8.10 + teensyduino 1.48 that has mostly worked ok. I was noting 100% cpu utilization that was associated with the arduino-IDE and saw teensyduino 1.52 mentioned a similiar cpu-maxed-out situation so decided to upgrade (and upgrade arduino to 1.8.12). After upgrade something is fouled up about how teensy is recognized as I can no longer get the extra usb roles of serial/keyboard/mouse/joyst. I've noted that the small configuration text in lower right corner of IDE shows proper extra usb roles for the project until upload then it changes to just some base level config of ttyAMC0 without the xtra roles.
Whatever changed also changed the previous teensyduino install (1.8.10+1.48) as it as the same usb-role stripping behavior now. I _think_ I have the udev rules as indicated in the instructions but there is a bit of confusion on that point and appears to be an logical prime target. udev tweaking is NOT one of my strongpoints and could use very clear instructions regarding troubleshoot in that area.
This is a retirement project to scratch a personal itch. I've just purchased 5 t-LC's to replicate this ChromeBook control for a number of my projects. I mention retirement to indicate I could spend considerable time if properly guided to figure this out if it happens to be something systemic that needs to be worked out for others. I'll let this sit for a while to see if there will be guidance before mucking it up worse.
Whatever changed also changed the previous teensyduino install (1.8.10+1.48) as it as the same usb-role stripping behavior now. I _think_ I have the udev rules as indicated in the instructions but there is a bit of confusion on that point and appears to be an logical prime target. udev tweaking is NOT one of my strongpoints and could use very clear instructions regarding troubleshoot in that area.
This is a retirement project to scratch a personal itch. I've just purchased 5 t-LC's to replicate this ChromeBook control for a number of my projects. I mention retirement to indicate I could spend considerable time if properly guided to figure this out if it happens to be something systemic that needs to be worked out for others. I'll let this sit for a while to see if there will be guidance before mucking it up worse.