janwillemp
New member
Hi,
I have a Teensy 3.2 connected via USB to a Raspberry Pi for general purpose data exchange in our application. When a user would accidentally press the reset button on the Teensy while the serial port is connected and exchanging data, we observe that the serial connection is obviously dropped, but a reconnect doesn't work until the Teensy has been power cycled. Judging by the output of lsusb, it seems that the Teensy gets (stuck) in bootloader mode. Can I do something about this? I know it's not a reset button and the purpose of the button is to get into the bootloader, but it seems as if I may have misconfigured the serial port so the bootloader is now expecting that I upload some new firmware, but I don't have any...
Thanks
I have a Teensy 3.2 connected via USB to a Raspberry Pi for general purpose data exchange in our application. When a user would accidentally press the reset button on the Teensy while the serial port is connected and exchanging data, we observe that the serial connection is obviously dropped, but a reconnect doesn't work until the Teensy has been power cycled. Judging by the output of lsusb, it seems that the Teensy gets (stuck) in bootloader mode. Can I do something about this? I know it's not a reset button and the purpose of the button is to get into the bootloader, but it seems as if I may have misconfigured the serial port so the bootloader is now expecting that I upload some new firmware, but I don't have any...
Thanks