Sysprogs forums › Forums › VisualGDB › NordicConnectSDK project creation fails
- This topic has 3 replies, 2 voices, and was last updated 3 years, 4 months ago by support.
-
AuthorPosts
-
July 8, 2021 at 01:55 #30913SdBParticipant
Moin,
using
Microsoft Visual Studio Enterprise 2019 Version 16.10.3
VisualGDB 5.6 beta 3 Build 4182
I tried to create a NRFConnectSDK project. The creation failed due to CMake error stating that a file is not found (See details below).
It complains about the file C:/SysGCC/NRFConnectSDK/v1.6.0/zephyr/cmake/toolchain/gccarmemb/generic.cmake not being found. The file is present but in the subfolder gnuarmemb rather than the expected gccarmbed. A previous ConnectSDK I tried (1.5.1) contains the same naming with gnuarmemb. Do you have a hint how to fix this?
Running CMake: C:\Users\stefa\AppData\Local\VisualGDB\CMake\bin\cmake.exe ../../.. -G “Ninja” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_MAKE_PROGRAM=”C:/Program Files (x86)/Sysprogs/VisualGDB/ninja.exe” -DBOARD=nrf52840dk_nrf52840
Including boilerplate (Zephyr base): C:/SysGCC/NRFConnectSDK/v1.6.0/zephyr/cmake/app/boilerplate.cmake
— Application: C:/Dev/EmbeddedSpielwiese/EmbeddedProject5
— Zephyr version: 2.6.0-rc1 (C:/SysGCC/NRFConnectSDK/v1.6.0/zephyr), build: v2.6.0-rc1-ncs1
— Found Python3: C:/SysGCC/NRFConnectSDK/v1.6.0/python-env/Scripts/python.exe (found suitable exact version “3.7.4”) found components: Interpreter
— Found west (found suitable version “0.11.0”, minimum required is “0.7.1”)
— Board: nrf52840dk_nrf52840
— Cache files will be written to: C:/SysGCC/NRFConnectSDK/v1.6.0/zephyr/.cache
— Found BOARD.dts: C:/SysGCC/NRFConnectSDK/v1.6.0/zephyr/boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840.dts
CMake Error at C:/SysGCC/NRFConnectSDK/v1.6.0/zephyr/cmake/generic_toolchain.cmake:36 (include):
include could not find requested file:C:/SysGCC/NRFConnectSDK/v1.6.0/zephyr/cmake/toolchain/gccarmemb/generic.cmake
Call Stack (most recent call first):
C:/SysGCC/NRFConnectSDK/v1.6.0/zephyr/cmake/app/boilerplate.cmake:553 (include)
C:/SysGCC/NRFConnectSDK/v1.6.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
C:/SysGCC/NRFConnectSDK/v1.6.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:35 (include_boilerplate)
CMakeLists.txt:9 (find_package)— Found devicetree overlay: C:/Dev/EmbeddedSpielwiese/EmbeddedProject5/boards/nrf52840dk_nrf52840.overlay
— Configuring incomplete, errors occurred!
CMake Error at C:/SysGCC/NRFConnectSDK/v1.6.0/zephyr/cmake/dts.cmake:157 (message):
command failed with return code: Das System kann die angegebene Datei nicht
finden
Call Stack (most recent call first):
C:/SysGCC/NRFConnectSDK/v1.6.0/zephyr/cmake/app/boilerplate.cmake:554 (include)
C:/SysGCC/NRFConnectSDK/v1.6.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
C:/SysGCC/NRFConnectSDK/v1.6.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:35 (include_boilerplate)
CMakeLists.txt:9 (find_package)System.Exception: CMake exited with code 1
July 8, 2021 at 09:24 #30922supportKeymasterHi,
We have rechecked the NRFConnect SDK 1.6.0 and it worked just fine with our latest toolchain (GCC 9.3.1). Please try deleting the SDK and reinstalling it with VisualGDB. Please make sure the SDK installation succeeds without any errors (e.g. due to insufficient disk space).
If the problem persists, please share the complete steps to reproduce it from scratch per our problem reporting guidelines, including all the relevant screenshots.
July 9, 2021 at 03:44 #30932SdBParticipantI reproduced the issue by installing Visual Studio Enterprise on a fresh installation of Windows 10. Then installed GIT (x86) and VisualGDB.
During creation of the NRF ConnectSDK using the project wizard I installed the ARM toolchain and the NRFConnectSDK. Project creation failed with the reported error.
July 14, 2021 at 19:26 #30957supportKeymasterThanks for emailing us the detailed repro instructions. We have double-checked everything and confirmed that NRFConnect SDK 1.6.0 was indeed not working out-of-the-box. It turned out, we could not reproduced it initially due to an old value cached in our test environment.
The problem was caused by this commit, removing the deprecated gccarmemb toolchain variant that VisualGDB used due to backward compatibility.
We have updated VisualGDB to use the correct gnuarmemb name: VisualGDB-5.6.5.4230.msi
If you need to build older NRFConnect versions using the old gccarmemb name, you can edit the NRFConnect/GCCToolchainName tag in the %VISUALGDB_DIR%\Rules\RegularExpressions.xml file and simply restart Visual Studio.
-
AuthorPosts
- You must be logged in to reply to this topic.