From: Dave Higton <davehigton@dsl.pipex.com>
To: linux-bluetooth@vger.kernel.org
Subject: Arguments to PIN Code Request Response
Date: Fri, 19 Aug 2011 22:25:23 +0100 [thread overview]
Message-ID: <7b86640552.davehigton@dsl.pipex.com> (raw)
According to the Core Spec versions 4.0, 3.0, 2.1 and 2.0, the
arguments to PIN Code Request Reply are BD_ADDR, PIN length, and
PIN code. However, this doesn't work with the devices I've tried
(an Android phone and a mini keyboard); there are several more
bytes of argument in a capture that I have. If I only send the
args as per the spec, I get an args not understood error; if I
add these other arg bytes, copied from the capture, the PIN code
is accepted and the pairing process continues.
Are these extra arguments documented in one of the earlier core
specifications, now deprecated?
The bytes I have are:
0D 04 17 3F 1B AC 26 2C DC 04 30 30 30 30 17 00 0C 11 0A 11 0B 11 16 11 02 0A
Unless I've badly misunderstood something, the PIN code length
above is 4, and the PIN code is ASCII "0000". I don't expect to
see any bytes following "30 30 30 30".
Dave
next reply other threads:[~2011-08-19 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 21:25 Dave Higton [this message]
[not found] ` <CAMhHtTy7vStrSEZsj6Gcy_VO-JfL4tuYZ=TJWtQ4TxqMMGQpTQ@mail.gmail.com>
2011-08-22 16:56 ` Arguments to PIN Code Request Response Ash K
2011-08-22 19:49 ` Dave Higton
2011-08-22 20:02 ` Luiz Augusto von Dentz
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=7b86640552.davehigton@dsl.pipex.com \
--to=davehigton@dsl.pipex.com \
--cc=linux-bluetooth@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).