Getting Started with nRF9160 DK

Maybe try to move your code to a folder without spaces?

Hello, thank you for your tutorial!

I followed all the steps of the tutorial, I was able to check all the points in the Getting started assistant. I use the NRF9160 DK. When i create an nrf connect sdk project I have an error that I don't understand. The terminal say :


 

Creating solution hello_world.emProject
C:/Program Files/CMake/bin/cmake.exe -GNinja -DBOARD=nrf9160dk_nrf9160 -DBOARD_DIR=D:\logiciels stage\Code source\ncs\zephyr\boards\arm\nrf9160dk_nrf9160 -BD:\logiciels stage\Code source\ncs\zephyr\samples\hello_world\build_nrf9160dk_nrf9160 -SD:\logiciels stage\Code source\ncs\zephyr\samples\hello_world -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=C:\gnuarmemb\9 2019-q4-major -DPYTHON_EXECUTABLE=C:/Python39/python.exe -DCMAKE_MAKE_PROGRAM=C:/ProgramData/chocolatey/bin/ninja.exe -DDTC=C:/ProgramData/chocolatey/bin/dtc.exe -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=D:\logiciels stage\emstudio\arm_segger_embedded_studio_v534a_win_x64_nordic/html/configure_nordic_project_menuconfig.py
-- Application: D:/logiciels stage/Code source/ncs/zephyr/samples/hello_world
-- Zephyr version: 2.4.99 (D:/logiciels stage/Code source/ncs/zephyr)
-- Found Python3: D:/logiciels stage/v1.5.1/toolchain/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter 
-- Found west (found suitable version "0.9.0", minimum required is "0.7.1")
-- Board: nrf9160dk_nrf9160, Revision: 0.7.0
-- Cache files will be written to: D:/logiciels stage/Code source/ncs/zephyr/.cache
-- Found dtc: C:/ProgramData/chocolatey/bin/dtc.exe (found suitable version "1.5.0", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (C:/gnuarmemb/9 2019-q4-major)
-- Found BOARD.dts: D:/logiciels stage/Code source/ncs/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160.dts
-- Generated zephyr.dts: D:/logiciels stage/Code source/ncs/zephyr/samples/hello_world/build_nrf9160dk_nrf9160/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: D:/logiciels stage/Code source/ncs/zephyr/samples/hello_world/build_nrf9160dk_nrf9160/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: D:/logiciels stage/Code source/ncs/zephyr/samples/hello_world/build_nrf9160dk_nrf9160/zephyr/include/generated/device_extern.h
-- Configuring incomplete, errors occurred!
Including boilerplate (Zephyr base): D:/logiciels stage/Code source/ncs/zephyr/cmake/app/boilerplate.cmake
-- Using NCS Toolchain 1.5.1 for building. (D:/logiciels stage/v1.5.1/toolchain/cmake)
nrf9160dk_nrf9160.dts.pre.tmp:59.42-71.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@50000000/flash-controller@39000: duplicate unit-address (also used in node /soc/peripheral@50000000/kmu@39000)
nrf9160dk_nrf9160.dts.pre.tmp:311.19-317.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@50000000/clock@5000: duplicate unit-address (also used in node /soc/peripheral@50000000/power@5000)
CMake Error at D:/logiciels stage/Code source/ncs/zephyr/cmake/kconfig.cmake:204 (message):
  File not found: D:/logiciels
Call Stack (most recent call first):
  D:/logiciels stage/Code source/ncs/zephyr/cmake/app/boilerplate.cmake:534 (include)
  D:/logiciels stage/Code source/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  D:/logiciels stage/Code source/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:35 (include_boilerplate)
  CMakeLists.txt:5 (find_package)



error: cmake failed
create_nordic_project.py failed (1)

Do you have any idea of the source of the problem?
Thank you in advance for your help

It might work but you should not. Your cell phone SIM is a higher LTE category SIM which most likely will not connect to LTE Cat-M1 or NB-IoT networks. You should use the SIM includes with the DK or Thingy:91 (from iBasis) or a SIM from a MNO or MVNO designed to connect to NB-IoT and/or LTE Cat-M1 networks.

can I use  LTE SIM card  used  with Samsung S9,, to nRF9160 DK board??

It looks like you have an open DevZone ticket here, please continue the conversation with our team there.