Part Number:CC1352R
I'm seeing a very random and rare issue. I don't really have any insight as to when and/or why it happens, but occasionally EasyLink_transmit() blocks.
I managed to capture a stack trace from ROV this time. Its in my receiverRadioTaskFunction task. I should note that I am using the DMM concurrent with the BLE stack, and I have that mostly working, but I am still squashing bugs. It took about 4.5 hours for this error to occur, so I really don't have any idea what could be causing it, or how to repeat it. I dont think I am running out of RAM, since there is plenty of space left on the heap.
I'm doing a seemingly innocuous call to EasyLink_transmit(), which usually returns pretty quickly (I haven't tried switching that call to EasyLink_transmitAsync(), but that is my only other idea at this point). I guess I am asking why EasyLink_transmit() would get stuck and how to prevent that... and if EasyLink_transmitAsync() would even fix it?
And, is this something possibly to do with the DMM? I do not think there was any activity on the BLE side when EasyLink_transmit() got stuck, but I'm not 100% on that. I don't think I've ever seen this happen during periods of activity on the BLE side either, but due to the time frames, I dont always have the debugger connected or handy.