You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a long hiatus I am back to using Tycommander 0.9.8 on Ubuntu 22.04. The reset button always draws the error "failed to reboot board 'XXXXXXXX-Teensy', but sometimes it does actually reboot. I'm loading manufacturing test code which has a 3 second timeout waiting for the Serial port to open, then prints some information about the code - so that's what I expect to see after clicking on the reset button.
Trying to understand this more, the serial port connection indicators are not reliable. When showing the port open it sometimes isn't. Also if I click reset repeatedly it goes through a repeatable cycle of connecting to the 'bootloader', then 'running' (with serial port indication not always correct). Eventually it will display the expected serial output. If I cause a hardware reset (i can do this on our custom board) that works as expected. It's just the reset over USB that is flaky.
The text was updated successfully, but these errors were encountered:
After a long hiatus I am back to using Tycommander 0.9.8 on Ubuntu 22.04. The reset button always draws the error "failed to reboot board 'XXXXXXXX-Teensy', but sometimes it does actually reboot. I'm loading manufacturing test code which has a 3 second timeout waiting for the Serial port to open, then prints some information about the code - so that's what I expect to see after clicking on the reset button.
Trying to understand this more, the serial port connection indicators are not reliable. When showing the port open it sometimes isn't. Also if I click reset repeatedly it goes through a repeatable cycle of connecting to the 'bootloader', then 'running' (with serial port indication not always correct). Eventually it will display the expected serial output. If I cause a hardware reset (i can do this on our custom board) that works as expected. It's just the reset over USB that is flaky.
The text was updated successfully, but these errors were encountered: