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

[Simonr]

Hi again

I don't see an assertion fail in the log you posted in your last reply, are you sure this is the complete log? Can you also confirm that you're setting CONFIG_ASSERT=y in the prj.conf file located in ...\NCS v1.x.x\nrf\samples\bluetooth\direction_finding_connectionless_rx\prj.conf?

Best regards,

Simon

[jakkra]

So I picked a new computer, installed nrfconnect, toolchain manager etc. and ncs version 1.6.1. My only modification is adding CONFIG_ASSERT=y in this folder: NrfConnect\v1.6.1\nrf\samples\bluetooth\direction_finding_connectionless_rx

Compiling with:

Transmitter:

west build -p -b nrf52833dk_nrf52833 -- -DOVERLAY_CONFIG=overlay-aoa.conf -DTC_OVERLAY_FILE=boards/nrf52833dk_nrf52833.overlay

west flash

Receiver:

west build -p -b nrf52833dk_nrf52833 -- -DTC_OVERLAY_FILE=boards/nrf52833dk_nrf52833.overlay

west flash

I have uploaded the log from receiver. You can see it crashing over and over again with error: 

ASSERTION FAIL [net_buf_simple_tailroom(buf) >= len] @ WEST_TOPDIR/zephyr/subsys/net/buf.c:800

I'm using two nRF52833-DK without any antenna connected (just PCB antenna)

putty.log