Set BT_CONFIG=y on prj.conf under direct test mode example causing "HARD FAULT"

[Anroll]

Hello,

I am working with the nRF5340 SoC and using the Nordic Connect SDK (NCS) version 2.4.0. My project involves the following configuration:

• Network Core: Direct Test Mode (Path: ...\ncs\v2.4.0\nrf\samples\bluetooth\direct_test_mode)
• Application Core: remote_shell

My goal is to enable the Bluetooth stack in Direct Test Mode by setting BT_CONFIG=y under prj.conf file. The project builds successfully and runs on the nRF5340DK board.

However, I encounter a problem when I start the Direct Test Mode (DTM) process using nRF-DTM-master. As soon as I do this, the network core crashes, displaying the log shown below.

 

Is it possible to enable the Bluetooth stack (by only configuring BT_CONFIG=y and not calling bt_enable() in main) while running the Direct Test Mode simultaneously?

The system crashes, and the only change I've made is setting BT_CONFIG=y.

Best regards

[Anroll]

Hello,

Apologies for the mistyping. The correct configuration in the prj.conf file is CONFIG_BT=y, as shown below.

#
# Copyright (c) 2020 Nordic Semiconductor
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#

CONFIG_BT=y

# Configure assertions
CONFIG_ASSERT=y
CONFIG_ASSERT_NO_COND_INFO=y
CONFIG_ASSERT_NO_MSG_INFO=y

CONFIG_HW_STACK_PROTECTION=y

CONFIG_CONSOLE=n
CONFIG_UART_CONSOLE=n

CONFIG_LOG=y
CONFIG_LOG_PRINTK=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_LOG_BACKEND_RTT=y

# Use necessary peripherals
CONFIG_NRFX_TIMER0=y
CONFIG_NRFX_TIMER1=y
CONFIG_NRFX_TIMER2=y

CONFIG_FEM_AL_LIB=y

Best regards