You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 2, 2025. It is now read-only.
We are using BlueHeron in combination with nerves. We use an RPI CM3 with USB Bluetooth dongle. We are experiencing some sporadic behaviour when bluetooth will stop working with following log statements:
2022-12-09 10:02:11.234 [warn] [module=Nerves.Runtime.Log.KmsgTailer pid=<0.1990.0> ] usb 1-1.4: Process 171 (hci_transport) called USBDEVFS_CLEAR_HALT for active endpoint 0x81
2022-12-09 10:02:11.234 [warn] [module=Nerves.Runtime.Log.KmsgTailer pid=<0.1990.0> ] usb 1-1.4: Process 171 (hci_transport) called USBDEVFS_CLEAR_HALT for active endpoint 0x81
2022-12-09 10:02:11.239 [warn] [module=BlueHeronTransportUSB function=handle_info/2 pid=<0.2297.0> ] BlueHeron(USB): Transfer stalled, trying again
...
a lot more of the same messages
...
2022-12-09 10:02:11.276 [warn] [module=BlueHeronTransportUSB function=handle_info/2 pid=<0.2297.0> ] BlueHeron(USB): Transfer stalled, trying again
2022-12-09 10:02:11.276 [warn] [module=Nerves.Runtime.Log.KmsgTailer pid=<0.1990.0> ] usb 1-1.4: Process 171 (hci_transport) called USBDEVFS_CLEAR_HALT for active endpoint 0x81
2022-12-09 10:02:11.573 [warn] [module=BlueHeronTransportUSB function=handle_info/2 pid=<0.2497.0> ] BlueHeron(USB): No acceptable Bluetooth modules found
2022-12-09 10:02:11.573 [error] [module=BlueHeronTransportUSB function=handle_info/2 pid=<0.2497.0> ] BlueHeron(USB): btusb_open failed
It seems that the only way to solve this at the moment is by temporary disconnecting the power on the RPI CM3.
Maybe someone has suggestions what could be the issue and how to prevent his from happening or restart some underlying linux systems?
Note: We are using a modified version of this USB transport, which allows replugging of the USB dongle. The default implementation will crash and not setup the transport after replugging the dongle. We applied these changes because of prior issues which caused the software not being able to start after boot.
Let me know when more information is needed about our nerves setup.
Thanks for the contributors for enabling Bluetooth in an easy way on elixir/nerves.
Kind regards,
Jochen
The text was updated successfully, but these errors were encountered:
Hello,
We are using BlueHeron in combination with nerves. We use an RPI CM3 with USB Bluetooth dongle. We are experiencing some sporadic behaviour when bluetooth will stop working with following log statements:
It seems that the only way to solve this at the moment is by temporary disconnecting the power on the RPI CM3.
Maybe someone has suggestions what could be the issue and how to prevent his from happening or restart some underlying linux systems?
Note: We are using a modified version of this USB transport, which allows replugging of the USB dongle. The default implementation will crash and not setup the transport after replugging the dongle. We applied these changes because of prior issues which caused the software not being able to start after boot.
Let me know when more information is needed about our nerves setup.
Thanks for the contributors for enabling Bluetooth in an easy way on elixir/nerves.
Kind regards,
Jochen
The text was updated successfully, but these errors were encountered: