• Windows 11
• Reproduced with Teensy Micromod and Teensy 4.0

The error is consistent with the PORT_SUSPEND message I see on Wireshark USB capture, maybe indicating that the board or the attached USB hub may have trouble waking up from a suspend state. I do get some back and forth, though, so I'm not sure what exactly is going on.

I did capture the entire communication on Saleae with USB 1.1 Full-Speed, but my knowledge of USB isn't deep enough to decypher what's going on. I attached the Saleae log, maybe someone else understands what's going on?

Thanks for this useful utility.

Unfortunately when I follow the instructions, I'm not seeing intended / expected behavior. I see Van Ooijen Technische Informatica Teensy Rebootor in lsusb, and I get this far:

$ cargo run --release --example teensy4_selfrebootor
    Finished release [optimized] target(s) in 0.02s
     Running `python3 examples/run.py target/thumbv7em-none-eabihf/release/examples/teensy4_selfrebootor`
Flashing target/thumbv7em-none-eabihf/release/examples/teensy4_selfrebootor ...
Teensy Loader, Command Line, Version 2.2
Read "/tmp/tmpk8p16hp7/firmware.hex": 36952 bytes, 1.8% usage
Hard Reboot performed
Waiting for Teensy device...
 (hint: press the reset button)

But then I must press the button to get the rest:

Found HalfKay Bootloader
Read "/tmp/tmpk8p16hp7/firmware.hex": 36952 bytes, 1.8% usage
Programming.....................................
Booting
Teensy successfully flashed.

Without this firmware I don't even get the Hard Reboot performed line, so something is going right, but I'm not sure what state it's getting into.

This is a Teensy 4.1 if it matters.