• State Verified Answer
  • Replies 2 replies
  • Subscribers 72 subscribers
  • Views 116 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 341590
Options

nRF Connect SDK Fundamentals Lesson 2

MapleMan

Hello,

I'm trying to work through exercise 2 of the Nordic Developer Academy. It has me using the Blinky Sample. When I add a build configuration I get an error. I have VS Code 1.97.2, Command Line Tools 10.24.2, J-Link JTAGLoad V8.16, and selected nrf5340dk/nrf5340/cpuapp/ns selected as the board target. I've tried using other sample applications. They result in errors as well when I try to build them.

Am I using the wrong combination of software? The only deviance I noticed during install was SEGGER J-Link wasn't an option during install so I downloaded it outside of exercise 1.

Here is the terminal output:

Fullscreen Terminal Output.txt Download 
 *  Executing task: nRF Connect: Generate config nrf5340dk/nrf5340/cpuapp/ns for c:\nordic\l1_e2 

Building l1_e2
C:\Windows\system32\cmd.exe /d /s /c "west build --build-dir c:/nordic/l1_e2/build c:/nordic/l1_e2 --pristine --board nrf5340dk/nrf5340/cpuapp/ns -- -DNCS_TOOLCHAIN_VERSION=NONE -DBOARD_ROOT=c:/nordic/l1_e2"

-- west build: generating a build system
Loading Zephyr module(s) (Zephyr base): sysbuild_default
-- Found Python3: C:/ncs/toolchains/b620d30767/opt/bin/python.exe (found suitable version "3.12.4", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: C:/ncs/v2.9.0/zephyr/.cache
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: nrf5340dk, qualifiers: nrf5340/cpuapp/ns
Parsing C:/ncs/v2.9.0/zephyr/share/sysbuild/Kconfig
Loaded configuration 'C:/nordic/l1_e2/build/_sysbuild/empty.conf'
Merged configuration 'C:/nordic/l1_e2/build/_sysbuild/empty.conf'
Configuration saved to 'C:/nordic/l1_e2/build/zephyr/.config'
Kconfig header saved to 'C:/nordic/l1_e2/build/_sysbuild/autoconf.h'
-- 
   ***************************
   * Running CMake for l1_e2 *
   ***************************

Loading Zephyr default modules (Zephyr base).
-- Application: C:/nordic/l1_e2
-- CMake version: 3.21.0
-- Found Python3: C:/ncs/toolchains/b620d30767/opt/bin/python.exe (found suitable version "3.12.4", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: C:/ncs/v2.9.0/zephyr/.cache
-- Zephyr version: 3.7.99 (C:/ncs/v2.9.0/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: nrf5340dk, qualifiers: nrf5340/cpuapp/ns
-- Found host-tools: zephyr 0.17.0 (C:/ncs/toolchains/b620d30767/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.17.0 (C:/ncs/toolchains/b620d30767/opt/zephyr-sdk)
-- Found Dtc: C:/ncs/toolchains/b620d30767/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6") 
-- Found BOARD.dts: C:/ncs/v2.9.0/zephyr/boards/nordic/nrf5340dk/nrf5340dk_nrf5340_cpuapp_ns.dts
-- Generated zephyr.dts: C:/nordic/l1_e2/build/l1_e2/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/nordic/l1_e2/build/l1_e2/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: C:/nordic/l1_e2/build/l1_e2/zephyr/dts.cmake
Parsing C:/ncs/v2.9.0/zephyr/Kconfig
Loaded configuration 'C:/ncs/v2.9.0/zephyr/boards/nordic/nrf5340dk/nrf5340dk_nrf5340_cpuapp_ns_defconfig'
Merged configuration 'C:/nordic/l1_e2/prj.conf'
Merged configuration 'C:/nordic/l1_e2/build/l1_e2/zephyr/.config.sysbuild'
Configuration saved to 'C:/nordic/l1_e2/build/l1_e2/zephyr/.config'
Kconfig header saved to 'C:/nordic/l1_e2/build/l1_e2/zephyr/include/generated/zephyr/autoconf.h'
-- Found GnuLd: c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd.exe (found version "2.38") 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
=========== Generating psa_crypto_config ===============
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_SPM: False
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_C: False
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_KEY_ID_ENCODES_OWNER: False
Backup: CONFIG_MBEDTLS_PLATFORM_SETUP_TEARDOWN_ALT: False
Backup: CONFIG_MBEDTLS_THREADING: False
Backup: CONFIG_MBEDTLS_THREADING_ALT: False
=========== Checkpoint: backup ===============
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_SPM: False
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_C: False
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_KEY_ID_ENCODES_OWNER: False
Restore: CONFIG_MBEDTLS_PLATFORM_SETUP_TEARDOWN_ALT: False
Restore: CONFIG_MBEDTLS_THREADING: False
Restore: CONFIG_MBEDTLS_THREADING_ALT: False
=========== End psa_crypto_config ===============
=========== Generating psa_crypto_library_config ===============
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_C: False
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_KEY_ID_ENCODES_OWNER: False
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_SPM: False
Backup: CONFIG_MBEDTLS_USE_PSA_CRYPTO: True
Backup: CONFIG_MBEDTLS_PLATFORM_PRINTF_ALT: False
Backup: CONFIG_MBEDTLS_THREADING: False
Backup: CONFIG_MBEDTLS_THREADING_ALT: False
=========== Checkpoint: backup ===============
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_C: False
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_KEY_ID_ENCODES_OWNER: False
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_SPM: False
Restore: CONFIG_MBEDTLS_USE_PSA_CRYPTO: True
Restore: CONFIG_MBEDTLS_PLATFORM_PRINTF_ALT: False
Restore: CONFIG_MBEDTLS_THREADING: False
Restore: CONFIG_MBEDTLS_THREADING_ALT: False
=========== End psa_crypto_library_config ===============
-- Setting build type to 'MinSizeRel' as none was specified.
-- Configuring done
-- Generating done
-- Build files have been written to: C:/nordic/l1_e2/build/l1_e2
Dropping partition 'nonsecure_storage' since it is empty.
-- Configuring done
-- Generating done
-- Build files have been written to: C:/nordic/l1_e2/build
-- west build: building application
[4/217] Generating include/generated/zephyr/version.h
-- Zephyr version: 3.7.99 (C:/ncs/v2.9.0/zephyr), build: v3.7.99-ncs2
[9/217] Generating ../../tfm/CMakeCache.txt
CMake Warning at cmake/version.cmake:31 (message):
  TFM_VERSION_MANUAL mismatches to actual TF-M version.  Please update
  TFM_VERSION_MANUAL in cmake/version.cmake
Call Stack (most recent call first):
  CMakeLists.txt:13 (include)


-- Found Git: C:/ncs/toolchains/b620d30767/mingw64/bin/git.exe (found version "2.37.3.windows.1") 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
-- Found Python3: C:/ncs/toolchains/b620d30767/opt/bin/python.exe (found version "3.12.4") found components: Interpreter 
-- Found Python3: C:/ncs/toolchains/b620d30767/opt/bin/python.exe (found suitable version "3.12.4", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: C:/ncs/v2.9.0/zephyr/.cache
-- Configuring done
-- Generating done
-- Build files have been written to: C:/nordic/l1_e2/build/l1_e2/tfm
[134/138] Linking C executable bin\tfm_s.axf
Memory region         Used Size  Region Size  %age Used
           FLASH:       32100 B        32 KB     97.96%
             RAM:       10404 B        32 KB     31.75%
[135/138] Generating ../bin/tfm_s.elf
FAILED: bin/tfm_s.elf C:/nordic/l1_e2/build/l1_e2/tfm/bin/tfm_s.elf 
cmd.exe /C "cd /D C:\nordic\l1_e2\build\l1_e2\tfm\secure_fw && CMAKE_OBJCOPY-NOTFOUND -O elf32-littlearm C:/nordic/l1_e2/build/l1_e2/tfm/bin/tfm_s.axf C:/nordic/l1_e2/build/l1_e2/tfm/bin/tfm_s.elf"
'CMAKE_OBJCOPY-NOTFOUND' is not recognized as an internal or external command,
operable program or batch file.
ninja: build stopped: subcommand failed.
FAILED: modules/trusted-firmware-m/tfm-prefix/src/tfm-stamp/tfm-build tfm/bin/tfm_s.elf tfm/bin/tfm_s.bin tfm/bin/tfm_s.hex tfm/bin/tfm_s_signed.bin tfm/bin/tfm_s_ns_signed.bin tfm/api_ns/interface/lib/s_veneers.o tfm/api_ns/interface/src/tfm_attest_api.c tfm/api_ns/interface/src/tfm_crypto_api.c tfm/api_ns/interface/src/tfm_fwu_api.c tfm/api_ns/interface/src/tfm_its_api.c tfm/api_ns/interface/src/tfm_platform_api.c tfm/api_ns/interface/src/tfm_ps_api.c tfm/api_ns/interface/src/tfm_tz_psa_ns_api.c tfm/api_ns/interface/src/tfm_ioctl_core_ns_api.c C:/nordic/l1_e2/build/l1_e2/modules/trusted-firmware-m/tfm-prefix/src/tfm-stamp/tfm-build C:/nordic/l1_e2/build/l1_e2/tfm/bin/tfm_s.elf C:/nordic/l1_e2/build/l1_e2/tfm/bin/tfm_s.bin C:/nordic/l1_e2/build/l1_e2/tfm/bin/tfm_s.hex C:/nordic/l1_e2/build/l1_e2/tfm/bin/tfm_s_signed.bin C:/nordic/l1_e2/build/l1_e2/tfm/bin/tfm_s_ns_signed.bin C:/nordic/l1_e2/build/l1_e2/tfm/api_ns/interface/lib/s_veneers.o C:/nordic/l1_e2/build/l1_e2/tfm/api_ns/interface/src/tfm_attest_api.c C:/nordic/l1_e2/build/l1_e2/tfm/api_ns/interface/src/tfm_crypto_api.c C:/nordic/l1_e2/build/l1_e2/tfm/api_ns/interface/src/tfm_fwu_api.c C:/nordic/l1_e2/build/l1_e2/tfm/api_ns/interface/src/tfm_its_api.c C:/nordic/l1_e2/build/l1_e2/tfm/api_ns/interface/src/tfm_platform_api.c C:/nordic/l1_e2/build/l1_e2/tfm/api_ns/interface/src/tfm_ps_api.c C:/nordic/l1_e2/build/l1_e2/tfm/api_ns/interface/src/tfm_tz_psa_ns_api.c C:/nordic/l1_e2/build/l1_e2/tfm/api_ns/interface/src/tfm_ioctl_core_ns_api.c 
cmd.exe /C "cd /D C:\nordic\l1_e2\build\l1_e2\tfm && C:\ncs\toolchains\b620d30767\opt\bin\cmake.exe --build . -j 1"
ninja: build stopped: subcommand failed.
FAILED: _sysbuild/sysbuild/images/l1_e2-prefix/src/l1_e2-stamp/l1_e2-build C:/nordic/l1_e2/build/_sysbuild/sysbuild/images/l1_e2-prefix/src/l1_e2-stamp/l1_e2-build 
cmd.exe /C "cd /D C:\nordic\l1_e2\build\l1_e2 && C:\ncs\toolchains\b620d30767\opt\bin\cmake.exe --build ."
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\b620d30767\opt\bin\cmake.EXE' --build C:/nordic/l1_e2/build

 *  The terminal process terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it.

Parents
  • 0

    Hello, 

    It seems like this is a toolchain issue if you're not able to build any samples. Can you try an uninstall and reinstallation of the nRF Connect SDK v2.9.0 toolchain and let me know if you see any difference from that.

    Please also let us know which nRF Connect for VS Code extension version you are using.

    J-Link JTAGLoad V8.16,

    This may not be an issue, but JTAGLoad is included in more than one software pack from SEGGER. Did you install the J-Link Software and Documentation pack?

    "nrfjprog --version" in a terminal will return a J-Link version if you have it installed.

    Best regards,

    Maria

Reply
  • 0

    Hello, 

    It seems like this is a toolchain issue if you're not able to build any samples. Can you try an uninstall and reinstallation of the nRF Connect SDK v2.9.0 toolchain and let me know if you see any difference from that.

    Please also let us know which nRF Connect for VS Code extension version you are using.

    J-Link JTAGLoad V8.16,

    This may not be an issue, but JTAGLoad is included in more than one software pack from SEGGER. Did you install the J-Link Software and Documentation pack?

    "nrfjprog --version" in a terminal will return a J-Link version if you have it installed.

    Best regards,

    Maria

Children
Related
Terms of service