RadioSpinelNoResponse: OpenThread daemon is not running (nRF52840 DK)

OpenThread daemon fails to run whenever using the nRF 52840 DK development board but works fine when using the nRF 52840 Dongle. I reinstalled it multiple times and started from scratch with so many tweaks but couldn't figure it out.

Default OTBR Agent: cat /etc/default/otbr-agent

# Default settings for otbr-agent. This file is sourced by systemd

# Options to pass to otbr-agent
OTBR_AGENT_OPTS="-I wpan0 -B wlan0 spinel+hdlc+uart:///dev/ttyACM0 trel://wlan0"
OTBR_NO_AUTO_ATTACH=0

I can confirm the development board appears in the same port as shown above. ls /dev/ttyA*

/dev/ttyACM0 /dev/ttyACM1 /dev/ttyAMA0

I tried manually enabling the OpenThread daemon like the following but no luck.

sudo otbr-agent -I wpan0 -B wlan0 spinel+hdlc+uart:///dev/ttyACM0 trel://wlan0 -v

otbr-agent[6151]: [NOTE]-AGENT---: Running 0.3.0-6e0cfbceec
otbr-agent[6151]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[6151]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[6151]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0
otbr-agent[6151]: [NOTE]-AGENT---: Radio URL: trel://wlan0
otbr-agent[6151]: [NOTE]-ILS-----: Infra link selected: wlan0
otbr-agent[6151]: [INFO]-NCP-----: OpenThread log level changed to 4
otbr-agent[6151]: 49d.17:20:20.325 [W] Platform------: Wait for response timeout
otbr-agent[6151]: 49d.17:20:20.326 [C] Platform------: HandleRcpTimeout() at radio_spinel_impl.hpp:2248: RadioSpinelNoResponse

And, here's the otbr-agent status: service otbr-agent status

otbr-agent.service - OpenThread Border Router Agent
Loaded: loaded (/lib/systemd/system/otbr-agent.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Mon 2022-12-12 01:10:20 CET; 3s ago
Process: 5969 ExecStartPre=service mdns start (code=exited, status=0/SUCCESS)
Process: 5985 ExecStart=/usr/sbin/otbr-agent $OTBR_AGENT_OPTS (code=exited, status=6)
Main PID: 5985 (code=exited, status=6)
CPU: 44ms

Hardware

  • Raspberry Pi 4 (4Gb)
  • nRF 52840 DK

Software

Does anybody have any idea what's going wrong? It's very odd since nRF 52840 Dongle works fine with the same sample template with the following build flag added.

-DOVERLAY_CONFIG="overlay-usb.conf" -DDTC_OVERLAY_FILE="usb.overlay"

Parents
  • Hi,

    If you supply power through PPK2 and have the nRF USB (J3) connected, that could potentially interfere with your PPK2 measurements yes.
    Guess you can try to see if you measure the same for another app with J3 vs J2.

    Let's look a bit more at the issue:

    When you plug your nRF52840DK into your PC, does it show up as a "JLINK" storage device?

    Regards,
    Sigurd Hellesvik

  • Sigurd Hellesvik said:
    When you plug your nRF52840DK into your PC, does it show up as a "JLINK" storage device?

    To clarify: Does this happen when you use J2?

    Md Mazedul Islam Khan said:
    But that's what I figured out after pulling my hair since the relevant doc doesn't show this for the Development Kit but show for the Dongle only.

    The dongle uses the USB driver of the nRF52840.
    This is the same that happens when you connect the nRF52840DK to the nRF USB (J3) connector. This is why these two behave in the same way.

    Since it works when you directly connect to the nRF USB, but not to the nRF via the Debugger, I suspect that something in the debugger is interfering here.
    This is why I ask about the "JLINK" storage device.

    Regards,
    Sigurd Hellesvik

Reply
  • Sigurd Hellesvik said:
    When you plug your nRF52840DK into your PC, does it show up as a "JLINK" storage device?

    To clarify: Does this happen when you use J2?

    Md Mazedul Islam Khan said:
    But that's what I figured out after pulling my hair since the relevant doc doesn't show this for the Development Kit but show for the Dongle only.

    The dongle uses the USB driver of the nRF52840.
    This is the same that happens when you connect the nRF52840DK to the nRF USB (J3) connector. This is why these two behave in the same way.

    Since it works when you directly connect to the nRF USB, but not to the nRF via the Debugger, I suspect that something in the debugger is interfering here.
    This is why I ask about the "JLINK" storage device.

    Regards,
    Sigurd Hellesvik

Children
Related