earl_5thgait
New member
I looked for a solution and the forums seemed to state to do the long hold of the programming button to get the teensy to launch its bootloader. This was non-responsive for me. What I read was that if this is the case that the board is effectively bricked. I found the following recovery method, though unadvised, to work on an "unsalvageable" board.
I had the MCU powered, in the on state (normal operating status), and plugged in over USB. I fast pressed the program_n button until I got to a point where LED would do a bright long strobe. At this point I stopped and allowed the MCU a minute or so to do its thing. I had to repeat several times but eventually The device showed up as an HID device on USB. from there I used Arduino to program the basic blinky code which told the Teensy to be a serial device. from here Platform IO was fully able to interface with the part again.
Though this is not an advised method for a working board, if its thought to be no worky worky, what is the harm?
I had the MCU powered, in the on state (normal operating status), and plugged in over USB. I fast pressed the program_n button until I got to a point where LED would do a bright long strobe. At this point I stopped and allowed the MCU a minute or so to do its thing. I had to repeat several times but eventually The device showed up as an HID device on USB. from there I used Arduino to program the basic blinky code which told the Teensy to be a serial device. from here Platform IO was fully able to interface with the part again.
Though this is not an advised method for a working board, if its thought to be no worky worky, what is the harm?