RE: Connection Creation Timeout in NCS v3.2.1

tesc — Mon, 02 Feb 2026 15:57:27 GMT

Hi,

Do you have a sniffer trace from when this is happening? (nRF Sniffer or other.)

Regards,
Terje

RE: Connection Creation Timeout in NCS v3.2.1

undra — Thu, 22 Jan 2026 02:51:14 GMT

Hi,
I tried using other types of addresses and reducing the number of zeros in the MAC address, yet the connection timeout issue still occurs.
I found during testing that the connection timeout issue still occurs when using the Zephyr stack, only with a lower occurrence rate—and this issue was not observed in previous tests.

RE: Connection Creation Timeout in NCS v3.2.1

tesc — Mon, 19 Jan 2026 14:35:31 GMT

Hi,

[quote user=""]Are the Nordic protocol stacks in nrf5-sdk and NCS different?[/quote]

The link layer (controller) is basically the same, since the SoftDevice Controller in nRF Connect SDK is a continuation of those layers from the SoftDevice from nRF5 SDK. It has however been updated and maintained since nRF5 SDK, so there are some differences, yes.

The host layer is different in nRF Connect SDK, but that host layer is also the same in nRF Connect SDK regardless of whether you use the SoftDevice or Zephyr controller.

err = bt_addr_le_from_str("e1:00:00:02:0a:a0", "public", &addr);

Do you see the same issue with other addresses as well? In particular, there are four sub-types of addresses, indicated by the two most significant bits of the address, where 0b00 is Non-resolvable private address, 0b01 is Resolvable private address, 0b11 is Static device address, and 0b10 is Reserved for future use. Is this happening with any static device address (which from what I understand is the address type you currently use), and also does it happen with addresses where there are shorter stretches of 0 bits (you currently have at least 20 consecutive zeroes in that address, each 0 in the above notation is four bits of 0.)

Regards,
Terje