New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nRF52840: hci_usb timeout during initialization by bluez #10678
Comments
I don't know why the controller would not respond to Read Local Supported Commands. It's something that's used even as part of a combined build HCI initialization. |
The only special thing I can think of regarding HCI_Read_Local_Supported_Commands is that its return parameters (as part of the Command Complete event) are probably some of the longest of any HCI command. Perhaps that could be an issue here (possibly with the way the HCI transport is implemented). |
I'm getting the same error, both on pca10056 and pca10059. |
The device does not enumerate on Windows. Looks like HCI ACL packet is interpreted incorrectly: |
@pawelzadrozniak I am suspecting a regression in 68cb7b3 |
Looks like Windows 7 does not support this type of device. Ubuntu 18.04, bluez 5.48. |
I suggest to create separate issue about Windows support, that never worked for me also (I haven't tested much), probably we need to add some special tweaks... |
I can confirm this issue. I tried reverting 68cb7b3 and related commits - that works. |
henrikbrixandersen, I'm not familiar with git (yet). How do I do that? |
Timeout issue fixed in #10934 . |
I can confirm that the timeout issue was fixed in #10934. Can this issue be closed? |
Fixed by #10934 Thank you @henrikbrixandersen |
Hey there,
encountered a problem with hci_usb sample on nrF52840,
Hardware:
USB-Devices:
nordic nRF52840 DK & laird DVK-BL654-1.0
USB-Host:
PC / x86 Ubuntu LTS 18.04 / Bluez 4.48 / Kernel 4.15.0-36-generic
Firmware:
zephyr-master @8b20f9d
While initializing the hci-device bluez gets a timeout:
[Thu Oct 18 02:36:18 2018] Bluetooth: hci0: command 0x1002 tx timeout
Here the output of:
btmon: https://pastebin.com/ypNTmTgC
journalct -f | grep bluetoothd* :https://pastebin.com/PT4V6Dpf
dmesg -T: https://pastebin.com/VQQ0tf1x
zephyr uart debug console: https://pastebin.com/v14JUCux
Wondering whether this is a usb or hci stack problem?
Best,
The text was updated successfully, but these errors were encountered: