Hi all - I’m working on an application that needs the RPI3 Bluetooth chip enabled on startup. I’ve followed the example from here but am getting exceptionally mixed results.
Typically, the first time I deploy the Resin application to a device, it starts up correctly, but when I deploy updates to the device, the results start to get very mixed.
About 75% of the time, when I run
/usr/bin/hciattach /dev/ttyAMA0 bcm43xx 921600 noflow -, the result is:
12.04.17 13:17:59 (-0500) bcm43xx_init
12.04.17 13:18:29 (-0500) Initialization timed out.
If I restart the newly deployed application, it works about 75% of the time after the restart, and almost always works eventually with enough restarts.
Any idea what the root cause of this might be and how we might attempt to resolve?