From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 28 22:40:53 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D47AB16A41F for ; Mon, 28 Nov 2005 22:40:53 +0000 (GMT) (envelope-from C.H.Zhu@herts.ac.uk) Received: from mta09-winn.ispmail.ntl.com (mta09-winn.ispmail.ntl.com [81.103.221.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id B515F43D67 for ; Mon, 28 Nov 2005 22:40:51 +0000 (GMT) (envelope-from C.H.Zhu@herts.ac.uk) Received: from aamta10-winn.ispmail.ntl.com ([81.103.221.35]) by mta09-winn.ispmail.ntl.com with ESMTP id <20051128224050.EWUW8609.mta09-winn.ispmail.ntl.com@aamta10-winn.ispmail.ntl.com>; Mon, 28 Nov 2005 22:40:50 +0000 Received: from [82.23.211.112] by aamta10-winn.ispmail.ntl.com with ESMTP id <20051128224050.KTCD11396.aamta10-winn.ispmail.ntl.com@[82.23.211.112]>; Mon, 28 Nov 2005 22:40:50 +0000 To: Maksim Yevmenkin References: <863blgzdz0.fsf@fastmail.fm> <438B7FB0.5030704@savvis.net> From: faigozhu Date: 28 Nov 2005 22:41:25 +0000 In-Reply-To: <438B7FB0.5030704@savvis.net> Message-ID: <86psok1jl6.fsf@fastmail.fm> Lines: 112 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Cc: freebsd-bluetooth@freebsd.org Subject: Re: Sdpcontrol search timeout in Motorola HS805 headset. X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Nov 2005 22:40:53 -0000 --=-=-= Maksim Yevmenkin writes: > Hello, Hi. Thanks for you reply. > > > First of all, I would like to thank BSD bluetooth team for their > > great work enable bluetooth support in FreeBSD. > > I have a Motorola HS805 headset and got the following message. > > #sdpcontrol -a 00:0b:2e:32:65:12 search HSET > > Could not execute command "search". Operation timed out > > did you try to repeat this command several times? does it always fail > with timeout? yes. > > > It seems no response from the headset after sending Link_Key_Reply? > > sigh... people, please, PLEASE, stop posting text hci dump. they are > not very useful. they give me some idea, but what i really need is > _binary_ hci dump. Sorry for that. The attached file is a binary file of "hcidump -w hcidump.log". --=-=-= Content-Type: application/octet-stream Content-Disposition: attachment; filename=hcidump.log Content-Transfer-Encoding: base64 EQAAAJiBi0OtQQkAAQUEDRJlMi4LABjMAAAAAAEHAAEAmIGLQ1P+CQAEDwQAAQUECQABAJmBi0Py 8AgABBcGEmUyLgsAGgAAAJmBi0N78QgAAQsEFhJlMi4LACcZINaDEpxA5ufM/wvMH/wNAAEAmYGL Q2gECQAEDgoBCwQAEmUyLgsADgABAJmBi0OYzwkABAMLAAYAEmUyLgsAAQAIAAAAmYGLQ5vPCQAB DQgEBgAHABEAAACZgYtDnc8JAAIGIAwACAABAAIBBAABAEAACQABAJmBi0MH4wkABA4GAQ0IAAYA CAABAJmBi0P/DQoABBMFAQYAAQAGAAEAmYGLQ49zCgAEGwMGAAUJAAEAmYGLQ0LPCwAEFwYSZTIu CwAaAAAAmYGLQ67PCwABCwQWEmUyLgsAJxkg1oMSnEDm58z/C8wf/A0AAQCZgYtDu+YLAAQOCgEL BAASZTIuCwA= --=-=-= > > > ------------hcidump------------------ > > HCIDump - HCI packet analyzer ver 1.5 > > device: any snap_len: 65535 filter: 0xffffffff > > < HCI Command: Create Connection(0x01|0x0005) plen 13 > > > HCI Event: Command Status(0x0f) plen 4 > > > HCI Event: Connect Complete(0x03) plen 11 > > ?? what happened here? baseband connection failed? > It could be a previous action before the real connect. Following msg would be the the real connect. > > < HCI Command: Create Connection(0x01|0x0005) plen 13 > > > HCI Event: Command Status(0x0f) plen 4 > > > HCI Event: Link Key Request(0x17) plen 6 > > < HCI Command: Link Key Request Reply(0x01|0x000b) plen 22 > > > HCI Event: Command Complete(0x0e) plen 10 > > > HCI Event: Connect Complete(0x03) plen 11 > > seems like baseband connection established > > > < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4 > > < ACL data: handle 0x0006 flags 0x02 dlen 12 > > L2CAP(s): Connect req: psm 1 scid 0x0045 > > here is the request to setup l2cap channel on psm 1 (sdp). > > > > HCI Event: Command Complete(0x0e) plen 6 > > > HCI Event: Number of Completed Packets(0x13) plen 5 > > > HCI Event: Max Slots Change(0x1b) plen 3 > > > HCI Event: Link Key Request(0x17) plen 6 > > < HCI Command: Link Key Request Reply(0x01|0x000b) plen 22 > > > HCI Event: Command Complete(0x0e) plen 10 no response from headset until sdpcontrol search timeout. The headset turn off(or stand by) in 1 minute if pairing unsuccess, that is why a disconnect occurs, I guest. > > < HCI Command: Disconnect(0x01|0x0006) plen 3 > > > HCI Event: Command Status(0x0f) plen 4 > > > HCI Event: Disconn Complete(0x05) plen 4 > > this block above does not make much sense to me. i'm confused why the > device requests link key again. could you please make binary hci dump > (-w option) and send it to me? > > > ------------hcsecd -d------------ > > hcsecd[98316]: Restored link key for the entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805' > > hcsecd[98316]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 00:0b:2e:32:65:12 > > hcsecd[98316]: Found matching entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805', link key exists > > hcsecd[98316]: Sending Link_Key_Reply to 'ubt0hci' for remote bdaddr 00:0b:2e:32:65:12 > > hcsecd[98316]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 00:0b:2e:32:65:12 > > hcsecd[98316]: Found matching entry, remote bdaddr 00:0b:2e:32:65:12, name 'Motorola HS805', link key exists > > hcsecd[98316]: Sending Link_Key_Reply to 'ubt0hci' for remote bdaddr 00:0b:2e:32:65:12 > > looks fine to, but like i said before i'm confused why the device > requests link key twice. > > > ------------hcsecd.conf---------- > > /etc/bluetooth/hcsecd.conf > > #headset > > device{ > > bdaddr 00:0b:2e:32:65:12; > > name "Motorola HS805"; > > key nokey; > > pin "0000"; > > } > > looks fine to. i assume you checked the pin code and it is correct, right? yes, it's a default pin. > > thanks, > max Many thanks, -- Faigozhu --=-=-=--