• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 3 replies
  • Subscribers 66 subscribers
  • Views 119 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 328523
Options

nrf5340 - bt_hci_core: bt_enable: No HCI driver registered Bluetooth init failed (err -19)

Lavanya_Manohar

Hi,

We have tested beacon sample in our custom board. Build with nrf7002dk_nrf5340_cpuapp_ns board config. Facing below issue but the same build is working fine in nrf7002 dk.(Our custom board is also same as nrf7002DK)

*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
Starting Beacon Demo
[00:00:01.001,251] <err> bt_hci_driver: Endpoint binding failed with -11
[00:00:01.001,281] <err> bt_hci_core: HCI driver open failed (-11)
Bluetooth init failed (err -11)

Here I share the conf file.

CONFIG_BT=y
CONFIG_LOG=y
CONFIG_BT_DEVICE_NAME="Test beacon"
CONFIG_BT_HCI=y

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_500PPM=y

CONFIG_USE_SEGGER_RTT=y
CONFIG_LOG_BACKEND_UART=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=y
CONFIG_LOG_MODE_DEFERRED=y

Parents
  • 0

    Hello,

    I assume you don't have an external LF crystal on your board since you've selected the CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC setting for your parent application. If so, did you make sure to apply the same clock configuration setting for the 'hci_ipc' child-image on the network core?

    Also, you should not enable CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION in the application core FW, as CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION defaults to 'y' in the network core FW when CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC is selected. Otherwise, the clock will be calibrated by both cores, leading to increased current consumption. 

    It's sufficient to only set CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y.  CONFIG_CLOCK_CONTROL_NRF_ACCURACY defaults to 500 ppm.

    Best regards,

    Vidar

Reply
  • 0

    Hello,

    I assume you don't have an external LF crystal on your board since you've selected the CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC setting for your parent application. If so, did you make sure to apply the same clock configuration setting for the 'hci_ipc' child-image on the network core?

    Also, you should not enable CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION in the application core FW, as CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION defaults to 'y' in the network core FW when CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC is selected. Otherwise, the clock will be calibrated by both cores, leading to increased current consumption. 

    It's sufficient to only set CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y.  CONFIG_CLOCK_CONTROL_NRF_ACCURACY defaults to 500 ppm.

    Best regards,

    Vidar

Children
Related