There is a problem sending auracast

RE: There is a problem sending auracast

chelalv — Wed, 06 Aug 2025 08:54:15 GMT

Hi, I added Kconfig.sysbuld and sysbuild\ipc_radio\prj.conf in the hci uart project folder like below:

Two images were compiled.

After burning, running bumble, HCI_LE_CREATE_BIG_COMMAND did not have any errors.

RE: There is a problem sending auracast

Amanda Hsieh — Tue, 05 Aug 2025 12:53:53 GMT

Add this Kconfig.sysbuild to app folder and add the ipc_radio configs for the net core by sysbuild/ipc_radio/prj.conf.

RE: There is a problem sending auracast

chelalv — Tue, 05 Aug 2025 06:31:14 GMT

I added the prj.conf in the link, and compilation errors occurred:

devzone.nordicsemi.com/.../addprjconf.txt

RE: There is a problem sending auracast

Amanda Hsieh — Thu, 31 Jul 2025 12:59:35 GMT

[quote user="chelalv"]You can see my original question, I use hci uart as app core, the net core image of other examples， the controller is responsive.[/quote]

According to the figure, it shows the controller doesn't support "creating BIG".

Probably you just use the default setting of the controller configs.

You can refer to the configs used in the audio project:

https://github.com/nrfconnect/sdk-nrf/blob/v3.0.2/applications/nrf5340_audio/sysbuild/ipc_radio/prj.conf

Since the default one for hci_uart might not enable LE audio-related features.

RE: There is a problem sending auracast

chelalv — Wed, 30 Jul 2025 07:07:01 GMT

Hi Amanda, I don't quite understand this question: "Does the hci_uart work as expected?"

I can run the iso_time_sync example on the nRF5340 audioDK without issue.

I have some doubts whether the combination of hci_uart as net core and empty_app_core as app core can work properly.

You can see my original question, I use hci uart as app core, the net core image of other examples， the controller is responsive.

RE: There is a problem sending auracast

Amanda Hsieh — Tue, 29 Jul 2025 14:35:27 GMT

[quote user="chelalv"]But when I use bumble to test, It looks like there is a problem with hci communication[/quote]

It appears that Bumble is attempting to initialize the controller, but is receiving invalid responses. Does the hci_uart work as expected?

Do you get the same result if testing with the NCS v3.0.2 iso_time_sync sample?

[quote user="chelalv"]Why can other programs sysbuild compile two hex, one application mcu and one network mcu, but hci uart only has one application mcu?[/quote]

There is no multi-image build config to support that combination.

RE: There is a problem sending auracast

chelalv — Tue, 15 Jul 2025 08:43:17 GMT

Hi, Sorry for the late reply.
I don't know how to do this: build the hci_uart sample with EXTRA_CONF_FILE='debug.conf' and connect the net core via RTT to check if it works as expected.
I recompiled the hci uart example according to docs.nordicsemi.com/.../hci_logger.html
But when I use bumble to test, It looks like there is a problem with hci communication

I enabled Monitor protocol over UART, so prj.conf will increase CONFIG_BT_DEBUG_MONITOR_UART=y and reduce CONFIG_CONSOLE=n.

CONFIG_STDOUT_CONSOLE=n
CONFIG_UART_CONSOLE=n
CONFIG_GPIO=y
CONFIG_SERIAL=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_BT=y
CONFIG_BT_HCI_RAW=y
CONFIG_BT_HCI_RAW_H4=y
CONFIG_BT_HCI_RAW_H4_ENABLE=y
CONFIG_BT_BUF_ACL_RX_SIZE=255
CONFIG_BT_BUF_CMD_TX_SIZE=255
CONFIG_BT_BUF_EVT_DISCARDABLE_SIZE=255
CONFIG_BT_CTLR_ASSERT_HANDLER=y
CONFIG_BT_MAX_CONN=16
CONFIG_BT_CTLR_DTM_HCI=y

CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=512

# Workaround: Unable to allocate command buffer when using K_NO_WAIT since
# Host number of completed commands does not follow normal flow control.
CONFIG_BT_BUF_CMD_TX_COUNT=10

CONFIG_BT_DEBUG_MONITOR_UART=y

