My setup:
ESP8266 communicating at 57600 baud, connected to boron in the same fashion that it was connected to an electron running almost the exact same code. The electron runs beautifully, however the boron will not. This is likely an issue with the boron's deviceOS (tested on 1.2.1-rc.3), but since the serial issues on deviceOS' GitHub have been marked 'solved', I guess that means this library should be updated to account for any changes?
Relevant code:
SerialBuffer<2048> serBuf(Serial1);
DBG_SERIAL_CONSOLE.print("serBuf available: ");
DBG_SERIAL_CONSOLE.println(serBuf.available());
DBG_SERIAL_CONSOLE.print("Serial1 available: ");
DBG_SERIAL_CONSOLE.println(Serial1.available());
Output:
serBuf available: 0<CR><LF>
Serial1 available: 50<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 50<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 50<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 50<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 50<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 50<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 50<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 50<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 50<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 70<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 77<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 82<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 88<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 94<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 100<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 106<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 111<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
serBuf available: 0<CR><LF>
Serial1 available: 128<CR><LF>
My setup:
ESP8266 communicating at 57600 baud, connected to boron in the same fashion that it was connected to an electron running almost the exact same code. The electron runs beautifully, however the boron will not. This is likely an issue with the boron's deviceOS (tested on 1.2.1-rc.3), but since the serial issues on deviceOS' GitHub have been marked 'solved', I guess that means this library should be updated to account for any changes?
Relevant code:
SerialBuffer<2048> serBuf(Serial1);Output: