Migrating a Zephyr Project from Child/Parent Build System to Sysbuild: First Steps and Questions

RE: Migrating a Zephyr Project from Child/Parent Build System to Sysbuild: First Steps and Questions

lincoln-lu — Mon, 31 Mar 2025 03:18:13 GMT

Andrea Verdecchia
How did you resove the strange warnnings below? I encounter this same waning but do not know how to fix it. Thanks

warning: HW_STACK_PROTECTION (defined at
C:/ncs/v2.9.0/zephyr/soc/nxp/s32\s32k1\Kconfig.defconfig:20, arch/Kconfig:283) was assigned the
value 'y' but got the value 'n'. Check these unsatisfied dependencies: ((SOC_SERIES_S32K1 &&
SOC_FAMILY_NXP_S32) || ARCH_HAS_STACK_PROTECTION) (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_HW_STACK_PROTECTION and/or look up
HW_STACK_PROTECTION 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.

RE: Migrating a Zephyr Project from Child/Parent Build System to Sysbuild: First Steps and Questions

Andrea Verdecchia — Mon, 10 Feb 2025 13:03:13 GMT

Ok. Now it all seems to make sense. Thank you very much for the help.

RE: Migrating a Zephyr Project from Child/Parent Build System to Sysbuild: First Steps and Questions

Sigurd Hellesvik — Fri, 07 Feb 2025 13:11:58 GMT

Hi,

I am also helping with this ticket.

[quote user="Thoraz"]I keep getting errors.[/quote]

You are likely getting errors due to two things:

1. Sysbuild has a check to check if sysbuild/mcuboot/prj.conf exist if you got sysbuild/mcuboot/boards/whatever.conf. So you must have sysbuild/mcuboot/prj.conf to use board files for MCUboot.

2. Overwriting means that MCUboots prj.conf is overwritten. Removing default configuration from MCUboot has a tendency to make MCUboot fail. I recommend copying all the contents from prj.conf to sysbuild/mcuboot/prj.conf.

Regards,
Sigurd Hellesvik

RE: Migrating a Zephyr Project from Child/Parent Build System to Sysbuild: First Steps and Questions

Andrea Verdecchia — Wed, 05 Feb 2025 18:20:44 GMT

I have found that if I use the standard Overlaying approach

├── sysbuild
    └── boards
        └── board_rev1.conf
        └── board_rev1.overlay
        └── board_rev2.conf
        └── board_rev2.overlay
    └── mcuboot.conf

I can compile without any issues. However, if I adopt the Overwriting approach

├── sysbuild
    └── mcuboot
        └── boards
            └── board_rev1.conf
            └── board_rev1.overlay
            └── board_rev2.conf
            └── board_rev2.overlay
        └── prj.conf

I keep getting errors.

The Overlaying approach is fine for me, but I would like to understand:

Why does the Overwriting approach keep failing? Does the prj.conf file necessarily need to contain specific configurations?
When using the Overlaying approach, is it correct to place the .conf and .overlay files for the different board revisions inside a boards/ folder?

RE: Migrating a Zephyr Project from Child/Parent Build System to Sysbuild: First Steps and Questions

AHaug — Wed, 05 Feb 2025 14:36:27 GMT

You're absolutely right, my bad. I was a bit too quick and missed the extra folder in the path you explicitly wrote out...

Moving back a bit then. Yes, it is as you say. mcuboot.conf must be directly under sysbuild/ (https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-sysbuild/topic/sysbuild-configuration/

You should be able to add the custom board structure as you say, but I believe we both need to go through the contents of that lesson step by step to better clarify any misconceptions w.r.t adding separate board configurations in sysbuild. I will get back to you tomorrow.

Kind regards,
Andreas

RE: Migrating a Zephyr Project from Child/Parent Build System to Sysbuild: First Steps and Questions

Andrea Verdecchia — Wed, 05 Feb 2025 14:05:19 GMT

[quote userid="107683" url="~/f/nordic-q-a/118562/migrating-a-zephyr-project-from-child-parent-build-system-to-sysbuild-first-steps-and-questions/521558"]As you can see from this sample showcasing how to set up mcuboot and external flash over SPI for the 54L15DK it does not give any build errors:[/quote]

If I compile the project as it is, I don't get any errors. But if I change the location of the mcuboot.conf and mcuboot.overlay files to /sysbuild/mcuboot/, then I get an error. Apparently, mcuboot.conf must be under sysbuild/ and not in its subdirectories.

RE: Migrating a Zephyr Project from Child/Parent Build System to Sysbuild: First Steps and Questions

AHaug — Wed, 05 Feb 2025 13:48:25 GMT

[quote user="Thoraz"]I hadn't seen the tutorial on the academy. Things are much clearer now.[/quote]

No worries, lesson 8 and parts of lesson 9 was as mentioned updated just now this week :)

[quote user="Thoraz"]If I have[/quote]

This is interesting. As you can see from this sample showcasing how to set up mcuboot and external flash over SPI for the 54L15DK it does not give any build errors:

devzone.nordicsemi.com/.../2_5F00_spi.zip

Are you able to compile this? If you're using command line, it should build out of the box for NCS v2.9.0 with 'west build -b nrf54l15dk/nrf54l15/cpuapp --sysbuild"

If it compiles, have you made sure to enable MCUboot in your sysbuild.conf through SB_CONFIG_BOOTLOADER_MCUBOOT=y?

Kind regards,
Andreas

RE: Migrating a Zephyr Project from Child/Parent Build System to Sysbuild: First Steps and Questions

Andrea Verdecchia — Wed, 05 Feb 2025 12:03:05 GMT

Thank you very much for your suggestions. I hadn't seen the tutorial on the academy. Things are much clearer now.

After that, I tried creating a project from scratch, also creating a new board from scratch, then gradually adding the configurations of my project to be converted, and finally adding all the application sources.

Everything works fine until I start having issues with the creation of the MCUBoot configuration file. Apparently, the configuration file, which I named mcuboot.conf, must necessarily be in the sysbuild/ folder and nowhere else. Even if I create an empty folder named mcuboot/, I get a compilation error.

The different cases are as follows:

If I have

├── sysbuild
    └── mcuboot.conf

This is ok!

If I have

├── sysbuild
    └── mcuboot
        └── mcuboot.conf

it give me error:

-- 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: gravity_sensor, qualifiers: nrf52840
Parsing C:/ncs/v2.9.0/zephyr/share/sysbuild/Kconfig
Loaded configuration 'C:/Users/Andrea/Desktop/sysbuild_test/build/_sysbuild/empty.conf'
Merged configuration 'c:/Users/Andrea/Desktop/sysbuild_test/sysbuild.conf'
Configuration saved to 'C:/Users/Andrea/Desktop/sysbuild_test/build/zephyr/.config'
Kconfig header saved to 'C:/Users/Andrea/Desktop/sysbuild_test/build/_sysbuild/autoconf.h'
-- 
   *****************************
   * Running CMake for mcuboot *
   *****************************

Loading Zephyr default modules (Zephyr base).
-- Application: C:/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr
-- 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: gravity_sensor, qualifiers: nrf52840
CMake Error at C:/ncs/v2.9.0/zephyr/cmake/modules/extensions.cmake:2923 (message):
  No prj.conf file(s) was found in the
  C:/Users/Andrea/Desktop/sysbuild_test/sysbuild/mcuboot folder(s), please
  read the Zephyr documentation on application development.
Call Stack (most recent call first):
  C:/ncs/v2.9.0/zephyr/cmake/modules/configuration_files.cmake:40 (zephyr_file)
  C:/ncs/v2.9.0/zephyr/cmake/modules/zephyr_default.cmake:133 (include)
  C:/ncs/v2.9.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/ncs/v2.9.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:12 (find_package)


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

  Location: C:/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/
Call Stack (most recent call first):
  cmake/modules/sysbuild_images.cmake:20 (ExternalZephyrProject_Cmake)
  cmake/modules/sysbuild_default.cmake:20 (include)
  C:/ncs/v2.9.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include)
  C:/ncs/v2.9.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  C:/ncs/v2.9.0/zephyr/share/sysbuild-package/cmake/SysbuildConfig.cmake:8 (include)
  template/CMakeLists.txt:10 (find_package)

