public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "Rolf E. Thorup" <rolft@daimi.au.dk>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] SDP problems on embedded device
Date: Mon, 19 Jul 2004 22:53:07 +0200	[thread overview]
Message-ID: <1090270387.4400.100.camel@pegasus> (raw)
In-Reply-To: <40FC2322.4060204@daimi.au.dk>

Hi Rolf,

> I have some problems with sdp on a Intrinsyc Cerfcube 255 
> (http://www.intrinsyc.com/products/cerfcube/) running a Linux 2.4.19 
> kernel patched with the mh17-patch (and some platform specific patches).
> 
> The problem is that I can't get to discover anything on the device. I 
> have tried with two mobile phones, and a laptop running RH 9.0.
> 
>  From the laptop I either try 'spdtool browse bdaddr' or 'sdptool search 
> SP' after adding SP service to the SDP record of the Cerfcube. I am able 
> to browse the service record of the mobile phone, but not the Cerfcube. 
> The output could be: 'Failed to connect to SDP server on 
> 00:0A:94:00:20:2A: Resource temporarily unavailable'. Other reasons I 
> have experienced are:  'Host is down', 'Connection timed out', and 
> 'Connection refused'.
> 
> My final goal is to make a connection (SP profile) between a Midlet 
> running on a Nokia 6600 and the Cerfcube. I have tested this setup with 
> the laptop and the phone and it works. But this will only work if 
> service discovery works.
> 
> At first I thought that maybe the problem was caused by using old 
> versions of bluez on the Cerfcube, but I have just cross-compiled and 
> installed bluez-2.8 (lib and utils) and the situation is the same.
> 
> Here's the output from 'hcidump -x' from the Cerfcube when trying 
> 'sdptool browse' from the laptop.
> 
> HCIDump - HCI packet analyzer ver 1.9
> device: hci0 snap_len: 1028 filter: 0xffffffff
>  > HCI Event: Connect Request (0x04) plen 10
>    74 05 B1 76 0C 00 00 01 00 01
> < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
>    74 05 B1 76 0C 00 01
>  > HCI Event: Command Status (0x0f) plen 4
>    00 01 09 04
>  > HCI Event: Connect Complete (0x03) plen 11
>    00 29 00 74 05 B1 76 0C 00 01 00
> < HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
>    29 00 0F 00
>  > HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
>    74 05 B1 76 0C 00 01
>  > HCI Event: Command Complete (0x0e) plen 6
>    01 0D 08 00 29 00
> < HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
>    29 00 18 CC
>  > HCI Event: Max Slots Change (0x1b) plen 3
>    29 00 05
>  > HCI Event: Command Status (0x0f) plen 4
>    00 01 0F 04
>  > HCI Event: Connection Packet Type Changed (0x1d) plen 5
>    00 29 00 18 CC
>  > ACL data: handle 0x0029 flags 0x02 dlen 12
>      L2CAP(s): Connect req: psm 1 scid 0x0040
> < ACL data: handle 0x0029 flags 0x02 dlen 16
>      L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
>  > HCI Event: Number of Completed Packets (0x13) plen 5
>    01 29 00 01 00
>  > ACL data: handle 0x0029 flags 0x02 dlen 12
>      L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 0
> < ACL data: handle 0x0029 flags 0x02 dlen 14
>      L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
> < ACL data: handle 0x0029 flags 0x02 dlen 12
>      L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 0
>  > HCI Event: Number of Completed Packets (0x13) plen 5
>    01 29 00 01 00
>  > ACL data: handle 0x0029 flags 0x02 dlen 12
>      L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> < ACL data: handle 0x0029 flags 0x02 dlen 12
>      L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
>  > HCI Event: Number of Completed Packets (0x13) plen 5
>    01 29 00 01 00
>  > HCI Event: Disconn Complete (0x05) plen 4
>    00 29 00 13
> 
> I'm using a USB bluetooth dongle for both the Cerfcube and the laptop.
> 
> So, what to do next?

looks like a kernel or scheduling bug. Run "hcidump -x -t" on both sides
so we can compare the data flow and the timestamps.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-07-19 20:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-19 19:38 [Bluez-users] SDP problems on embedded device Rolf E. Thorup
2004-07-19 20:53 ` Marcel Holtmann [this message]
2004-07-20 10:31   ` Rolf E. Thorup
2004-07-20 14:47     ` Marcel Holtmann
2004-07-20 17:10       ` Rolf E. Thorup
2004-07-20 17:43         ` Marcel Holtmann
2004-07-21  9:43           ` Rolf E. Thorup
2004-07-21 10:04             ` Marcel Holtmann
2004-07-21 10:56               ` Rolf E. Thorup
2004-07-21 12:18                 ` Marcel Holtmann
2004-07-21 12:30                   ` Rolf E. Thorup
2004-07-28 14:05                     ` Rolf E. Thorup
2004-07-28 18:57                       ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1090270387.4400.100.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=rolft@daimi.au.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox