OpenThread crashes on 5340

Basic OpenThread application built for 5340 crashes in net app.

The same application works fine on 21540 (52840 + 21540)

The crash seems to happen when some thread packet is received. If I turn off all other thread transmitters, the crash doesn't happen.

Details:

I: [N] Mle-----------: Role detached -> child
I:   Local IPv6 = Origin:SLACC * fd11:22:0:0:8f99:b944:f28f:617b
E: No response within timeout 500
ASSERTION FAIL @ WEST_TOPDIR/zephyr/drivers/ieee802154/ieee802154_nrf5.c:1149
    802.15.4 serialization error
E: r0/a1:  0x00000004  r1/a2:  0x0000047d  r2/a3:  0x00000001
E: r3/a4:  0x00011cc9 r12/ip:  0xa0000000 r14/lr:  0x000180af
E:  xpsr:  0x41000000
E: Faulting instruction address (r15/pc): 0x00058b1e
E: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
E: Current thread: 0x200035b8 (openthread)
E: Resetting

Parents
  • Started with an OpenThread sample but have made a lot of changes.  Doesn't seem to matter what the config is (I have taken everything out beside openthread with the same results).  Sometimes it works for a bit, but mostly it gets in to this crash loop eventually.

    Sending spinel frame
        data: 0x80 0x03 0x8d 0x78 0x43 0x98
        data_address: 0x20029af0
    Received spinel frame
        data: 0x80 0x06 0x00 0x00
        data_address: 0x20070814
    Received response for status_ok_await
        status: OK
    Calling nrf_802154_ack_data_clear
        p_addr: 0x00 0x98
        p_addr_address: 0x20029bf4
        extended: false
    Sending spinel frame
        data: 0x80 0x03 0xa1 0x78 0x02 0x00 0x00 0x98 0x01
        data_address: 0x20029a78
    Received spinel frame
        data: 0x80 0x06 0xa1 0x78 0x00
        data_address: 0x20070a14
    Received response for net_generic_bool_response_await
        net response: false
    Calling nrf_802154_ack_data_clear
        p_addr: 0xd4 0xb6 0x3e 0x7b 0xe4 0xa0 0xd5 0xca
        p_addr_address: 0x20029bf8
        extended: true
    Sending spinel frame
        data: 0x80 0x03 0xa1 0x78 0x08 0x00 0xd4 0xb6 0x3e 0x7b 0xe4 0xa0 0xd5 0xca 0x01
        data_address: 0x20029a78
    Received spinel frame
        data: 0x80 0x06 0xa1 0x78 0x00
        data_address: 0x20070c14
    Received response for net_generic_bool_response_await
        net response: false
    Calling nrf_802154_receive_at_cancel
    Sending spinel frame
        data: 0x80 0x03 0xa8 0x78 0x00 0x00 0x00 0x00
        data_address: 0x20029a90
    Received spinel frame
        data: 0x80 0x06 0xa8 0x78 0x00
        data_address: 0x20070e14
    Received response for net_generic_bool_response_await
        net response: false
    Calling nrf_802154_receive_at_cancel
    Sending spinel frame
        data: 0x80 0x03 0xa8 0x78 0x01 0x00 0x00 0x00
        data_address: 0x20029a90
    Received spinel frame
        data: 0x80 0x06 0xa8 0x78 0x00
        data_address: 0x20071014
    Received response for net_generic_bool_response_await
        net response: false
    Calling nrf_802154_csl_writer_period_set
    Sending spinel frame
        data: 0x80 0x03 0xac 0x78 0x00 0x00
        data_address: 0x20029a90
    E: No response within timeout 500
    ASSERTION FAIL @ WEST_TOPDIR/zephyr/drivers/ieee802154/ieee802154_nrf5.c:1149
        802.15.4 serialization error
    E: r0/a1:  0x00000004  r1/a2:  0x0000047d  r2/a3:  0x00000001
    E: r3/a4:  0x00011e61 r12/ip:  0xa0000000 r14/lr:  0x0001960f
    E:  xpsr:  0x41000000
    E: Faulting instruction address (r15/pc): 0x00055d58
    E: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
    E: Current thread: 0x

  • Hi,

    Which version of nRF Connect SDK are you using? How are you building and programming the application?

    Best regards,

    Marte

  • 2.0.1.  Using regular west build and west flash methods

  • Hi,

    Are you running a custom application on the network core as well, or are you running the nRF IEEE 802.15.4: Serialization RPMsg sample?

    Best regards,

    Marte

  • I am running out of the box code on the network core.. whatever the openthread sample app builds

  • Hi,

    Can you check if you see the same behavior in nRF Connect SDK v2.1.1?

    Best regards,

    Marte

Reply Children
No Data
Related