NFC Commissioning timeout

[Mary]

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

[Jørgen Holmefjord]

Hi,

Have you tested to run unmodified applications from freshly extracted SDK version, to make sure that nothing have been modified?

Best regards,
Jørgen

[Mary]

Yes. 

I loaded the SDK 2.0.0 NCP uart example onto a development board, and connected J2 to the Border Router. Commissioning worked fine.

I loaded the SDK 2.0.0 NCP usb example onto a development board, and connected 'nRF USB' (J3) to the Border Router.  LED1 came on, but commissioning failed.  

The 'thread_ncp_usb_pca10056' output the following:

[0000164906] -MESH-CP-: handshake timeout

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

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

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

For my custom board, I have modified the NCP usb project by adding a 'custom_board.h' to define the pin for the LEDs and defining BOARD_CUSTOM in the project settings.  I cleaned and recompiled the project.  Again, the LED indicated a network connection, but commissioning failed.  My board is connected to the Border Router via the native USB port.

Mary