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

NRF5280 dongle - open thread cli issue

Hello, I have two nrf52840 dongles with CLI FTD example programmed on both dongles (https://infocenter.nordicsemi.com/index.jsp?topic=%2Fstruct_sdk%2Fstruct%2Fsdk_thread_zigbee_latest.html). I issued on both dongles following commands:

panid 0xABCD

ifconfig up

thread start

Then dongles after few seconds are successfully connected to network (LED is not blinking). Then I tried ping each other device using ipaddr and ping command.

From one dongle if I ping to another, LEDs on second dongle blinks red and green, but in console no response is shown. Its sometimes shows a response but it is with large latency:

16 bytes from fdde:ad00:beef:0:fe3b:d88d:b1b3:aa56: icmp_seq=5 hlim=64 time=46203ms

I even tried to ping the other direction. LEDs not blinking at all and no response is shown. So there is some difference between dongles. But both dongles has the same firmware programmed.

If I try to program NCP FTD example on one dongle and plug in into ARM Linux machine with debian and otbr-agent running, then they "see" each other (border agent with NCP dongle and dongle with CLI agent). But the CLI dongle dont join the network created by border router. If I replace dongle with cli firmware with my custom board with nrf52840 it same result. None of devices are able to join existing network created by NCP dongle. I have same settings on border router and other devices (PANID: 0xABCD, channel: 15). There is logs from otbr-agent:

Dec 06 22:14:45 rockpro64 otbr-agent[2695]: [INFO]-MAC-----:     src:[fe80:0:0:0:409:d1ba:7603:a246]:19788Dec 06 22:14:45 rockpro64 otbr-agent[2695]: [INFO]-MAC-----:     dst:[ff02:0:0:0:0:0:0:1]:19788
Dec 06 22:14:45 rockpro64 otbr-agent[2695]: [INFO]-MLE-----: Receive Announce (fe80:0:0:0:409:d1ba:7603:a246)
Dec 06 22:14:51 rockpro64 otbr-agent[2695]: otbr-agent[2695]: [INFO]-MAC-----: Received IPv6 UDP msg, len:83, chksum:f30f, from:0609d1ba7603a246, sec:yes, prio:net, rss:-77.0
Dec 06 22:14:51 rockpro64 otbr-agent[2695]: otbr-agent[2695]: [INFO]-MAC-----:     src:[fe80:0:0:0:409:d1ba:7603:a246]:19788
Dec 06 22:14:51 rockpro64 otbr-agent[2695]: otbr-agent[2695]: [INFO]-MAC-----:     dst:[ff02:0:0:0:0:0:0:1]:19788
Dec 06 22:14:51 rockpro64 otbr-agent[2695]: [INFO]-MAC-----: Received IPv6 UDP msg, len:83, chksum:f30f, from:0609d1ba7603a246, sec:yes, prio:net, rss:-77.0
Dec 06 22:14:51 rockpro64 otbr-agent[2695]: otbr-agent[2695]: [INFO]-MLE-----: Receive Announce (fe80:0:0:0:409:d1ba:7603:a246)
Dec 06 22:14:51 rockpro64 otbr-agent[2695]: [INFO]-MAC-----:     src:[fe80:0:0:0:409:d1ba:7603:a246]:19788Dec 06 22:14:51 rockpro64 otbr-agent[2695]: [INFO]-MAC-----:     dst:[ff02:0:0:0:0:0:0:1]:19788
Dec 06 22:14:51 rockpro64 otbr-agent[2695]: [INFO]-MLE-----: Receive Announce (fe80:0:0:0:409:d1ba:7603:a246)
Dec 06 22:15:09 rockpro64 otbr-agent[2695]: otbr-agent[2695]: [INFO]-MLE-----: Send Advertisement (ff02:0:0:0:0:0:0:1)
Dec 06 22:15:09 rockpro64 otbr-agent[2695]: [INFO]-MLE-----: Send Advertisement (ff02:0:0:0:0:0:0:1)
Dec 06 22:15:09 rockpro64 otbr-agent[2695]: [INFO]-MAC-----: Sent IPv6 UDP msg, len:90, chksum:54f4, to:0xffff, sec:no, prio:net
Dec 06 22:15:09 rockpro64 otbr-agent[2695]: otbr-agent[2695]: [INFO]-MAC-----: Sent IPv6 UDP msg, len:90, chksum:54f4, to:0xffff, sec:no, prio:netDec 06 22:15:09 rockpro64 otbr-agent[2695]: otbr-agent[2695]: [INFO]-MAC-----:     src:[fe80:0:0:0:44d2:b035:d23e:c56a]:19788
Dec 06 22:15:09 rockpro64 otbr-agent[2695]: otbr-agent[2695]: [INFO]-MAC-----:     dst:[ff02:0:0:0:0:0:0:1]:19788
Dec 06 22:15:09 rockpro64 otbr-agent[2695]: [INFO]-MAC-----:     src:[fe80:0:0:0:44d2:b035:d23e:c56a]:19788
Dec 06 22:15:09 rockpro64 otbr-agent[2695]: [INFO]-MAC-----:     dst:[ff02:0:0:0:0:0:0:1]:19788

Where could be a problem? Thanks for response

Parents Reply
  • It was not hardware issue. I suspected that the application has some invalid configuration inside flash memory. So I created HEX file with all 'ones' and flash it. Now ping works. It would be useful to have some erase option in nRF Connect Programmer software. But for others who might have similar issue I attach HEX file which solved the problem. It also solve problem with connecting to openthread gateway

    > ping fdde:ad00:beef:0:a53e:5333:1dcf:bca
    Done
    > 16 bytes from fdde:ad00:beef:0:a53e:5333:1dcf:bca: icmp_seq=1 hlim=64 time=11ms

    HexFile.hex

Children
No Data
Related