Thread (3 messages) flat view 3 messages, 3 authors, 2011-08-22

Re: Arguments to PIN Code Request Response

From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Date: 2011-08-22 20:02:36

Hi Dave,

On Mon, Aug 22, 2011 at 10:49 PM, Dave Higton [off-list ref] wrote:
In message
[ref]
         Ash K [off-list ref] wrote:
quoted
Hi Dave,

If you see specification the PIN_Code parameter for
PIN_Code_request_reply command, it says

Value
----
0xXXXXXXXXXX
XXXXXXXXXXX
XXXXXXXXXXX
 Parameter Description
----
PIN code for the device that is to be connected. The Host should
ensure that strong PIN Codes are used. PIN Codes can be up to a
maximum of 128 bits. Note: The PIN_Code Parameter is a string
parameter. Endianess does therefore not apply to the PIN_Code
Parameter. The first octet of the PIN code should be transmitted first.
Which means, even if your PIN code of 4 byte length you have to send
16 byte length of PIN code to controller. And controller uses initial
bytes from the 16byte PIN code, the length of the PIN code is defined
by length parameter.
What you are looking at is correct, after 4 bytes of PIN code, you
have some junk/host selected data which is of no interest to
controller.
Many thanks for your explanation, Ash.
Btw, you can use hcidump to get some traces.

-- 
Luiz Augusto von Dentz
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help