nRF5340 Dynamic Connection Event Length

RE: nRF5340 Dynamic Connection Event Length

dejans — Wed, 26 Mar 2025 09:57:42 GMT

Hi,

Yes, it is available starting from NCS v2.9.0.
https://github.com/nrfconnect/sdk-nrf/tree/v2.9.0/samples/bluetooth/scanning_while_connecting

Best regards,
Dejan

RE: nRF5340 Dynamic Connection Event Length

AKV — Tue, 25 Mar 2025 11:14:45 GMT

The file hci_vs_sdc.h is not there in my NCS 2.6.1 folder.

Is this file available only in a higher version?

RE: nRF5340 Dynamic Connection Event Length

dejans — Fri, 21 Mar 2025 10:31:30 GMT

Hi,

There is a sample that demonstrates how to use hci_vs_sdc_event_length_set() - scanning while connecting. This sample builds for nrf53. In this sample, SoftDevice controller is on the network core while Zephyr host and application reside on the application core, and no cmake changes are needed.

Best regards,
Dejan

RE: nRF5340 Dynamic Connection Event Length

AKV — Wed, 19 Mar 2025 06:26:05 GMT

Hi,

1. I have added the hci_vs_sdc.h file to the NCS library path:

nRFConnectSDK\v2.6.1\zephyr\include\zephyr\bluetooth\hci_vs_sdc.h

2. I have added the hci_vs_sdc.c file to the NCS library path:

nRFConnectSDK\v2.6.1\zephyr\subsys\bluetooth\hci_vs_sdc.c

3. I have modified the CMakeLists.txt file in the NCS library path:

nRFConnectSDK\v2.6.1\zephyr\subsys\bluetooth\CMakeLists.txt

Added the following line:

zephyr_sources_ifdef(CONFIG_BT_LL_SOFTDEVICE hci_vs_sdc.c)

# SPDX-License-Identifier: Apache-2.0

add_library(subsys__bluetooth INTERFACE)

target_include_directories(subsys__bluetooth INTERFACE ${CMAKE_CURRENT_SOURCE_DIR})

add_subdirectory(common)
add_subdirectory_ifdef(CONFIG_BT_HCI host)
add_subdirectory_ifdef(CONFIG_BT_SHELL shell)
add_subdirectory_ifdef(CONFIG_BT_CONN services)
add_subdirectory_ifdef(CONFIG_BT_MESH mesh)
add_subdirectory_ifdef(CONFIG_BT_AUDIO audio)
add_subdirectory_ifdef(CONFIG_BT_CRYPTO crypto)

zephyr_sources_ifdef(CONFIG_BT_LL_SOFTDEVICE hci_vs_sdc.c)

if(CONFIG_BT_CTLR AND CONFIG_BT_LL_SW_SPLIT)
  add_subdirectory(controller)
endif()

zephyr_include_directories(${ZEPHYR_BASE}/subsys/bluetooth)

add_subdirectory(lib)

4. I have enabled the CONFIG_BT_LL_SOFTDEVICE option by adding CONFIG_BT_LL_SOFTDEVICE=y in both the app core and net core config files.

But still I am getting the error

