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
Just got a HiFive1 board (https://www.crowdsupply.com/sifive/hifive1) which generates a line break whenever the reset button is pushed (power supply is cycled so the input to the FTDI serial-USB is low for a while). In other terminal programs like screen or minicom in Linux the line break is ignored. But in beagle term there is no further communication after the line break. The documentation suggests that after an error chrome.serial will put the connection in a paused state.
To check this is what is happening I added an error listener to registerConnectBtnEvent_.
Have you tried intercepting the input? You would need an if statement to check for a line break. You would then only continue if the if statement fails then that should fix your issue because you'd be ignoring the line break.
Just got a HiFive1 board (https://www.crowdsupply.com/sifive/hifive1) which generates a line break whenever the reset button is pushed (power supply is cycled so the input to the FTDI serial-USB is low for a while). In other terminal programs like screen or minicom in Linux the line break is ignored. But in beagle term there is no further communication after the line break. The documentation suggests that after an error chrome.serial will put the connection in a paused state.
To check this is what is happening I added an error listener to registerConnectBtnEvent_.
This seems to work, printing [break] when the line break happens (I also set the parity incorrectly and it seems to work for parity errors too).
Not sure if this is the best fix (especially where there are a bunch of errors) but it works for my case.
The text was updated successfully, but these errors were encountered: