How to setup zephyr RTOS with SEGGER Embedded Studio

Hi,

You can use Segger Embedded Studio Nordic Edition with Zephyr SDK and nRF Connect SDK projects. See our Getting started guide for how to install the SDK and tools, and how to build and program applications using SES.

Please be aware that SES is not recommended for new projects (from nRF Connect SDK v1.9.1 Release Notes):

nRF Connect SDK v1.9.1 is supported by both nRF Connect extensions for Visual Studio Code and SEGGER Embedded Studio Nordic Edition. In future releases, documentation on the setup and usage of Segger Embedded Studio Nordic Edition will no longer be available and all references to IDE support will instruct users with nRF Connect extensions for Visual Studio Code. In future releases, Segger Embedded Studio will no longer be tested with the build system and it is not recommended for new projects.

nRF Connect extensions for Visual Studio Code will be under continued active development and supported and tested with future nRF Connect SDK releases. It is recommended for all new projects.

Best regards,

Marte

after all setup i am getting this error, can you suggest how to solve it ?

Hi,

When you get this error pop-up you also get a more detailed description of the error or errors in the output terminal. Make sure you have selected to show 'Transcript' and 'Output', then copy the complete text output and upload it here.

Best regards,

Marte

Below is error log

Creating solution blinky.emProject
cmake -GNinja -DBOARD=nrf52dk_nrf52832 -DBOARD_DIR=C:\Users\Ecloud10\ncs\v1.9.1\zephyr\boards\arm\nrf52dk_nrf52832 -BC:\Users\Ecloud10\ncs\v1.9.1\zephyr\samples\basic\blinky\build_nrf52dk_nrf52832 -SC:\Users\Ecloud10\ncs\v1.9.1\zephyr\samples\basic\blinky -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=C:\gnuarmemb -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=C:\Nordic Semiconductor\arm_segger_embedded_studio_v568_win_x64_nordic/html/configure_nordic_project_menuconfig.py
-- Application: C:/Users/Ecloud10/ncs/v1.9.1/zephyr/samples/basic/blinky
-- Zephyr version: 2.7.99 (C:/Users/Ecloud10/ncs/v1.9.1/zephyr), build: v2.7.99-ncs1-1
-- Found west (found suitable version "0.12.0", minimum required is "0.7.1")
-- Board: nrf52dk_nrf52832
-- Cache files will be written to: C:/Users/Ecloud10/ncs/v1.9.1/zephyr/.cache
-- Found dtc: C:/Users/Ecloud10/ncs/v1.9.1/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (C:/gnuarmemb)
-- Configuring incomplete, errors occurred!
Including boilerplate (Zephyr base (cached)): C:/Users/Ecloud10/ncs/v1.9.1/zephyr/cmake/app/boilerplate.cmake
CMake Error at C:/Users/Ecloud10/ncs/v1.9.1/zephyr/cmake/compiler/gcc/generic.cmake:9 (message):
Zephyr was unable to find the toolchain. Is the environment misconfigured?

User-configuration:

ZEPHYR_TOOLCHAIN_VARIANT: gnuarmemb

Internal variables:

CROSS_COMPILE: C:/gnuarmemb/bin/arm-none-eabi-

TOOLCHAIN_HOME: C:/gnuarmemb

Call Stack (most recent call first):
C:/Users/Ecloud10/ncs/v1.9.1/zephyr/cmake/generic_toolchain.cmake:42 (include)
C:/Users/Ecloud10/ncs/v1.9.1/zephyr/cmake/app/boilerplate.cmake:542 (include)
C:/Users/Ecloud10/ncs/v1.9.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
C:/Users/Ecloud10/ncs/v1.9.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:40 (include_boilerplate)
CMakeLists.txt:4 (find_package)



error: cmake failed
create_nordic_project.py failed (1)

Hi,

Is there a specific reason for why you are selecting NONE/PATH as toolchain version when opening the project in SES even though you have installed the SDK using Toolchain Manager? If not, I would suggest selecting the toolchain installed with Toolchain Manager, i.e. select 1.9.1 here:

If you are still seeing an issue when selecting this, please try the fixes in Common fixes for nRF Connect SDK build problems and see if any of them fixes the issue.

Best regards,

Marte

yes, the reason is that there is only one option that i can choose in nRF Connect Toolchain Version. The reference is shown in attached image link.

yes, the reason is that there is only one option that i can choose in nRF Connect Toolchain Version. The reference is shown in attached image link.

Hi,

Please try to install the SDK directly under C:/ instead of under a user, so the path is C:/ncs/v1.9.1. Then make sure the environment settings are set correct in SES:

Best regard,

Marte