• State Not Answered
  • Replies 8 replies
  • Subscribers 26 subscribers
  • Views 463 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 288435
Options

Direction finding beacon and 802.15.4 in the nRF5340

user115782

Hello,

Is it possible to enable the BLE direction finding beacon along with 802.15.4 in the nRF5340? I am using Nordic SDK version 1.9.1.

Thanks,

Mike

Parents
  • 0

    Hi Simon,

    Thank you for the speedy reply.

    I've taken the approach that you recommend. I started with the samples direction_finding_connectionless_tx and multiprotocol_rpmsg for the nRF5340 and combined the samples. However, I am encountering a hard fault on the application processor when I enable 802.15.4 on the nRF5340.

    Bluetooth initialization...ASSERTION FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:305
    *** Booting Zephyr OS build v2.7.99-ncs1-1 ***
    Starting Connectionless Beacon Demo
    Bluetooth initialization...

    I enable 802.15.4 on the network processor with these configurations in prj.conf:

    CONFIG_NRF_802154_SER_RADIO=y
    CONFIG_NRF_RTC_TIMER_USER_CHAN_COUNT=2
    I enable 802.15.4 on the application processor with this configuration in prj.conf:
    CONFIG_NRF_802154_SER_HOST=y
    It appears as if the application is timing out waiting for a network buffer in the application processor and triggering an ASSERT. 
    Thanks,
    Mike
Reply
  • 0

    Hi Simon,

    Thank you for the speedy reply.

    I've taken the approach that you recommend. I started with the samples direction_finding_connectionless_tx and multiprotocol_rpmsg for the nRF5340 and combined the samples. However, I am encountering a hard fault on the application processor when I enable 802.15.4 on the nRF5340.

    Bluetooth initialization...ASSERTION FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:305
    *** Booting Zephyr OS build v2.7.99-ncs1-1 ***
    Starting Connectionless Beacon Demo
    Bluetooth initialization...

    I enable 802.15.4 on the network processor with these configurations in prj.conf:

    CONFIG_NRF_802154_SER_RADIO=y
    CONFIG_NRF_RTC_TIMER_USER_CHAN_COUNT=2
    I enable 802.15.4 on the application processor with this configuration in prj.conf:
    CONFIG_NRF_802154_SER_HOST=y
    It appears as if the application is timing out waiting for a network buffer in the application processor and triggering an ASSERT. 
    Thanks,
    Mike
Children
No Data
Related
Terms of service