• State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Subscribers 87 subscribers
  • Views 1565 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 276276
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

direction_finding_connectionless_rx crashes if CONFIG_ASSERT=y

jakkra

If I enable CONFIG_ASSERT=y this example will crash (or code using the DF APIs)

To reproduce:

- nRF Connect 1.6.1

- In direction_finding_connectionless_rx add CONFIG_ASSERT=y to the prj.conf

- Build direction_finding_connectionless_rx and direction_finding_connectionless_tx

- Flash and run, then you will see the log below on the device running direction_finding_connectionless_rx

Log from the example:

Enable receiving of CTE...
success. CTE receive enabled.
Scan disable...Success.
Waiting for periodic sync lost...
PER_ADV_SYNC[0]: [DEVICE]: 30:A0:F1:E2:87:5D (random), tx_power 127, RSSI -58, CTE AOA, data length 0, data:
ASSERTION FAIL [0] @ WEST_TOPDIR/zephyr/subsys/net/buf.c:800

Parents
  • 0

    Hi

    I tried this on my end and did not run into an assertion fail like this. Are you running the RX and TX examle projects on nRF52833 DKs or custom boards? Is the RX device connected to an antenna array or is it just using a single antenna?

    Best regards,

    Simon

  • 0 in reply to Simonr

    Hi thanks for input, at first I useed our custom board with our antenna, however after your reply I also tried rebuilding and re-flashing the RX code on a nRF52833 DK without antenna array, so nRF52833 DK using only single PCB antenna and I get the same crash. I verified that I have no diff in the sdk except:

    ...DF/v1.6.1/zephyr/samples/bluetooth/direction_finding_connectionless_rx ((v2.6.0-rc1-ncs1))
    $ git diff
    diff --git a/samples/bluetooth/direction_finding_connectionless_rx/prj.conf b/samples/bluetooth/direction_finding_connectionless_rx/prj.conf
    index 6de448fa5a..2761c58a9f 100644
    --- a/samples/bluetooth/direction_finding_connectionless_rx/prj.conf
    +++ b/samples/bluetooth/direction_finding_connectionless_rx/prj.conf
    @@ -10,3 +10,4 @@ CONFIG_BT_OBSERVER=y
    # Enable Direction Finding Feature including AoA and AoD
    CONFIG_BT_DF=y
    CONFIG_BT_DF_CONNECTIONLESS_CTE_RX=y
    +CONFIG_ASSERT=y
    \ No newline at end of file

    I'll try to find another nRF52833 DK so that I can flash the transmitter code on that and not use our custom board for TX also if that makes a difference.

Reply
  • 0 in reply to Simonr

    Hi thanks for input, at first I useed our custom board with our antenna, however after your reply I also tried rebuilding and re-flashing the RX code on a nRF52833 DK without antenna array, so nRF52833 DK using only single PCB antenna and I get the same crash. I verified that I have no diff in the sdk except:

    ...DF/v1.6.1/zephyr/samples/bluetooth/direction_finding_connectionless_rx ((v2.6.0-rc1-ncs1))
    $ git diff
    diff --git a/samples/bluetooth/direction_finding_connectionless_rx/prj.conf b/samples/bluetooth/direction_finding_connectionless_rx/prj.conf
    index 6de448fa5a..2761c58a9f 100644
    --- a/samples/bluetooth/direction_finding_connectionless_rx/prj.conf
    +++ b/samples/bluetooth/direction_finding_connectionless_rx/prj.conf
    @@ -10,3 +10,4 @@ CONFIG_BT_OBSERVER=y
    # Enable Direction Finding Feature including AoA and AoD
    CONFIG_BT_DF=y
    CONFIG_BT_DF_CONNECTIONLESS_CTE_RX=y
    +CONFIG_ASSERT=y
    \ No newline at end of file

    I'll try to find another nRF52833 DK so that I can flash the transmitter code on that and not use our custom board for TX also if that makes a difference.

Children
No Data
Related
Terms of service