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

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

Simonr — Mon, 20 Dec 2021 08:29:04 GMT

Please check out the answers/suggestions by Saleh in this ticket for details on how to configure the direction finding project to work as intended on an nRF5340 DK.

Best regards,

Simon

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

Jpittevils — Fri, 17 Dec 2021 11:00:00 GMT

I did the copying of the overlay and conf file to the hci_rpmsg sample but I still have the exact same issue. Did you get the direction_finding_rx sample to work on a nrf53 development board Simonr?

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

Majoris — Thu, 09 Dec 2021 13:24:19 GMT

Do you solve this problem on nrf5340? I met the same problem when receiving, thank you.

Best regards,

Majoris

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

Simonr — Mon, 06 Dec 2021 08:52:01 GMT

We'll follow up this in your latest ticket instead of this one. But what I describe here should be sufficient to add the following to your nRF53 locator project.

Best regards,

Simon

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

Majoris — Tue, 30 Nov 2021 16:41:15 GMT

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:

devzone.nordicsemi.com/.../6457.df_5F00_rx.log

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

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

Simonr — Mon, 22 Nov 2021 08:16:11 GMT

Okay, so after some testing on my end I think I found the issue. By default, the direction finding connectionless RX project does not have board and overlay files for the nRF53 DK by default, and these need to be added to your locator project. Please note that this overlay will be part of the network core of the nRF5340, so the overlay file should be stored in /samples/bluetooth/hci_rpmsg/boards/nrf5340dk_nrf5340_cpunet.overlay instead of on the application core.

It should be sufficient to do the following:

Copy :zephyr_file:`samples/bluetooth/direction_finding_connectionless_rx/boards/nrf52833dk_nrf52833.overlay` to a new file, :file:`samples/bluetooth/hci_rpmsg/boards/nrf5340dk_nrf5340_cpunet.overlay`.
Copy :zephyr_file:`samples/bluetooth/direction_finding_connectionless_rx/boards/nrf52833dk_nrf52833.conf` to a new file, :file:`samples/bluetooth/hci_rpmsg/boards/nrf5340dk_nrf5340_cpunet.conf`. Add the line CONFIG_BT_EXT_ADV=y to enable extended size of :kconfig:`CONFIG_BT_BUF_CMD_TX_SIZE` to support the LE Set Extended Advertising Data command.

The beacon device works as intended by default, as using an nRF52833 locator is able to read the advertising data from an nRF5340 beacon.

Best regards,

Simon

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

Jpittevils — Thu, 18 Nov 2021 14:39:25 GMT

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

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

Jpittevils — Thu, 18 Nov 2021 14:26:17 GMT

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.

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

Simonr — Thu, 18 Nov 2021 14:11:13 GMT

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

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

Jpittevils — Thu, 18 Nov 2021 08:52:24 GMT

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.

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

Simonr — Tue, 16 Nov 2021 11:55:31 GMT

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

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

Jpittevils — Mon, 15 Nov 2021 11:38:38 GMT

I downloaded it using the Toolchain manager app. The child images are added automatically I think, but I think I am wrongly building with the overlay-aoa.conf Kconfig enabled. I first added the contents from overlay-aod.conf to /child_image/hci_rpmsg.conf and then I try to build with

west build -b nrf5340dk_nrf5340_cpuapp -- -Dhci_rpmsg_CONF_FILE=hci_rpmsg.conf

but this does not work.

Could you give me the correct command for building the sample projects for the nrf5340dk? I'm having difficulties understanding how to correctly add the Kconfig files to the child image and the project and I think that's where my issues come from.

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

Simonr — Thu, 11 Nov 2021 10:16:59 GMT

Do you build with the overlay-aoa.conf Kconfig enabled in both cases, and have you added the necessary child images mentioned in the documentation to run the Bluetooth LE controller on the network core, etc.? It should indeed work using West. Have you downloaded the nRFConnect SDK using the Toolchain manager app or manually?

Best regards,

Simon

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

Jpittevils — Wed, 10 Nov 2021 13:46:33 GMT

Yeah, I was hoping to get useless data from the beacon. Both the beacon and locator are PCA10095 1.0.0 kits. I still did not get it to work.

To recreate the issue, as maybe something is wrong with this?:

west build -b nrf5340dk_nrf5340_cpuapp nrf/samples/bluetooth/direction_finding_connectionless_rx --pristine

west flash --erase

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

Simonr — Wed, 10 Nov 2021 13:25:56 GMT

Well, you won't be able to read out any useful IQ samples with the default antenna, but I you should be able to get data (that would be useless), from the beacon. Are both beacon and receiver nRF5340 DKs? Can you post what version of the DKs you're working with (what it says below PCA10095 on the sticker)?

For more information on an antenna array, please contact the regional sales manager of your area. If you don't know who this is or need help getting in touch either fill in our sales related questions form here, or let me know and I'll help you get in touch.

Best regards,

Simon

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

Jpittevils — Tue, 09 Nov 2021 13:55:32 GMT

Hi, I do not currently have an antenna array connected, I wanted to make sure the software compiles and everything works before buying extra hardware. In the readmse.rst file it mentions a nordic designed 12-patch antenna array, is this up for sale somewhere?

Is it possible to test if the software is working as intended before buying this extra antenna patch?

thank you very much

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

Simonr — Tue, 09 Nov 2021 13:07:38 GMT

Do you have an antenna array connected to your nRF5340DK? To make sure everything is configured correctly, please also read through the README.rst file that is located under C:\...\ncs\v1.7.0\nrf\samples\bluetooth\direction_finding_connectionless_rx. I'm assuming this is due to bad sensitiviry either in the receiver or transmitter on your end.

Best regards,

Simon