main.c:118: undefined reference to `hci_vs_sdc_event_length_set'

devzone.nordicsemi.com/.../log19032025.txt

Can you please confirm if the above steps are correct or if I am missing anything?

RE: nRF5340 Dynamic Connection Event Length

dejans — Tue, 18 Mar 2025 14:08:16 GMT

Hi,

The issue you observed might be related to APIs inability to access controller which is on the network core.
You could try to use hci_vs_sdc which is currently recommended API for sending VS commands to the controller. This API will build and send HCI command to the controller and works even if the controller is on another CPU compared to the host/application. You can look at this commit.

Best regards,
Dejan

RE: nRF5340 Dynamic Connection Event Length

dejans — Tue, 18 Mar 2025 13:07:28 GMT

Hi,

I have reproduced your issue. I will look further into it. I expect to get back to you by the end of the week.

Best regards,
Dejan

RE: nRF5340 Dynamic Connection Event Length

AKV — Mon, 17 Mar 2025 17:50:12 GMT

Hi,

[quote userid="111786" url="~/f/nordic-q-a/119819/nrf5340-dynamic-connection-event-length/527717"]There are many files (including several zip files) in your previous ticket. Which file contains your code?[/quote]

You can download any code, If you need latest one you download "ridegrid_06_28012025".

[quote userid="111786" url="~/f/nordic-q-a/119819/nrf5340-dynamic-connection-event-length/527717"]Can you look at the sample which I linked in my previous edited reply?[/quote]

Yes, I have tried as given below. But the error is

main.c:30:10: fatal error: bluetooth/hci_vs_sdc.h: No such file or directory
30 | #include <bluetooth/hci_vs_sdc.h>

#include <bluetooth/hci_vs_sdc.h>
#include <zephyr/bluetooth/bluetooth.h>
#include <zephyr/bluetooth/addr.h>
#include <zephyr/bluetooth/conn.h>
#include <zephyr/bluetooth/hci.h>



sdc_hci_cmd_vs_event_length_set_t event_length_params = {
		.event_length_us = 2000,
	};

hci_vs_sdc_event_length_set(&event_length_params);

RE: nRF5340 Dynamic Connection Event Length

dejans — Mon, 17 Mar 2025 16:38:18 GMT

Hi,

Thank you for additional information.

[quote user="AKV"]I have attached our code in this private ticket. If needed you can refer this. [/quote]

There are many files (including several zip files) in your previous ticket. Which file contains your code?

[quote user="dejans"]Edit: You can look at the scanning while connecting sample. It shows how to set event_length_us parameter.[/quote]

Can you look at the sample which I linked in my previous edited reply?

Best regards,
Dejan

RE: nRF5340 Dynamic Connection Event Length

AKV — Mon, 17 Mar 2025 11:05:00 GMT

Hi,

I have developed a custom BLE application code by using this custom_ncs_ble_service_sample tutorial. Its working fine.

We are developing a mesh network. Our requirement is the one device can connect to three other devices. Using one connection as a peripheral and up to two connections as a central for mesh connections.

We are using nRF5340 and the nRF Connect SDK Version 2.6.1.

I have attached our code in this private ticket. If needed you can refer this.

Private ticket of other issue

RE: nRF5340 Dynamic Connection Event Length

dejans — Mon, 17 Mar 2025 10:27:51 GMT

Hi,

Can you provide more information about your application? Is it based on any of our Bluetooth samples?

Edit: You can look at the scanning while connecting sample. It shows how to set event_length_us parameter.

Best regards,
Dejan

RE: nRF5340 Dynamic Connection Event Length

AKV — Mon, 17 Mar 2025 09:51:51 GMT

Hi,

Any updates?

If you can provide an example code or implementation, that would be great.

RE: nRF5340 Dynamic Connection Event Length

AKV — Sat, 15 Mar 2025 03:24:04 GMT

Hi,

Yes I am using this in the net core file (custom_nrf5340_cpunet_defconfig file.)

CONFIG_BT_CTLR_SDC_MAX_CONN_EVENT_LEN_DEFAULT=5000.

I have tried removing this config, but still getting the same error.

RE: nRF5340 Dynamic Connection Event Length

dejans — Fri, 14 Mar 2025 17:02:10 GMT

Hi,

Can you check if you have included CONFIG_BT_CTLR_SDC_MAX_CONN_EVENT_LEN_DEFAULT in your configuration for the bluetooth controller running on the network core as described in this ticket?

Best regards,
Dejan

RE: nRF5340 Dynamic Connection Event Length

AKV — Fri, 14 Mar 2025 11:24:44 GMT

Hi,

[quote userid="111786" url="~/f/nordic-q-a/119819/nrf5340-dynamic-connection-event-length/527348"]Which NCS version do you use?[/quote]

NCS version 2.6.1.

[quote userid="111786" url="~/f/nordic-q-a/119819/nrf5340-dynamic-connection-event-length/527348"]Is your application based on any of our samples?
[/quote]

No, Our custom board code.

Please check the complete log.

devzone.nordicsemi.com/.../log14032025.txt

RE: nRF5340 Dynamic Connection Event Length

dejans — Fri, 14 Mar 2025 11:16:31 GMT

Hi,

Is your application based on any of our samples?

Which NCS version do you use?

Can you provide complete error log?

Best regards,
Dejan