Issue with command line compilation of NRF9160 samples

Question

Hello, 
 I have configured the toolchain and SDK by following the NRF Connect getting started guide and followed the below steps to compile the mqtt_simple application (on master branch and using a MAC): 
 export ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb  export GNUARMEMB_TOOLCHAIN_PATH="/path/to/gcc-arm-none-eabi-Qx-2018/"  source /path/to/ncs/zephyr/zephyr-env.sh  cd /path/to/ncs/nrf/samples/nrf9160/mqtt_simple/  mkdir build && cd build  cmake .. -DBOARD=nrf9160_pca10090ns -GNinja 
 After executing cmake this is the output: 
 Zephyr version: 1.14.0  -- Selected BOARD nrf9160_pca10090ns  -- Found west: /usr/local/bin/west (found suitable version "0.5.5", minimum required is "0.5.4")  -- Loading /path/to/ncs/zephyr/boards/arm/nrf9160_pca10090/nrf9160_pca10090ns.dts as base  -- Overlaying /path/to/ncs/zephyr//dts/common/common.dts  Parsing Kconfig tree in /path/to/ncs/nrf/samples/nrf9160/mqtt_simple/Kconfig  Loading /path/to/ncs/zephyr/boards/arm/nrf9160_pca10090/nrf9160_pca10090ns_defconfig as base  Merging /path/to/ncs/nrf/samples/nrf9160/mqtt_simple/prj.conf 
 /path/to/ncs/nrf/samples/nrf9160/mqtt_simple/prj.conf:11: warning: attempt to assign the value 'y' to the undefined symbol LTE_LINK_CONTROL /path/to/ncs/nrf/samples/nrf9160/mqtt_simple/prj.conf:12: warning: attempt to assign the value 'n' to the undefined symbol LTE_AUTO_INIT_AND_CONNECT /path/to/ncs/nrf/samples/nrf9160/mqtt_simple/prj.conf:15: warning: attempt to assign the value 'y' to the undefined symbol BSD_LIBRARY /path/to/ncs/nrf/samples/nrf9160/mqtt_simple/prj.conf:19: warning: attempt to assign the value 'y' to the undefined symbol AT_HOST_LIBRARY 
 Error: Aborting due to non-whitelisted Kconfig warning '/path/to/ncs/nrf/samples/nrf9160/mqtt_simple/prj.conf:11: warning: attempt to  assign the value 'y' to the undefined symbol LTE_LINK_CONTROL'. Note: If this warning doesn't point  to an actual problem, you can add it to the whitelist at the top of /path/to/ncs/zephyr//scripts/kconfig/kconfig.py. CMake Error at /path/to/ncs/zephyr/cmake/kconfig.cmake:191 (message):  command failed with return code: 1  Call Stack (most recent call first): /path/to/ncs/zephyr/cmake/app/boilerplate.cmake:397 (include)  CMakeLists.txt:9 (include) 
  -- Configuring incomplete, errors occurred! 
 Any help would be appreciated. 
 Kind regards

Ryan Farrelly · Accepted Answer

Ok, managed to get this to work i.e, build, compile and flash. 
 Before anything, follow the steps in the NRF Connect making sure all dependancies are installed but stay on Master branch. 
 Set up your .bash_profile like this: 
 export ZEPHYR_BASE=/path/to/ncs/zephyr export ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb export GNUARMEMB_TOOLCHAIN_PATH=/path/to/gcc-arm-none-eabi-7-2018-q2-update source /path/to/ncs/zephyr/zephyr-env.sh 
 From the ncs root directory: west init -l nrf west update 
 Go to mqtt_simple/build ( clean the build folder if already exists ) cmake -DBOARD=nrf9160_pca10090ns -GNinja .. 
 NOTE: You may get an error about &lsquo;pykwalify&rsquo; not being installed: pip uninstall pykwalify pip install pykwalify 
 Run cmake: cmake -DBOARD=nrf9160_pca10090ns -GNinja .. ninja ninja flash 
 NOTE: Make sure you have the latest nrfjprog otherwise the ninja flash command won&rsquo;t work and will complain about memory access alignment. And of course, the secure boot should be flashed prior to the main application.

Bjørn Kvaale · Answer

Yes, there should be a new release tagged soon. In regards to the NCS master branch, there has been an update in this blog post here . Segger finally has support for the Zephyr master branch now! 
 I have tested this myself & followed the following procedure (using Windows 10). Remember to run choco commands using an Administrator command prompt. First, I upgraded to the latest nRF Getting Started Assistant guide in nRF Connect. If you have already installed the toolchain, you can skip the first two commands: 
 choco feature enable -n allowGlobalConfirmation
choco install -y cmake --installargs 'ADD_CMAKE_TO_PATH=System'
 
 For all of the following choco install commands, I instead ran choco upgrade (see example below): 
 choco upgrade git 
 After each upgrade, I verified the upgrade by pressing the Verify button in the nRF Connect for Desktop app. 
 In the "Clone the nRF Connect SDK" section, I ran the following command first: 
 pip3 install west --upgrade 
 I then created a new ncs folder. After running the "west init" command, I then ran "west update" when prompted to do so in the command prompt (if you want to use the master branch). If you want to use a tagged branch, see the command below this one. I was not able to verify the west init step unfortunately (most likely because I named by ncs folder ncs_master instead of ncs). 
 I then deleted the old Segger v4.14 (the one used for NCS) & installed the new v4.16. I find it is helpful to make a shortcut of the emStudio.exe file. That way, you won't need to go to that folder every time you want to launch SES. 
 
 The first time, I received an error code 1. I needed to change the zephyr base as described in the linked blog post. 
 If you have any more questions regarding this, please open a new devzone case, as this thread is becoming large & slightly disorganized.

Bjørn Kvaale · Answer

Martin Thanks for letting us know! We are aware of this issue & are busy looking for a fix. 
 Ryan Farrelly Thanks for the tips! 
 In addition to using cmake & ninja, it is also possible to use the Zephyr west tool to build & program the board. These two links helped me figure this out: link 1 , link 2 . 
 Inside ncs/zephyr/zephyr-env.cmd: 
 @echo off
set ZEPHYR_BASE=%~dp0

if exist "%userprofile%\zephyrrc.cmd" (
	call "%userprofile%\zephyrrc.cmd"
)
 
 If you define zephyrrc.cmd inside your user profile (i.e. C:/Users/<username>/), you can write: 
 @echo off
echo zephyrrc_running

set ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb
set GNUARMEMB_TOOLCHAIN_PATH=C:\gnuarmemb
 
 That way, when you call zephyr-env.cmd from a command prompt window, you set the Zephyr base, zephyr toolchain variant & gnuarmemb toolchain path without needing to write the three commands each time. This may not work with a bash window (e.g. git bash) because the username may be different. 
 You can then follow this link to download NCS using west . To build the at_client example for example, change directory to ncs/samples/nrf9160/at_client & then run the following commands: 
 west build -b nrf9160_pca10090ns -d build
west flash -d build

 
 You can then flash using: 
 west flash -d build

Issue with command line compilation of NRF9160 samples

Top Replies