CMake error

[Yano]

Hi,

We are trying to install the nRF toolchain/SDK/SES etc. so that we can compile (modify for NB-IOT) and evaluate the nRF91 asset tracker.

We have followed all the steps in the Getting Started Assistant but the project is not compiling (see below).

Could you let me know where we are going wrong?

Thanks Ian

BTW:

During installation we got these error:

ERROR: pyocd 0.21.0 has requirement pyyaml<6.0,>=5.1, but you'll have pyyaml 4.2b4 which is incompatible.
ERROR: gitlint 0.11.0 has requirement Click==6.7, but you'll have click 7.0 which is incompatible

Loading solution asset_tracker.emProject
Executing load commands
cmake -GNinja -DBOARD=nrf9160_pca10090 -DBOARD_DIR=C:/Develop/nRF91_DK/ncs/zephyr/boards/arm/nrf9160_pca10090 -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=C:/gnuarmemb -BC:/Develop/nRF91_DK/ncs/nrf/applications/asset_tracker/build -HC:/Develop/nRF91_DK/ncs/nrf/applications/asset_tracker -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=C:/Develop/nRF91_DK/ses/arm_segger_embedded_studio_v418_win_x64_nordic/html/configure_nordic_project_menuconfig.py
-- Using application from 'C:/Develop/nRF91_DK/ncs/nrf/applications/asset_tracker'
Zephyr version: 1.14.99
-- Selected BOARD nrf9160_pca10090
-- Found west: C:/Python37/Scripts/west.exe (found suitable version "0.5.8", minimum required is "0.5.6")
-- Cache files will be written to: C:\Users\Ian\AppData\Local/.cache/zephyr
USING OUT OF TREE BOARD
CMake Error at C:/Develop/nRF91_DK/ncs/zephyr/cmake/compiler/gcc/generic.cmake:24 (message):
Executing the below command failed. Are permissions set correctly?

'C:/Users/Ian/Downloads/EmbeddedStudio_ARM_Nordic_v418_win_x64
(1)/arm_segger_embedded_studio_v418_win_x64_nordic/bin/cc.exe --version'

Call Stack (most recent call first):
C:/Develop/nRF91_DK/ncs/zephyr/cmake/generic_toolchain.cmake:68 (include)
C:/Develop/nRF91_DK/ncs/zephyr/cmake/app/boilerplate.cmake:483 (include)
CMakeLists.txt:11 (include)

-- Configuring incomplete, errors occurred!
See also "C:/Develop/nRF91_DK/ncs/nrf/applications/asset_tracker/build/CMakeFiles/CMakeOutput.log".
See also "C:/Develop/nRF91_DK/ncs/nrf/applications/asset_tracker/build/CMakeFiles/CMakeError.log".
Project load failed
Reported error: solution load command failed (1)

[Øyvind]

Hello Ian, 

What version of the Getting Started Assistant are you using?

ERROR: pyocd 0.21.0 has requirement pyyaml<6.0,>=5.1, but you'll have pyyaml 4.2b4 which is incompatible.
ERROR: gitlint 0.11.0 has requirement Click==6.7, but you'll have click 7.0 which is incompatible

Can you specify when you get these errors? 

Selected BOARD nrf9160_pca10090

 You have selected the wrong board when compiling, this should be nrf9160_pca10090ns. This is due to the Secure Partition Manager.

The following image shows how "Open nRF Connect SDK Project..." in SES should be configured.

Kind regards,
Øyvind

[Yano]

Hi Øyvind,

We are using version 1.0.0.

Thanks, that has fixed the error and we have successfully compiled the project.

We have modified the project to work on nb-iot  but when we try to flash the DK we get and error.

To download we are using SES>Target>Download Zephyr/merged.hex

Are we doing something wrong?

Thanks Ian

[Øyvind]

Have you tried using Build --> Build & Run in SES v4.18? For SES v4.16 we had a work-around to support flashing a multi-image project (SPM + APP). This should be fixed in v4.18.

That said, you should not get the error you get when manually downloading the .hex file. I will report this internally.

Kind regards,
Øyvind

[Yano]

OK that worked, but only LED 3 is flashing (even after a wait) so I assume its not connecting?

What is the best way to debug?

We have set the unit to nb-iot mode, is that all we have to do?

Also where are the source files for the project?

[Øyvind]

Yano said:

OK that worked, but only LED 3 is flashing (even after a wait) so I assume its not connecting?

Glad to hear you got it working. Yes, as long as LED3 is blinking alone, it is not connected.

Please have a look at the Asset Tracker Application documentation

 

Yano said:

We have set the unit to nb-iot mode, is that all we have to do?

Yes, this should be all you need to do. You can verify with issuing the command AT%XSYSTEMMODE=? in LTE Link Monitor.

Yano said:

What is the best way to debug?

Using the LTE Link Monitor found in the nRF Connect for Desktop, you should be able to issue AT+CFUN? command. This should give much more information regarding your connection. If it does not work using Asset tracker, you may have to load the AT_client sample.

Yano said:

Also where are the source files for the project?

 You can find source files under <sourcecode_root>nrf\applications\asset_tracker, while AT_client is found under nrf\samples\nrf9160\at_client.


Let me know how it works out for you.

Kind regards,
Øyvind