To check the config error

[Mr.NCK]

HI,

 I have tried to read the I2S data by using nrf5340 and I successfully did that. Now, I want to work on the sample with BLE. for that I have made some configurations. But, that triggers Py config error while compiling the project. I need the Nordic people to help to correct that configuration. I have attached my prj.conf file and also the error log here.

1411.prj.conf

Fullscreen I2S_Error_log.txt Download

Creating solution I2S_MIC_BLE.emProject
C:/v1.9.1/toolchain/opt/bin/cmake.exe -GNinja -DBOARD=nrf5340dk_nrf5340_cpuapp -DBOARD_DIR=C:\v1.9.1\zephyr\boards\arm\nrf5340dk_nrf5340 -BC:\v1.9.1\zephyr\samples\My_Projects\I2S_MIC_BLE\build_nrf5340dk_nrf5340_cpuapp -SC:\v1.9.1\zephyr\samples\My_Projects\I2S_MIC_BLE -DNCS_TOOLCHAIN_VERSION=1.9.1 -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=C:\v1.9.1\toolchain\segger_embedded_studio/html/configure_nordic_project_menuconfig.py
-- Application: C:/v1.9.1/zephyr/samples/My_Projects/I2S_MIC_BLE
-- Zephyr version: 2.7.99 (C:/v1.9.1/zephyr), build: v2.7.99-ncs1-1
-- Found Python3: C:/v1.9.1/toolchain/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter 
-- Found west (found suitable version "0.12.0", minimum required is "0.7.1")
-- Board: nrf5340dk_nrf5340_cpuapp
-- Cache files will be written to: C:/v1.9.1/zephyr/.cache
-- Found dtc: C:/v1.9.1/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (C:/v1.9.1/toolchain/opt)
-- Found BOARD.dts: C:/v1.9.1/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpuapp.dts
-- Generated zephyr.dts: C:/v1.9.1/zephyr/samples/My_Projects/I2S_MIC_BLE/build_nrf5340dk_nrf5340_cpuapp/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: C:/v1.9.1/zephyr/samples/My_Projects/I2S_MIC_BLE/build_nrf5340dk_nrf5340_cpuapp/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: C:/v1.9.1/zephyr/samples/My_Projects/I2S_MIC_BLE/build_nrf5340dk_nrf5340_cpuapp/zephyr/include/generated/device_extern.h
-- Including generated dts.cmake file: C:/v1.9.1/zephyr/samples/My_Projects/I2S_MIC_BLE/build_nrf5340dk_nrf5340_cpuapp/zephyr/dts.cmake
Parsing C:/v1.9.1/zephyr/Kconfig
Loaded configuration 'C:/v1.9.1/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpuapp_defconfig'
Merged configuration 'C:/v1.9.1/zephyr/samples/My_Projects/I2S_MIC_BLE/prj.conf'
-- Configuring incomplete, errors occurred!
-- Using NCS Toolchain 1.9.1 for building. (C:/v1.9.1/toolchain/cmake)

warning: SPM_NRF_I2S0_NS (defined at C:/v1.9.1/nrf\subsys\spm/Kconfig:354) was assigned the value
'y' but got the value 'n'. Check these unsatisfied dependencies: IS_SPM (=n). See
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_SPM_NRF_I2S0_NS.html and/or look up
SPM_NRF_I2S0_NS in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.


warning: BT_CTLR_RX_BUFFERS (defined at subsys/bluetooth\controller/Kconfig:192) was assigned the
value '2' but got the value ''. Check these unsatisfied dependencies: BT_CTLR (=n). See
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_BT_CTLR_RX_BUFFERS.html and/or look up
BT_CTLR_RX_BUFFERS in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.


warning: BT_CTLR_DATA_LENGTH_MAX (defined at subsys/bluetooth\controller/Kconfig:367) was assigned
the value '251' but got the value ''. Check these unsatisfied dependencies: BT_CTLR_DATA_LENGTH
(=n), BT_CTLR (=n). See
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_BT_CTLR_DATA_LENGTH_MAX.html and/or
look up BT_CTLR_DATA_LENGTH_MAX in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.


warning: BT_CTLR_PHY_2M (defined at subsys/bluetooth\controller/Kconfig:451) was assigned the value
'y' but got the value 'n'. Check these unsatisfied dependencies: (BT_CTLR_PHY || BT_CTLR_ADV_EXT)
(=n), BT_CTLR_PHY_2M_SUPPORT (=n), BT_CTLR (=n). See
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_BT_CTLR_PHY_2M.html and/or look up
BT_CTLR_PHY_2M in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.


C:/v1.9.1/zephyr/samples/My_Projects/I2S_MIC_BLE/prj.conf:35: warning: attempt to assign the value 'n' to the undefined symbol BT_NUS_SECURITY_ENABLED

C:/v1.9.1/zephyr/samples/My_Projects/I2S_MIC_BLE/prj.conf:36: warning: attempt to assign the value '100' to the undefined symbol BT_NUS_UART_BUFFER_SIZE

error: Aborting due to Kconfig warnings

CMake Error at C:/v1.9.1/zephyr/cmake/kconfig.cmake:272 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  C:/v1.9.1/zephyr/cmake/app/boilerplate.cmake:544 (include)
  CMakeLists.txt:3 (include)



error: cmake failed
create_nordic_project.py failed (1)

Thanks & Regards

Navin

[ovrebekk]

Hi Navin

I believe the issue here is that you're missing the project specific configuration parameters used by the peripheral_uart sample, such as CONFIG_BT_NUS_SEURITY_ENABLED and CONFIG_BT_NUS_UART_BUFFER_SIZE. 

Could you try to copy the Kconfig file from the peripheral_uart sample folder into your own project, and rebuild?

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

source "Kconfig.zephyr"

menu "Nordic UART BLE GATT service sample"

config BT_NUS_THREAD_STACK_SIZE
	int "Thread stack size"
	default 1024
	help
	  Stack size used in each of the two threads

config BT_NUS_UART_BUFFER_SIZE
	int "UART payload buffer element size"
	default 40
	help
	  Size of the payload buffer in each RX and TX FIFO element

config BT_NUS_SECURITY_ENABLED
	bool "Enable security"
	default y
	select BT_SMP
	help
	  "Enable BLE security for the UART service"

config BT_NUS_UART_DEV
	string "UART device name"
	default "UART_0"
	help
	  Name of the used UART device. The sample uses uart0 by default.
	  The UART device should not be used as logger backend.

config BT_NUS_UART_RX_WAIT_TIME
	int "Timeout for UART RX complete event"
	default 50
	help
	  Wait for RX complete event time in milliseconds

config BT_NUS_UART_ASYNC_ADAPTER
	bool "Enable UART async adapter"
	select SERIAL_SUPPORT_ASYNC
	help
	  Enables asynchronous adapter for UART drives that supports only
	  IRQ interface.

endmenu

Then these parameters should be accessible to the build system. 

Best regards
Torbjørn

[Mr.NCK]

Thank you Torbjorn,

Now its working fine. I want to know how to find out these type of error. Kindly, explain me 

[ovrebekk]

Hi

Essentially you have to read the build logs carefully, and try to figure out what is wrong with the configuration. 

Granted, some times the logs are hard to understand unless you have a good understanding of the build system, including the Kconfig and device tree. 

Have you followed our tutorials and guides to get started with NCS, suchas the nRF Connect SDK tutorial series?

Also, I would recommend checking out the first course in our new Nordic Academy, available here.
It doesn't really cover Kconfig in a lot of detail, but it provides a lot of other tips and tricks on using the nRF Connect SDK. 

Best regards
Torbjørn