https://devzone.nordicsemi.com/f/nordic-q-a/115342/pawr-samples-not-working-on-ncs-2-7-0My setup includes 2 nRF52840 DKs, one flashed with periodic_adv_rsp and the other with periodic_sync_rsp. I copied the samples and auto-generated a build configuration for each for an nRF52840 DK target but the outcome was very similar to a previous ticketen-USTelligent Community 13Tue, 08 Oct 2024 19:14:50 GMThttps://devzone.nordicsemi.com/thread/505427?ContentTypeID=1Tue, 08 Oct 2024 19:14:50 GMT137ad170-7792-4731-bb38-c0d22fbe4515:71595ba9-d862-45f7-8385-855804576ca1rbmarcus<p>Update: when I roll back to NCS 2.6.2 the program works and the HCI error on the advertiser/central is resolved by updating the min/max periodic advertising intervals to <code>0x50 * NUM_SUBEVENTS</code>. This seems to be a new issue introduced in 2.7.0 and specifically affects the periodic_sync_rsp functionality. <a href="https://github.com/zephyrproject-rtos/zephyr/commit/7bc63985af7e3f274ca4b09a325da0ce0892a826#diff-a97ebe1dbbdd6cd114236d720942f8d510fce54686d45255f8434368a481b722R229">This commit</a> from the main Zephyr repo introduces the bug, and <a href="https://github.com/nrfconnect/sdk-zephyr/commit/94d86b9501f8f6a48ee67930e527e011fd020e36">this commit</a> solves it. My guess is putting the name in the scan response data rather than the advertisement data prevents the central/advertiser from successfully identifying and connecting to the node. The issue is still present in 2.7.99-cs2.</p><div style="clear:both;"></div>