If I have

├── sysbuild
    └── mcuboot/
    └── mcuboot.conf

it give me error:

-- 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: gravity_sensor, qualifiers: nrf52840
Parsing C:/ncs/v2.9.0/zephyr/share/sysbuild/Kconfig
Loaded configuration 'C:/Users/Andrea/Desktop/sysbuild_test/build/_sysbuild/empty.conf'
Merged configuration 'c:/Users/Andrea/Desktop/sysbuild_test/sysbuild.conf'
Configuration saved to 'C:/Users/Andrea/Desktop/sysbuild_test/build/zephyr/.config'
Kconfig header saved to 'C:/Users/Andrea/Desktop/sysbuild_test/build/_sysbuild/autoconf.h'
-- 
   *****************************
   * Running CMake for mcuboot *
   *****************************

Loading Zephyr default modules (Zephyr base).
-- Application: C:/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr
-- 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: gravity_sensor, qualifiers: nrf52840
CMake Error at C:/ncs/v2.9.0/zephyr/cmake/modules/extensions.cmake:2923 (message):
  No prj.conf file(s) was found in the
  C:/Users/Andrea/Desktop/sysbuild_test/sysbuild/mcuboot folder(s), please
  read the Zephyr documentation on application development.
Call Stack (most recent call first):
  C:/ncs/v2.9.0/zephyr/cmake/modules/configuration_files.cmake:40 (zephyr_file)
  C:/ncs/v2.9.0/zephyr/cmake/modules/zephyr_default.cmake:133 (include)
  C:/ncs/v2.9.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/ncs/v2.9.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:12 (find_package)


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

  Location: C:/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/
