getting started: can't load project file: 'solution load command failed (-1)'

RE: getting started: can't load project file: 'solution load command failed (-1)'

Nobel Kuo — Fri, 01 Feb 2019 22:43:11 GMT

Sorry. I mean the problem is possibly caused by skipping these steps. Because I missed the pip3 steps, and appeared the same error message.

RE: getting started: can't load project file: 'solution load command failed (-1)'

Bjørn Kvaale — Fri, 01 Feb 2019 15:14:47 GMT

Why would you want to skip those steps? I believe they are required to properly setup the Nordic Connect SDK.

RE: getting started: can't load project file: 'solution load command failed (-1)'

Nobel Kuo — Fri, 01 Feb 2019 04:57:14 GMT

I think you may skip some instructions of the 3rd step while installing nRF Connect SDK

RE: getting started: can't load project file: 'solution load command failed (-1)'

Bjørn Kvaale — Mon, 14 Jan 2019 09:47:00 GMT

I just tested running the whole nRF91 Getting Started Assistant v0.5.1 from nRF Connect v2.6.0. I have been running it on a Mac Book Air from Mid 2011 running macOS Sierra Version 10.12.6. The mac is so old that I am not able to upgrade to the latest & greatest OS. It should work with newer versions of MacOS too.

I followed the whole getting started assistant & was able to successfully open & compile the secure boot example. Unfortunately, I was unable to reproduce your issue. The output I received when opening the asset tracker example (i.e. from Output window, Show: Transcript, Output tab) was a lot shorter:

Preparing project 'zephyr/kernel/libkernel.a'
Restoring state from previous session
Preparing to load data
Loading session data from file
SEGGER Embedded Studio is ready to use

For some reason, the Getting Started Assistant suggests to extract gnuarmemb in the /opt/gnuarmemb folder. At first, I could not find the opt folder, so I decided to place it in the /Applications/gnuarmemb folder. I was able to successfully open & build the secure boot example that way.

Next, I tried placing the gnuarmemb folder inside /usr/local/opt/gnuarmemb. That worked too. The path of the gnuarmemb folder was the only thing that I changed compared with what the Getting Started Assistant said to do. Hopefully that will help in solving your problem!

RE: getting started: can't load project file: 'solution load command failed (-1)'

Ray — Mon, 07 Jan 2019 14:52:42 GMT

I just rm -rf'ed the old sdk, and downloaded and replaced it with:
gcc-arm-none-eabi-7-2018-q2-update-mac.tar.bz2

I then restarted segger. Same failure:

