Other Parts Discussed in Thread: CC2650
A project I'm working on seems to have developed a problem where after a period of time of being connected, usually 1-2h, the device will stop responding and seems to be frozen.
On investigating the problem further it appears that when this happens, simply removing and replacing the CR2016 coin cell battery will allow the device to function again. Looking at the power consumption when after failure occurs shows the current draw jump up to 4mA and remain there until power cycled.
No failures happen if the device is left unconnected and not advertising. I'm currently testing if a device will fail when advertising but not connected.
It appears that a previous revision of the firmware does not suffer the same problem. The only difference is that the earlier version does not require the central to take its connection parameters so will use the device's preferred params, and a clock to measure the battery level runs more frequently (1h vs 8h).
Currently we're using custom hardware, but I have not been able to reproduce the problem on a CC2650 launchpad. I've connected up out own hardware and run it in debug mode but I so far cannot replicate the issue like that either. What is additionally strange is that the devices that fail consistently when connected to android function fine for prolonged periods on iOS.
Does anyone have any idea what the cause of the issue could be? Or even any tips on how to go about debugging this?
Thanks
Craig