Sdpcontrol search timeout in Motorola HS805 headset.

[Maksim Yevmenkin]

[...]

>>># /etc/rc.bluetooth start ubt0
>>>BD_ADDR: 00:0a:3a:63:de:86
>>>Features: 0xff 0xfe 0xd 0x38 0x8 0x8 00 00 <3-Slot> <5-Slot>
>>><Encryption> <Slot offset>
>>><Timing accuracy> <Switch> <Hold mode> <Sniff mode> <RSSI>
>>><Channel quality> <SCO link> <HV2 packets> <HV3 packets>
>>><u-law log> <A-law log> <CVSD> <Power control>
>>><Transparent SCO data> Max. ACL packet size: 377 bytes
>>>Number of ACL packets: 10
>>>Max. SCO packet size: 16 bytes
>>>Number of SCO packets: 0
>>
>>this looks good. number of sco packets == 0 is strange, but its not
>>your problem. i've seen this in other devices. is this a broadcom chip
>>based device?
> 
> Yes.
> 
> ubt0: Broadcom Belkin Bluetooth Device, rev 1.10/0.01, addr 2
> ubt0: Broadcom Belkin Bluetooth Device, rev 1.10/0.01, addr 2
> ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
> ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320

i thought so :)

>>>ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, IOERROR (13). No new xfer will be submitted!
>>
>>aha! this is your problem. usb bulk transfer failed. that explains why
>>sdpcontrol failed. bluetooth usb device use usb control transfers to
>>send hci command and usb interrupt transfers to receive hci
>>event. bulk usb transfers used to transfer the data.
>>
>>so, in your case, usb control/interrupt transfers with your device
>>work just fine. that explains why you can send commands to the device
>>and get responses back. however, as soon as you try to transfer data
>>(which require usb bulk transfer) the device chokes. that is why you
>>never see sdp response from the headset - it probably never saw the
>>sdp request, because bulk transfer failed and the data were never
>>transmitted over the radio.
>>
>>what is the model of your bluetooth usb dongle? are you using usb hub?
>>what is your usb controller type uhci, ohci or ehci?
> 
> sigh, belkin again. 
> 
> It's a belkin bluetooth usb adapter, model F8T008. Another usb device is a usb mouse.
> Both of them directly connection to my laptop, no usb hub.

i guess you could try to plug it into different usb slots. use

# usbdevs -dv

to see where it got connected. if you have usb hub around try to plug it 
  through hub. i have f8t001 in my collection, and, it works for me. 
f8t001 is a broadcom bcm2033 chip based device, so i need to download 
firmware into it to make it work. i will see if i can get f8t008 cheap 
locally.

> dmesg|grep uhci
> uhci0: <Intel 82801DB (ICH4) USB controller USB-A> port 0x1820-0x183f irq 16 at device 29.0 on pci0
> uhci0: [GIANT-LOCKED]
> usb0: <Intel 82801DB (ICH4) USB controller USB-A> on uhci0
> uhci1: <Intel 82801DB (ICH4) USB controller USB-B> port 0x1840-0x185f irq 19 at device 29.1 on pci0
> uhci1: [GIANT-LOCKED]
> usb1: <Intel 82801DB (ICH4) USB controller USB-B> on uhci1
> uhci2: <Intel 82801DB (ICH4) USB controller USB-C> port 0x1860-0x187f irq 18 at device 29.2 on pci0
> uhci2: [GIANT-LOCKED]
> usb2: <Intel 82801DB (ICH4) USB controller USB-C> on uhci2

what does

# usbdevs -dv

say?

> Is that any solution? Or, likely NDIS, to use windows native driver?

at this point, it does look like usb related problem. try different usb 
dongle. i recommend csr chip based devices. you can not use windows 
native driver with freebsd ndis'ulator. it wont work.

thanks,
max