• State Not Answered
  • Replies 17 replies
  • Subscribers 26 subscribers
  • Views 1273 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 279354
Options
nRF5 SDK is not maintained anymore
More Info: Consider nRF Connect SDK for new designs

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

user108946

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?
Parents Reply
  • 0 in reply to user75734

    Hi Simon

    Sorry for that I locked my question by accident, I tried what you said but it didn't work. By the way, no matter how I moved two boards, the IQ data changed nothing. Then I found where nrf samples are, I followed this page, I found that I don't have to change any file, so I just run this code:

    G:\ncs_v1.7.1\ncs1.7.1\nrf\samples\bluetooth\direction_finding_connectionless_rx>west build -b nrf5340dk_nrf5340_cpuapp
    Build and flash succeeded, but output was wrong:

    This error is similar to this ticket's, so I found here. I'm not sure that I've added necessary child images on the network core, I just run one code and I think it worked well. Hope to get your reply.

    Best regards,

    Majoris

Children
Related
Terms of service