From: Mark Watson <mark@marubeca.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Building btsco for Fedora 3
Date: Sun, 15 May 2005 20:58:40 +0100 [thread overview]
Message-ID: <4287A9F0.7000400@marubeca.net> (raw)
In-Reply-To: <42879F86.8090902@xmission.com>
Brad Midgley wrote:
> try it without specifying the '1' (the channel should be autodetected)
>
> btw, does it say anywhere in our docs that you need to specify the
> channel?
You're right, it doesn't. I was following various examples from Google.
Here's my attempt to connect, with tail -f /var/log/messages in the
background:
> [bluetooth]# btsco 00:07:A4:07:52:3D
> May 15 20:51:02 localhost hcid[7935]: pin_code_request
> (sba=00:20:E0:74:66:58, dba=00:07:A4:07:52:3D)
> Error: Failed to connect to SDP server: Function not implemented
> Assuming channel 2
>
> Can't connect RFCOMM channel: Resource temporarily unavailable
And here's the hcidump -X output
> [bluetooth]# hcidump -X
> HCIDump - HCI packet analyzer ver 1.11
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: Create Connection (0x01|0x0005) plen 13
> 0000: 3d 52 07 a4 07 00 18 cc 02 00 00 00 00 =R...........
> > HCI Event: Command Status (0x0f) plen 4
> 0000: 00 01 05 04 ....
> > HCI Event: PIN Code Request (0x16) plen 6
> 0000: 3d 52 07 a4 07 00 =R....
> < HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23
> 0000: 3d 52 07 a4 07 00 2b 53 65 72 76 69 63 65 20 22 =R....+Service "
> 0010: 6f 72 67 2e 62 6c 75 org.blu
> > HCI Event: Command Complete (0x0e) plen 10
> 0000: 01 0d 04 12 3d 52 07 a4 07 00 ....=R....
> > HCI Event: Connect Complete (0x03) plen 11
> 0000: 22 29 00 3d 52 07 a4 07 00 01 00 ").=R......
> < HCI Command: Read Voice Setting (0x03|0x0025) plen 0
> > HCI Event: Command Complete (0x0e) plen 6
> 0000: 01 25 0c 00 60 00 .%..`.
> < HCI Command: Create Connection (0x01|0x0005) plen 13
> 0000: 3d 52 07 a4 07 00 18 cc 02 00 00 00 00 =R...........
> > HCI Event: Command Status (0x0f) plen 4
> 0000: 00 01 05 04 ....
> > HCI Event: PIN Code Request (0x16) plen 6
> 0000: 3d 52 07 a4 07 00 =R....
> < HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23
> 0000: 3d 52 07 a4 07 00 2b 53 65 72 76 69 63 65 20 22 =R....+Service "
> 0010: 6f 72 67 2e 62 6c 75 org.blu
> > HCI Event: Command Complete (0x0e) plen 10
> 0000: 01 0d 04 12 3d 52 07 a4 07 00 ....=R....
> > HCI Event: Connect Complete (0x03) plen 11
> 0000: 22 2a 00 3d 52 07 a4 07 00 01 00 "*.=R......
/etc/bluetooth/pin contains:
0000
I'm not confident the pin number is actually moving across ... bluepin
never asks for input during the run
Mark
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-05-15 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 0:47 [Bluez-devel] Building btsco for Fedora 3 Mark Watson
2005-05-15 1:08 ` Henryk Plötz
2005-05-15 6:02 ` Brad Midgley
2005-05-15 15:04 ` Mark Watson
2005-05-15 19:14 ` Brad Midgley
2005-05-15 19:58 ` Mark Watson [this message]
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=4287A9F0.7000400@marubeca.net \
--to=mark@marubeca.net \
--cc=bluez-devel@lists.sourceforge.net \
/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