Import nRF Connect SDK Example into Segger Embedded Studio Failure

[chrismy]

Hi,

I have just setup the nRF Connect SDK for the first time.  I am running Ubuntu 20.04 in a Virtual Machine.  I followed the instructions in the "Getting Started Assistant".  I initially has some errors installing the "Additional Python Dependencies":

These errors have since gone away.  Ie when I re-run "pip3 install ..." command I don't get the error again.  Everything else seemed to be successful.  All the "Verify" steps gave the thumbs up.

I have tried to open the "Blinky" project for the nrf52dk_nrf52832.  It fails with "create_nordic_project.py failed".

Do you have any suggestions re: where to start to solve the problem?  Is there a log file somewhere that may suggest what the problem is?

Thanks,

Chris.

[chrismy]

Hi Carl,

Sorry for the delayed reply.  Log shown below.  The TOOLCHAIN_HOME folder seems to be correct (ie it exists on my system).  The CROSS_COMPILE path doesn't seem right (there's an extra bin in there).  And the arm-none-eabi- part doesn't seem right.  Or is that just a prefix, and "gcc" (or similar will be appended to the end?  Where abouts is the CROSS_COMPILE variable defined?

Thanks,

Chris.

Creating solution blinky.emProject
cmake -GNinja -DBOARD=nrf52dk_nrf52832 -DBOARD_DIR=/home/chris/Nordic/nRFConnect/SDK/ncs/zephyr/boards/arm/nrf52dk_nrf52832 -B/home/chris/Nordic/nRFConnect/SDK/ncs/zephyr/samples/basic/blinky/build_nrf52dk_nrf52832 -S/home/chris/Nordic/nRFConnect/SDK/ncs/zephyr/samples/basic/blinky -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=/opt/gnuarmemb/bin -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=/home/chris/Nordic/arm_segger_embedded_studio_v550d_linux_x64_nordic/html/configure_nordic_project_menuconfig.py
-- Application: /home/chris/Nordic/nRFConnect/SDK/ncs/zephyr/samples/basic/blinky
-- Zephyr version: 2.6.0-rc1 (/home/chris/Nordic/nRFConnect/SDK/ncs/zephyr), build: v2.6.0-rc1-ncs1
-- Found west (found suitable version "0.11.0", minimum required is "0.7.1")
-- Board: nrf52dk_nrf52832
-- Cache files will be written to: /home/chris/.cache/zephyr
-- Found dtc: /usr/bin/dtc (found suitable version "1.5.0", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (/opt/gnuarmemb/bin)
-- Configuring incomplete, errors occurred!
Including boilerplate (Zephyr base (cached)): /home/chris/Nordic/nRFConnect/SDK/ncs/zephyr/cmake/app/boilerplate.cmake
CMake Error at /home/chris/Nordic/nRFConnect/SDK/ncs/zephyr/cmake/compiler/gcc/generic.cmake:8 (message):
Zephyr was unable to find the toolchain. Is the environment misconfigured?

User-configuration:

ZEPHYR_TOOLCHAIN_VARIANT: gnuarmemb

Internal variables:

CROSS_COMPILE: /opt/gnuarmemb/bin/bin/arm-none-eabi-

TOOLCHAIN_HOME: /opt/gnuarmemb/bin

Call Stack (most recent call first):
/home/chris/Nordic/nRFConnect/SDK/ncs/zephyr/cmake/generic_toolchain.cmake:42 (include)
/home/chris/Nordic/nRFConnect/SDK/ncs/zephyr/cmake/app/boilerplate.cmake:553 (include)
/home/chris/Nordic/nRFConnect/SDK/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
/home/chris/Nordic/nRFConnect/SDK/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:40 (include_boilerplate)
CMakeLists.txt:4 (find_package)



error: cmake failed
create_nordic_project.py failed (1)

[Carl Richard]

Hello!

Could you try to change GNUARMEMB_TOOLCHAIN_PATH to "/opt/gnuarmemb". I.e. excluding the "bin" from the path.

chrismy said:

CROSS_COMPILE: /opt/gnuarmemb/bin/bin/arm-none-eabi-

 As you can see the "bin" is appended by the build system.

Best regards,
Carl Richard