• State Not Answered
  • Replies 10 replies
  • Subscribers 89 subscribers
  • Views 2411 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 264465
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Having trouble getting any NRF Connect project to connect to board

RSemple

I am attempting to load up the default NRF project "AT_Client" located at ...\ncs\v1.4.2\nrf\samples\nrf9160\at_client project, however, whenever I attempt to load it with the SEGGER Embedded Studio software that the nRF Connect Tool Chain Manager installed, it keeps breaking during the cmake of the project. Following error has been posted below. Also, I cannot actually connect to my device by going to the "Target -> connect" option in the toolbar. Can I have some assistance please? I seem to be chasing my tail here...

"""

Creating solution at_client.emProject
.../ncs/v1.4.2/toolchain/opt/bin/cmake.exe -GNinja -DBOARD=thingy91_nrf9160ns -DBOARD_DIR=...\ncs\v1.4.2\nrf\boards\arm\thingy91_nrf9160 -B...\ncs\v1.4.2\nrf\samples\nrf9160\at_client\build_thingy91_nrf9160ns -S...\ncs\v1.4.2\nrf\samples\nrf9160\at_client -DNCS_TOOLCHAIN_VERSION=1.4.2 -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=...\ncs\v1.4.2\toolchain\segger_embedded_studio/html/configure_nordic_project_menuconfig.py
-- Application: .../ncs/v1.4.2/nrf/samples/nrf9160/at_client
-- Zephyr version: 2.4.0 (.../ncs/v1.4.2/zephyr)
-- Found Python3: .../ncs/v1.4.2/toolchain/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter
-- Found west (found suitable version "0.7.2", minimum required is "0.7.1")
-- Board: thingy91_nrf9160ns
-- Cache files will be written to: .../ncs/v1.4.2/zephyr/.cache
-- Found dtc: .../ncs/v1.4.2/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (.../ncs/v1.4.2/toolchain/opt)
-- Found BOARD.dts: .../ncs/v1.4.2/nrf/boards/arm/thingy91_nrf9160/thingy91_nrf9160ns.dts
-- Generated zephyr.dts: .../ncs/v1.4.2/nrf/samples/nrf9160/at_client/build_thingy91_nrf9160ns/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: .../ncs/v1.4.2/nrf/samples/nrf9160/at_client/build_thingy91_nrf9160ns/zephyr/include/generated/devicetree_unfixed.h
-- Configuring incomplete, errors occurred!
Including boilerplate (Zephyr base): .../ncs/v1.4.2/zephyr/cmake/app/boilerplate.cmake
-- Using NCS Toolchain 1.4.2 for building. (.../ncs/v1.4.2/toolchain/cmake)
CMake Error at .../ncs/v1.4.2/zephyr/cmake/kconfig.cmake:181 (message):
File not found: ...
Call Stack (most recent call first):
.../ncs/v1.4.2/zephyr/cmake/app/boilerplate.cmake:591 (include)
.../ncs/v1.4.2/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
.../ncs/v1.4.2/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:35 (include_boilerplate)
CMakeLists.txt:9 (find_package)



error: cmake failed
create_nordic_project.py failed (1)

"'"

Parents
  • 0

    Hi,

    From the board you chose when opening the project, I'm assuming you are trying to program a Thingy:91. Have you connected the Thingy:91 directly to your computer with the USB or are you using an external debug probe? In order to program the Thingy:91 with SES you need to use an external debug probe, such as nRF9160 DK or any J-Link device supporting ARM Cortex-M33. When connecting the Thingy:91 directly to your PC through USB, the device uses MCUboot in order to program the device, so you can only program MCUboot compatible images, such as app_signed.hex, and you must to so with the nRF Connect Programmer, which can be found in nRF Connect for Desktop. Please see the working with Thingy:91 page for more information about how to program the device.

    Best regards,

    Marte

Reply
  • 0

    Hi,

    From the board you chose when opening the project, I'm assuming you are trying to program a Thingy:91. Have you connected the Thingy:91 directly to your computer with the USB or are you using an external debug probe? In order to program the Thingy:91 with SES you need to use an external debug probe, such as nRF9160 DK or any J-Link device supporting ARM Cortex-M33. When connecting the Thingy:91 directly to your PC through USB, the device uses MCUboot in order to program the device, so you can only program MCUboot compatible images, such as app_signed.hex, and you must to so with the nRF Connect Programmer, which can be found in nRF Connect for Desktop. Please see the working with Thingy:91 page for more information about how to program the device.

    Best regards,

    Marte

Children
No Data
Related