Another question: Why can other programs sysbuild compile two hex, one application mcu and one network mcu, but hci uart only has one application mcu?

RE: There is a problem sending auracast

Amanda Hsieh — Wed, 02 Jul 2025 20:53:44 GMT

Hi,

You could build the hci_uart sample with EXTRA_CONF_FILE='debug.conf' and connect the net core via RTT to check if it works as expected. You could also capture HCI packets in Wireshark and provide the output PCAP file to help investigate the issue.

-Amanda H.

RE: There is a problem sending auracast

chelalv — Wed, 02 Jul 2025 08:34:11 GMT

Hi Amanda, I can run the iso_time_sync example on the nRF5340 audioDK without issue.

I can now compile empty_app_core successfully, nrf5340 empty_app_core compilation failed

I now use hci_uart to flash net core and empty_app_core to flash app core

The following is the log of hci_uart compilation and flash

devzone.nordicsemi.com/.../hci_5F00_uart.txt

empty_app_core compilation and flash log

devzone.nordicsemi.com/.../empty_5F00_app_5F00_core.txt

I used bumble to test HCI_RESET_COMMAND and it didn't respond

RE: There is a problem sending auracast

Amanda Hsieh — Tue, 01 Jul 2025 16:47:25 GMT

Hi,

Sigurd is out of the office, so I take this case again.

Are you able to run the iso_time_sync example on the nRF5340 audioDK without issue?

[quote user="chelalv"]

After flashing, VCOM0 COM18:

I have previously flashed the iso_time_sync example,

[/quote]

This is probably caused the net core has not flashed the image correctly. If you are using VS Code, the default build setting would also build for net Core. Please check the programming log to ensure the netcore got flashed.

Let me know your current status.

Regards,
Amana H.

RE: There is a problem sending auracast

chelalv — Mon, 23 Jun 2025 09:43:43 GMT

I use Nrf5340 audio DK as controller, bumble(google.github.io/.../index.html) as host and it fails to send.

PC-> Bumble -> nRF5340 audio DK,

I haven't used the nrf5340 DK, sorry for confusing you.

RE: There is a problem sending auracast

Sigurd — Fri, 20 Jun 2025 08:32:30 GMT

[quote user=""]I use nRF5340 audio DK,iso_time_sync example, can successfully send BIS data, then I use DK as controller, bumble[/quote]

Is this your setup still?

Something like this:

PC-> Bumble -> nRF5340-DK <wireless-link> nRF5340 AUDIO DK.

RE: There is a problem sending auracast

chelalv — Fri, 20 Jun 2025 03:31:14 GMT

I selected the target board as nrf5340dk/nrf5340/cpuapp and it compiled successfully and flashed it in, but I think it can't run properly on the nrf5340 audio DK.

I used bumble to test HCI_RESET_COMMAND and it didn't respond

RE: There is a problem sending auracast

chelalv — Fri, 13 Jun 2025 08:57:41 GMT

