Home
last modified time | relevance | path

Searched refs:sysbuild (Results 1 – 25 of 66) sorted by relevance

123

/Zephyr-Core-3.5.0/samples/application_development/sysbuild/with_mcuboot/
DREADME.rst8 A simple example that demonstrates how building a sample using sysbuild can
17 sysbuild.
19 This is achieved with a sysbuild specific Kconfig configuration,
20 :file:`sysbuild.conf`.
22 The `SB_CONFIG_BOOTLOADER_MCUBOOT=y` setting in the sysbuild Kconfig file
23 enables the bootloader when building with sysbuild.
25 The :file:`sysbuild/mcuboot.conf` file will be used as an extra fragment that
28 :file:`sysbuild/mcuboot.conf` adjusts the log level in MCUboot, as well as
35 :app: samples/application_development/sysbuild/with_mcuboot
38 :west-args: --sysbuild
[all …]
/Zephyr-Core-3.5.0/tests/cmake/zephyr_get/
DCMakeLists.txt19 # at the end, either here or in sysbuild.cmake.
87 # Test with a local variable not controlled by sysbuild.
131 # LOCAL sysbuild-defined value for this primary image.
132 IMAGE zephyr_get "sysbuild.main"
134 # the LOCAL sysbuild-defined value for this secondary image.
135 IMAGE zephyr_get_2nd "sysbuild.2nd"
137 # GLOBAL sysbuild-defined value for this tertiary image;
139 IMAGE zephyr_get_3rd "sysbuild.main"
148 IMAGE zephyr_get "sysbuild.main"
149 IMAGE zephyr_get_2nd "sysbuild.2nd"
[all …]
/Zephyr-Core-3.5.0/doc/build/sysbuild/
Dindex.rst11 For example, you can use sysbuild to build a Zephyr application together
19 Like Zephyr's :ref:`build system <build_overview>`, sysbuild is written in
28 When sysbuild is used to create and manage just one Zephyr application's
32 When sysbuild is used to manage multiple build systems.
37 Every Zephyr CMake build system managed by sysbuild.
40 When more than one Zephyr CMake build system (domain) is managed by sysbuild.
45 This figure is an overview of sysbuild's inputs, outputs, and user interfaces:
47 .. figure:: sysbuild.svg
53 The following are some key sysbuild features indicated in this figure:
55 - You can run sysbuild either with :ref:`west build
[all …]
/Zephyr-Core-3.5.0/share/sysbuild/
DCMakeLists.txt16 # Add sysbuild/cmake/modules to CMAKE_MODULE_PATH which allows us to integrate
17 # sysbuild CMake modules with general Zephyr CMake modules.
19 # List of Zephyr and sysbuild CMake modules we need for sysbuild.
25 project(sysbuild LANGUAGES) project
DKconfig7 osource "$(BOARD_DIR)/Kconfig.sysbuild"
11 source "modules/Kconfig.sysbuild"
/Zephyr-Core-3.5.0/samples/subsys/ipc/openamp/
DREADME.rst13 independently, but sysbuild must be used in order to build the images.
22 :west-args: --sysbuild
31 :west-args: --sysbuild
40 :west-args: --sysbuild
49 :west-args: --sysbuild
58 :west-args: --sysbuild
/Zephyr-Core-3.5.0/tests/boot/mcuboot_recovery_retention/
Dsysbuild.cmake4 …list(APPEND mcuboot_OVERLAY_CONFIG "${CMAKE_CURRENT_LIST_DIR}/sysbuild/mcuboot/${mcuboot_TARGET_OV…
10 …list(APPEND mcuboot_DTC_OVERLAY_FILE "${CMAKE_CURRENT_LIST_DIR}/sysbuild/mcuboot/${mcuboot_TARGET_…
/Zephyr-Core-3.5.0/cmake/modules/
Dbasic_settings.cmake8 # - sysbuild defined configuration settings
10 # Details for sysbuild settings:
15 # For this to work, sysbuild manages other Zephyr CMake build systems by setting
17 # This CMake modules loads the sysbuild cache variables as target properties on
/Zephyr-Core-3.5.0/share/sysbuild/image_configurations/
DMAIN_image_default.cmake5 # This sysbuild CMake file sets the sysbuild controlled settings as properties
DBOOTLOADER_image_default.cmake5 # This sysbuild CMake file sets the sysbuild controlled settings as properties
/Zephyr-Core-3.5.0/boards/xtensa/esp32s2_franzininho/doc/
Dindex.rst86 The sysbuild makes possible to build and flash all necessary images needed to
89 To build the sample application using sysbuild use the command:
96 :west-args: --sysbuild
99 By default, the ESP32 sysbuild creates bootloader (MCUboot) and application
102 Build directory structure created by sysbuild is different from traditional
120 With ``--sysbuild`` option the bootloader will be re-build and re-flash
123 For more information about the system build please read the :ref:`sysbuild` documentation.
131 The instructions following are relevant for both manual build and sysbuild.
/Zephyr-Core-3.5.0/share/sysbuild/cmake/modules/
Dsysbuild_kconfig.cmake20 elseif(EXISTS ${APP_DIR}/sysbuild.conf)
21 set(SB_CONF_FILE ${APP_DIR}/sysbuild.conf)
54 # Not adding it to CMake cache ensures that a later created sysbuild.conf
73 if(EXISTS ${APP_DIR}/Kconfig.sysbuild)
74 set(KCONFIG_ROOT ${APP_DIR}/Kconfig.sysbuild)
/Zephyr-Core-3.5.0/tests/boot/test_mcuboot/
DREADME.rst5 using sysbuild. The first application is the MCUBoot bootloader. The second
6 application is the main sysbuild target, and will request an image swap
/Zephyr-Core-3.5.0/boards/riscv/stamp_c3/doc/
Dindex.rst88 The sysbuild makes possible to build and flash all necessary images needed to
91 To build the sample application using sysbuild use the command:
98 :west-args: --sysbuild
101 By default, the ESP32 sysbuild creates bootloader (MCUboot) and application
104 Build directory structure created by sysbuild is different from traditional
122 With ``--sysbuild`` option the bootloader will be re-build and re-flash
125 For more information about the system build please read the :ref:`sysbuild` documentation.
133 The instructions following are relevant for both manual build and sysbuild.
/Zephyr-Core-3.5.0/modules/
DKconfig.sysbuild8 source "$(KCONFIG_BINARY_DIR)/Kconfig.sysbuild.modules"
27 osource "modules/*/Kconfig.sysbuild"
/Zephyr-Core-3.5.0/boards/xtensa/odroid_go/doc/
Dindex.rst130 The sysbuild makes possible to build and flash all necessary images needed to
133 To build the sample application using sysbuild use the command:
140 :west-args: --sysbuild
143 By default, the ESP32 sysbuild creates bootloader (MCUboot) and application
146 Build directory structure created by sysbuild is different from traditional
164 With ``--sysbuild`` option the bootloader will be re-build and re-flash
167 For more information about the system build please read the :ref:`sysbuild` documentation.
175 The instructions following are relevant for both manual build and sysbuild.
/Zephyr-Core-3.5.0/share/sysbuild/images/boards/
DCMakeLists.txt5 include(${BOARD_DIR}/sysbuild.cmake OPTIONAL)
/Zephyr-Core-3.5.0/boards/xtensa/heltec_wifi_lora32_v2/doc/
Dindex.rst74 The sysbuild makes possible to build and flash all necessary images needed to
77 To build the sample application using sysbuild use the command:
84 :west-args: --sysbuild
87 By default, the ESP32 sysbuild creates bootloader (MCUboot) and application
90 Build directory structure created by sysbuild is different from traditional
108 With ``--sysbuild`` option the bootloader will be re-build and re-flash
111 For more information about the system build please read the :ref:`sysbuild` documentation.
119 The instructions following are relevant for both manual build and sysbuild.
/Zephyr-Core-3.5.0/boards/xtensa/xiao_esp32s3/doc/
Dindex.rst128 The sysbuild makes possible to build and flash all necessary images needed to
131 To build the sample application using sysbuild use the command:
138 :west-args: --sysbuild
141 By default, the ESP32 sysbuild creates bootloader (MCUboot) and application
144 Build directory structure created by sysbuild is different from traditional
162 With ``--sysbuild`` option the bootloader will be re-build and re-flash
165 For more information about the system build please read the :ref:`sysbuild` documentation.
173 The instructions following are relevant for both manual build and sysbuild.
/Zephyr-Core-3.5.0/boards/xtensa/esp32s2_saola/doc/
Dindex.rst120 The sysbuild makes possible to build and flash all necessary images needed to
123 To build the sample application using sysbuild use the command:
130 :west-args: --sysbuild
133 By default, the ESP32 sysbuild creates bootloader (MCUboot) and application
136 Build directory structure created by sysbuild is different from traditional
154 With ``--sysbuild`` option the bootloader will be re-build and re-flash
157 For more information about the system build please read the :ref:`sysbuild` documentation.
165 The instructions following are relevant for both manual build and sysbuild.
/Zephyr-Core-3.5.0/samples/drivers/ipm/ipm_mcux/
DKconfig.sysbuild5 source "share/sysbuild/Kconfig"
/Zephyr-Core-3.5.0/doc/build/
Dindex.rst16 sysbuild/index.rst
/Zephyr-Core-3.5.0/boards/riscv/xiao_esp32c3/doc/
Dindex.rst112 The sysbuild makes possible to build and flash all necessary images needed to
115 To build the sample application using sysbuild use the command:
122 :west-args: --sysbuild
125 By default, the ESP32 sysbuild creates bootloader (MCUboot) and application
146 With ``--sysbuild`` option the bootloader will be re-build and re-flash
149 For more information about the system build please read the :ref:`sysbuild` documentation.
157 The instructions following are relevant for both manual build and sysbuild.
/Zephyr-Core-3.5.0/tests/boot/with_mcumgr/
DREADME.rst5 using **sysbuild**. Tests are automated with pytest, a new harness of Twister
23 like ``erase``) to use sysbuild.
/Zephyr-Core-3.5.0/boards/riscv/esp32c3_devkitm/doc/
Dindex.rst124 The sysbuild makes possible to build and flash all necessary images needed to
127 To build the sample application using sysbuild use the command:
134 :west-args: --sysbuild
137 By default, the ESP32 sysbuild creates bootloader (MCUboot) and application
140 Build directory structure created by sysbuild is different from traditional
158 With ``--sysbuild`` option the bootloader will be re-build and re-flash
161 For more information about the system build please read the :ref:`sysbuild` documentation.
169 The instructions following are relevant for both manual build and sysbuild.

123