direction_finding_connectionless_rx只会一直打印[DRIVER]信息，在收到合适的蓝牙时，也不会进行CTE解析、捕获 My direction_finding_connectionless_rx keeps printing [DRIVER] messages continuously. Even when it receives a suitable Bluetooth packet, it does not perform CTE parsing or capture

[RZX]

我现在有两块调试板，一块是nRF5340DK，一块是nRF52833DK，我现在在nRF52833DK中烧录了direction_finding_connectionless_rx项目，它的地址是nrf\samples\bluetooth\direction_finding_connectionless_rx。在nRF5340中烧录了direction_finding_connectionless_tx项目。两个项目烧录完毕后，direction_finding_connectionless_rx通过串口打印了以下信息：
Bluetooth initialization...success

Scan callbacks register...success.

Periodic Advertising callbacks register...success.

Start scanning...success

[DEVICE]: 08:5E:C5:87:11:1E (random), AD evt type 3, Tx Pwr: 127, RSSI -86 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

[DEVICE]: 5E:0F:3B:46:29:1C (random), AD evt type 0, Tx Pwr: 127, RSSI -79 C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

[DEVICE]: 15:4C:30:43:DB:A2 (random), AD evt type 3, Tx Pwr: 127, RSSI -55 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

......

[DEVICE]: 34:A9:42:AA:EE:78 (random), AD evt type 5, Tx Pwr: 127, RSSI -47 DF Connectionless Beacon App C:0 S:0 D:0 SR:0 E:1 Prim: LE 1M, Secn: LE 2M, Interval: 0x0780 (2400 ms), SID: 0

[DEVICE]: 05:25:11:00:0D:00 (random), AD evt type 3, Tx Pwr: 127, RSSI -84 RH_YAA C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

......
[DEVICE]: 75:58:AC:2A:51:E3 (random), AD evt type 4, Tx Pwr: 127, RSSI -73 SJM C:1 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

[DEVICE]: 25:2D:13:35:CF:93 (random), AD evt type 3, Tx Pwr: 127, RSSI -64 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

[DEVICE]: 34:A9:42:AA:EE:78 (random), AD evt type 5, Tx Pwr: 127, RSSI -45 DF Connectionless Beacon App C:0 S:0 D:0 SR:0 E:1 Prim: LE 1M, Secn: LE 2M, Interval: 0x0780 (2400 ms), SID: 0

......

从调试信息可以看到，它确实监测到了DF Connectionless Beacon设备，但是从未开始进行CTE信息的解析。通过调试，我发现程序已经运行了以下代码：

        sync_create_timeout_ms =

            adv_interval_to_ms(info->interval) * SYNC_CREATE_TIMEOUT_INTERVAL_NUM;

        per_adv_found = true;

        per_sid = info->sid;

        bt_addr_le_copy(&per_addr, info->addr);

        k_sem_give(&sem_per_adv);

那么理论上应该运行以下代码：

err = k_sem_take(&sem_per_adv, K_FOREVER);

if (err) {

            printk("failed (err %d)\n", err);

            return 0;

        }

        printk("success. Found periodic advertising.\n");

但实际并未看到打印消息，似乎是k_sem_take未正确返回。我在 k_sem_give(&sem_per_adv); 函数后添加了休眠函数k_msleep(10000);

发现程序正常运行了以下代码：

err = k_sem_take(&sem_per_adv, K_FOREVER);

if (err) {

            printk("failed (err %d)\n", err);

            return 0;

        }

        printk("success. Found periodic advertising.\n");

调试信息如下：[2026-05-18T16:19:51.666] *** Booting nRF Connect SDK v3.3.0-ba167d9f3db4 ***

*** Using Zephyr OS v4.3.99-fd9

[2026-05-18T16:19:51.679] 204a02d52 ***

Starting Connectionless Locator Demo

Bluetooth initialization...success

Scan callbacks register...success.

P

[2026-05-18T16:19:51.690] eriodic Advertising callbacks register...success.

Start scanning...success

Waiting for periodic advertising...

[2026-05-18T16:19:51.703] [DEVICE]: 34:A9:42:AA:EE:78 (random), AD evt type 5, Tx Pwr: 127, RSSI -46 DF Connectionless Beac

[2026-05-18T16:19:51.715] on App C:0 S:0 D:0 SR:0 E:1 Prim: LE 1M, Secn: LE 2M, Interval: 0x0780 (2400 ms), SID: 0

success. Found periodic advertisi

[2026-05-18T16:19:51.729] ng.

Creating Periodic Advertising Sync...success.