build error：zephyr/drivers/regulator/libdrivers__regulator.a(regulator_npm1100.c.obj):(.rodata.config_0+0x0): undefined reference to `__device_dts_ord_8

devzone.nordicsemi.com/.../builderror.txt

RE: There is a problem sending auracast

Sigurd — Wed, 11 Jun 2025 11:27:14 GMT

Hi,

Try flashing the https://github.com/nrfconnect/sdk-nrf/tree/main/samples/nrf5340/empty_app_core to the app core, and the hci_uart to the network core.

RE: There is a problem sending auracast

chelalv — Tue, 10 Jun 2025 01:26:51 GMT

Hi, the configuration is:

After compilation:

After flashing, VCOM0 COM18:

I have previously flashed the iso_time_sync example,

Using the bumble test, there are these logs, and there are no logs later.

BUMBLE_LOGLEVEL=DEBUG python auracast.py transmit --input file:audioclub.wav --input-format auto --broadcast-name bumble serial:/dev/ttyACM0,115200
DEBUG:asyncio:Using selector: EpollSelector
DEBUG:bumble.drivers:Probing driver class: rtk
DEBUG:bumble.drivers.rtk:USB metadata not found
DEBUG:bumble.drivers:Probing driver class: intel
DEBUG:bumble.drivers.intel:USB metadata not sufficient
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_RESET_COMMAND

I think the HCI communication is unsuccessful.

RE: There is a problem sending auracast

Sigurd — Thu, 05 Jun 2025 15:03:32 GMT

Hi!

[quote user="chelalv"]No, I build hci_uart sample for board nrf5340_audio_dk/nrf5340/cpuapp.[/quote]

Could you try nrf5340_audio_dk/nrf5340/cpunet ?

RE: There is a problem sending auracast

chelalv — Thu, 05 Jun 2025 09:10:47 GMT

Hi Sigurd,

1) You built hci_uart sample for board nrf5340_audio_dk/nrf5340/cpunet , correct?

No, I build hci_uart sample for board nrf5340_audio_dk/nrf5340/cpuapp.

2. there is no CONFIG_BT_CTLR_PHY_2M in prj.conf, Later I added CONFIG_BT_CTLR_PHY_2M=y, recompiled and downloaded, but still got the same error

I use the iso_time_sync example, and select nrf5340_audio_dk/nrf5340/cpuapp as the borad target. Two images will be automatically generated.

Why doesn't the hci_uart example generate two images?

RE: There is a problem sending auracast

Sigurd — Mon, 02 Jun 2025 13:13:24 GMT

Hi!

1) You built hci_uart sample for board nrf5340_audio_dk/nrf5340/cpunet , correct?

DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_LE_CREATE_BIG_COMMAND:
  big_handle:            0
  advertising_handle:    0
  num_bis:               2
  sdu_interval:          10000
  max_sdu:               100
  max_transport_latency: 65
  rtn:                   4
  phy:                   PhyBit.LE_2M
  packing:               0
  framing:               0
  encryption:            0
  broadcast_code:        00000000000000000000000000000000

The parameters itself looks correct. But, it could be that 2M is not enabled.

Could you check that you have CONFIG_BT_CTLR_PHY_2M=y in the .config file?

RE: There is a problem sending auracast

chelalv — Wed, 28 May 2025 08:43:57 GMT

I used the hci uart in v3.0.2, but still got the same error

BUMBLE_LOGLEVEL=DEBUG python auracast.py transmit --input file:audioclub.wav --input-format auto --broadcast-name bumble serial:/dev/ttyACM0,115200
DEBUG:asyncio:Using selector: EpollSelector
DEBUG:bumble.drivers:Probing driver class: rtk
DEBUG:bumble.drivers.rtk:USB metadata not found
DEBUG:bumble.drivers:Probing driver class: intel
DEBUG:bumble.drivers.intel:USB metadata not sufficient
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_RESET_COMMAND
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_RESET_COMMAND
  return_parameters:       HCI_SUCCESS
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_READ_LOCAL_SUPPORTED_COMMANDS_COMMAND
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_READ_LOCAL_SUPPORTED_COMMANDS_COMMAND
  return_parameters:
    status:             HCI_SUCCESS
    supported_commands: 2000800000c0000c0000e40000002822000000000000040000f7ffff7f00000030007ef6ffffff0720e4ffff0740000000000000000000000000000000000000
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_LE_READ_LOCAL_SUPPORTED_FEATURES_COMMAND
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_LE_READ_LOCAL_SUPPORTED_FEATURES_COMMAND
  return_parameters:
    status:      HCI_SUCCESS
    le_features: dd7900f410000000
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_READ_LOCAL_VERSION_INFORMATION_COMMAND
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_READ_LOCAL_VERSION_INFORMATION_COMMAND
  return_parameters:
    status:             HCI_SUCCESS
    hci_version:        14
    hci_subversion:     8346
    lmp_version:        14
    company_identifier: 89
    lmp_subversion:     8346
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_READ_LOCAL_SUPPORTED_FEATURES_COMMAND
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_READ_LOCAL_SUPPORTED_FEATURES_COMMAND
  return_parameters:
    status:       HCI_SUCCESS
    lmp_features: 0000000060000000
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_SET_EVENT_MASK_COMMAND:
  event_mask: ff9ffbbf07f8bf3d
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_SET_EVENT_MASK_COMMAND
  return_parameters:       HCI_SUCCESS
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_LE_SET_EVENT_MASK_COMMAND:
  le_event_mask: fffff7ff07e80300
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_LE_SET_EVENT_MASK_COMMAND
  return_parameters:       HCI_SUCCESS
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_LE_READ_BUFFER_SIZE_V2_COMMAND
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_LE_READ_BUFFER_SIZE_V2_COMMAND
  return_parameters:
    status:                        HCI_SUCCESS
    le_acl_data_packet_length:     27
    total_num_le_acl_data_packets: 3
    iso_data_packet_length:        14
    total_num_iso_data_packets:    3
DEBUG:bumble.host:HCI LE flow control: le_acl_data_packet_length=27,total_num_le_acl_data_packets=3iso_data_packet_length=14,total_num_iso_data_packets=3
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_LE_READ_NUMBER_OF_SUPPORTED_ADVERTISING_SETS_COMMAND
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_LE_READ_NUMBER_OF_SUPPORTED_ADVERTISING_SETS_COMMAND
  return_parameters:
    status:                         HCI_SUCCESS
    num_supported_advertising_sets: 1
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_LE_READ_MAXIMUM_ADVERTISING_DATA_LENGTH_COMMAND
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_LE_READ_MAXIMUM_ADVERTISING_DATA_LENGTH_COMMAND
  return_parameters:
    status:                      HCI_SUCCESS
    max_advertising_data_length: 62
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_READ_BD_ADDR_COMMAND
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_READ_BD_ADDR_COMMAND
  return_parameters:
    status:  HCI_SUCCESS
    bd_addr: 00:00:00:00:00:00/P
DEBUG:bumble.device:BD_ADDR: 00:00:00:00:00:00/P
DEBUG:bumble.keys:JSON keystore: /home/matt/.local/share/Bumble/Pairing/f0-f1-f2-f3-f4-f5.json
DEBUG:bumble.device:LE Random Address: F0:F1:F2:F3:F4:F5
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_LE_SET_RANDOM_ADDRESS_COMMAND:
  random_address: F0:F1:F2:F3:F4:F5
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_LE_SET_RANDOM_ADDRESS_COMMAND
  return_parameters:       HCI_SUCCESS
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_LE_SET_EXTENDED_ADVERTISING_PARAMETERS_COMMAND:
  advertising_handle:               0
  advertising_event_properties:
  primary_advertising_interval_min: 160
  primary_advertising_interval_max: 320
  primary_advertising_channel_map:  CHANNEL_37|CHANNEL_38|CHANNEL_39
  own_address_type:                 RANDOM
  peer_address_type:                PUBLIC_DEVICE
  peer_address:                     00:00:00:00:00:00/P
  advertising_filter_policy:        0
  advertising_tx_power:             127
  primary_advertising_phy:          LE 1M
  secondary_advertising_max_skip:   0
  secondary_advertising_phy:        LE 1M
  advertising_sid:                  0
  scan_request_notification_enable: 0
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_LE_SET_EXTENDED_ADVERTISING_PARAMETERS_COMMAND
  return_parameters:
    status:            HCI_SUCCESS
    selected_tx_power: 0
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_LE_SET_ADVERTISING_SET_RANDOM_ADDRESS_COMMAND:
  advertising_handle: 0
  random_address:     F0:F1:F2:F3:F4:F5
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_LE_SET_ADVERTISING_SET_RANDOM_ADDRESS_COMMAND
  return_parameters:       HCI_SUCCESS
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_LE_SET_EXTENDED_ADVERTISING_DATA_COMMAND:
  advertising_handle:  0
  operation:           COMPLETE_DATA
  fragment_preference: 1
  advertising_data:    0616521840e201073062756d626c65
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_LE_SET_EXTENDED_ADVERTISING_DATA_COMMAND
  return_parameters:       HCI_SUCCESS
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_LE_SET_PERIODIC_ADVERTISING_PARAMETERS_COMMAND:
  advertising_handle:                0
  periodic_advertising_interval_min: 80
  periodic_advertising_interval_max: 160
  periodic_advertising_properties:   Properties.0
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_LE_SET_PERIODIC_ADVERTISING_PARAMETERS_COMMAND
  return_parameters:       HCI_SUCCESS
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_LE_SET_PERIODIC_ADVERTISING_DATA_COMMAND:
  advertising_handle: 0
  operation:          COMPLETE_DATA
  advertising_data:   35165118409c00010206000000000a020108020201030464000c0404656e670603446973636f01060503010000000206050302000000
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_LE_SET_PERIODIC_ADVERTISING_DATA_COMMAND
  return_parameters:       HCI_SUCCESS
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_LE_SET_EXTENDED_ADVERTISING_ENABLE_COMMAND:
  enable:                             1
  advertising_handles[0]:             0
  durations[0]:                       0
  max_extended_advertising_events[0]: 0
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_LE_SET_EXTENDED_ADVERTISING_ENABLE_COMMAND
  return_parameters:       HCI_SUCCESS
Start Periodic Advertising
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_LE_SET_PERIODIC_ADVERTISING_ENABLE_COMMAND:
  enable:             1
  advertising_handle: 0
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_COMPLETE_EVENT:
  num_hci_command_packets: 1
  command_opcode:          HCI_LE_SET_PERIODIC_ADVERTISING_ENABLE_COMMAND
  return_parameters:       HCI_SUCCESS
Encoding with 480 PCM samples per 100 byte frame
Setup BIG
/mnt/c/Users/Mji/Downloads/bumble/apps/auracast.py:948: FutureWarning: Only for testing.
  big = await device.create_big(
DEBUG:bumble.host:### HOST -> CONTROLLER: HCI_LE_CREATE_BIG_COMMAND:
  big_handle:            0
  advertising_handle:    0
  num_bis:               2
  sdu_interval:          10000
  max_sdu:               100
  max_transport_latency: 65
  rtn:                   4
  phy:                   PhyBit.LE_2M
  packing:               0
  framing:               0
  encryption:            0
  broadcast_code:        00000000000000000000000000000000
DEBUG:bumble.host:### CONTROLLER -> HOST: HCI_COMMAND_STATUS_EVENT:
  status:                  HCI_UNSUPPORTED_FEATURE_OR_PARAMETER_VALUE_ERROR
  num_hci_command_packets: 1
  command_opcode:          HCI_LE_CREATE_BIG_COMMAND
WARNING:bumble.host:HCI_LE_CREATE_BIG_COMMAND failed (HCI_UNSUPPORTED_FEATURE_OR_PARAMETER_VALUE_ERROR)
ERROR:bumble.host:!!! Exception while sending command: HCI_Error(hci/HCI_UNSUPPORTED_FEATURE_OR_PARAMETER_VALUE_ERROR [0x11])
Traceback (most recent call last):
  File "/home/matt/.local/lib/python3.10/site-packages/bumble/host.py", line 683, in send_command
    raise hci.HCI_Error(status)
bumble.hci.HCI_Error: HCI_Error(hci/HCI_UNSUPPORTED_FEATURE_OR_PARAMETER_VALUE_ERROR [0x11])
!!! An error occurred while executing the command: HCI_Error(hci/HCI_UNSUPPORTED_FEATURE_OR_PARAMETER_VALUE_ERROR [0x11])

devzone.nordicsemi.com/.../audioclub.wav

RE: There is a problem sending auracast

chelalv — Tue, 27 May 2025 08:26:23 GMT

I upgraded to 3.0.1 with vscode, but I can't find DK in vscode.

There are two more USBs.

I reinstalled segger jlink but it still doesn't work

https://docs.nordicsemi.com/bundle/nrfutil/page/guides/installing.html#prerequisites

JLink_Windows_V818_x86_64.exe -InstUSBDriver=1

I use the nrf52832 development board and it can be recognized normally

Today, when I right-clicked the device in the device manager and updated the driver, JLink CDC UART Port was displayed.

Now I can flash the development board

RE: There is a problem sending auracast

chelalv — Thu, 22 May 2025 08:52:00 GMT

2.9.1, I will try 3.0.1

RE: There is a problem sending auracast

Amanda Hsieh — Mon, 19 May 2025 14:11:23 GMT

Hi,

Which NCS version are you using? Could you try the latest version, v3.0.1?

Regards,
Amanda H.