Unable to Build "RF Test sample" of nRF 52832 with nRF Connect SDK (v2.3.0. rc1).

RE: Unable to Build "RF Test sample" of nRF 52832 with nRF Connect SDK (v2.3.0. rc1).

Hoko — Mon, 06 Mar 2023 06:33:34 GMT

Thanks.

I chkecked v2.3.0.

Then no problem.

File fixed.

RE: Unable to Build "RF Test sample" of nRF 52832 with nRF Connect SDK (v2.3.0. rc1).

Sigurd Hellesvik — Wed, 01 Mar 2023 11:09:51 GMT

Try to copy your sample to C:/radio_test_220.

Regards,
Sigurd Hellesvik

RE: Unable to Build "RF Test sample" of nRF 52832 with nRF Connect SDK (v2.3.0. rc1).

Hoko — Wed, 01 Mar 2023 09:31:26 GMT

>I'll go back to 2.2 and try again.

Same result.

Why?

log --

west build --build-dir c:\L\src\Nordic\radio_test_220\build c:\L\src\Nordic\radio_test_220 --pristine --board nrf52840dk_nrf52840 -- -DNCS_TOOLCHAIN_VERSION:STRING="NONE" -DBOARD_ROOT:STRING="c:/L/src/Nordic/peripheral_lbs_230rc1;c:/L/src/Nordic/radio_test_230rc1;c:/L/src/Nordic/direct_test_mode_230rc1;c:/L/src/Nordic/peripheral_hr_230rc1;c:/L/src/Nordic/peripheral_hr_220;c:/L/src/Nordic/radio_test_220"

