About Request hexadecimal key (hex 16 octets) in the provisining between nRF52832 and Jetson nano(ubuntu arm64)

[colin.tan]

Hi all,

         When I use the Bluez tool meshctl on Jetson nano(ubuntu arm64) to provision a nRF52832 device, failed at the authentication step, as follow:

Request hexadecimal key (hex 16 octets)
[[mesh-agent]# ] Enter key (hex number): 6E6F726469635F6578616D706C655F31
GATT-TX: 03 05 01 1d 76 81 64 b2 90 3c bc c8 65 9d e6 72 
GATT-TX: 94 32 
GATT-RX: 03 05 ed 95 17 e6 48 51 cf 5c 6a 1c 90 2b 95 ae 
GATT-RX: e5 94 
Got provisioning data (17 bytes)
05 ed 95 17 e6 48 51 cf 5c 6a 1c 90 2b 95 ae e5 
94 
GATT-TX: 03 06 ec cd 5c da 77 bb 86 80 46 97 58 93 b1 93 
GATT-TX: 9d 1e 
GATT-RX: 03 09 04 
Got provisioning data (2 bytes)
09 04 
Provisioning failed
Attempting to disconnect from EF:9B:8E:75:2D:E4
Characteristic property changed /org/bluez/hci0/dev_EF_9B_8E_75_2D_E4/service000e/char0011
Write closed
Services resolved no
Characteristic property changed /org/bluez/hci0/dev_EF_9B_8E_75_2D_E4/service000e/char000f

the 16 octets keys I get from STATIC_AUTH_DATA in the example_common.h file for nrf5_SDK_for_Mesh_v4.2.0_src.

Q: The key I used is correct？Or what might be the cause。

Thanks!

[Hung Bui]

Hi, 
I would suspect the endianess was reversed. So if you try again with 315F65.. it may work. 

But i'm not sure it's the authentication causing the issue, have you tried to test without static authentication ? 

[colin.tan]

Thank you for your reply，I also had tried with 315F65..， but also failed with the same issue。

[colin.tan]

By the way， because the Unprovisioned device I developing just support static OOB， so I only tried  static authentication with the device。

[Hung Bui]

Could you give more information about the unprovisioned device ?
Have you tried to test  provisioning the stock example in the SDK , the light_switch project for example. 
I'm just wondering if you have fetched the STATIC_AUTH_DATA into the firmware of your unprovisioned device. 

[colin.tan]

Hi Hung,

   I sorry for bother you again, could you tell me what kond of the AES_CMAC algorithm the Nordic Mesh SDK 4.2.0 using for provisioning confirm value compute？