• State Not Answered
  • Replies 9 replies
  • Subscribers 74 subscribers
  • Views 1895 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 295863
Options

CoAP Client/Server not attaching

kaushalyasat

Hi,

I have been successfully working with CoAP customized client/sever app for a custom dev board. This custom dev board was based on Minew MS88SF21 module. I have created a custom board definition based on nrf52840dk. I did my custom sensor board design based on this module, which can also accept Raytac MDBT50Q-1MV2. The prototype was built using Raytac module.

When our custom board prototypes arrived, I tried flashing one with CoAP Client app and try to pair it with a CoAP server, which is running on nrf52840dk dev board. But this time the LED1 on server was not lighting up. When I checked using the UART terminal, I could see the server is not attaching 

[00:00:00.466,766] <inf> net_openthread: [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:88, chksum:c284, ecn:no, to:4ec8a3aa4415e77e, sec:no, error:NoAck, prio:net
[00:00:00.467,071] <inf> net_openthread: [N] MeshForwarder-:     src:[fe80:0:0:0:f0dd:73af:496a:9446]:19788
[00:00:00.467,407] <inf> net_openthread: [N] MeshForwarder-:     dst:[fe80:0:0:0:4cc8:a3aa:4415:e77e]:19788
[00:00:01.389,923] <inf> net_openthread: [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:88, chksum:e8ac, ecn:no, to:4ec8a3aa4415e77e, sec:no, error:NoAck, prio:net
[00:00:01.390,228] <inf> net_openthread: [N] MeshForwarder-:     src:[fe80:0:0:0:f0dd:73af:496a:9446]:19788
[00:00:01.390,533] <inf> net_openthread: [N] MeshForwarder-:     dst:[fe80:0:0:0:4cc8:a3aa:4415:e77e]:19788
[00:00:02.368,011] <inf> net_openthread: [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:88, chksum:aa10, ecn:no, to:4ec8a3aa4415e77e, sec:no, error:NoAck, prio:net
[00:00:02.368,316] <inf> net_openthread: [N] MeshForwarder-:     src:[fe80:0:0:0:f0dd:73af:496a:9446]:19788
[00:00:02.368,652] <inf> net_openthread: [N] MeshForwarder-:     dst:[fe80:0:0:0:4cc8:a3aa:4415:e77e]:19788
[00:00:03.351,379] <inf> net_openthread: [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:88, chksum:4b6d, ecn:no, to:4ec8a3aa4415e77e, sec:no, error:NoAck, prio:net
[00:00:03.351,684] <inf> net_openthread: [N] MeshForwarder-:     src:[fe80:0:0:0:f0dd:73af:496a:9446]:19788
[00:00:03.351,989] <inf> net_openthread: [N] MeshForwarder-:     dst:[fe80:0:0:0:4cc8:a3aa:4415:e77e]:19788
[00:00:04.356,262] <inf> net_openthread: [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:88, chksum:0e6d, ecn:no, to:4ec8a3aa4415e77e, sec:no, error:NoAck, prio:net
[00:00:04.356,567] <inf> net_openthread: [N] MeshForwarder-:     src:[fe80:0:0:0:f0dd:73af:496a:9446]:19788
[00:00:04.356,903] <inf> net_openthread: [N] MeshForwarder-:     dst:[fe80:0:0:0:4cc8:a3aa:4415:e77e]:19788
[00:00:05.215,667] <inf> net_openthread: [N] Mle-----------: RLOC16 7c03 -> fffe
[00:00:05.638,854] <inf> net_openthread: [N] Mle-----------: Attempt to attach - attempt 1, AnyPartition reattaching with Active Dataset
[00:00:07.679,626] <inf> net_openthread: [N] Mle-----------: Attach attempt 1 unsuccessful, will try again in 0.261 seconds

Then I tried using another nrf52840dk dev board as the CoAP client and repeat the test, but no luck.

Then I created the CoAP client/server apps fresh from the examples, build, flash to two dev boards, still same. 

Then I update my SDK using nrf Connect Desktop and rebuild the two apps, same result. 

My SDK is 2.0.0.

Looking at first few error messages, it seems server is not getting ACK for IPV6 UDP message sent by server.

The src/dst IP addresses seems correct for my server/client instances.

What could be going wrong here?

Thanks,

Kaushalya

Parents
  • 0

    Hi,

    How have you modified the samples? Could you provide the code/projects?

    Looking at you sniffer log, it seems that initially there is a router\parent present (fe80::4cc8:a3aa:4415:e77e) with two children attached (fe80::cc96:a5e5:3ec1:4aec and fe80::f0dd:73af:496a:9446).

    In the end of the sniffer trace, it seems these two children are looking for a parent, but the previous parent is no longer sending packets. However, there seems to be another device present in the sniffer log (fe80::7c02:908c:d37b:8a79), but this is configured at another PANID (0xFFFF, not 0xABCD like the other nodes), so this may be interference from another network.

    Best regards,
    Jørgen

  • 0 in reply to Jørgen Holmefjord

    Thanks .

    Apologies for my delay, I had to sort out a production issue.

    The code I am trying now is straight out of the example code. So no modifications.

    There were no other OpenThread devices in the vicinity. So I am not sure how these fe80::cc96:a5e5:3ec1:4aec and fe80::f0dd:73af:496a:9446 became children. We only have number of Thread devices in the lab. Can they be attaching to OpenThread networks?

    To become a child, it should have the same PANID, network name and network key as the server, am I correct?

    To make it even worse(??) the server is now becoming a Leader. I didnt do anything. I can see LED1 on server lighting up.

    Really need some help here.

    This is the network session from wireshark. CoAP session-Working.pcapng

    Thanks,

  • 0 in reply to kaushalyasat

    Hi ,

    Now I have been testing my modified server/client projects successfully until this morning and again the system went back to that phantom state of server/client failing to attach.

    I am desperate for a solution now.

    Thanks

Reply Children
Related
Terms of service