Waiting for periodic sync...

[2026-05-18T16:20:01.721] [DEVICE]: 00:00:00:04:03:00 (random), AD evt type 3, Tx Pwr: 127, RSSI -79 RH_Y2 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M,

[2026-05-18T16:20:01.731] Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

[DEVICE]: 58:04:A1:04:30:E8 (random), AD evt type

[2026-05-18T16:20:01.741] 3, Tx Pwr: 127, RSSI -87 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

[2026-05-18T16:20:01.753]

[DEVICE]: 19:45:AA:3E:56:54 (random), AD evt type 3, Tx Pwr: 127, RSSI -83 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval

[2026-05-18T16:20:01.765] : 0x0000 (0 ms), SID: 255

[DEVICE]: 29:38:1C:B5:56:9A (random), AD evt type 3, Tx Pwr: 127, RSSI -78 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M,

 

我现在不知道该如何让这个示例项目正常运行。nRF Connect for VS Code版本：2026.4.1766

Translate：

I currently have two debug boards, one is nRF5340DK and the other is nRF52833DK. I have now programmed the direction_finding_connectionless_rx project into the nRF52833DK. Its address is nrf\samples\bluetooth\direction_finding_connectionless_rx. The direction_finding_connectionless_tx project was programmed into the nRF5340. After both projects were programmed, the direction_finding_connectionless_rx printed the following information through the serial port: Bluetooth initialization... success

Scan callbacks register... success.

Periodic Advertising callbacks register... success.

Start scanning... success

[DEVICE]: 08:5E:C5:87:11:1E (random), AD evt type 3, Tx Pwr: 127, RSSI -86 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

[DEVICE]: 5E:0F:3B:46:29:1C (random), AD evt type 0, Tx Pwr: 127, RSSI -79 C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

[DEVICE]: 15:4C:30:43:DB:A2 (random), AD evt type 3, Tx Pwr: 127, RSSI -55 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

......

[DEVICE]: 34:A9:42:AA:EE:78 (random), AD evt type 5, Tx Pwr: 127, RSSI -47 DF Connectionless Beacon App C:0 S:0 D:0 SR:0 E:1 Prim: LE 1M, Secn: LE 2M, Interval: 0x0780 (2400 ms), SID: 0

[DEVICE]: 05:25:11:00:0D:00 (random), AD evt type 3, Tx Pwr: 127, RSSI -84 RH_YAA C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

......
[DEVICE]: 75:58:AC:2A:51:E3 (random), AD evt type 4, Tx Pwr: 127, RSSI -73 SJM C:1 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

[DEVICE]: 25:2D:13:35:CF:93 (random), AD evt type 3, Tx Pwr: 127, RSSI -64 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

[DEVICE]: 34:A9:42:AA:EE:78 (random), AD evt type 5, Tx Pwr: 127, RSSI -45 DF Connectionless Beacon App C:0 S:0 D:0 SR:0 E:1 Prim: LE 1M, Secn: LE 2M, Interval: 0x0780 (2400 ms), SID: 0

......

From the debugging information, it can be seen that it did indeed detect the DF Connectionless Beacon device, but it never started to parse the CTE information. Through debugging, I found that the program has run the following code:
sync_create_timeout_ms =
adv_interval_to_ms(info->interval) * SYNC_CREATE_TIMEOUT_INTERVAL_NUM;
per_adv_found = true;
per_sid = info->sid;
bt_addr_le_copy(&per_addr, info->addr);

k_sem_give(&sem_per_adv);

Then, theoretically, the following code should be run: err = k_sem_take(&sem_per_adv, K_FOREVER);
if (err) {
printk("failed (err %d)\n", err);
return 0;
}
printk("success. Found periodic advertising.\n");

However, the print message was not actually seen. It seems that k_sem_take did not return correctly. I added a sleep function k_msleep(10000) after the k_sem_give(&sem_per_adv); function and found that the program ran normally with the following code:
err = k_sem_take(&sem_per_adv, K_FOREVER);
if (err) {
printk("failed (err %d)\n", err);
return 0;
}
printk("success. Found periodic advertising.\n");
Debug information as follows: [2026-05-18T16:19:51.666] *** Booting nRF Connect SDK v3.3.0-ba167d9f3db4 ***
*** Using Zephyr OS v4.3.99-fd9
[2026-05-18T16:19:51.679] 204a02d52 ***

[May 18, 2026, 16:19:51.679] 204a02d52 ***
Starting Connectionless Locator Demo

Bluetooth initialization... success

Scan callbacks register... success.

