lincolnwang
New member
Hi,
I have multiple Teensy 4.1 connected to a robotic system running Linux. I do NOT have physical access of the Teensy so I can't push the program button but I can connect to the host through networking. I set udev rule like this to identify them during serial communication with my program so each Teensy doing its own tasks.
I am trying to use `teensy-cli` to push different firmware to each Teensy, but I couldn't find a way to do it. Since Teensy appear as HID device during programming, the udev rule I set is useless. And based on the documentation, it looks like I don't have a deterministic way to control which Teensy is being programmed.
Please let me know what you think
Thanks
Lincoln
I have multiple Teensy 4.1 connected to a robotic system running Linux. I do NOT have physical access of the Teensy so I can't push the program button but I can connect to the host through networking. I set udev rule like this to identify them during serial communication with my program so each Teensy doing its own tasks.
Code:
SUBSYSTEM=="tty", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="0483", KERNELS=="1-1.4", SYMLINK+="teensy_base"
SUBSYSTEM=="tty", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="0483", KERNELS=="1-1.3", SYMLINK+="teensy_arm"
I am trying to use `teensy-cli` to push different firmware to each Teensy, but I couldn't find a way to do it. Since Teensy appear as HID device during programming, the udev rule I set is useless. And based on the documentation, it looks like I don't have a deterministic way to control which Teensy is being programmed.
-s : Use soft reboot if device not online. Perform a soft request to enter programming mode by searching for any Teensy running USB Serial code built by Teensyduino. A request to reboot and enter programming mode is transmitted to the first device found.
Please let me know what you think
Thanks
Lincoln