-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: C:/L/src/Nordic/radio_test_220
-- Found Python3: C:/ncs/toolchains/v2.2.0/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.2.0/zephyr/.cache
-- Zephyr version: 3.2.99 (C:/ncs/v2.2.0/zephyr)
-- Found west (found suitable version "0.14.0", minimum required is "0.7.1")
-- Board: nrf52840dk_nrf52840
-- Found host-tools: zephyr 0.15.1 (C:/ncs/toolchains/v2.2.0/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.15.1 (C:/ncs/toolchains/v2.2.0/opt/zephyr-sdk)
-- Found Dtc: C:/ncs/toolchains/v2.2.0/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found BOARD.dts: C:/ncs/v2.2.0/zephyr/boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840.dts
-- Generated zephyr.dts: C:/L/src/Nordic/radio_test_220/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/L/src/Nordic/radio_test_220/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: C:/L/src/Nordic/radio_test_220/build/zephyr/dts.cmake
Parsing C:/L/src/Nordic/radio_test_220/Kconfig
C:/ncs/v2.2.0/zephyr/scripts/kconfig/kconfig.py: C:/L/src/Nordic/radio_test_220/Kconfig:27: 'C:/L/src/Nordic/radio_test_220\../../bluetooth/direct_test_mode/src/fem/Kconfig' not found (in 'rsource "../../bluetooth/direct_test_mode/src/fem/Kconfig"'). Check that environment variables are set correctly (e.g. $srctree, which is set to 'C:/ncs/v2.2.0/zephyr'). Also note that unset environment variables expand to the empty string.
CMake Error at C:/ncs/v2.2.0/zephyr/cmake/modules/kconfig.cmake:328 (message):
command failed with return code: 1
Call Stack (most recent call first):
C:/ncs/v2.2.0/nrf/cmake/modules/kconfig.cmake:29 (include)
C:/ncs/v2.2.0/zephyr/cmake/modules/zephyr_default.cmake:108 (include)
C:/ncs/v2.2.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
C:/ncs/v2.2.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
CMakeLists.txt:32 (find_package)

-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: 'c:\ncs\toolchains\v2.2.0\opt\bin\cmake.EXE' '-DWEST_PYTHON=c:\ncs\toolchains\v2.2.0\opt\bin\python.exe' '-Bc:\L\src\Nordic\radio_test_220\build' -GNinja -DBOARD=nrf52840dk_nrf52840 -DNCS_TOOLCHAIN_VERSION:STRING=NONE '-DBOARD_ROOT:STRING=c:/L/src/Nordic/peripheral_lbs_230rc1;c:/L/src/Nordic/radio_test_230rc1;c:/L/src/Nordic/direct_test_mode_230rc1;c:/L/src/Nordic/peripheral_hr_230rc1;c:/L/src/Nordic/peripheral_hr_220;c:/L/src/Nordic/radio_test_220' '-Sc:\L\src\Nordic\radio_test_220'

RE: Unable to Build "RF Test sample" of nRF 52832 with nRF Connect SDK (v2.3.0. rc1).

Hoko — Wed, 01 Mar 2023 09:05:05 GMT

The error log as of v2.3.0-rc1 is below, but I'll go back to 2.2 and try again.

Thanks

- log -

west build -t clean --build-dir c:\L\src\Nordic\radio_test_230rc1\build

-- west build: generating a build system
Loading Zephyr default modules (Zephyr base (cached)).
-- Application: C:/L/src/Nordic/radio_test_230rc1
-- Cache files will be written to: C:/ncs/v2.3.0-rc1/zephyr/.cache
-- Zephyr version: 3.2.99 (C:/ncs/v2.3.0-rc1/zephyr)
-- Found west (found suitable version "0.14.0", minimum required is "0.7.1")
-- Board: nrf52840dk_nrf52840
-- Found host-tools: zephyr 0.15.2 (C:/ncs/toolchains/v2.3.0-rc1/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.15.2 (C:/ncs/toolchains/v2.3.0-rc1/opt/zephyr-sdk)
-- Found BOARD.dts: C:/ncs/v2.3.0-rc1/zephyr/boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840.dts
-- Generated zephyr.dts: C:/L/src/Nordic/radio_test_230rc1/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/L/src/Nordic/radio_test_230rc1/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: C:/L/src/Nordic/radio_test_230rc1/build/zephyr/dts.cmake
Parsing C:/L/src/Nordic/radio_test_230rc1/Kconfig
C:/ncs/v2.3.0-rc1/zephyr/scripts/kconfig/kconfig.py: C:/L/src/Nordic/radio_test_230rc1/Kconfig:27: 'C:/L/src/Nordic/radio_test_230rc1\../../bluetooth/direct_test_mode/src/fem/Kconfig' not found (in 'rsource "../../bluetooth/direct_test_mode/src/fem/Kconfig"'). Check that environment variables are set correctly (e.g. $srctree, which is set to 'C:/ncs/v2.3.0-rc1/zephyr'). Also note that unset environment variables expand to the empty string.
CMake Error at C:/ncs/v2.3.0-rc1/zephyr/cmake/modules/kconfig.cmake:328 (message):
command failed with return code: 1
Call Stack (most recent call first):
C:/ncs/v2.3.0-rc1/nrf/cmake/modules/kconfig.cmake:29 (include)
C:/ncs/v2.3.0-rc1/zephyr/cmake/modules/zephyr_default.cmake:108 (include)
C:/ncs/v2.3.0-rc1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
C:/ncs/v2.3.0-rc1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:97 (include_boilerplate)
CMakeLists.txt:32 (find_package)

-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: 'c:\ncs\toolchains\v2.3.0-rc1\opt\bin\cmake.EXE' '-DWEST_PYTHON=c:\ncs\toolchains\v2.3.0-rc1\opt\bin\python.exe' '-Bc:\L\src\Nordic\radio_test_230rc1\build' -GNinja '-SC:\L\src\Nordic\radio_test_230rc1'

RE: Unable to Build "RF Test sample" of nRF 52832 with nRF Connect SDK (v2.3.0. rc1).

Sigurd Hellesvik — Wed, 01 Mar 2023 08:22:29 GMT

[quote user="Hoko"]The example in 2.3.0.rc1 no longer has direct_test_mode code. Could this be the cause?[/quote]

Earlier, you say you have the same issue on 2.2.0 and 2.0.2, right?
In that case, I suspect it is not related to 2.3.0-rc1.

Do you see the same issue for samples inside the nRF Connect SDK?

Try to shorten the path of your example as well. Does this help?

Regards,
Sigurd Hellesvik

RE: Unable to Build "RF Test sample" of nRF 52832 with nRF Connect SDK (v2.3.0. rc1).

Hoko — Wed, 01 Mar 2023 07:16:00 GMT

I tried shortening the PATH, but it was the same. The example in 2.3.0.rc1 no longer has direct_test_mode code. Could this be the cause?
The error code below also says so.

Naturally, the situation is the same in direct_test_mode.

'C:/Users/hiroa/Documents/PlatformIO/Projects/radio_test_230_rc1\../../bluetooth/direct_test_mode/src/fem/Kconfig' not found

If so, please tell me another try method.

Thanks.

RE: Unable to Build "RF Test sample" of nRF 52832 with nRF Connect SDK (v2.3.0. rc1).

Sigurd Hellesvik — Mon, 27 Feb 2023 12:22:15 GMT

Hi,

Windows is not able to handle path lengths longer than 256 characters. nRF Connect SDK will generate build folders with many sub-folders when building. If the path to the nRF Connect SDK install directory is too long, this could cause your build to fail. Change the install directory destination to fix this. You can change this in the Toolchain Manager Settings menu. For example, change from "C:/Users/longusername/Desktop/nrf-connect-sdk" to "C:/ncs/".

Regards,
Sigurd Hellesvik