From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 28 22:07:49 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 A3B2A16A41F for ; Mon, 28 Nov 2005 22:07:49 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4178E43D66 for ; Mon, 28 Nov 2005 22:07:49 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jASM7kJ21026; Mon, 28 Nov 2005 17:07:47 -0500 Message-ID: <438B7FB0.5030704@savvis.net> Date: Mon, 28 Nov 2005 14:07:44 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: faigozhu References: <863blgzdz0.fsf@fastmail.fm> In-Reply-To: <863blgzdz0.fsf@fastmail.fm> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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:07:49 -0000 Hello, > 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? > 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. > ------------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? > < 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 > < 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? thanks, max