
- #Cambridge silicon radio bluetooth driver linux how to#
- #Cambridge silicon radio bluetooth driver linux windows#
Result: Connection refused - PSM not supported (0x0002) Status: No further information available (0x0000) L2CAP: Connection Response (0x03) ident 3 len 8 HCI Event: Number of Completed Packets (0x13) plen 5 #33 22.549461 L2CAP: Information Response (0x0b) ident 2 len 12 HCI Event: Number of Completed Packets (0x13) plen 5 #30 22.543231 Type: Extended features supported (0x0002) L2CAP: Information Response (0x0b) ident 1 len 8 HCI Event: Number of Completed Packets (0x13) plen 5 #27 22.536970 Set Connection Encryption (0x01|0x0013) ncmd 1 Read Remote Extended Features (0x01|0x001c) ncmd 1 > HCI Event: Read Remote Supported Featu. Read Remote Supported Features (0x01|0x001b) ncmd 1

HCI Event: Command Status (0x0f) plen 4 #2 6.047900 Linux board log created with btmon: complete log wireshark version, syslog: bluetoothd syslog Windows10 machine Bluetooth: Manufacturer: Cambridge Silicon Radio Ltd.
#Cambridge silicon radio bluetooth driver linux windows#
Question 2: Why is windows refusing the connection?
#Cambridge silicon radio bluetooth driver linux how to#
(this is my understanding from Linux logs, and I do not know how to get any logs form windows side) Issue: It works well until Linux board is rebooted, then when Linux board is trying to connect to Windows machine, windows is always refusing to connect to bnep service as if it does not supported it.

Setup: embedded Linux board connected via bluetooth to Windows10 machineĬonnection: The Linux board is connecting to Windows10 machine using bluetooth bnep service, it works well. Question: How to debug Windows10 Bluetooth stack? what tools to use?
