• State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Subscribers 87 subscribers
  • Views 1561 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 again

    Thank you for pointing out that the "Booting Zephyr" message overwrote the ASSERTION FAIL. I missed it because of that. Very sorry about that.

    So, after some debugging I found out that the CONFIG_BT_BUF_ACL_RX_COUNT and CONFIG_BT_BUF_ACL_RX_SIZE were too small for the length and caused this ASSERT when CONFIG_ASSERT=y in the connectionless_rx sample project. If you change these to the following values you should be out of harms way. I have also reported this internally, and we'll update the project in a future NCS release to fix this issue. Thank you again for reporting this to us!

    CONFIG_BT_BUF_ACL_RX_COUNT=10
    CONFIG_BT_BUF_ACL_RX_SIZE=200

    Best regards,

    Simon

Reply
  • 0

    Hi again

    Thank you for pointing out that the "Booting Zephyr" message overwrote the ASSERTION FAIL. I missed it because of that. Very sorry about that.

    So, after some debugging I found out that the CONFIG_BT_BUF_ACL_RX_COUNT and CONFIG_BT_BUF_ACL_RX_SIZE were too small for the length and caused this ASSERT when CONFIG_ASSERT=y in the connectionless_rx sample project. If you change these to the following values you should be out of harms way. I have also reported this internally, and we'll update the project in a future NCS release to fix this issue. Thank you again for reporting this to us!

    CONFIG_BT_BUF_ACL_RX_COUNT=10
    CONFIG_BT_BUF_ACL_RX_SIZE=200

    Best regards,

    Simon

Children
No Data
Related
Terms of service