This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Pairing two devices nRF52

Hi all,

I am working on my Central device to request pairing to my peripheral (I asked about the peripheral in my previous post, both are running a nRF52DK and SDK13.

I am having the following 'issue' at the moment I don't know if I am performing LESC + Just Works or Legacy + Just Works.

My sniffer captures have a big difference when I use nRF connect (version PC using a nRF51DK) to perform the pairing with a nRF52DK running the lesc_multirole vs two nRF52 Boards running lesc_multirole example. I both cases the example code was unmodified

my sec_parms are:

sec_params.bond           = true;
sec_params.mitm           = false;
sec_params.lesc           = true;
sec_params.keypress       = false;
sec_params.io_caps        = false;
sec_params.oob            = false;
sec_params.min_key_size   = 7;
sec_params.max_key_size   = 16;
sec_params.kdist_own.enc  = 1;
sec_params.kdist_own.id   = 1;
sec_params.kdist_peer.enc = 1;
sec_params.kdist_peer.id  = 1;

Test1

  • I got the following sequence when two nRF52DK are running the lesc_multirole example with not display or input image description

also in the sniffer capture it looks like is using a 000000 passkey and not the Elliptic-curve for the encryption and it is not pairing

Test2

  • For otherwise when I am running the lesc_multirole example on a nRF52 like a peripheral and the central using the connecitivy firmware for nRF Connect (PC version) this sequence differs a lot when are 2 devices with no display or inputs, and it looks is generating random values and it is pairing: image description

why are so different the sequence when using a nRF connect/PC/Smartphone like central vs a nRF52DK running the lesc_multirole example?.

An additional question LESC + 'Just works' requires bonding?

Thanks

Parents Reply Children
No Data
Related