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

NFC Commissioning timeout

I am using nRF5 SDK for Thread and Zigbee 2.0.0

I am having trouble commissioning using NFC, either with the nfc_meshcop example or my own code (based on the nfc_meshcop example).

After bringing the NFC antenna near the antenna on the Raspberry Pi based Border Router, I see the following messages after about a minute and a half:

[0000137496] -MESH-CP-: handshake timeout

[0000137496] -MESH-CP-: mbedtls_ssl_fetch_input() returned -26624 (-0x6800)

[0000137496] -MESH-CP-: mbedtls_ssl_read_record_layer() returned -26624 (-0x6800)

[0000137496] -MESH-CP-: mbedtls_ssl_read_record() returned -26624 (-0x6800)

<info> app: State changed! Flags: 0x00008000 Current role: 0

<info> app: State changed! Flags: 0x0000800B Current role: 0

<info> app: State changed! Flags: 0x00008000 Current role: 0

<info> app: State changed! Flags: 0x0000800B Current role: 0

<info> app: State changed! Flags: 0x00008000 Current role: 0

<info> app: State changed! Flags: 0x0000800B Current role: 0

Also, the function joiner_calback(otError error, void * p_context) is called with the 'error' parameter set to OT_ERROR_SECURITY.

The Raspberry Pi is running from the RaspPi_OT_Border_Router_Demov2.0.0-1.alpha.img

What do these messages mean? and how do I fix it?

Mary

Parents Reply Children
Related