This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

The project file ncs/applications/asset_tracker/build_nrf52_pca10040/asset_tracker.emProject is invalid

Hi:

I am having trouble just trying to build the asset_tracker_image.

I followed the instruction on setting the nRF Connect. (nRF Connect v3.2.0). However I got the following errors. I need help. The transcript output from the Segger Embedded Studio is as follows:

Loading solution asset_tracker.emProject
Executing load commands
cmake -GNinja -DBOARD=nrf52_pca10040 -DBOARD_DIR=C:/Users/baklengc/ncs/zephyr/boards/arm/nrf52_pca10040 -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=C:/gnuarmemb/7.2018-q2-update -BC:/Users/baklengc/ncs/nrf/applications/asset_tracker/build_nrf52_pca10040 -HC:/Users/baklengc/ncs/nrf/applications/asset_tracker -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=C:/Users/baklengc/EmbeddedStudio_ARM_Nordic_v420a_win_x64/arm_segger_embedded_studio_v420a_win_x64_nordic/html/configure_nordic_project_menuconfig.py
-- Using application from 'C:/Users/baklengc/ncs/nrf/applications/asset_tracker'
Zephyr version: 2.0.99
CMake Warning at C:/Users/baklengc/ncs/zephyr/cmake/app/boilerplate.cmake:195 (message):
-- Selected BOARD nrf52810_pca10040
  The build directory must be cleaned pristinely when changing boards
Call Stack (most recent call first):
  CMakeLists.txt:11 (include)

-- Found west: C:/Python38/Scripts/west.exe (found suitable version "0.6.3", minimum required is "0.6.0")
-- Cache files will be written to: C:\Users\baklengc\AppData\Local/.cache/zephyr
USING OUT OF TREE BOARD
CMake Error at C:/Users/baklengc/ncs/zephyr/cmake/kconfig.cmake:168 (message):
  File not found:
  C:/Users/baklengc/ncs/zephyr/boards/arm/nrf52_pca10040/nrf52810_pca10040_defconfig
Call Stack (most recent call first):
  C:/Users/baklengc/ncs/zephyr/cmake/app/boilerplate.cmake:567 (include)
  CMakeLists.txt:11 (include)

-- Configuring incomplete, errors occurred!
Parents
  • Hi.

    When changing board, you have to do a "pristine build", i.e., you must delete all the files in the build directory.

    If you build with west, you can do this automatically by appending the -p flag. If you are using SES, you must check the "Clean Build directory" checkbox when loading the project.

    However, the asset_tracker application is made for the nRF9160, and will not work for an nRF52.

    This is also true for the nRF Connect SDK in general. At the moment, the only chip supported by NCS is the nRF91. Is there a specific reason for why you try to use NCS and not the nRF5 SDK with an nRF52?

    Best regards,

    Didrik

Reply
  • Hi.

    When changing board, you have to do a "pristine build", i.e., you must delete all the files in the build directory.

    If you build with west, you can do this automatically by appending the -p flag. If you are using SES, you must check the "Clean Build directory" checkbox when loading the project.

    However, the asset_tracker application is made for the nRF9160, and will not work for an nRF52.

    This is also true for the nRF Connect SDK in general. At the moment, the only chip supported by NCS is the nRF91. Is there a specific reason for why you try to use NCS and not the nRF5 SDK with an nRF52?

    Best regards,

    Didrik

Children
Related