Call Stack (most recent call first):
  cmake/modules/sysbuild_images.cmake:20 (ExternalZephyrProject_Cmake)
  cmake/modules/sysbuild_default.cmake:20 (include)
  C:/ncs/v2.9.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include)
  C:/ncs/v2.9.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  C:/ncs/v2.9.0/zephyr/share/sysbuild-package/cmake/SysbuildConfig.cmake:8 (include)
  template/CMakeLists.txt:10 (find_package)

Did I miss something?

RE: Migrating a Zephyr Project from Child/Parent Build System to Sysbuild: First Steps and Questions

AHaug — Tue, 04 Feb 2025 14:12:11 GMT

Looks like the individual board configuration is working as it should. Issue should not be there. See https://github.com/nrfconnect/sdk-nrf/tree/main/samples/nrf5340/extxip_smp_svr/sysbuild/mcuboot as an example.

This loops back to having to individually go through the configurations to isolate the issue.

Kind regards,
Andreas

RE: Migrating a Zephyr Project from Child/Parent Build System to Sysbuild: First Steps and Questions

AHaug — Tue, 04 Feb 2025 13:36:25 GMT

Hi,

Just FYI, the sysbuild course was just released on the academy pages https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-sysbuild/

[quote user="AHaug"] but I need to check up on the individual configuration for sysbuild for the various boards. I believe that there might be some limitations there.[/quote]

It does look like we don't support individual sysbuild configurations for the various boards as of now, meaning that sysbuild/mcuboot/boards does not work in sysbuild as of now. This worked with child_image because Key was an MCUboot-specific options, but now it is a sysbuild option.

Could you strip down the port of your application even further and see if you're able to make it work without sysbuild specific board configurations, i.e this:

I've also started an ongoing internal discussion w.r.t this is possible, but if you're able to get the latest suggestion compiling and flashing (and to whatever extent it will be running), then the root case is indeed this.

Kind regards,
Andreas

RE: Migrating a Zephyr Project from Child/Parent Build System to Sysbuild: First Steps and Questions

Andrea Verdecchia — Mon, 03 Feb 2025 19:47:37 GMT

Thank you very much for your advice. I checked the links you sent me and reviewed everything. In my opinion, everything should be configured correctly, but I keep getting errors/warnings regarding some configurations in prj.conf and in the file generated by the nRF Connect script for VS Code when creating the board from scratch: CONFIG_ARM_MPU, CONFIG_HW_STACK_PROTECTION, CONFIG_FLASH_MAP, etc.

