nRF9160 Cannot make Kconfig options have an effect in Segger Embedded Studio

[Johan]

I have a nRF9160 DK and I'm adapting the asset tracker to connect to our own AWS cloud solution.

I see the code nrf_cloud uses defines coming from the Kconfig at \nrf\subsys\net\lib\nrf_cloud\Kconfig.
For example: NRF_CLOUD_HOST_NAME, NRF_CLOUD_PORT, NRF_CLOUD_PROVISION_CERTIFICATES, NRF_CLOUD_CERTIFICATES_FILE etc

How do I make changes to the Kconfig have an effect when building in Segger Embedded Studio? No matter what I do, changes to this Kconfig doesn't have an effect to the built result.

Am I missing the point, how it's supposed to work perhaps?
Anyone who can educate me, how to work "correctly" with this, would be appreciated.

I tried to build from commandline, but couldn't make it work, so I'm sticking with Segger Embedded Studio so far.
Build platform: win7

Johan

[Johan]

Thanks Martin! Now I can progress with ease!
Cheers mate!

[Johan]

Martin,

I'm having problems to build in SES and I cannot figure out what's wrong.
I see it's looking for the compiler, but in the wrong place, and I don't know why.
It should look in the toolchain dir, but it is instead looking in the segger bin path.. fails!

LOG from segger embedded studio.
(I have checked out tag v0.4.0-rc2 as Brian Kim recommended)

Loading solution lte_ble_gateway.emProject
Executing load commands
cmake -GNinja -DBOARD=nrf9160_pca10090 -DBOARD_DIR=F:/nsd_src_root2/zephyr/boards/arm/nrf9160_pca10090 -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=F:/gnuarmemb/7 2018-q2-update/bin -BF:/nsd_src_root2/nrf/samples/nrf9160/lte_ble_gateway/build_nrf9160_pca10090 -HF:/nsd_src_root2/nrf/samples/nrf9160/lte_ble_gateway -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=F:/segger/arm_segger_embedded_studio_v416_win_x64_nordic/html/configure_nordic_project_menuconfig.py
CMake Error at CMakeLists.txt:20 (include):
include could not find load file:

F:/nsd_src_root2/ncs/zephyr/cmake/app/boilerplate.cmake

-- The C compiler identification is GNU 8.2.1
-- The CXX compiler identification is unknown
-- Check for working C compiler: F:/segger/arm_segger_embedded_studio_v416_win_x64_nordic/bin/cc.exe
-- Check for working C compiler: F:/segger/arm_segger_embedded_studio_v416_win_x64_nordic/bin/cc.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Detecting C compile features
-- Detecting C compile features - failed
CMake Error at CMakeLists.txt:21 (project):
No CMAKE_CXX_COMPILER could be found.

Tell CMake where to find the compiler by setting either the environment
variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
to the compiler, or to the compiler name if it is in the PATH.

-- Configuring incomplete, errors occurred!
See also "F:/nsd_src_root2/nrf/samples/nrf9160/lte_ble_gateway/build_nrf9160_pca10090/CMakeFiles/CMakeOutput.log".
See also "F:/nsd_src_root2/nrf/samples/nrf9160/lte_ble_gateway/build_nrf9160_pca10090/CMakeFiles/CMakeError.log".
Project load failed
Reported error: solution load command failed (1)

[Johan]

When building (lte_ble_gateway) it works ok.
Running it, gives errors I don't understand or can fix.

