nRF9160 SES project load

RE: nRF9160 SES project load

ThL — Wed, 03 Apr 2019 16:07:25 GMT

Dear Bjorn,

No answer here but since I just ran into the same issue today, I can answer you that your rollback works perfectly. Thanks a lot for your support.

Best regards,

Thierry

RE: nRF9160 SES project load

Otso Jousimaa — Mon, 04 Mar 2019 09:18:39 GMT

This solved my problem. I had a space in CMake executable, i.e. `/usr/local/bin/cmake `. After removing the space I can open the project.

RE: nRF9160 SES project load

Torsten Rasmussen — Mon, 04 Mar 2019 08:31:45 GMT

The only way I have been able to reproduce this, is if CMake is not in the PATH when launching SES.

If launching SES from the command line, then you can easily verify that CMake is in PATH by trying to type `cmake --version`

which should give you the version of the installed CMake.

Another approach to ensure the correct CMake is used by SES is to specify it directly in SES.

Go to: Tools -> Options

Then find: `nRF Connect`

Under executables, find `CMake Executeable`, which is probably set to `None`

Specify the full path to your CMake executable, e.g. `/usr/local/bin/cmake` or `c:\Program Files\CMake\bin\`

Delete the existing build folder or use a new one.

Then try to open the project again, and see if SES is able to invoke CMake.

RE: nRF9160 SES project load

Bjørn Kvaale — Fri, 01 Mar 2019 08:00:29 GMT

riw Could you please open a new devzone case? Thank you.

RE: nRF9160 SES project load

riw — Thu, 28 Feb 2019 13:55:06 GMT

I had the same problem, only to realize I missed installing ninja and some other stuff. Guess I was not paying enough attention. That didnt get me much further than a more verbose error log though. I have made no changes to the code, and have the right tags aswell, why Im very confused as to why UART_1 and UART_2 makes a fuzz here... Perhaps Bjørn has an idea what this might be?

Loading solution hci_uart.emProject
Executing load commands
cmake -GNinja -DBOARD=nrf52840_pca10090 -DBOARD_DIR=C:/kod/1852/ncs/zephyr/boards/arm/nrf52840_pca10090 -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=C:/gnuarmemb -BC:/kod/1852/ncs/zephyr/samples/bluetooth/hci_uart/build -HC:/kod/1852/ncs/zephyr/samples/bluetooth/hci_uart -DDTC_OVERLAY_FILE=C:/kod/1852/ncs/zephyr/samples/bluetooth/hci_uart/nrf52840_pca10090.overlay
-- Found PythonInterp: C:/Users/riw/AppData/Local/Programs/Python/Python37-32/python.exe (found suitable version "3.7.2", minimum required is "3.4")
-- Selected BOARD nrf52840_pca10090
Zephyr version: 1.13.99

warning: the choice symbol UART_1 (defined at drivers\serial\Kconfig.stm32:22, ..\nrf\lib\at_host\Kconfig:24) is defined with a prompt outside the choice

warning: the choice symbol UART_2 (defined at drivers\serial\Kconfig.stm32:31, ..\nrf\lib\at_host\Kconfig:26) is defined with a prompt outside the choice
Parsing Kconfig tree in C:/kod/1852/ncs/zephyr/Kconfig
Loading C:/kod/1852/ncs/zephyr/boards/arm/nrf52840_pca10090/nrf52840_pca10090_defconfig as base
Merging nrf52840_pca10090.conf

Error: Aborting due to non-whitelisted Kconfig warning 'warning: the choice symbol UART_1 (defined
at drivers\serial\Kconfig.stm32:22, ..\nrf\lib\at_host\Kconfig:24) is defined with a prompt outside
the choice'. Note: If this warning doesn't point to an actual problem, you can add it to the
whitelist at the top of C:/kod/1852/ncs/zephyr/scripts/kconfig/kconfig.py.

CMake Error at C:/kod/1852/ncs/zephyr/cmake/kconfig.cmake:159 (message):
command failed with return code: 1
Call Stack (most recent call first):
C:/kod/1852/ncs/zephyr/cmake/app/boilerplate.cmake:282 (include)
CMakeLists.txt:10 (include)

-- Configuring incomplete, errors occurred!
Project load failed
Reported error: solution load command failed (1)

RE: nRF9160 SES project load

RicFlair — Wed, 27 Feb 2019 16:17:15 GMT

Yea that works but I am trying to figure out why ninja flash will not work.

I am able to compile and build but unable to flash via cmd prompt.

RE: nRF9160 SES project load

RicFlair — Wed, 27 Feb 2019 16:11:36 GMT

Those work but what are the steps on using cmake and ninja flash? What I was able to do was load the current master into SES and it successfully opens in SES. Then I use cmd prompt and navigate to the build directory. I then send ninja and it builds the project.

I then try to use ninja flash and that's where I'm seeing the above errors.

I am even at the point where after I do all of that I can successfully build the project using SES since after I send ninja via command prompt. I just am unable to flash and receive a failed to write to memory error.

RE: nRF9160 SES project load

Bjørn Kvaale — Wed, 27 Feb 2019 16:01:04 GMT

Otso Jousimaa I have asked about this internally & will let you know when I receive an update.

RE: nRF9160 SES project load

Bjørn Kvaale — Wed, 27 Feb 2019 15:46:56 GMT

RicFlair The master's will not work with Segger Embedded Studio. Please roll back to the v0.3.0 tag using:

Please let us know if it works.

RE: nRF9160 SES project load

RicFlair — Sat, 23 Feb 2019 04:28:00 GMT

Hey Guys, Seeing similar behavior as well. I have the latest masters for all repos updated as of 2/22/19

Windows 10.
SES: V4.14
Phyton: 3.7.2
GNU Arm Embedded toolchain 7-2018-q2-update also tried q4(latest and no luck)

Hi Bjorn, Are you seeing these errors as well?

This is what I am seeing when building solution with SES:

Building ‘zephyr/include/generated/driver-validation.h’ from solution ‘build’ in configuration ‘Common’
1> Combining ‘zephyr/include/generated/driver-validation.h’
Building ‘zephyr/include/generated/kobj-types-enum.h’ from solution ‘build’ in configuration ‘Common’
1> Combining ‘zephyr/include/generated/kobj-types-enum.h’
Building ‘zephyr/include/generated/otype-to-str.h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/misc/generated/syscalls.json’ from solution ‘build’ in configuration ‘Common’
1> Combining ‘zephyr/misc/generated/syscalls.json’
Building ‘zephyr/include/generated/syscall_list.h’ from solution ‘build’ in configuration ‘Common’
1> Combining ‘zephyr/include/generated/syscall_list.h’
Building ‘zephyr/include/generated/syscall_dispatch.c’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/syscall_macros.h’ from solution ‘build’ in configuration ‘Common’
1> Combining ‘zephyr/include/generated/syscall_macros.h’
Building ‘zephyr/include/generated/offsets.h’ from solution ‘build’ in configuration ‘Common’
1> Combining ‘zephyr/include/generated/offsets.h’
1> Traceback (most recent call last):
1> File "C:/Nordic/ncs/zephyr/scripts/gen_offset_header.py", line 72, in <module>
1> input_file = open(args.input, 'rb')
1> FileNotFoundError: [Errno 2] No such file or directory: 'C:/Nordic/ncs/nrf/applications/asset_tracker/build/zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj'
Build failed

But When I send ninja clean via cmd prompt and then ninja to build the application this is what i see.

C:\Nordic\ncs\nrf\applications\asset_tracker\build>ninja clean
[1/1] Cleaning all built files...
Cleaning... 7 files.

C:\Nordic\ncs\nrf\applications\asset_tracker\build>ninja
[15/137] Building C object CMakeFiles/app.dir/src/main.c.obj
In file included from C:/Nordic/ncs/zephyr/include/sched_priq.h:9:0,
from C:/Nordic/ncs/zephyr/include/kernel_includes.h:23,
from C:/Nordic/ncs/zephyr/include/kernel.h:17,
from C:/Nordic/ncs/zephyr/include/zephyr.h:18,
from ../src/main.c:7:
../src/main.c: In function 'button_handler':
C:/Nordic/ncs/zephyr/include/misc/util.h:135:22: warning: left shift count is negative [-Wshift-count-negative]
#define BIT(n) (1UL << (n))
^
../src/main.c:56:22: note: in expansion of macro 'BIT'
#define FLIP_INPUT BIT(CONFIG_FLIP_INPUT - 1)
^~~
../src/main.c:727:57: note: in expansion of macro 'FLIP_INPUT'
if (IS_ENABLED(CONFIG_ACCEL_USE_SIM) && (has_changed & FLIP_INPUT)) {
^~~~~~~~~~
[47/137] Building C object zephyr/CMakeFiles/zephyr.dir/misc/generated/configs.c.obj
FAILED: zephyr/CMakeFiles/zephyr.dir/misc/generated/configs.c.obj
C:\gnuarmemb\bin\arm-none-eabi-gcc.exe -DBUILD_VERSION=v1.13.99-ncs1-4489-ga869285d26 -DKERNEL -DNRF9160_XXAA -D_FORTIFY_SOURCE=2 -D__LINUX_ERRNO_EXTENSIONS__ -D__ZEPHYR__=1 -IC:/Nordic/ncs/zephyr/kernel/include -IC:/Nordic/ncs/zephyr/arch/arm/include -IC:/Nordic/ncs/zephyr/include -IC:/Nordic/ncs/zephyr/include/drivers -Izephyr/include/generated -IC:/Nordic/ncs/zephyr/soc/arm/nordic_nrf/nrf91 -IC:/Nordic/ncs/zephyr/soc/arm/nordic_nrf/include -IC:/gnuarmemb/arm-none-eabi/include -IC:/Nordic/ncs/zephyr/ext/hal/cmsis/Include -IC:/Nordic/ncs/zephyr/ext/hal/nordic/nrfx -IC:/Nordic/ncs/zephyr/ext/hal/nordic/nrfx/drivers/include -IC:/Nordic/ncs/zephyr/ext/hal/nordic/nrfx/hal -IC:/Nordic/ncs/zephyr/ext/hal/nordic/nrfx/mdk -IC:/Nordic/ncs/zephyr/ext/hal/nordic/. -IC:/Nordic/ncs/zephyr/subsys/net/lib/sockets/. -IC:/Nordic/ncs/nrf/include -IC:/Nordic/ncs/nrf/ext/cjson/. -IC:/Nordic/ncs/nrf/subsys/net/lib/nrf_cloud/./include -IC:/Nordic/ncs/nrfxlib/bsdlib/include -IC:/Nordic/ncs/nrf/applications/asset_tracker/src -IC:/Nordic/ncs/nrfxlib/crypto/nrf_oberon/include -isystem c:/gnuarmemb/bin/../lib/gcc/arm-none-eabi/7.3.1/include -isystem c:/gnuarmemb/bin/../lib/gcc/arm-none-eabi/7.3.1/include-fixed -Os -g -Wall -Wformat -Wformat-security -Wno-format-zero-length -imacros C:/Nordic/ncs/nrf/applications/asset_tracker/build/zephyr/include/generated/autoconf.h -ffreestanding -Wno-main -fno-common -mthumb -mcpu=cortex-m33 -mfpu=fpv5-sp-d16 -mfloat-abi=hard -fno-asynchronous-unwind-tables -fno-pie -fno-pic -fno-strict-overflow -Wno-pointer-sign -Wno-unused-but-set-variable -fno-reorder-functions -fno-defer-pop -Werror=implicit-int -Wpointer-arith -ffunction-sections -fdata-sections -mabi=aapcs -march=armv8-m.main+dsp -std=c99 -MD -MT zephyr/CMakeFiles/zephyr.dir/misc/generated/configs.c.obj -MF zephyr\CMakeFiles\zephyr.dir\misc\generated\configs.c.obj.d -o zephyr/CMakeFiles/zephyr.dir/misc/generated/configs.c.obj -c zephyr/misc/generated/configs.c
In file included from C:/Nordic/ncs/zephyr/include/toolchain.h:21:0,
from zephyr/misc/generated/configs.c:3:
zephyr/misc/generated/configs.c: In function '_ConfigAbsSyms':
C:/Nordic/ncs/zephyr/include/toolchain/gcc.h:331:51: error: expected expression before ')' token
"\n\t.type\t" #name ",%%object" : : "n"(~(value)))
^
zephyr/misc/generated/configs.c:18:1: note: in expansion of macro 'GEN_ABSOLUTE_SYM'
GEN_ABSOLUTE_SYM(CONFIG_FLIP_INPUT, );
^~~~~~~~~~~~~~~~
C:/Nordic/ncs/zephyr/include/toolchain/gcc.h:331:51: error: expected expression before ')' token
"\n\t.type\t" #name ",%%object" : : "n"(~(value)))
^
zephyr/misc/generated/configs.c:25:1: note: in expansion of macro 'GEN_ABSOLUTE_SYM'
GEN_ABSOLUTE_SYM(CONFIG_TEMP_SIM_BUTTON, );
^~~~~~~~~~~~~~~~
[52/137] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/printk.c.obj
ninja: build stopped: subcommand failed.

Then I re-ran in SES and see the following.

Building ‘zephyr/include/generated/driver-validation.h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/kobj-types-enum.h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/otype-to-str.h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/misc/generated/syscalls.json’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/syscall_list.h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/syscall_dispatch.c’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/syscall_macros.h’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/include/generated/offsets.h’ from solution ‘build’ in configuration ‘Common’
1> Combining ‘zephyr/include/generated/offsets.h’
Building ‘zephyr/linker.cmd’ from solution ‘build’ in configuration ‘Common’
1> Combining ‘zephyr/linker.cmd’
Building ‘app/libapp.a’ from solution ‘build’ in configuration ‘Common’
Building ‘zephyr/libzephyr.a’ from solution ‘build’ in configuration ‘Common’
1> Compiling ‘configs.c’
2> Compiling ‘soc.c’
3> Compiling ‘mpu_regions.c’
4> Compiling ‘system_nrf9160.c’
1> In file included from C:/Nordic/ncs/zephyr/include/toolchain.h:21:0,
1> from zephyr/misc/generated/configs.c:3:
1> C:/Nordic/ncs/zephyr/include/toolchain/gcc.h:331:51: error: expected expression before ')' token
1> zephyr/misc/generated/configs.c:18:1: note: in expansion of macro 'GEN_ABSOLUTE_SYM'
1> C:/Nordic/ncs/zephyr/include/toolchain/gcc.h:331:51: error: expected expression before ')' token
1> zephyr/misc/generated/configs.c:25:1: note: in expansion of macro 'GEN_ABSOLUTE_SYM'
Build failed

It appears there are some known compiler errors with SES when building the solution but if you build the solution using ninja in the build directory using Command prompt after you load the project in ses, it will compile but there are some failures (See above)

I had it working previously but not sure why this is happening now..I also tried the licence suggestions mentioned here and no luck.

RE: nRF9160 SES project load

Otso Jousimaa — Fri, 22 Feb 2019 15:43:36 GMT

Bjørn Kvaale

I checked out the tags, the error remains the same. I can compile the project with cmake, but it would be nice to have an IDE.

RE: nRF9160 SES project load

Bjørn Kvaale — Fri, 22 Feb 2019 15:18:44 GMT

Otso Jousimaa It seems that you need to use branch v0.3.0 to be able to use Segger Embedded Studio (SES) with Nordic Connect SDK (NCS). If you want to use SES, I would suggest to checkout this NCS tag. Just follow the commands given in the NCS Getting Started Assistant in nRF Connect for Desktop:

If you are using the master branch by chance, you will need to follow this documentation here. You'll need to currently build the example via cmake, like shown here:

cmake -GNinja -DBOARD=nrf9160_pca10090ns ..

I would recommend using the v0.3.0 branch & following the NCS Getting Started Guide, as that seems like the easier option currently.

This note may also be useful:

RE: nRF9160 SES project load

DanMsc — Thu, 21 Feb 2019 07:15:52 GMT

My license shows Cortex-M V4

RE: nRF9160 SES project load

Bjørn Kvaale — Wed, 20 Feb 2019 15:40:23 GMT

Otso JousimaaDo not believe this will make a difference, as the Segger license is valid for all Nordic products. I did however notice that I received a compile issue (different to what you three are noticing) when I activated my Segger license. Before, my license was not active & I was able to build the asset tracker example without any issues. Now, with an active license, I get a compile issue. So it may have something to do with the license. I will have to investigate further.

DanMsc Does your license show Cortex M4 or Cortex M33?

RE: nRF9160 SES project load

Otso Jousimaa — Mon, 18 Feb 2019 21:06:34 GMT

I tried reinstalling the license with no luck. However I noticed the license is for "Cortex-M V4" whereas nrf9160 is Cortex-M33, could that be related?

RE: nRF9160 SES project load

DanMsc — Mon, 18 Feb 2019 17:41:03 GMT

Now it works and I don't know why, because I didn't make any changes.
I've only re-installed the license key in SES.
Thank you for the support.

RE: nRF9160 SES project load

Otso Jousimaa — Mon, 18 Feb 2019 13:02:58 GMT

I rm -rf'd the ncs directory and updated with west. No difference in the SES logging output as far as I can see

Loading solution asset_tracker.emProject
Executing load commands
/usr/local/bin/cmake  -GNinja -DBOARD=nrf9160_pca10090 -DBOARD_DIR=/Users/otsojousimaa/git/ncs/zephyr/boards/arm/nrf9160_pca10090 -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=/opt/local/gcc-arm-none-eabi-7-2018-q2-update -B/Users/otsojousimaa/git/ncs/nrf/samples/nrf9160/asset_tracker/build -H/Users/otsojousimaa/git/ncs/nrf/samples/nrf9160/asset_tracker -DPYTHON_EXECUTABLE=/usr/local/bin/python3 -DCMAKE_MAKE_PROGRAM=/usr/local/bin/ninja -DDTC=/usr/local/bin/dtc
Project load failed
Reported error: solution load command failed (-1)

RE: nRF9160 SES project load

Bjørn Kvaale — Mon, 18 Feb 2019 12:16:01 GMT

This applies to all three of you. I find it weird that you all receive so little logging information. Normally, you can easily see where the error lies. If you have recently downloaded the Nordic Connect SDK (around the12.2.2019), I believe the cause of this may be that we are now using west, Zephyr's meta-tool. There is more documentation here that may be helpful. Could you try to download west, update to the newest repositories & then try opening the SES examples again? Hopefully, you will then receive more logging information that can help you debug the issue.

RE: nRF9160 SES project load

HAO — Thu, 14 Feb 2019 02:26:41 GMT

Hi Bjørn, thanks for your prompt response. Please see the screen shot below - similar to others'. I tried a couple of GNU versions as well. I did setup as indicated in the guide. Thanks.

RE: nRF9160 SES project load

DanMsc — Wed, 13 Feb 2019 15:53:49 GMT

Same issue:

Windows 10.
SES: V4.14
Phyton: 3.7.2
GNUA Arm Embedded toolchain 7-2018-q2-update

Everything setup like explained in the Getting Started Assistant v2.6.1. All checks are ok.

Loading solution asset_tracker.emProject
Executing load commands
cmake -GNinja -DBOARD=nrf9160_pca10090 -DBOARD_DIR=E:/Nordic/ncs/zephyr/boards/arm/nrf9160_pca10090 -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=C:/gnuarmemb -BE:/Nordic/ncs/nrf/samples/nrf9160/asset_tracker/build -HE:/Nordic/ncs/nrf/samples/nrf9160/asset_tracker
Project load failed
Reported error: solution load command failed (-1)

Thanks

RE: nRF9160 SES project load

Otso Jousimaa — Wed, 13 Feb 2019 12:54:11 GMT

I'm having the same issue.

SES: V4.14,
OS: Mac OS 10.14.2
Python: 3.7.2
GCC: Gnu 7.3.1

I've set up the project as instructed in Getting Started assistant 0.5.1. So far I've tried steps here, here and here .

GCC is rolled back to 2018 q2
I've tried compiling the samples under zephyr directory
I've unset ZEPHYR_SDK_INSTALL_DIR and sourced zephyr_env.sh (and ran SES with the same terminal)

The getting started assistant fails verifying cmake and python3, however the programs are found by `which cmake` and `which python3`

My SES Target & Output log:

Loading solution asset_tracker.emProject
Executing load commands
/usr/local/bin/cmake  -GNinja -DBOARD=nrf9160_pca10090 -DBOARD_DIR=/Users/otsojousimaa/git/ncs/zephyr/boards/arm/nrf9160_pca10090 -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=/opt/local/gcc-arm-none-eabi-7-2018-q2-update -B/Users/otsojousimaa/git/ncs/nrf/samples/nrf9160/asset_tracker/build -H/Users/otsojousimaa/git/ncs/nrf/samples/nrf9160/asset_tracker -DPYTHON_EXECUTABLE=/usr/local/bin/python3 -DCMAKE_MAKE_PROGRAM=/usr/local/bin/ninja -DDTC=/usr/local/bin/dtc
Project load failed
Reported error: solution load command failed (-1)

My asset_tracker.emProject, note the `"` and `&` in the file:

