PAwR Sync: Log Warning: bt_hci_core: opcode 0x2036 status 0x0c

[AlexandraK_04]

Hello,

I am using the nrf21540 with the shield nrf21540ek; nRF Connect SDK 2.6.2 and the toolchain 2.7.0.

Currently I am getting the following warning on the log output for the pawr_sync_rsp sample:

*** Booting nRF Connect SDK v3.5.99-ncs1-2 ***
Starting Periodic Advertising with Responses Synchronization Demo
[00:00:00.000,762] <inf> bt_sdc_hci_driver: SoftDevice Controller build revision: 
                                            36 f0 e5 0e 87 68 48 fb  02 fd 9f 82 cc 32 e5 7b |6....hH. .....2.{
                                            91 b1 5c ed                                      |..\.             
[00:00:00.003,021] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.003,051] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:00.003,082] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 54.58864 Build 1214809870
[00:00:00.003,906] <inf> bt_hci_core: Identity: E4:4F:F0:12:33:95 (random)
[00:00:00.003,936] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x118f, manufacturer 0x0059
[00:00:00.003,967] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x118f
Waiting for periodic sync...
Timed out while synchronizing
Waiting for periodic sync...
Timed out while synchronizing
[00:00:20.005,706] <wrn> bt_hci_core: opcode 0x2036 status 0x0c
Advertising failed to start (err -5)

The following is the log output from the pawr_adv_rsp sample:

*** Booting nRF Connect SDK v3.5.99-ncs1-2 ***
Starting Periodic Advertising Demo
[00:00:00.000,762] <inf> bt_sdc_hci_driver: SoftDevice Controller build revision: 
                                            36 f0 e5 0e 87 68 48 fb  02 fd 9f 82 cc 32 e5 7b |6....hH. .....2.{
                                            91 b1 5c ed                                      |..\.             
[00:00:00.002,990] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.003,021] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:00.003,051] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 54.58864 Build 1214809870
[00:00:00.003,875] <inf> bt_hci_core: Identity: FD:26:4A:90:5B:5F (random)
[00:00:00.003,906] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x118f, manufacturer 0x0059
[00:00:00.003,936] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0x118f
Start Periodic Advertising
Scanning successfully started

In the code I only added set(SHIELD nrf21540ek) in the CMakeFile:

# SPDX-License-Identifier: Apache-2.0

cmake_minimum_required(VERSION 3.20.0)
set(SHIELD nrf21540ek)
find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
project(periodic_adv_rsp)

target_sources(app PRIVATE src/main.c)

Does anyone know how I can fix the problem so that the sample works without warnings or error messages?

Thank you.

[Amanda Hsieh]

Hi,

I am using the nrf21540 with the shield nrf21540ek;

Which DK are you using with the shield nrf21540ek? I need to know the DK to reproduce the issue. 

nRF Connect SDK 2.6.2 and the toolchain 2.7.0.

The versions of the SDK and Toolchain should be the same. 

Regards,
Amanda H.

[AlexandraK_04]

Hi, 

I am using the nRF21540DK and the nrf21540 ek as shield. 

Amanda Hsieh said:

The versions of the SDK and Toolchain should be the same. 

The warning is the same when i use SDK 2.6.2 and toolchain 2.6.2.

Regards,

Alexandra

[Amanda Hsieh]

Hi, 

AlexandraK_04 said:

I am using the nRF21540DK and the nrf21540 ek as shield. 

nRF21540DK already has nRF21540, so it doesn't need the nrf21540 ek which is for other kits without nRF21540 such as nRF52840DK.

My colleague already explained the error in your other private case: 

The error is BT_HCI_ERR_CMD_DISALLOWED as described in an ealier post in this thread. This seems to be a known issue in Zephyr that is described in this post.

PS: We don't have test coverage on Zephyr samples with the Softdevice controller, as described in the SDK documentation:

"Zephyr also provides a variety of Samples and Demos, including very simple Basic Samples. These samples are a good starting point for understanding how to put together your own application. However, Zephyr samples and applications are not tested and verified to work with the nRF Connect SDK releases."