Start scanning...failed (err -5) NCS2.2.0

RE: Start scanning...failed (err -5) NCS2.2.0

Elfving — Tue, 03 Jan 2023 15:25:54 GMT

Hello Yo,

You need to enable periodic sync in the child image as well. How this is done is described here.

Keep in mind that it might be tempting to change the configurations directly in the hci_rpmsg project, though if you do this you change the configuration for all other projects that use this as well - it is not just a part of you local sample project. Instead, this is what I'd recommend:

1. Add a child image folder in the build folder. Name it child_image.

2. Add a hci_rpmsg.conf configuration file to it.

3. Add the configurations from your previous project to it.

I believe this might work for you too Jeffrey.

Regards,

Elfving

RE: Start scanning...failed (err -5) NCS2.2.0

Jeffrey Haynes — Fri, 23 Dec 2022 22:57:51 GMT

I'm getting a similar error trying to run the Zephyr 'unicast_audio_client' sample on the 5340.

<wrn> bt_hci_core: opcode 0x2041 status 0x01
Scanning failed to start (err -5)

RE: Start scanning...failed (err -5) NCS2.2.0

yoyou — Sat, 17 Dec 2022 07:34:31 GMT

Hi,

thanks for reply,

my project is long rang communication that 5340+21540,

another project and le audio.

Best regards

RE: Start scanning...failed (err -5) NCS2.2.0

Elfving — Fri, 16 Dec 2022 16:39:27 GMT

I am not exactly sure what the issue is, most likely it is related to related to the communication between the application and network core, since the error returned is -5 (EIO). I need a bit more time to look into this.

Is periodic sync important to your project? Could you expand a bit more on what you're trying to achieve?

Regards,

Elfving

RE: Start scanning...failed (err -5) NCS2.2.0

Elfving — Thu, 15 Dec 2022 15:31:26 GMT

Hello,

Typically you'll find a list over the boards that we've tested and made sure works with a sample in its documentation. Though, as this is a zephyr sample (as opposed to the the ones in NCS), it might not necessarily work with our boards right out of the box; you might have to make some modifications. It seems that nRF52832 is listed as a supported device for this sample though.

I do see the same issue as you on our 5340DK, though it does work with our nRF52s. I'll look a bit further at this issue tomorrow.

Regards,

Elfving