direction_finding_connectionless_rx nRF5340dk rebooting after "Waiting for periodic sync lost..."

[Jpittevils]

I succesfully flashed both direction finding samples to two different nRF5340dk's, but the rx board keeps rebooting afer the "Waiting for periodic sync lost..." message, while the sample page says that the next output should be:

PER_ADV_SYNC[X]: [DEVICE]: XX:XX:XX:XX:XX:XX, tx_power XXX, RSSI XX, CTE XXX, data length X, data: XXX
CTE[X]: samples count XX, cte type XXX, slot durations: X [us], packet status XXX, RSSI XXX
"



any idea on why this is? It seems to me like this is stopping me from correctly reading out the IQ samples?

[Simonr]

Hi

Glad you got it working on your nRF52833 DKs at least.

In the GitHub documentation of Zephyr there are some information on what to configure to run the application on an nRF5340 DK.
https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/bluetooth/direction_finding_connectionless_rx 
https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/bluetooth/direction_finding_connectionless_tx 

Are you sure that you flash the Bluetooth controller onto the network core of the nRF5340 DKs here?

Best regards,

Simon

[Jpittevils]

yeah, the HCI_RPMSG child image gets uploaded correctly to the network core I think. At least the compiler shows no errors when building the child image and all the logged outputs while building point to it being built for the network core correctly.

Just out of curiosity/sanity check: did you already get it to work on the nRF5340dk's or are you just going on the available documentation? Because if you did actually get it to work then I'm sure I'm doing something wrong and I will continue to look for a solution.

[Jpittevils]

Also, Simon, I would like to thank you for your efforts in trying to figure this out. I really appreciate it