Serial reading issue(Corrupted input serial packets) about microbit-web-bridge

[taylow]

Thanks for posting the issue. It'll be good to have all of this in one place.

As for the implementation of a byte-by-byte read, I have looked into DAPLink's commands and have yet to find a single byte read. It appears DAPjs is sending the value 0x83 (READ) during the timer found at startSerialRead(). I was hoping there would be a similar value for reading a single byte.

I understand you have some alternate approaches than DAPjs. It will be interesting to see what you come up with.

[taylow]

Actually, just thinking bout it, has anyone tried changing the serialDelay parameter passed into startSerialRead()? I'm wondering if slowing the timer in which the data is read would help as the data may be being processed before all data is available?

Another possible solution is that we implement the SLIP_* fully so that each command has a start and an end character. This way, we can fill a buffer with the incoming data until a SLIP_END character is found.

This would be as simple as appending the data to a buffer and only emitting the DAPLink.EVENT_SERIAL_DATA event when the buffer contains both the start and end characters.

[yarsanich]

@Taylor-Woodcock I tried lowering serial_delay value, but no-luck.

[yarsanich]

@Taylor-Woodcock your second suggestion is possible, but we need to fork dapJS then.

[yarsanich]

Received to write: ���^���DATA SENT�
WebBridge.bundle.js:5261 Received: ���^���DATA SENT�oricalData/�3�tnw3�gl�celsius���7�tnw3

additional logs