Loading solution secure_boot.emProject
Executing load commands
/usr/local/bin/cmake -GNinja -DBOARD=nrf9160_pca10090 -DBOARD_DIR=/Users/rozzie/dev/nrf/ncs/zephyr/boards/arm/nrf9160_pca10090 -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=/opt/gnuarmemb -B/Users/rozzie/dev/nrf/ncs/nrf/samples/nrf9160/secure_boot/build -H/Users/rozzie/dev/nrf/ncs/nrf/samples/nrf9160/secure_boot -DPYTHON_EXECUTABLE=/usr/local/bin/python3 -DCMAKE_MAKE_PROGRAM=/usr/local/bin/ninja -DDTC=/usr/local/bin/dtc -DDTC_OVERLAY_FILE=/Users/rozzie/dev/nrf/ncs/nrf/samples/nrf9160/secure_boot/nrf9160_pca10090.overlay
-- Found PythonInterp: /usr/local/bin/python3 (found suitable version "3.7.2", minimum required is "3.4") 
-- Selected BOARD nrf9160_pca10090
Zephyr version: 1.13.99
Parsing Kconfig tree in /Users/rozzie/dev/nrf/ncs/zephyr/Kconfig
Loading /Users/rozzie/dev/nrf/ncs/nrf/samples/nrf9160/secure_boot/build/zephyr/.config as base
-- Loading /Users/rozzie/dev/nrf/ncs/zephyr/boards/arm/nrf9160_pca10090/nrf9160_pca10090.dts as base
-- Overlaying /Users/rozzie/dev/nrf/ncs/zephyr/dts/common/common.dts
-- Overlaying /Users/rozzie/dev/nrf/ncs/nrf/samples/nrf9160/secure_boot/nrf9160_pca10090.overlay
nrf9160_pca10090.dts_compiled: Warning (unit_address_format): /soc/adc@0x5000e000: unit name should not have leading "0x"
nrf9160_pca10090.dts_compiled: Warning (unit_address_format): /soc/ficr@00ff0000: unit name should not have leading 0s
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/uart@50008000: duplicate unit-address (also used in node /soc/i2c@50008000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/uart@50009000: duplicate unit-address (also used in node /soc/i2c@50009000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/uart@5000a000: duplicate unit-address (also used in node /soc/i2c@5000a000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/uart@5000b000: duplicate unit-address (also used in node /soc/i2c@5000b000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/uart@50008000: duplicate unit-address (also used in node /soc/spi@50008000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/i2c@50008000: duplicate unit-address (also used in node /soc/spi@50008000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/uart@50009000: duplicate unit-address (also used in node /soc/spi@50009000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/i2c@50009000: duplicate unit-address (also used in node /soc/spi@50009000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/uart@5000a000: duplicate unit-address (also used in node /soc/spi@5000a000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/i2c@5000a000: duplicate unit-address (also used in node /soc/spi@5000a000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/uart@5000b000: duplicate unit-address (also used in node /soc/spi@5000b000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/i2c@5000b000: duplicate unit-address (also used in node /soc/spi@5000b000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/clock@50005000: duplicate unit-address (also used in node /soc/power@50005000)
-- Cache files will be written to: /Users/rozzie/Library/Caches/zephyr
-- The C compiler identification is GNU 7.3.1
-- The CXX compiler identification is GNU 7.3.1
-- The ASM compiler identification is GNU
-- Found assembler: /opt/gnuarmemb/bin/arm-none-eabi-gcc
-- Performing Test toolchain_is_ok
-- Performing Test toolchain_is_ok - Success
CMake Warning (dev) at /Users/rozzie/dev/nrf/ncs/zephyr/cmake/extensions.cmake:837 (target_link_libraries):
  Policy CMP0079 is not set: target_link_libraries allows use with targets in
  other directories.  Run "cmake --help-policy CMP0079" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  Target

    zephyr_interface

  is not created in this directory.  For compatibility with older versions of
  CMake, link library

    -mabi=aapcs

  will be looked up in the directory in which the target was created rather
  than in this calling directory.
Call Stack (most recent call first):
  /Users/rozzie/dev/nrf/ncs/zephyr/cmake/extensions.cmake:1055 (target_link_libraries_ifdef)
  /Users/rozzie/dev/nrf/ncs/zephyr/cmake/extensions.cmake:115 (target_ld_options)
  /Users/rozzie/dev/nrf/ncs/zephyr/arch/arm/CMakeLists.txt:20 (zephyr_ld_options)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at /Users/rozzie/dev/nrf/ncs/zephyr/cmake/extensions.cmake:837 (target_link_libraries):
  Policy CMP0079 is not set: target_link_libraries allows use with targets in
  other directories.  Run "cmake --help-policy CMP0079" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  Target

    zephyr_interface

  is not created in this directory.  For compatibility with older versions of
  CMake, link library

    -march=armv8-m.main+dsp

  will be looked up in the directory in which the target was created rather
  than in this calling directory.
Call Stack (most recent call first):
  /Users/rozzie/dev/nrf/ncs/zephyr/cmake/extensions.cmake:1055 (target_link_libraries_ifdef)
  /Users/rozzie/dev/nrf/ncs/zephyr/cmake/extensions.cmake:115 (target_ld_options)
  /Users/rozzie/dev/nrf/ncs/zephyr/arch/arm/CMakeLists.txt:20 (zephyr_ld_options)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring done
-- Generating done
-- Build files have been written to: /Users/rozzie/dev/nrf/ncs/nrf/samples/nrf9160/secure_boot/build
/Applications/SEGGER NORDIC/bin/ninja_import zephyr/zephyr.elf zephyr/liboffsets.a zephyr/liboutput_lib.a zephyr/libpriv_stacks_output_lib.a zephyr/app_sizing_prebuilt.elf zephyr/zephyr_prebuilt.elf zephyr/zephyr_app_sizing_prebuilt.elf zephyr/priv_stacks_prebuilt.elf
Project load failed
Reported error: solution load command failed (-1)

RE: getting started: can't load project file: 'solution load command failed (-1)'

Bjørn Kvaale — Mon, 07 Jan 2019 14:02:55 GMT

Most likely the issue is that you are using v8 of the armemb toolchain. There is a bug when compiling nRF91 examples from Nordic Connect SDK with this version which has already been reported. The solution for now is to download & use the v7 (q2 2018) of the armemb toolchain. That should most likely make this error disappear.

RE: getting started: can't load project file: 'solution load command failed (-1)'

Ray — Mon, 07 Jan 2019 13:22:39 GMT

Here is full output:

Loading solution secure_boot.emProject
Executing load commands
/usr/local/bin/cmake -GNinja -DBOARD=nrf9160_pca10090 -DBOARD_DIR=/Users/rozzie/dev/nrf/ncs/zephyr/boards/arm/nrf9160_pca10090 -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=/opt/gnuarmemb -B/Users/rozzie/dev/nrf/ncs/nrf/samples/nrf9160/secure_boot/build -H/Users/rozzie/dev/nrf/ncs/nrf/samples/nrf9160/secure_boot -DPYTHON_EXECUTABLE=/usr/local/bin/python3 -DCMAKE_MAKE_PROGRAM=/usr/local/bin/ninja -DDTC=/usr/local/bin/dtc -DDTC_OVERLAY_FILE=/Users/rozzie/dev/nrf/ncs/nrf/samples/nrf9160/secure_boot/nrf9160_pca10090.overlay
-- Found PythonInterp: /usr/local/bin/python3 (found suitable version "3.7.2", minimum required is "3.4") 
-- Selected BOARD nrf9160_pca10090
Zephyr version: 1.13.99
Parsing Kconfig tree in /Users/rozzie/dev/nrf/ncs/zephyr/Kconfig
Loading /Users/rozzie/dev/nrf/ncs/nrf/samples/nrf9160/secure_boot/build/zephyr/.config as base
-- Loading /Users/rozzie/dev/nrf/ncs/zephyr/boards/arm/nrf9160_pca10090/nrf9160_pca10090.dts as base
-- Overlaying /Users/rozzie/dev/nrf/ncs/zephyr/dts/common/common.dts
-- Overlaying /Users/rozzie/dev/nrf/ncs/nrf/samples/nrf9160/secure_boot/nrf9160_pca10090.overlay
nrf9160_pca10090.dts_compiled: Warning (unit_address_format): /soc/adc@0x5000e000: unit name should not have leading "0x"
nrf9160_pca10090.dts_compiled: Warning (unit_address_format): /soc/ficr@00ff0000: unit name should not have leading 0s
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/uart@50008000: duplicate unit-address (also used in node /soc/i2c@50008000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/uart@50009000: duplicate unit-address (also used in node /soc/i2c@50009000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/uart@5000a000: duplicate unit-address (also used in node /soc/i2c@5000a000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/uart@5000b000: duplicate unit-address (also used in node /soc/i2c@5000b000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/uart@50008000: duplicate unit-address (also used in node /soc/spi@50008000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/i2c@50008000: duplicate unit-address (also used in node /soc/spi@50008000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/uart@50009000: duplicate unit-address (also used in node /soc/spi@50009000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/i2c@50009000: duplicate unit-address (also used in node /soc/spi@50009000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/uart@5000a000: duplicate unit-address (also used in node /soc/spi@5000a000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/i2c@5000a000: duplicate unit-address (also used in node /soc/spi@5000a000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/uart@5000b000: duplicate unit-address (also used in node /soc/spi@5000b000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/i2c@5000b000: duplicate unit-address (also used in node /soc/spi@5000b000)
nrf9160_pca10090.dts_compiled: Warning (unique_unit_address): /soc/clock@50005000: duplicate unit-address (also used in node /soc/power@50005000)
-- Cache files will be written to: /Users/rozzie/Library/Caches/zephyr
-- The C compiler identification is GNU 8.2.1
-- The CXX compiler identification is GNU 8.2.1
-- The ASM compiler identification is GNU
-- Found assembler: /opt/gnuarmemb/bin/arm-none-eabi-gcc
-- Performing Test toolchain_is_ok
-- Performing Test toolchain_is_ok - Success
CMake Warning (dev) at /Users/rozzie/dev/nrf/ncs/zephyr/cmake/extensions.cmake:837 (target_link_libraries):
  Policy CMP0079 is not set: target_link_libraries allows use with targets in
  other directories.  Run "cmake --help-policy CMP0079" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  Target

    zephyr_interface

  is not created in this directory.  For compatibility with older versions of
  CMake, link library

    -mabi=aapcs

  will be looked up in the directory in which the target was created rather
  than in this calling directory.
Call Stack (most recent call first):
  /Users/rozzie/dev/nrf/ncs/zephyr/cmake/extensions.cmake:1055 (target_link_libraries_ifdef)
  /Users/rozzie/dev/nrf/ncs/zephyr/cmake/extensions.cmake:115 (target_ld_options)
  /Users/rozzie/dev/nrf/ncs/zephyr/arch/arm/CMakeLists.txt:20 (zephyr_ld_options)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at /Users/rozzie/dev/nrf/ncs/zephyr/cmake/extensions.cmake:837 (target_link_libraries):
  Policy CMP0079 is not set: target_link_libraries allows use with targets in
  other directories.  Run "cmake --help-policy CMP0079" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  Target

    zephyr_interface

  is not created in this directory.  For compatibility with older versions of
  CMake, link library

    -march=armv8-m.main+dsp

  will be looked up in the directory in which the target was created rather
  than in this calling directory.
Call Stack (most recent call first):
  /Users/rozzie/dev/nrf/ncs/zephyr/cmake/extensions.cmake:1055 (target_link_libraries_ifdef)
  /Users/rozzie/dev/nrf/ncs/zephyr/cmake/extensions.cmake:115 (target_ld_options)
  /Users/rozzie/dev/nrf/ncs/zephyr/arch/arm/CMakeLists.txt:20 (zephyr_ld_options)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring done
-- Generating done
-- Build files have been written to: /Users/rozzie/dev/nrf/ncs/nrf/samples/nrf9160/secure_boot/build
/Applications/SEGGER NORDIC/bin/ninja_import zephyr/zephyr.elf zephyr/liboffsets.a zephyr/liboutput_lib.a zephyr/libpriv_stacks_output_lib.a zephyr/app_sizing_prebuilt.elf zephyr/zephyr_prebuilt.elf zephyr/zephyr_app_sizing_prebuilt.elf zephyr/priv_stacks_prebuilt.elf
Project load failed
Reported error: solution load command failed (-1)

RE: getting started: can't load project file: 'solution load command failed (-1)'

Ray — Mon, 07 Jan 2019 13:17:55 GMT

I downloaded:

gcc-arm-none-eabi-8-2018-q4-major-mac.tar.bz2

RE: getting started: can't load project file: 'solution load command failed (-1)'

Bjørn Kvaale — Mon, 07 Jan 2019 12:40:56 GMT

Hi Ray,

Could you please switch the Tab in the Output window from Tasks to Output like shown below & upload the screenshot? This can often help finding the cause of the issue.

Also, which version of the gnuarmemb toolchain did you download? v7 or v8?

RE: getting started: can't load project file: 'solution load command failed (-1)'

brendanyounger — Mon, 07 Jan 2019 05:34:20 GMT

This does not work. OP was on Mac OS X. I am also having the same problem.

RE: getting started: can't load project file: 'solution load command failed (-1)'

RicFlair — Mon, 07 Jan 2019 04:02:47 GMT

Hey Ray, I had a similar issue. Check the File Paths for CMakeLists.txt and Build Directory. What worked for me was I placed the nrf9160 folder from samples into the samples directory for zephyr and was able to get the project to load.

For example:

C:/Nordic/ncs/zephyr/samples/nrf9160/asset_tracker/CMakeLists.txt

C:/Nordic/ncs/zephyr/samples/nrf9160/asset_tracker/build