Not sure, flow control is unlikely to be an issue, but it should be off. Frustrating as I know the one character thing was an issue on Windows and Chromebook initially and it seemed to have been fixed by a big USB rewrite in 1v80. I wonder if WireShark could tell you if the characters are actually being sent and received from USB (eg, whether it's Espruino's problem or the OS's).
Interesting about the crash in the Web IDE - thanks for posting that. In normal Linux, if there are no devices then an empty array is returned from chrome.serial.getDevices (and the chrome docs don't mention anything different), so looks like Chrome's serial port detection might be broken somehow?
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Not sure, flow control is unlikely to be an issue, but it should be off. Frustrating as I know the one character thing was an issue on Windows and Chromebook initially and it seemed to have been fixed by a big USB rewrite in 1v80. I wonder if WireShark could tell you if the characters are actually being sent and received from USB (eg, whether it's Espruino's problem or the OS's).
Interesting about the crash in the Web IDE - thanks for posting that. In normal Linux, if there are no devices then an empty array is returned from
chrome.serial.getDevices
(and the chrome docs don't mention anything different), so looks like Chrome's serial port detection might be broken somehow?