SDK v3.2.1, Toolchain v3.2.1

cptel

I made a dreaded mistake of upgrading the SDK & Toolchain at the nth hour to v3.2.1. As a result, I am somewhat stuck.
I am using nrf connect in VS on a mac and it is unable to find board ‘circuitdojo_feather/nrf9151’. I have followed the guidelines from this link: https://docs.circuitdojo.com/nrf9151-feather/using-vscode.html and there’s a disconnect as it downloads for v 3.0.x while SDK is already at v3.2.1. I see the files in /ncs directory but VS Code does not pick up the 9151 board.
fyi.. it finds the circuitdojo_feather/nrf9160 and the ns variant - which is part of zephyr

jaredwolff

@cptel the way you update the toolchain with the nRF9151 Feather is by changing the branch of nfed, if supported, to the appropriate version. I just created the v3.2.x branch recently. It’s not the default but most of the samples are building.

Zephyr uses the west.yml file to determine what dependencies are required. Looks like maybe you’re overriding to use the NCS west.yml instead of nfed. Do you have an nfed directory?

cptel

yes, here’s the directory structure:

jaredwolff

If you go to the Manage SDKs -> Manage west workspace... -> Set west manifest repository and make sure nfed is selected you should be back to square one

You should be able to check out the v3.2.x branch and then run nRF Connect: West Update and get everything pulled in.

I do recommend though that you set up your own west.yml in your project that way you can control the dependencies and they’re committed to source control.

Here’s an example of that:

manifest:
  remotes:
    - name: nrfconnect
      url-base: https://github.com/nrfconnect
  projects:
    - name: nrf
      repo-path: sdk-nrf
      remote: nrfconnect
      revision: v2.7.0
      import:
        name-blocklist:
          - matter
          - nrf-802154
          - openthread
          - cmock
          - unity
          - cddl-gen
          - homekit
          - loramac-node
          - lz4
          - lvgl
          - mipi-sys-t
    - name: nfed
      url: https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers.git
      path: nfed
      revision: v2.7.x
  self:
    # This repository should be cloned to 
    path: app

This is for NCS 2.7 but you should get the idea.

cptel

good news - I am able to build the blinky program.

Next step: figure out why i am getting this error:

-- Configuring incomplete, errors occurred!
CMake Error at cmake/modules/sysbuild_extensions.cmake:530 (message):
  CMake configure failed for Zephyr project: PWL

  Location: /Users/summer/PWL
Call Stack (most recent call first):
  cmake/modules/sysbuild_images.cmake:43 (ExternalZephyrProject_Cmake)
  cmake/modules/sysbuild_default.cmake:21 (include)
  /opt/nordic/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include)
  /opt/nordic/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  /opt/nordic/zephyr/share/sysbuild-package/cmake/SysbuildConfig.cmake:8 (include)
  template/CMakeLists.txt:10 (find_package)

Looking back, you have outlined steps at: https://docs.circuitdojo.com/nrf9151-feather/using-vscode.html and is fairly spot-on. I am just not a build setup guy. Lessons learned and time to make some progress.

jaredwolff

Is it possible you have a space in your path? Zephyr does not like spaces.

Other than that I would delete/clean your build directory as it probably has artifacts from your last attempted build

cptel

no spaces in any path. Did a clean build and issue still there. Appears to be configuration error:

 *  Executing task: nRF Connect: Generate config circuitdojo_feather_nrf9151/nrf9151/ns for /opt/PWL 

Building PWL
west build --build-dir /opt/PWL/build /opt/PWL --pristine --board circuitdojo_feather_nrf9151/nrf9151/ns --sysbuild -- -DCONFIG_DEBUG_THREAD_INFO=y

