- #Bluetooth usb host controller no divice found vitral box code
- #Bluetooth usb host controller no divice found vitral box Pc
usb_descriptor.ascii7_to_utf16le: char B : 42, idx 3 -> 7 usb_descriptor.ascii7_to_utf16le: char 1 : 31, idx 4 -> 9 usb_descriptor.ascii7_to_utf16le: char A : 41, idx 5 -> 11 usb_descriptor.ascii7_to_utf16le: char 2 : 32, idx 6 -> 13 usb_descriptor.ascii7_to_utf16le: char A : 41, idx 7 -> 15 usb_descriptor.ascii7_to_utf16le: char B : 42, idx 8 -> 17 usb_descriptor.ascii7_to_utf16le: char 3 : 33, idx 9 -> 19 usb_descriptor.ascii7_to_utf16le: char F : 46, idx 10 -> 21 Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread. You can add DBG logs by adding the line in prj.conf: I do not have nrf52840_mdk with me but I've checked that with nrf52840_pca10056 and everything works as expected.Ĭould You please check what is the log output to console by the sample? Subject: Re: sample hci_usb fails with zephyr 2.2.0 (worked with zephyr 2.1.0) ( #23866) I wonder if you use an external USB 2.0 hub between your computer and the pca10056 if you will see the same issue? I suspect the hub is whatever is cheapest, possibly Microchip USB2422T/MJ. I can’t go into the office to use the microscope read the part number off the chip, so the part number of the hub will have to remain an unknown for now. The hub chip used on the MDK is of course not called out on the schematic (just the generic name “USB 2.0 Hub”).
#Bluetooth usb host controller no divice found vitral box Pc
The biggest difference I see between the two boards (at least as far as the nrf52840 goes) is the USB from the processor to the host PC goes through a hub on the NRF board, whereas on the pca10056 the connection is direct to the processor. I took a look at the MDK schematic and the pca10056 schematic. *** Booting Zephyr OS build zephyr-v2.2.0 *** Sure, here are the logs from v2.2.0 with debug turned on. The v2.2.0 hci_usb does not work on either Windows or Linux. Note the v2.1.0 hci_usb works correctly on both Windows and linux.
#Bluetooth usb host controller no divice found vitral box code
I have not yet tested my other Bluetooth code using kernel v2.2.0, but the fact that a 'simple' sample doesn't work makes me nervous.Įnvironment (please complete the following information):
To test this, repeat the above steps except checkout v2.1.0. When the same sample is built with Zephyr v2.1.0 it works as hci0 perfectly. The hciconfig command should complete without an error message.
The sample zephyrproject/zephyr/samples/bluetooth/hci_usb/ fails to operate as expected when built with Zephyr v2.2.0.