Can't connect central to peripheral after peripheral resets

RE: Can't connect central to peripheral after peripheral resets

dejans — Tue, 18 Jul 2023 08:00:51 GMT

Hi,

I have tested button reset on our central UART and peripheral UART samples and connection was automatically established after the reset. It did not matter if the reset was performed on peripheral or central device. There was no need for reboot.

Best regards,
Dejan

RE: Can't connect central to peripheral after peripheral resets

mul — Fri, 14 Jul 2023 19:55:01 GMT

I've added my disconnect() function to the post above.

When this is called on the central, it executes fine, disconnects, then the disconnected() callback gets invoked also.

I can then call connect() again after this without a reset and it connects again to the peripheral.

I'm just struggling to understand why, when the peripheral causes the disconnect itself, the disconnected() callback on the central gets invoked in the same way, but can't connect() again afterwards until I reboot the central.

RE: Can't connect central to peripheral after peripheral resets

mul — Fri, 14 Jul 2023 19:45:51 GMT

Hi dejans Thanks for your reply. When I start scanning from the disconnected() callback, then try to connect again, I now get Connection failed. Error : -11 meaning No more contexts

RE: Can't connect central to peripheral after peripheral resets

dejans — Fri, 14 Jul 2023 18:41:45 GMT

Hi,

You could try adding the lines below to your disconnected() callback:

err = bt_scan_start(BT_SCAN_TYPE_SCAN_ACTIVE);
	if (err) {
		LOG_ERR("Scanning failed to start (err %d)",
			err);
	}

As a reference, you could have a look at central UART sample.

Best regards,
Dejan