Search results

No I did not update the Teensy. Also I got the new Teensy 4.1 in and it works fine. I have no idea why the last one died. I'm going to just chalk it up to a random fluke.

I've already ordered another Teensy 4.1, so I think I can finally write this one off although I have absolutely no idea what happened to it. My best guess is that I somehow managed to damage the Cortex-M7's USB transceiver, although I find that surprising given my use case. The target machine...

No pattern. The RED LED blinks about once a second with a 50% duty cycle. I also verified that I was able to get continuity on both the D+ and D- lines between the male side of my USB A cable and the two test pads on the bottom side of the Teensy below the MicroUSB port. So the MicroUSB port...

It's not a power draw issue. Even with nothing connected to the Teensy 4.1 my Linux machine refuses to recognize it. It just gives the same message in /var/log/syslog about refusing to enumerate the device. I've also tried connecting the Teensy to my Windows machine using both the same a cable...

Sorry I didn't communicate this clearly enough. It used to work fine on my laptop but now I can't even get the Teensy 4.1 to show up as a USB device on Linux anymore. I'm using the same cable and everything. It won't show up under lsusb and /var/log/syslog prints the message from my original...

The test was preformed with nothing connected to the Teensy. I used the same generic 3ft cable that worked the first time. Wireshark definitely detected some traffic after the Teensy was connected, but nothing that looked like HID traffic.

I recently purchased a Teensy 4.1 and began using it on Linux at first with Arduino and then PlatformIO. I was using the Teensy to read data from a USB device using the USBHost_t36 library then sending data out the other USB port (the builtin MicroUSB) in a different format. This worked fine...