***** Booting Zephyr OS v1.13.99-ncs2 *****
Secure Boot: configure flash
Secure Boot: SPU: set region 0 as Secure
Secure Boot: SPU: set region 1 as Secure
Secure Boot: SPU: set region 2 as Secure
Secure Boot: SPU: set region 3 as Secure
Secure Boot: SPU: set region 4 as Secure
Secure Boot: SPU: set region 5 as Secure
Secure Boot: SPU: set region 6 as Secure
Secure Boot: SPU: set region 7 as Secure
Secure Boot: SPU: set Flash region 8 as Non-Secure
Secure Boot: SPU: set Flash region 9 as Non-Secure
Secure Boot: SPU: set Flash region 10 as Non-Secure
Secure Boot: SPU: set Flash region 11 as Non-Secure
Secure Boot: SPU: set Flash region 12 as Non-Secure
Secure Boot: SPU: set Flash region 13 as Non-Secure
Secure Boot: SPU: set Flash region 14 as Non-Secure
Secure Boot: SPU: set Flash region 15 as Non-Secure
Secure Boot: SPU: set Flash region 16 as Non-Secure
Secure Boot: SPU: set Flash region 17 as Non-Secure
Secure Boot: SPU: set Flash region 18 as Non-Secure
Secure Boot: SPU: set Flash region 19 as Non-Secure
Secure Boot: SPU: set Flash region 20 as Non-Secure
Secure Boot: SPU: set Flash region 21 as Non-Secure
Secure Boot: SPU: set Flash region 22 as Non-Secure
Secure Boot: SPU: set Flash region 23 as Non-Secure
Secure Boot: SPU: set Flash region 24 as Non-Secure
Secure Boot: SPU: set Flash region 25 as Non-Secure
Secure Boot: SPU: set Flash region 26 as Non-Secure
Secure Boot: SPU: set Flash region 27 as Non-Secure
Secure Boot: SPU: set Flash region 28 as Non-Secure
Secure Boot: SPU: set Flash region 29 as Non-Secure
Secure Boot: SPU: set Flash region 30 as Non-Secure
Secure Boot: SPU: set Flash region 31 as Non-Secure
Secure Boot: configure SRAM
Secure Boot: SPU: set SRAM region 0 as Secure
Secure Boot: SPU: set SRAM region 1 as Secure
Secure Boot: SPU: set SRAM region 2 as Secure
Secure Boot: SPU: set SRAM region 3 as Secure
Secure Boot: SPU: set SRAM region 4 as Secure
Secure Boot: SPU: set SRAM region 5 as Secure
Secure Boot: SPU: set SRAM region 6 as Secure
Secure Boot: SPU: set SRAM region 7 as Secure
Secure Boot: SPU: set SRAM region 8 as Non-Secure
Secure Boot: SPU: set SRAM region 9 as Non-Secure
Secure Boot: SPU: set SRAM region 10 as Non-Secure
Secure Boot: SPU: set SRAM region 11 as Non-Secure
Secure Boot: SPU: set SRAM region 12 as Non-Secure
Secure Boot: SPU: set SRAM region 13 as Non-Secure
Secure Boot: SPU: set SRAM region 14 as Non-Secure
Secure Boot: SPU: set SRAM region 15 as Non-Secure
Secure Boot: SPU: set SRAM region 16 as Non-Secure
Secure Boot: SPU: set SRAM region 17 as Non-Secure
Secure Boot: SPU: set SRAM region 18 as Non-Secure
Secure Boot: SPU: set SRAM region 19 as Non-Secure
Secure Boot: SPU: set SRAM region 20 as Non-Secure
Secure Boot: SPU: set SRAM region 21 as Non-Secure
Secure Boot: SPU: set SRAM region 22 as Non-Secure
Secure Boot: SPU: set SRAM region 23 as Non-Secure
Secure Boot: SPU: set SRAM region 24 as Non-Secure
Secure Boot: SPU: set SRAM region 25 as Non-Secure
Secure Boot: SPU: set SRAM region 26 as Non-Secure
Secure Boot: SPU: set SRAM region 27 as Non-Secure
Secure Boot: SPU: set SRAM region 28 as Non-Secure
Secure Boot: SPU: set SRAM region 29 as Non-Secure
Secure Boot: SPU: set SRAM region 30 as Non-Secure
Secure Boot: SPU: set SRAM region 31 as Non-Secure
Secure Boot: configure peripherals
Secure Boot: MSP_NS 2002c898
Secure Boot: prepare to jump to Non-Secure image
***** Booting Zephyr OS v1.13.99-ncs2 *****
Application started
[00:00:05.615,112] <err> bt_driver.h4_get_type: Unknown H:4 type 0x3e
[00:00:05.615,112] <err> bt_driver.h4_get_type: Unknown H:4 type 0x21
[00:00:05.621,185] <err> bt_driver.read_payload: Not enough spac e in buffer
ASSERTION FAIL [err == 0] @ F:/nsd_src_root/ncs/zephyr/subsys/bluetooth/host/hci_core.c:272
k_sem_take failed with err -11

/Johan