<!DOCTYPE CrossStudio_Project_File>
<solution cmakelists_end_section="# NORDIC SDK APP END" cmakelists_file_name="/Users/otsojousimaa/git/ncs/nrf/samples/nrf9160/asset_tracker/CMakeLists.txt" cmakelists_project="asset_tracker;build;libapp.a" target="8" version="2" source_directory="/Users/otsojousimaa/git/ncs/zephyr" board_directory="/Users/otsojousimaa/git/ncs/zephyr/boards/arm/nrf9160_pca10090" dts_compiled_file_name="/Users/otsojousimaa/git/ncs/nrf/samples/nrf9160/asset_tracker/build/zephyr/nrf9160_pca10090.dts_compiled" build_directory="/Users/otsojousimaa/git/ncs/nrf/samples/nrf9160/asset_tracker/build" dts_overlay_file_name="/Users/otsojousimaa/git/ncs/nrf/samples/nrf9160/asset_tracker/nrf9160_pca10090.overlay" load_command_environment="ZEPHYR_BASE=/Users/otsojousimaa/git/ncs/zephyr" cmakelists_start_section="# NORDIC SDK APP START" Name="asset_tracker" load_command=""/usr/local/bin/cmake " -GNinja -DBOARD=nrf9160_pca10090 -DBOARD_DIR=/Users/otsojousimaa/git/ncs/zephyr/boards/arm/nrf9160_pca10090 -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH="/opt/local/gcc-arm-none-eabi-7-2018-q2-update" -B"/Users/otsojousimaa/git/ncs/nrf/samples/nrf9160/asset_tracker/build" -H"/Users/otsojousimaa/git/ncs/nrf/samples/nrf9160/asset_tracker" -DPYTHON_EXECUTABLE="/usr/local/bin/python3" -DCMAKE_MAKE_PROGRAM="/usr/local/bin/ninja" -DDTC="/usr/local/bin/dtc" && $(StudioDir)/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">
  <configuration properties_filter="Debug" arm_target_device_name="nRF9160" debug_target_connection="J-Link" debug_register_definition_file="$(PackagesDir)/nRF/Device/Registers/nrf9160.svd" arm_architecture="v8M_Mainline" external_link_command=""$(ToolChainDir)/arm-none-eabi-gcc" $(Objects) $(LinkOptions) -o "$(RelTargetPath)"" arm_core_type="Cortex-M33" external_assemble_command=""$(ToolChainDir)/arm-none-eabi-gcc" $(AsmOptions) -MD -MF "$(RelDependencyPath)" -o "$(RelTargetPath)" -c "$(RelInputPath)"" Name="Common" external_c_compile_command=""$(ToolChainDir)/arm-none-eabi-gcc" $(COptions) -MD -MF "$(RelDependencyPath)" -fno-diagnostics-show-caret -o "$(RelTargetPath)" -c "$(RelInputPath)"" arm_fpu_type="FPv5-SP-D16" external_archive_command=""$(ToolChainDir)/arm-none-eabi-ar" -rcs "$(RelTargetPath)" $(Objects)" linker_section_placements_segments="FLASH RX 0x00000000 0x00100000;RAM RWX 0x20000000 0x00040000" source_code_control_directory="/Users/otsojousimaa/git/ncs/zephyr" build_toolchain_directory="/opt/local/gcc-arm-none-eabi-7-2018-q2-update/bin" debug_start_from_entry_point_symbol="No" arm_target_interface_type="SWD"/>
  <folder path="/Users/otsojousimaa/git/ncs/nrf/samples/nrf9160/asset_tracker" filter="nrf9160_pca10090.overlay" Name="dts files">
    <configuration Name="Common" c_user_include_directories="/Users/otsojousimaa/git/ncs/zephyr/dts/common" c_system_include_directories="/Users/otsojousimaa/git/ncs/zephyr/include;/Users/otsojousimaa/git/ncs/zephyr/dts/arm;/Users/otsojousimaa/git/ncs/zephyr/dts"/>
    <file file_name="/Users/otsojousimaa/git/ncs/zephyr/boards/arm/nrf9160_pca10090/nrf9160_pca10090.dts"/>
    <file file_name="/Users/otsojousimaa/git/ncs/zephyr/boards/arm/nrf9160_pca10090/nrf9160_pca10090.yaml"/>
    <file file_name="/Users/otsojousimaa/git/ncs/zephyr/dts/common/common.dts"/>
    <file file_name="/Users/otsojousimaa/git/ncs/nrf/samples/nrf9160/asset_tracker/build/zephyr/nrf9160_pca10090.dts_compiled"/>
  </folder>
  <import can_modify_solution="No" file_name="build.emProject"/>
</solution>

I can run the SES load command to configure the project and then `ninja` in terminal to compile the project without errors, although I've not flashed the binary to dk.

RE: nRF9160 SES project load

Bjørn Kvaale — Wed, 13 Feb 2019 11:32:56 GMT

Could you please change to the Target & Output window in Segger Embedded Studio & upload the log here? Which version of gnuarmemb are you using? If you are using the Q4 one, I would recommend changing to the Q2 version (the second to last version). There is a compiling bug in the latest version (Q4). Did you setup everything like explained in the nRF91 Getting Started Guide?