Thread connection failure with mcr20a-rf-driver

[maclobdell]

K64F + MCR20A shield GCC_ARM & IAR compilers MESH_THREAD configuration Channel 12 connecting to mbed border router with thread dynamic binary image

6lowpan works, but thread fails.

mbed-os-example-client (514b735fd3d |- esp8266-driver (450cc128865f) |- mbed-os (4b506280eb4d) `- mcr20a-rf-driver (70ce90214856)

Logs attached thread_rc4_mcr20a_gcc.txt thread_rc4_mcr20a_iar.txt

[ciarmcom]

ARM Internal Ref: IOTCLT-888

[hasnainvirk]

@maclobdell Please look at the PR https://github.com/ARMmbed/mbed-os-example-client/pull/64 This is an issue we can't do much about. Its documented. What you need to do is to put the firmware again in Border Router and reset your client board. Or wait for 240 seconds after the failure and reset the client board. The client will always connect for the first time but then if you will reboot the client Board, it will not join the network for next 240 seconds because of MLE frame counter mismatch.

[hasnainvirk]

You can checck from the border router logs there would be a warning about dropping packets because of MLE frame counter not higher

[hasnainvirk]

This should fix your issue. https://github.com/ARMmbed/mbed-os-example-client/commit/b73b6d68f967ac37786e8e695de08c1c9c1130a8 Gateway binaries are changed. We have gone to a version which do not have MLE frame counter implemented. #64 is removed.

[yogpan01]

@hasnainvirk Can this issue be closed now ? If yes, please close it.

[hasnainvirk]

Positive. This should be closed. @maclobdell can you please close this ?

[maclobdell]

Let me test this again just to confirm.

[maclobdell]

There is still an issue connecting to a thread network with this example and mcr20a rf shield and driver. I tested this twice with slightly different results each time. Attached are the two logs. This exact setup works fine with atmel shield and rf driver. I waited 5+ minutes between all tests.

mbed-os-example-client-5.1.0-mcr20a_test_log_2.txt

mbed-os-example-client-5.1.0-mcr20a_test_log.txt

Logs say No IP Address. Later it shows other failing attempts.

mbed-os-5.1.0 tag K64F + MCR20A shield GCC_ARM compiler MESH_THREAD configuration Channel 12 connecting to mbed border router with thread dynamic binary image

mbed-os-example-client (2b5ecfb5f770 |- esp8266-driver (450cc128865f) |- mbed-os (0712b8adf6bb) `- mcr20a-rf-driver (70ce90214856)

MESH_LOWPAN_ND configuration works fine. Just Thread fails consistently.

[hasnainvirk]

@maclobdell I will ask someone in cambridge to send me this rf shield. Without having hardware I can't help you no matter how much I want to do so.

[yogpan01]

@hasnainvirk @maclobdell Is this issue resolved ?

[hasnainvirk]

@yogpan01 I have the hardware now. But I had not have any time to look into it.

[hasnainvirk]

@yogpan01 @AnttiKauppila I am not able to Connect to Connector using Thread with any RF shield. I tried with both atme-rf-shield and mcr20a-rf-shield.

-> Thread network gets established. -> Node gets the IP address (both with atmel-rf and mcr20a) -> Then it tries to connect to Connector

Symptoms:

• I can only see Client Hello messages in Wireshark.
• No reponse from Connector.

The end result is that I am unable to connect to Connector.

[hasnainvirk]

@yogpan01 @AnttiKauppila @maclobdell

Alright, it seems that the my 4G Elisa device (for backhaul connectivity) needed a firmware update. Its DHCPv6 mechanism was not working properly. So I was getting an IPv6 address but it wasn't routable at ISP's end. I updated the firmware and everything worked fine.

I tried with both atmel-rf-shield and mcr20a-rf-shield. Both worked fine.

I think this issue can be closed.

[TuomoHautamaki]

@yogpan01, @maclobdell please close this one unless you think this requires further studies. In our tests things worked fine

[yogpan01]

@maclobdell can you please close this issue ?

[maclobdell]

Looks like the issue could have been due to an unconnected antenna on my mcr20a shield. Both 6lowpan and thread networking is passing now. This can be closed. Thanks.