P

[2026-05-18T16:19:51.690] Periodic advertising callbacks registration... success.

Start scanning... success

Waiting for periodic advertising...

[2026-05-18T16:19:51.703] [DEVICE]: 34:A9:42:AA:EE:78 (random), AD evt type 5, Tx Pwr: 127, RSSI -46, DF Connectionless Beacon
[2026-05-18T16:19:51.715] on App C:0 S:0 D:0 SR:0 E:1 Prim: LE 1M, Secn: LE 2M, Interval: 0x0780 (2400 ms), SID: 0
success. Found periodic advertisi

[2026-05-18T16:19:51.729] ng.

（由于原文中“ng.”没有明确的含义，所以直接保留原样。）
Creating Periodic Advertising Sync... success.

Waiting for periodic sync...

[2026-05-18T16:20:01.721] [DEVICE]: 00:00:00:04:03:00 (random), AD event type 3, Tx Power: 127, RSSI -79 RH_Y2 C:0 S:0 D:0 SR:0 E:0 Primary: LE 1M,
[2026-05-18T16:20:01.731] Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 58:04:A1:04:30:E8 (random), AD evt type

[2026-05-18T16:20:01.741] 3, Tx Pwr: 127, RSSI -87 C:0 S:0 D:0 SR:0 E:0 Primary: LE 1M, Secondary: No packets, Interval: 0x0000 (0 ms), SID: 255

[May 18, 2026 4:20:01 PM]
[DEVICE]: 19:45:AA:3E:56:54 (random), AD evt type 3, Tx Pwr: 127, RSSI -83 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval

[2026-05-18T16:20:01.765] : 0x0000 (0 ms), SID: 255
[DEVICE]: 29:38:1C:B5:56:9A (random), AD evt type 3, Tx Pwr: 127, RSSI -78 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M,

I currently have no idea how to get this sample project running properly. nRF Connect for VS Code version: 2026.4.1766

我希望能够使用中文来进行沟通，不过英文我这里也可以进行翻译来理解。

[Elfving]

Hi,

So these are the completely default samples from the NCS SDK? 

Are you using an antenna matrix too? 

Regards,

Elfving

[RZX]

你好，我使用的是16阵源天线矩阵，使用的是官方示例，使用的是NCS SDK3.3版本。
Hello, I'm using a 16-element antenna array with the official example and NCS SDK version 3.3.

[Elfving]

Understood. That is what I use as well. And you have connected the antenna array to the rx/locator device using the SWF antenna connector?

What you are seeing here is similar to what I see when I haven't connected the antenna to the DK, so that is my first assumption as to what is wrong here. Another problem, though, could be whether the right configuration is used on the 5340, although I think this should happen automatically.

RZX said:

Could it be that there are too many Bluetooth devices around?

Theoretically, it could be, though that is typically not a problem.

Regards,

Elfving

[RZX]

My current solution is to add the following code:

if (!per_adv_found && info->interval != 0) {

        sync_create_timeout = sync_create_timeout_get(info->interval);

        per_adv_found = true;

        per_sid = info->sid;

        bt_addr_le_copy(&per_addr, info->addr);

        (void)bt_le_scan_stop();

        scan_enabled = false;

        k_sem_give(&sem_per_adv);

        per_adv_found = false;

    }


I let it actively pause the thread, which allows me to output IQ data and complete one-to-one CTE data parsing.
After making such modifications, I believe it is a problem related to thread priority. I wonder if my analysis is correct.
Currently, I am using the 5340DK device as the transmitter and the 52833DK as the receiver.

[Elfving]

I just tried this with the same boards and NCS version you are using. I see now that the antenna matrix I happen to use has 12 patches - although that shouldn't matter much.

With the completely default samples, this is what I am seeing on the rx side.

*** Booting nRF Connect SDK v3.3.0-ba167d9f3db4 ***
*** Using Zephyr OS v4.3.99-fd9204a02d52 ***
Starting Connectionless Locator Demo
Bluetooth initialization...success
Scan callbacks register...success.
Periodic Advertising callbacks register...success.
Start scanning...success
Waiting for periodic[DEVICE]: 2C:05:B8:08:E8:B6 (random), AD evt type 3, Tx Pwr: 127, RSSI -78  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 72:81:10:54:C5:D7 (random), AD evt type 0, Tx Pwr: 127, RSSI -78  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 46:FB:73:B3:01:2B (random), AD evt type 2, Tx Pwr: 127, RSSI -75  C:0 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 14:53:B8:4E:99:FD (random), AD evt type 3, Tx Pwr: 127, RSSI -76  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
 advertising...