-- west build: generating a build system
Loading Zephyr module(s) (Zephyr base): sysbuild_default
-- Found Python3: /opt/nordic/ncs/toolchains/322ac893fe/opt/python@3.12/bin/python3.12 (found suitable version "3.12.4", minimum required is "3.10") found components: Interpreter 
-- Cache files will be written to: /Users/summer/Library/Caches/zephyr
-- Found west (found suitable version "1.4.0", minimum required is "0.14.0")
-- Board: circuitdojo_feather_nrf9151, Revision: 1, qualifiers: nrf9151/ns
Parsing /opt/nordic/zephyr/share/sysbuild/Kconfig
Loaded configuration '/opt/PWL/build/_sysbuild/empty.conf'
Merged configuration '/opt/PWL/build/_sysbuild/empty.conf'
Merged configuration '/opt/PWL/sysbuild.conf'
Configuration saved to '/opt/PWL/build/zephyr/.config'
Kconfig header saved to '/opt/PWL/build/_sysbuild/autoconf.h'
-- Sysbuild assigned MCUboot image IDs:
   * Application: 0
-- 
   *****************************
   * Running CMake for mcuboot *
   *****************************

Loading Zephyr default modules (Zephyr base).
-- Application: /opt/nordic/bootloader/mcuboot/boot/zephyr
-- CMake version: 3.21.0
-- Found Python3: /opt/nordic/ncs/toolchains/322ac893fe/bin/python (found suitable version "3.12.4", minimum required is "3.10") found components: Interpreter 
-- Cache files will be written to: /Users/summer/Library/Caches/zephyr
-- Zephyr version: 4.2.99 (/opt/nordic/zephyr)
-- Found west (found suitable version "1.4.0", minimum required is "0.14.0")
-- Board: circuitdojo_feather_nrf9151, Revision: 1, qualifiers: nrf9151
-- Found host-tools: zephyr 0.17.0 (/opt/nordic/ncs/toolchains/322ac893fe/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.17.0 (/opt/nordic/ncs/toolchains/322ac893fe/opt/zephyr-sdk)
-- Found Dtc: /opt/nordic/ncs/toolchains/322ac893fe/bin/dtc (found suitable version "1.6.1", minimum required is "1.4.6") 
-- Found BOARD.dts: /opt/nordic/nfed/boards/circuitdojo/feather_nrf9151/circuitdojo_feather_nrf9151.dts
-- Found devicetree overlay: /opt/nordic/bootloader/mcuboot/boot/zephyr/app.overlay
-- Generated zephyr.dts: /opt/PWL/build/mcuboot/zephyr/zephyr.dts
-- Generated pickled edt: /opt/PWL/build/mcuboot/zephyr/edt.pickle
-- Generated devicetree_generated.h: /opt/PWL/build/mcuboot/zephyr/include/generated/zephyr/devicetree_generated.h

warning: UART_CONSOLE (defined at drivers/console/Kconfig:42) was assigned the value 'y' but got the
value 'n'. Check these unsatisfied dependencies: CONSOLE (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_UART_CONSOLE and/or look up UART_CONSOLE in
the menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration
Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful too.


warning: I2C (defined at drivers/i2c/Kconfig:9) was assigned the value 'n' but got the value 'y'.
See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_I2C and/or look up I2C in the
menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration Values,
and Kconfig - Tips and Best Practices sections of the manual might be helpful too.

Parsing /opt/nordic/bootloader/mcuboot/boot/zephyr/Kconfig
Loaded configuration '/opt/nordic/nfed/boards/circuitdojo/feather_nrf9151/circuitdojo_feather_nrf9151_defconfig'
Merged configuration '/opt/nordic/bootloader/mcuboot/boot/zephyr/prj.conf'
Merged configuration '/opt/PWL/sysbuild/mcuboot.conf'
Merged configuration '/opt/nordic/nrf/modules/mcuboot/tfm.conf'
Merged configuration '/opt/PWL/build/mcuboot/zephyr/.config.sysbuild'
Configuration saved to '/opt/PWL/build/mcuboot/zephyr/.config'
Kconfig header saved to '/opt/PWL/build/mcuboot/zephyr/include/generated/zephyr/autoconf.h'
-- Found GnuLd: /opt/nordic/ncs/toolchains/322ac893fe/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd (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: /opt/nordic/ncs/toolchains/322ac893fe/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
-- Using ccache: /opt/nordic/ncs/toolchains/322ac893fe/bin/ccache
-- Found gen_kobject_list: /opt/nordic/zephyr/scripts/build/gen_kobject_list.py
CMake Warning at /opt/nordic/zephyr/CMakeLists.txt:1096 (message):
  No SOURCES given to Zephyr library:
  ..__nfed__boards__circuitdojo__feather_nrf9151

  Excluding target from build.


MCUBoot bootloader key file: /opt/nordic/bootloader/mcuboot/root-ec-p256.pem
CMake Warning at CMakeLists.txt:442 (message):
  WARNING: Using default MCUboot signing key file, this file is for debug use
  only and is not secure!


-- Configuring done
-- Generating done
-- Build files have been written to: /opt/PWL/build/mcuboot
-- 
   *************************
   * Running CMake for PWL *
   *************************

Loading Zephyr default modules (Zephyr base).
-- Application: /opt/PWL
-- CMake version: 3.21.0
-- Found Python3: /opt/nordic/ncs/toolchains/322ac893fe/bin/python (found suitable version "3.12.4", minimum required is "3.10") found components: Interpreter 
-- Cache files will be written to: /Users/summer/Library/Caches/zephyr
-- Zephyr version: 4.2.99 (/opt/nordic/zephyr)
-- Found west (found suitable version "1.4.0", minimum required is "0.14.0")
-- Board: circuitdojo_feather_nrf9151, Revision: 1, qualifiers: nrf9151/ns
-- Found host-tools: zephyr 0.17.0 (/opt/nordic/ncs/toolchains/322ac893fe/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.17.0 (/opt/nordic/ncs/toolchains/322ac893fe/opt/zephyr-sdk)
-- Found Dtc: /opt/nordic/ncs/toolchains/322ac893fe/bin/dtc (found suitable version "1.6.1", minimum required is "1.4.6") 
-- Found BOARD.dts: /opt/nordic/nfed/boards/circuitdojo/feather_nrf9151/circuitdojo_feather_nrf9151_ns.dts
-- Found devicetree overlay: /opt/PWL/boards/circuitdojo_feather_nrf9151_ns.overlay
-- Generated zephyr.dts: /opt/PWL/build/PWL/zephyr/zephyr.dts
-- Generated pickled edt: /opt/PWL/build/PWL/zephyr/edt.pickle
-- Generated devicetree_generated.h: /opt/PWL/build/PWL/zephyr/include/generated/zephyr/devicetree_generated.h

warning: UPDATEABLE_IMAGE_NUMBER (defined at
/opt/nordic/nrf/modules/../samples/common/mcumgr_bt_ota_dfu/Kconfig:87, subsys/dfu/Kconfig:96) was
assigned the value '1' but got the value ''. Check these unsatisfied dependencies:
(((BOARD_THINGY53_NRF5340_CPUAPP || BOARD_THINGY53_NRF5340_CPUAPP_NS) && SOC_SERIES_NRF53X &&
NCS_SAMPLE_MCUMGR_BT_OTA_DFU) || (!MCUBOOT && IMG_MANAGER)) (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_UPDATEABLE_IMAGE_NUMBER and/or look up
UPDATEABLE_IMAGE_NUMBER in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.


warning: MCUBOOT_UPDATE_FOOTER_SIZE (defined at subsys/dfu/Kconfig:55) was assigned the value
'0x2000' but got the value ''. Check these unsatisfied dependencies: MCUBOOT_IMG_MANAGER (=n),
IMG_MANAGER (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_MCUBOOT_UPDATE_FOOTER_SIZE and/or look up
MCUBOOT_UPDATE_FOOTER_SIZE in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.

Parsing /opt/nordic/zephyr/Kconfig
Loaded configuration '/opt/nordic/nfed/boards/circuitdojo/feather_nrf9151/circuitdojo_feather_nrf9151_ns_defconfig'
Merged configuration '/opt/PWL/prj.conf'
Merged configuration '/opt/PWL/boards/circuitdojo_feather_nrf9151_ns.conf'
Merged configuration '/opt/PWL/build/PWL/zephyr/misc/generated/extra_kconfig_options.conf'
Merged configuration '/opt/PWL/build/PWL/zephyr/.config.sysbuild'
**-- Configuring incomplete, errors occurred!**

/opt/PWL/prj.conf:96: warning: attempt to assign the value 'y' to the undefined symbol LED_NPM1300

/opt/PWL/boards/circuitdojo_feather_nrf9151_ns.conf:2: warning: attempt to assign the value 'y' to the undefined symbol MFD_NPM1300

error: Aborting due to Kconfig warnings

CMake Error at /opt/nordic/zephyr/cmake/modules/kconfig.cmake:387 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  /opt/nordic/nrf/cmake/modules/kconfig.cmake:112 (include)
  /opt/nordic/zephyr/cmake/modules/zephyr_default.cmake:131 (include)
  /opt/nordic/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  /opt/nordic/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:6 (find_package)


CMake Error at cmake/modules/sysbuild_extensions.cmake:530 (message):
  CMake configure failed for Zephyr project: PWL

  Location: /opt/PWL
Call Stack (most recent call first):
  cmake/modules/sysbuild_images.cmake:43 (ExternalZephyrProject_Cmake)
  cmake/modules/sysbuild_default.cmake:21 (include)
  /opt/nordic/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include)
  /opt/nordic/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  /opt/nordic/zephyr/share/sysbuild-package/cmake/SysbuildConfig.cmake:8 (include)
  template/CMakeLists.txt:10 (find_package)


-- Configuring incomplete, errors occurred!
See also "/opt/PWL/build/CMakeFiles/CMakeOutput.log".
FATAL ERROR: command exited with status 1: /opt/nordic/ncs/toolchains/322ac893fe/bin/cmake -DWEST_PYTHON=/opt/nordic/ncs/toolchains/322ac893fe/opt/python@3.12/bin/python3.12 -B/opt/PWL/build -GNinja -DBOARD=circuitdojo_feather_nrf9151/nrf9151/ns -DCONFIG_DEBUG_THREAD_INFO=y -S/opt/nordic/zephyr/share/sysbuild -DAPP_DIR:PATH=/opt/PWL

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

jaredwolff

There’s all types of errors you need to address from changing SDK versions. Your application is still using Kconfig values that no longer exist in 3.2.x.

I have yet to run though and resolve some of the same errors you’re having. If I were you I would stick with 3.1.x unless there are certain features you absolutely need in 3.2.x. This is always the risk from going from one SDK version to another.

Side note: Nordic usually has a good change log in the nrf folder which tells you what has changed. They often indicate what the old Kconfig values are mapped to in the new version.

cptel

jaredwolff I do not have any reason to run ahead of you. Just made a fatal error or trying to update the SDK, thinking what could go wrong, without knowing the full impact.
I’ll revert back to NFED 3.1.x.
Do I need to revert the SDK & Toolchain from v3.2.1 to anything else?

jaredwolff

I would make sure that the SDK is the same version for sanity sake.

cptel

jaredwolff fyi… set SDK + Toolchain to 3.1.1 and NFED to 3.1.x. My app built as expected, moving forward again.
Appreciate your help!
Next time, i’ll look for an email/notification from you that its safe to update to next rev of SDK/Toolchain before I attempt.

AchimKraus

Side note: Nordic usually has a good change log

The nasty point of that is the size of that log ;-).
May app (plain nRF9160-DK) on NCS 3.2.1 currently sticks in an “fatal error” calling “sendto”.