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

NCP wpantund stops transmitting

I am running a nrf52840 dev board as an NCP connected to a RASPBERRY Pi running wpantund. I have 10 other nrf52840 devices in the network. The PI has LIBCOAP coap-client on it sending COAP packets to the other devices at a rate of 1 per second. After about 1 hour the NCP will stop transmitting.

The return from the NCP is

Oct 17 13:00:14 r1 wpantund[1695]: [NCP->] CMD_PROP_VALUE_IS(PROP_LAST_STATUS) tid:0
Oct 17 13:00:14 r1 wpantund[1695]: [-NCP-]: Last status (STATUS_NOMEM, 11)

I have been in Contact with Johnathan *** through the THREAD USERS Group and he has looked at the syslog and RTT logs. His suggestion was to contact Nordic support. I can get you the logs or they are available on the the thread user group. The Topic is NCP status NO_MEM. Johnathan pulled this snippet from the RTT log.

$ cat NCP_101817_1252_RTT.log | grep Sent
...
 0> [0004290560] -MAC-----: Sent IPv6 UDP msg, len:77, chksum:ae13, to:0x5c00, sec:yes, prio:low
 0> [0004290567] -MLE-----: Sent link request
 0> [0004290573] -MAC-----: Sent IPv6 UDP msg, len:95, chksum:e68f, to:0xffff, sec:no, prio:high
 0> [0004290747] -MLE-----: Sent link accept
 0> [0004290753] -MAC-----: Sent IPv6 UDP msg, len:107, chksum:a894, to:b227a3406e162b82, sec:no, prio:high
 0> [0004291154] -MAC-----: Sent IPv6 UDP msg, len:75, chksum:af6a, to:0xffff, sec:yes, prio:low
 0> [0004291188] -MLE-----: Sent advertisement
 0> [0004291194] -MAC-----: Sent IPv6 UDP msg, len:91, chksum:825a, to:0xffff, sec:no, prio:high
 0> [0004291202] -MLE-----: Sent link accept
 0> [0004291208] -MAC-----: Sent IPv6 UDP msg, len:97, chksum:2880, to:5a40c9b1f073e26a, sec:no, prio:high
 0> [0004292164] -MAC-----: Sent IPv6 UDP msg, len:86, chksum:139b, to:0xffff, sec:yes, prio:low
 0> [0004292442] -MLE-----: Sent delayed response
 0> [0004292450] -MAC-----: Sent IPv6 UDP msg, len:129, chksum:9374, to:e217f6f202a582ee, sec:no, prio:high
 0> [0004293076] -MLE-----: Sent advertisement
 0> [0004293079] -MAC-----: Sent IPv6 UDP msg, len:91, chksum:b4be, to:0xffff, sec:no, prio:high
 0> [0004293088] -MLE-----: Sent link accept
 0> [0004293114] -MAC-----: Sent IPv6 UDP msg, len:97, chksum:0c23, to:b270eb30f2fc8333, sec:no, prio:high
 0> [0004293395] -MLE-----: Sent delayed response
 0> [0004293457] -MAC-----: Sent IPv6 UDP msg, len:129, chksum:aceb, to:e217f6f202a582ee, sec:no, prio:high
 0> [0004294178] -MAC-----: Sent IPv6 UDP msg, len:86, chksum:1f5d, to:0xffff, sec:yes, prio:low
 0> [0004296189] -MAC-----: Sent IPv6 UDP msg, len:77, chksum:0ca1, to:0xffff, sec:yes, prio:low
 0> [0004296769] -MLE-----: Sent advertisement
 0> [0004303861] -MLE-----: Sent advertisement
 0> [0004319394] -MLE-----: Sent delayed response
 0> [0004320824] -MLE-----: Sent advertisement
 0> [0004332413] -MLE-----: Sent delayed response
 0> [0004332531] -MLE-----: Sent delayed response
 0> [0004332681] -MLE-----: Sent link request
 0> [0004333615] -MLE-----: Sent advertisement
 0> [0004333944] -MLE-----: Sent link request
 0> [0004334793] -MLE-----: Sent link request
 0> [0004335390] -MLE-----: Sent advertisement
 0> [0004335636] -MLE-----: Sent link request
 0> [0004336870] -MLE-----: Sent advertisement
 0> [0004338148] -MLE-----: Sent link request
 0> [0004338672] -MLE-----: Sent link request
 0> [0004341191] -MLE-----: Sent advertisement
 0> [0004345556] -MLE-----: Sent link request
 0> [0004345971] -MLE-----: Sent advertisement
 0> [0004355637] -MLE-----: Sent link request
 0> [0004356362] -MLE-----: Sent delayed response
 0> [0004357869] -MLE-----: Sent link request
 0> [0004357935] -MLE-----: Sent advertisement
 0> [0004359076] -MLE-----: Sent advertisement
 0> [0004362439] -MLE-----: Sent link request
 0> [0004363303] -MLE-----: Sent advertisement
 0> [0004368216] -MLE-----: Sent link request
 0> [0004371464] -MLE-----: Sent advertisement
Parents
  • I think we're seeing different problem with nRF52840 in similar areas. Namely, we're compiling our app with latest OpenThread from master branch, and it seems that radio operations (e.g. scanning, trying to join), do slow down a lot (like joining takes half an hour instead of 5 seconds) exactly after 4294 seconds (2^32 microseconds?) since boot - every single time, down to the second. It doesn't matter whether we try to join network every 5 seconds or every 20 seconds. We didn't noticed that slowdown on older OpenThread repository.

Reply
  • I think we're seeing different problem with nRF52840 in similar areas. Namely, we're compiling our app with latest OpenThread from master branch, and it seems that radio operations (e.g. scanning, trying to join), do slow down a lot (like joining takes half an hour instead of 5 seconds) exactly after 4294 seconds (2^32 microseconds?) since boot - every single time, down to the second. It doesn't matter whether we try to join network every 5 seconds or every 20 seconds. We didn't noticed that slowdown on older OpenThread repository.

Children
No Data
Related