warning: HW_STACK_PROTECTION (defined at
C:/ncs/v2.9.0/zephyr/soc/nxp/s32\s32k1\Kconfig.defconfig:20, arch/Kconfig:283) was assigned the
value 'y' but got the value 'n'. Check these unsatisfied dependencies: ((SOC_SERIES_S32K1 &&
SOC_FAMILY_NXP_S32) || ARCH_HAS_STACK_PROTECTION) (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_HW_STACK_PROTECTION and/or look up
HW_STACK_PROTECTION 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: ARM_MPU (defined at C:/ncs/v2.9.0/zephyr/arch/arm64\core\cortex_r/Kconfig:10,
C:/ncs/v2.9.0/zephyr/arch/arm\core\mpu/Kconfig:8) was assigned the value 'y' but got the value 'n'.
Check these unsatisfied dependencies: ((CPU_HAS_MPU && CPU_AARCH64_CORTEX_R && ARM64) ||
(CPU_HAS_MPU && ARM)) (=n). See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_ARM_MPU
and/or look up ARM_MPU 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: FLASH_MAP (defined at subsys/storage/flash_map/Kconfig:10) has direct dependencies FLASH_HAS_DRIVER_ENABLED with value n, but is currently being y-selected by the following symbols:
 - MCUBOOT_DEVICE_SETTINGS (defined at C:/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/Kconfig:995), with value y, direct dependencies y (value: y)

error: Aborting due to Kconfig warnings

If you want to take a look, I have stripped my project down to the bare minimum, keeping only the structure and configuration files intact. I am trying to use NCS 2.9.0. You can find the project here.

RE: Migrating a Zephyr Project from Child/Parent Build System to Sysbuild: First Steps and Questions

AHaug — Mon, 03 Feb 2025 13:36:07 GMT

Hi,

[quote user=""]From what I understand, the first step is to delete the child_image folder, create a sysbuild folder, and add a sysbuild.conf file. But what exactly should I include in these two elements, and what modifications, if any, do I need to make to prj.conf and CMakeLists.txt?[/quote]

Yes, this is correct. You'll need to move the child_image overlays and configurations present within the child_image folder and place them within the sysbuild folder which contains the new companion components, which replaces the child_image system.

In addition, you need to consult the sysbuild migration guide https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_sysbuild.html and the three links here:

The last link, sysbuild forced options, shows a list of which options that were previously defined within prj.conf that you now need to add to sysbuild.conf. If these configurations are present within prj.conf but not within sysbuild.conf they will be ignored.

[quote user=""]project as follows:[/quote]

The structure looks good to me at first glance, but I need to check up on the individual configuration for sysbuild for the various boards. I believe that there might be some limitations there.

[quote user="Thoraz"]I reanalyzed the issue and noticed that the error might have been due to using HWMv1 instead of HWMv2. So,[/quote]

Yup, that is correct! As the warning states:

---------------------------------------------------------------------
--- WARNING: Functionality to describe SoCs in HWMv1 is ---
--- deprecated and should be replaced with HWMv2, including ---
--- boards. HWMv1 SoCs support remains only to ease the migration ---
--- of out-of-tree SoCs and associated boards. It will not be ---
--- possible to build using HWMv1 SoCs at all in future releases. ---
---------------------------------------------------------------------

There's a guide for how to migrate here: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_hwmv2.html

[quote user="Thoraz"]I copied the new files into my project, but during compilation, I still encounter errors, different from the previous ones:[/quote]

The next set of warnings seems to be Kconfig related, i.e "error: Aborting due to Kconfig warnings". This is most likely due to either changes in the configurations in between the upmerge you've done, or that there is something that should've been a SB_Configuration instead of a prj.configuration. It will require some manual labour from you to go through the migration notes for the respective versions you've gone through.

Let me know if this is enough to get you pointed, and I'll get back to you w.r.t the multiple sysbuild/board configurations.

Kind regards,
Andreas

RE: Migrating a Zephyr Project from Child/Parent Build System to Sysbuild: First Steps and Questions

Andrea Verdecchia — Mon, 03 Feb 2025 08:33:29 GMT

I reanalyzed the issue and noticed that the error might have been due to using HWMv1 instead of HWMv2. So, I created a new board using the nRF Connect tool in VS Code, which generated the files according to the new protocol.

boards
└── my_company
    └── my_board.overlay
    └── my_board
        ├── board.cmake
        ├── board.yml
        ├── my_board_defconfig
        ├── my_board-pinctrl.dtsi
        ├── my_board.dts
        ├── my_board.yml
        ├── Kcongig.defconfif
        ├── Kcongig.my_board
        └── pre_dt_noard.cmake

I copied the new files into my project, but during compilation, I still encounter errors, different from the previous ones:

-- 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: gravity_sensor, qualifiers: nrf52840
Parsing C:/ncs/v2.9.0/zephyr/share/sysbuild/Kconfig
Loaded configuration 'C:/Users/Andrea/Desktop/gravity_sensor/build/_sysbuild/empty.conf'
Merged configuration 'c:/Users/Andrea/Desktop/gravity_sensor/sysbuild.conf'
Configuration saved to 'C:/Users/Andrea/Desktop/gravity_sensor/build/zephyr/.config'
Kconfig header saved to 'C:/Users/Andrea/Desktop/gravity_sensor/build/_sysbuild/autoconf.h'
-- 
   *****************************
   * Running CMake for mcuboot *
   *****************************

Loading Zephyr default modules (Zephyr base).
-- Application: C:/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr
-- 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: gravity_sensor, qualifiers: nrf52840
-- 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:/Users/Andrea/Desktop/gravity_sensor/boards/ardesia_technologies/gravity_sensor/gravity_sensor.dts
-- Generated zephyr.dts: C:/Users/Andrea/Desktop/gravity_sensor/build/mcuboot/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/Users/Andrea/Desktop/gravity_sensor/build/mcuboot/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: C:/Users/Andrea/Desktop/gravity_sensor/build/mcuboot/zephyr/dts.cmake

warning: HW_STACK_PROTECTION (defined at
C:/ncs/v2.9.0/zephyr/soc/nxp/s32\s32k1\Kconfig.defconfig:20, arch/Kconfig:283) was assigned the
value 'y' but got the value 'n'. Check these unsatisfied dependencies: ((SOC_SERIES_S32K1 &&
SOC_FAMILY_NXP_S32) || ARCH_HAS_STACK_PROTECTION) (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_HW_STACK_PROTECTION and/or look up
HW_STACK_PROTECTION 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: ARM_MPU (defined at C:/ncs/v2.9.0/zephyr/arch/arm64\core\cortex_r/Kconfig:10,
C:/ncs/v2.9.0/zephyr/arch/arm\core\mpu/Kconfig:8) was assigned the value 'y' but got the value 'n'.
Check these unsatisfied dependencies: ((CPU_HAS_MPU && CPU_AARCH64_CORTEX_R && ARM64) ||
(CPU_HAS_MPU && ARM)) (=n). See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_ARM_MPU
and/or look up ARM_MPU 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: FLASH_MAP (defined at subsys/storage/flash_map/Kconfig:10) has direct dependencies FLASH_HAS_DRIVER_ENABLED with value n, but is currently being y-selected by the following symbols:
 - MCUBOOT_DEVICE_SETTINGS (defined at C:/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/Kconfig:995), with value y, direct dependencies y (value: y)
Parsing C:/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/Kconfig
Loaded configuration 'C:/Users/Andrea/Desktop/gravity_sensor/boards/ardesia_technologies/gravity_sensor/gravity_sensor_defconfig'
Merged configuration 'C:/Users/Andrea/Desktop/gravity_sensor/sysbuild/mcuboot/prj.conf'
Merged configuration 'C:/Users/Andrea/Desktop/gravity_sensor/build/mcuboot/zephyr/.config.sysbuild'

error: Aborting due to Kconfig warnings

CMake Error at C:/ncs/v2.9.0/zephyr/cmake/modules/kconfig.cmake:396 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  C:/ncs/v2.9.0/nrf/cmake/modules/kconfig.cmake:29 (include)
  C:/ncs/v2.9.0/zephyr/cmake/modules/zephyr_default.cmake:133 (include)
  C:/ncs/v2.9.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/ncs/v2.9.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:12 (find_package)


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

  Location: C:/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/
Call Stack (most recent call first):
  cmake/modules/sysbuild_images.cmake:20 (ExternalZephyrProject_Cmake)
  cmake/modules/sysbuild_default.cmake:20 (include)
  C:/ncs/v2.9.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include)
  C:/ncs/v2.9.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  C:/ncs/v2.9.0/zephyr/share/sysbuild-package/cmake/SysbuildConfig.cmake:8 (include)
  template/CMakeLists.txt:10 (find_package)


-- Configuring incomplete, errors occurred!
See also "C:/Users/Andrea/Desktop/gravity_sensor/build/CMakeFiles/CMakeOutput.log".
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\b620d30767\opt\bin\cmake.EXE' -DWEST_PYTHON=C:/ncs/toolchains/b620d30767/opt/bin/python.exe '-Bc:\Users\Andrea\Desktop\gravity_sensor\build' -GNinja -DBOARD=gravity_sensor/nrf52840 -DNCS_TOOLCHAIN_VERSION=NONE -DBOARD_ROOT=c:/users/andrea/desktop/gravity_sensor '-SC:\ncs\v2.9.0\zephyr\share\sysbuild' '-DAPP_DIR:PATH=c:\Users\Andrea\Desktop\gravity_sensor'

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