[DEVICE]: 35:2C:A8:E9:08:D1 (random), AD evt type 3, Tx Pwr: 127, RSSI -86  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 52:DD:C0:7B:E3:C5 (random), AD evt type 0, Tx Pwr: 127, RSSI -71 LE_WH-1000XM5 C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 52:DD:C0:7B:E3:C5 (random), AD evt type 4, Tx Pwr: 127, RSSI -70  C:1 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 2A:9E:8C:4D:05:0B (random), AD evt type 5, Tx Pwr: 127, RSSI -67 DF Connectionless Beacon App C:0 S:0 D:0 SR:0 E:1 Prim: LE 1M, Secn: LE 2M, Interval: 0x0780 (2400 ms), SID: 0
success. Found periodic advertising.
Creating Periodic Advertising Sync...success.
Waiting for periodic sync...
[DEVICE]: 0D:FE:90:F0:F4:04 (random), AD evt type 3, Tx Pwr: 127, RSSI -85  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 54:0D:FE:3B:49:75 (random), AD evt type 0, Tx Pwr: 127, RSSI -60  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 54:0D:FE:3B:49:75 (random), AD evt type 4, Tx Pwr: 127, RSSI -60  C:1 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 09:45:5B:AF:69:EC (random), AD evt type 3, Tx Pwr: 127, RSSI -77  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 66:95:52:45:AD:D5 (random), AD evt type 0, Tx Pwr: 127, RSSI -77  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 66:95:52:45:AD:D5 (random), AD evt type 4, Tx Pwr: 127, RSSI -77  C:1 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 5E:D4:3F:BC:A5:4E (random), AD evt type 0, Tx Pwr: 127, RSSI -88  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 5E:D4:3F:BC:A5:4E (random), AD evt type 4, Tx Pwr: 127, RSSI -87  C:1 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 10:B5:02:16:0F:63 (random), AD evt type 0, Tx Pwr: 127, RSSI -90  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 7C:1A:48:95:50:9D (random), AD evt type 3, Tx Pwr: 127, RSSI -77  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 05:BC:AE:5B:AC:DF (random), AD evt type 0, Tx Pwr: 127, RSSI -91  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 60:D5:F7:7D:2E:C0 (random), AD evt type 0, Tx Pwr: 127, RSSI -85  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 60:D5:F7:7D:2E:C0 (random), AD evt type 4, Tx Pwr: 127, RSSI -83  C:1 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 15:A7:79:BC:3A:8F (random), AD evt type 3, Tx Pwr: 127, RSSI -91  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 2C:05:B8:08:E8:B6 (random), AD evt type 3, Tx Pwr: 127, RSSI -81  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 64:9E:7F:1B:B5:05 (random), AD evt type 0, Tx Pwr: 127, RSSI -81 Jabra Evolve2 65 C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: EB:EA:A1:4D:E6:72 (random), AD evt type 0, Tx Pwr: 127, RSSI -89  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 2C:B4:9A:8F:1A:82 (random), AD evt type 3, Tx Pwr: 127, RSSI -90  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 14:53:B8:4E:99:FD (random), AD evt type 3, Tx Pwr: 127, RSSI -73  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: CC:9D:50:3B:B9:A7 (random), AD evt type 0, Tx Pwr: 127, RSSI -77  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 2A:9E:8C:4D:05:0B (random), AD evt type 5, Tx Pwr: 127, RSSI -65 DF Connectionless Beacon App C:0 S:0 D:0 SR:0 E:1 Prim: LE 1M, Secn: LE 2M, Interval: 0x0780 (2400 ms), SID: 0
[DEVICE]: 0D:FE:90:F0:F4:04 (random), AD evt type 3, Tx Pwr: 127, RSSI -86  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 72:81:10:54:C5:D7 (random), AD evt type 0, Tx Pwr: 127, RSSI -80  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 72:81:10:54:C5:D7 (random), AD evt type 4, Tx Pwr: 127, RSSI -80  C:1 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 09:45:5B:AF:69:EC (random), AD evt type 3, Tx Pwr: 127, RSSI -76  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: EB:EA:A1:4D:E6:72 (random), AD evt type 4, Tx Pwr: 127, RSSI -89 Seos C:1 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 52:DD:C0:7B:E3:C5 (random), AD evt type 0, Tx Pwr: 127, RSSI -61 LE_WH-1000XM5 C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 54:0D:FE:3B:49:75 (random), AD evt type 0, Tx Pwr: 127, RSSI -60  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 54:0D:FE:3B:49:75 (random), AD evt type 4, Tx Pwr: 127, RSSI -59  C:1 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 35:2C:A8:E9:08:D1 (random), AD evt type 3, Tx Pwr: 127, RSSI -89  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 52:DD:C0:7B:E3:C5 (random), AD evt type 4, Tx Pwr: 127, RSSI -60  C:1 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 66:95:52:45:AD:D5 (random), AD evt type 0, Tx Pwr: 127, RSSI -81  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 66:95:52:45:AD:D5 (random), AD evt type 4, Tx Pwr: 127, RSSI -81  C:1 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 46:FB:73:B3:01:2B (random), AD evt type 2, Tx Pwr: 127, RSSI -78  C:0 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 5E:D4:3F:BC:A5:4E (random), AD evt type 0, Tx Pwr: 127, RSSI -92  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: D4:8D:61:F3:D3:D4 (random), AD evt type 0, Tx Pwr: 127, RSSI -84  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 2C:05:B8:08:E8:B6 (random), AD evt type 3, Tx Pwr: 127, RSSI -82  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 7C:1A:48:95:50:9D (random), AD evt type 3, Tx Pwr: 127, RSSI -79  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: C3:F9:EA:7C:BA:D7 (random), AD evt type 3, Tx Pwr: 127, RSSI -90  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 2C:B4:9A:8F:1A:82 (random), AD evt type 3, Tx Pwr: 127, RSSI -88  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
PER_ADV_SYNC[0]: [DEVICE]: 2A:9E:8C:4D:05:0B (random) synced, Interval 0x0780 (2400 ms), PHY LE 2M
success. Periodic sync established.
Enable receiving of CTE...
success. CTE receive enabled.
Scan disable...Success.
Waiting for periodic sync lost...
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -630
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -630
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -630
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -630
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -630
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -660
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -660
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -660
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -670
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -670
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -600
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -600
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -600
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -600
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -600
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -640
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -640
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -640
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -640
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -640
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -590
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -590
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -590
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -590
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -590
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -620
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -610
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -620
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -620
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -610
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -650
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -650
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -650
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -650
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -650
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -600
CTE[0]: samples count 45, cte type AOA, slot durations: 2 [us], packet status CRC OK, RSSI -600

