My entire use case for Particle products is simply internet-LTE-uploading minutely binary UART packets sent by a Teensy 3.5 microcontroller.
I have a couple remote installations with Boron 1.3.1-rc1 which are doing this great, but the entire platform is dysfunctional for me on 2.0.1, and this issue I am pretty sure was also happening on 1.5.something before I upgraded.
ISSUE: Serial1 RX randomly, repeatedly, eventually dies. It stops giving data even though I have confirmed my minutely UART packets are indeed getting sent to it. When it enters this state, a cloud call retriggering “Serial1.begin(115200)” causes the Boron to red LED SOS hard crash and reset, whereas re-calling “Serial1.begin(115200)” before the RX-dropout condition happens returns normal, i.e., nothing happens, as Serial1 was already started. But it causes a kernel panic crash in the state where Serial1.available() returns 0 incorrectly.
Details: I am using SerialBufferRK as my packets are 256 bytes and the receive buffer is frustratingly 64 bytes, but I do not believe this is an issue with the SerialBufferRK library because I’ve used that on older Borons where I never had this problem. I believe this is a firmware issue that Particle recently introduced. I can’t downgrade to 1.3.1-rc1 because I am using base64 library now which crashes red SOS panic on this older version.
Does anyone else experience this? What is the cause?