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

If you're not familiar with building with West, I would recommend using Visual Studio Code and its nRFConnect extension. It will let you use VS code as an IDE to build, program and debug your projects. When setting up I.E. the AoA beacon you get the choice to add the overlay-aoa.conf as a Kconfig fragment.

In my last reply I said you needed to add this Kconfig to both beacon and locator, but that's not the case (my bad). It should only be added to the beacon device.

Best regards,

Simon

[Jpittevils]

I tried using VS code but I get the exact same behavior as in my very first picture (receiver restarts after the waiting for periodic sync lost message).

I got my hands on two nrf52833dk's and for them, it worked out of the box. I will be using these kits from now on, but I would still appreciate any info on getting this thing to work on the nRF5340dk's.