periodic_sync_rsp error code pawr

RE: periodic_sync_rsp error code pawr

tesc — Mon, 24 Feb 2025 09:01:11 GMT

Hi,

That easily explains the issues you were seeing. Thanks for sharing the solution!

Regards,
Terje

RE: periodic_sync_rsp error code pawr

DanisXZ — Sun, 23 Feb 2025 18:53:56 GMT

I think the issue was one of the boards. I changed the board and it is working now. Thanks

RE: periodic_sync_rsp error code pawr

tesc — Fri, 21 Feb 2025 15:52:11 GMT

Hi,

Did you make it work?

I have tested the samples on my desk, using an nRF52833 DK and an nRF52840 DK, and everything seems fine here. I was using zephyr\samples\bluetooth\periodic_adv_rsp on the nRF52840 DK and zephyr\samples\bluetooth\periodic_sync_rsp on the nRF52833 DK, from nRF Connect SDK v2.9.0.

Please check and make sure that when you made the build configuration, you selected the correct board (nrf52840dk/nrf52840 for one sample, and nrf52dk/nrf52832 for the other, if those are the DKs that you use.) Also make sure that you program the correct sample on the correct board.

Also, as mentioned by Jakob Ruhe, have you tested a simpler sample, such as a basic BLE sample, to confirm that the board is fully functional, including the radio? E.g. the Bluetooth: Peripheral LBS sample on the board, and use either nRF Connect for Desktop with the BLE app, or the nRF Connect smartphone app, to connect to it and confirm the connection works.

Regards,
Terje

RE: periodic_sync_rsp error code pawr

Jakob Ruhe — Wed, 19 Feb 2025 10:24:04 GMT

I see. Strange.

The warning from bt_hci_core happens because the periodic_adv_sync example is a bit broken. It times out after 10 seconds and then tries to start advertising when one is already active.

To get rid of that warning, consider changing the timeout when waiting for periodic sync from 10 seconds to K_FOREVER instead.

But it should work anyway. I have tested it on two nRF52840DKs here.

Have you verified that the two boards you have can communicate using some other examples? Perhaps try to exchange the roles of the two boards you have. Or change to other boards if you have any other. Just to rule out such basic things. I am afraid I have no more advice to give from the top of my head right now.

RE: periodic_sync_rsp error code pawr

DanisXZ — Tue, 18 Feb 2025 22:03:02 GMT

Updated, still the same

*** Booting nRF Connect SDK v2.9.0-7787b2649840 ***
*** Using Zephyr OS v3.7.99-1f8f3dc29142 ***
Starting Periodic Advertising with Responses Synchronization Demo
[00:00:01.919,250] <inf> bt_sdc_hci_driver: SoftDevice Controller build revision: 
                                            2d 79 a1 c8 6a 40 b7 3c  f6 74 f9 0b 22 d3 c4 80 |-y..j@.< .t.."...
                                            74 72 82 ba                                      |tr..             
[00:00:01.922,058] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:01.922,058] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:01.922,088] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 45.41337 Build 3074452168
[00:00:01.923,126] <inf> bt_hci_core: Identity: C4:C1:82:92:F3:CA (random)
[00:00:01.923,156] <inf> bt_hci_core: HCI: version 6.0 (0x0e) revision 0x106b, manufacturer 0x0059
[00:00:01.923,187] <inf> bt_hci_core: LMP: version 6.0 (0x0e) subver 0x106b
Waiting for periodic sync...
Timed out while synchronizing
Waiting for periodic sync...
Timed out while synchronizing
[00:00:21.925,292] <wrn> bt_hci_core: opcode 0x2036 status 0x0c 
Advertising failed to start (err -13)

*** Booting nRF Connect SDK v2.9.0-7787b2649840 ***
*** Using Zephyr OS v3.7.99-1f8f3dc29142 ***
Starting Periodic Advertising Demo
[00:00:11.572,509] <inf> bt_sdc_hci_driver: SoftDevice Controller build revision: 
                                            2d 79 a1 c8 6a 40 b7 3c  f6 74 f9 0b 22 d3 c4 80 |-y..j@.< .t.."...
                                            74 72 82 ba                                      |tr..             
[00:00:11.575,347] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:11.575,378] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:11.575,408] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 45.41337 Build 3074452168
[00:00:11.576,446] <inf> bt_hci_core: Identity: F5:77:91:DE:B5:65 (random)
[00:00:11.576,477] <inf> bt_hci_core: HCI: version 6.0 (0x0e) revision 0x106b, manufacturer 0x0059
[00:00:11.576,507] <inf> bt_hci_core: LMP: version 6.0 (0x0e) subver 0x106b
Start Periodic Advertising
Scanning successfully started
Subevent data set 3
Subevent data set 5
Subevent data set 8
Subevent data set 10
Subevent data set 13
Subevent data set 15
Subevent data set 18

RE: periodic_sync_rsp error code pawr

Jakob Ruhe — Tue, 18 Feb 2025 21:05:49 GMT

I see. Confusing indeed. Then I would suggest you to upgrade from nRF Connect SDK 2.7.0 rc3 to 2.9.0. A lot of updates have been introduced since the summer.

RE: periodic_sync_rsp error code pawr

DanisXZ — Tue, 18 Feb 2025 20:35:13 GMT

Hi tesc and Jakob Ruhe ,

Thank you for your replies. Sorry, that was a typo in my post - I actually flashed periodic_adv_rsp and not periodic_adv. I have now updated my post.

On the advertising side, the output is as shown below:

*** Booting nRF Connect SDK v2.7.0-rc3-cb7b6efdf17a ***
*** Using Zephyr OS v3.6.99-3e80418dd59f ***
Starting Periodic Advertising Demo
[00:00:01.449,798] <inf> bt_sdc_hci_driver: SoftDevice Controller build revision: 
                                            d6 da c7 ae 08 db 72 6f  2a a3 26 49 2a 4d a8 b3 |......ro *.&I*M..
                                            98 0e 07 7f                                      |....             
[00:00:01.452,667] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:01.452,697] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:01.452,728] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 214.51162 Build 1926957230
[00:00:01.453,674] <inf> bt_hci_core: Identity: C4:C1:82:92:F3:CA (random)
[00:00:01.453,704] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x11fb, manufacturer 0x0059
[00:00:01.453,735] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x11fb
Start Periodic Advertising
Scanning successfully started
Subevent data set 3
Subevent data set 5
Subevent data set 8
Subevent data set 10
Subevent data set 13
Subevent data set 15
Subevent data set 18

I am using the examples as it is, I have not edited anything

RE: periodic_sync_rsp error code pawr

tesc — Mon, 17 Feb 2025 15:22:57 GMT

Hi,

The log message indicates that the PAwR Synchronization device did not find any PAwR Advertiser to synchronize to. Please note that in order for the samples to work as intended, those two samples are the ones to pair up. While there are samples for other types of periodic advertising (without responses), those are note expected to work with the periodic advertising with responses samples.

Regards,
Terje

RE: periodic_sync_rsp error code pawr

Jakob Ruhe — Mon, 17 Feb 2025 09:50:51 GMT

Hello DanisXZ,

Welcome to the world of BLE PAwR!

Perhaps the error handling/reporting can be improved in the `periodic_sync_rsp` example a bit. But I think that the devicies will have a higher chance to synchronize if you load the firmware `periodic_adv_rsp` on the other board instead of `periodic_adv`. Give it a try and write again here after you have tested. Good luck!