Without the antenna connected, I am just getting this:

*** Using Zephyr OS v4.3.99-fd9204a02d52 ***
Starting Connectionless Locator Demo
Bluetooth initialization...success
Scan callbacks register...success.
Periodic Advertising callbacks register...success.
Start scanning...success
Waiting for periodic advertis[DEVICE]: 2B:69:7E:E5:F3:F6 (random), AD evt type 0, Tx Pwr: 127, RSSI -70  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 2B:3F:F0:52:6D:7E (random), AD evt type 3, Tx Pwr: 127, RSSI -57  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 04:CB:01:EB:39:F2 (public), AD evt type 3, Tx Pwr: 127, RSSI -88  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 2F:DC:9A:9B:0F:15 (random), AD evt type 3, Tx Pwr: 127, RSSI -77  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: E7:BF:12:4C:A0:2D (random), AD evt type 0, Tx Pwr: 127, RSSI -83  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 63:02:0A:62:4B:20 (random), AD evt type

I assumed that was your issue too. How are you connecting the antenna? What connector are you using?

Regards,

Elfving

[RZX]

I used a 16-array antenna. The connection method can be seen from my environment.
There should be no problem with my antenna connections. The antenna switching pins of them are connected to the P0.03, P0.04, P0.28, and P0.29 pins.

[Elfving]

That does look correct. On my side I see I am getting CTEs logged by just having the SWF connected, so this should be more than good enough. Atleast if you feel the SWF snap into place.

Are you seeing the same thing with these hex files? Just to make sure that there is nothing wrong with the SDK you have downloaded,  and that you are in fact using the right samples (not the ones requiring connection, or the ones from zephyr for instance).

merged_nrf5340dk_nrf5340_cpunet.hexmerged_nrf5340dk_nrf5340_cpuapp.hex53822dk_df_rx.hex

Regards,

Elfving

[RZX]

I am sending you the current case I am using. In this case, I only added the aforementioned code.           (void)bt_le_scan_stop();
   scan_enabled = false;
   k_sem_give(&sem_per_adv);direction_finding_connectionless_rx_5.zip
   per_adv_found = false;

And it has been modified to a 16-array antenna.

[RZX]

I noticed that all the files you sent me were ".hex" files. Could you please send me the entire project?