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
The target arduino is a ProMicro (Leonardo). I haven't used the plugin for many months. Recently I installed the very latest version. With this release it seems that the serial monitor will not display text from the target board unless I press the "reset" button on the serial monitor. Once pressed the serial monitor output works as expected.
Also, pressing the serial monitor "reset" button a second time does not seem to actually cause the target board to reset. It just continues to operate normally.
The text was updated successfully, but these errors were encountered:
Yeah, ProMicro/Leonardo is a bit different, however this is a new behavior that wasn't a problem in the older version of the plugin. In fact, I don't recall a serial monitor "reset" button (or if there was one I never had to use it -- the serial monitor just worked).
BTW: What is the reset button doing? As I mentioned, it doesn't seem to actually reset the target board.
The reset button has always been there (it used to be the same code as for the upload -now there are multiple upload protocols and not all need a reset-).
The code pulls up a port; keeps it high for some time and then drops it back to low (or visa versa)
There is some hardware needed on the board for this to trigger a reset and Arduino has done changes in this area in the past.
The target arduino is a ProMicro (Leonardo). I haven't used the plugin for many months. Recently I installed the very latest version. With this release it seems that the serial monitor will not display text from the target board unless I press the "reset" button on the serial monitor. Once pressed the serial monitor output works as expected.
Also, pressing the serial monitor "reset" button a second time does not seem to actually cause the target board to reset. It just continues to operate normally.
The text was updated successfully, but these errors were encountered: