• State Not Answered
  • Replies 2 replies
  • Subscribers 75 subscribers
  • Views 37 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 347001
Options

the CLI device on a thread network can only sometimes communicate with internet

Jinxiu Liu

I have set up the OTBR with a RPi 5 and an nRF 52840 DK as an RCP. The CLI device can join the thread network as a child, the OTBR as the leader.(https://www.youtube.com/watch?v=xCyzNzYSG4U&t=1931s). Everything is ok except the last step: ot ping 8.8.8.8 from my CLI device. it can ping 8.8.8.8 successfully 1 in 10.
the question is I can ping IPv4 like 8.8.8.8 or the IPv4 of my phone (in the same LAN) with sudo ot-ctl ping 8.8.8.8 on RPi,
but in the CLI device (nRF5340 DK), it can only ping 8.8.8.8 sometimes; most times it fails. But sometimes it can ping 8.8.8.8 successfully and receive the return packet. What should I do?
I have installed the newest version of RPi from the official website(https://www.raspberrypi.com/software/). System: 32-bit Kernel version: 6.12 Debian version: 12 (bookworm)

Does anyone know what is happening? Thank you in advance for your help!

Best regards,
Jinxiu

Parents
  • 0

    Hi,

    Where did you get the RCP image file from?

    Can you show the output of "netdata show"?

    If you are able to, get a  nRF Sniffer for 802.15.4 log. With this, we can analyze the traffic on the air to get more information about the error.

    Regards,
    Sigurd Hellesvik

  • 0 in reply to Sigurd Hellesvik

    Hi Sigurd,

    Thank you greatly for your timely reply!

    I got the RCP .hex file following this guide https://openthread.io/codelabs/openthread-hardware#3. When I flashed it for the first time, everything works well. When this error occurred, I thought there maybe something wrong with the RCP file so I want to flash it again but the nRF Connect for Desktop exit with Error Code 1 llike this: 

    Failed "reading readback protection status for application core". Error: code: 1, description: Generic, message: Batch task protection-get failed, Device error: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1)

    Error: Failed with exit code 1. One or more batch tasks failed: * 1050249266: Device error: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1) (Generic). Message: Batch task protection-get failed, Device error: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1).

    Error: Failed with exit code 1. One or more batch tasks failed: * 1050249266: Device error: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1) (Generic). Message: Batch task protection-get failed, Device error: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1).

    I couldn't recover or erase this nRF52840 DK with the same error. But it still can works as an RCP. The J-Link is recognized and I can see the two COM.

    The following is the output of netdata show

    Prefixes:
    fd4d:a638:726:1::/64 paros low 9400
    Routes:
    ::/0 s med 9400
    fd4d:a638:726:2:0:0::/96 sn low 9400
    Services:
    44970 01 31000500000e10 s 9400 0
    44970 5d fdfc53baf620225bf46cdeb73cbd8cead120 s 9400 1
    Contexts:
    fd4d:a638:726:1::/64 1 sc
    Commissioning:
    8844 - - -
    Done

    When I do ot ping fd4d:a638:726:2:0:0::8.8.8.8 or ot ping 8.8.8.8 on my CLI device, sometimes it works and get the return package (1 in 10).

    How could I get a  nRF Sniffer for 802.15.4 log? Is there any guidance?

    Best regards,

    Jinxiu Liu

Reply
  • 0 in reply to Sigurd Hellesvik

    Hi Sigurd,

    Thank you greatly for your timely reply!

    I got the RCP .hex file following this guide https://openthread.io/codelabs/openthread-hardware#3. When I flashed it for the first time, everything works well. When this error occurred, I thought there maybe something wrong with the RCP file so I want to flash it again but the nRF Connect for Desktop exit with Error Code 1 llike this: 

    Failed "reading readback protection status for application core". Error: code: 1, description: Generic, message: Batch task protection-get failed, Device error: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1)

    Error: Failed with exit code 1. One or more batch tasks failed: * 1050249266: Device error: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1) (Generic). Message: Batch task protection-get failed, Device error: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1).

    Error: Failed with exit code 1. One or more batch tasks failed: * 1050249266: Device error: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1) (Generic). Message: Batch task protection-get failed, Device error: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1).

    I couldn't recover or erase this nRF52840 DK with the same error. But it still can works as an RCP. The J-Link is recognized and I can see the two COM.

    The following is the output of netdata show

    Prefixes:
    fd4d:a638:726:1::/64 paros low 9400
    Routes:
    ::/0 s med 9400
    fd4d:a638:726:2:0:0::/96 sn low 9400
    Services:
    44970 01 31000500000e10 s 9400 0
    44970 5d fdfc53baf620225bf46cdeb73cbd8cead120 s 9400 1
    Contexts:
    fd4d:a638:726:1::/64 1 sc
    Commissioning:
    8844 - - -
    Done

    When I do ot ping fd4d:a638:726:2:0:0::8.8.8.8 or ot ping 8.8.8.8 on my CLI device, sometimes it works and get the return package (1 in 10).

    How could I get a  nRF Sniffer for 802.15.4 log? Is there any guidance?

    Best regards,

    Jinxiu Liu

Children
No Data
Related
Terms of service