Ok .. something definitely to do with the driver because this pops up in the logs:
[Tue Aug 22 14:49:26 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 14:49:28 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 14:49:37 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 14:49:39 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 14:49:45 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 14:49:47 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 14:50:00 2017] Bluetooth: hci0 command 0x0c1a tx timeout [Tue Aug 22 15:01:30 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 15:01:32 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 15:01:34 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 15:01:36 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 15:01:51 2017] Bluetooth: hci0 command 0x0c1a tx timeout [Tue Aug 22 15:12:17 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 15:12:19 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 15:12:22 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 15:12:24 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 15:21:07 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 15:21:09 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 15:22:25 2017] usbcore: deregistering interface driver btusb [Tue Aug 22 15:22:25 2017] Bluetooth: hci0 urb ffff9b81a786e6c0 failed to resubmit (2) [Tue Aug 22 15:22:49 2017] usbcore: registered new interface driver btusb [Tue Aug 22 15:22:49 2017] Bluetooth: hci0: Firmware revision 0.1 build 82 week 37 2016 [Tue Aug 22 15:25:24 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 15:25:26 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 15:25:43 2017] Bluetooth: hci0 command 0x0c1a tx timeout [Tue Aug 22 15:27:35 2017] Bluetooth: hci0 command 0x0c1a tx timeout [Tue Aug 22 15:29:45 2017] Bluetooth: hci0 command 0x200c tx timeout [Tue Aug 22 15:29:47 2017] Bluetooth: hci0 command 0x200c tx timeout
I'll chat to the bluetooth subsystem guys see if I can get a definitive answer to what is going on.
@MyBlueBoo started
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Ok .. something definitely to do with the driver because this pops up in the logs:
I'll chat to the bluetooth subsystem guys see if I can get a definitive answer to what is going on.