Home
last modified time | relevance | path

Searched full:bootloader (Results 1 – 25 of 386) sorted by relevance

12345678910>>...16

/Zephyr-Core-3.5.0/subsys/retention/
DKconfig.blinfo5 bool "Bootloader info"
7 Adds a bootloader information sharing system which allows for
8 retreiving data from the bootloader when data sharing is enabled.
13 DT_CHOSEN_BOOTLOADER_INFO := zephyr,bootloader-info
21 Adds a bootloader information sharing system for MCUboot and
28 the "zephyr,bootloader-info" chosen node via device tree, MCUboot
29 must be built with the same "zephyr,bootloader-info" DTS node and
35 int "Bootloader info init priority"
38 Bootloader info initialization priority (must be higher than init
45 Allows bootloader settings to be fetched by calling a function which
[all …]
/Zephyr-Core-3.5.0/soc/arm/ti_simplelink/cc13x2_cc26x2/
DKconfig.soc39 bool "ROM bootloader"
41 Enable the serial bootloader which resides in ROM on CC13xx / CC26xx
45 bool "ROM bootloader backdoor"
48 Enable the ROM bootloader backdoor which starts the bootloader if the
52 int "ROM bootloader backdoor pin"
57 Set the pin that is level checked if the bootloader backdoor is
61 int "ROM bootloader backdoor level"
66 Set the active level of the pin selected for the bootloader backdoor.
/Zephyr-Core-3.5.0/soc/arm/ti_simplelink/cc13x2x7_cc26x2x7/
DKconfig.soc39 bool "ROM bootloader"
41 Enable the serial bootloader which resides in ROM on CC13xx / CC26xx
45 bool "ROM bootloader backdoor"
48 Enable the ROM bootloader backdoor which starts the bootloader if the
52 int "ROM bootloader backdoor pin"
57 Set the pin that is level checked if the bootloader backdoor is
61 int "ROM bootloader backdoor level"
66 Set the active level of the pin selected for the bootloader backdoor.
/Zephyr-Core-3.5.0/doc/services/retention/
Dblinfo.rst3 Bootloader Information
6 The bootloader information (abbreviated to blinfo) subsystem is an extension of
7 the :ref:`retention_api` which allows for reading shared data from a bootloader
9 the information retrieved from the bootloader and storing it in the
15 To use the bootloader information subsystem, a retention area needs to be
44 zephyr,bootloader-info = &boot_info0;
54 Note that this configuration needs to be applied on both the bootloader
77 bootloader information subsystem to function:
84 The following include is needed to use the bootloader information subsystem:
91 application can call this to query the information from the bootloader. This
[all …]
/Zephyr-Core-3.5.0/soc/arm/st_stm32/stm32f0/
Dsoc.c29 * A Zephyr image that is run from the mcuboot bootloader must relocate the
31 * bootloader.
33 * A zephyr image that is a bootloader does not have to relocate the
36 * Alternatively both switches SW_VECTOR_RELAY (for Bootloader image) and
37 * SW_VECTOR_RELAY_CLIENT (for image loaded by a bootloader) can be used to
43 * @note Zephyr applications that will not be loaded by a bootloader should
44 * pretend to be a bootloader if the SRAM vector table is not needed.
/Zephyr-Core-3.5.0/soc/xtensa/espressif_esp32/esp32/
DCMakeLists.txt38 SOURCE_DIR ${espidf_components_dir}/bootloader/subproject
39 BINARY_DIR ${espidf_build_dir}/bootloader
42 -S ${espidf_components_dir}/bootloader/subproject
43 -B ${espidf_build_dir}/bootloader -DSDKCONFIG=${espidf_build_dir}/sdkconfig
71 …board_finalize_runner_args(esp32 "--esp-flash-bootloader=${espidf_build_dir}/bootloader/bootloader…
90 …board_finalize_runner_args(esp32 "--esp-flash-bootloader=${CMAKE_BINARY_DIR}/zephyr/${CONFIG_KERNE…
/Zephyr-Core-3.5.0/soc/riscv/espressif_esp32/esp32c3/
DCMakeLists.txt37 SOURCE_DIR ${espidf_components_dir}/bootloader/subproject
38 BINARY_DIR ${espidf_build_dir}/bootloader
41 -S ${espidf_components_dir}/bootloader/subproject
42 -B ${espidf_build_dir}/bootloader -DSDKCONFIG=${espidf_build_dir}/sdkconfig
70 …board_finalize_runner_args(esp32 "--esp-flash-bootloader=${espidf_build_dir}/bootloader/bootloader…
89 …board_finalize_runner_args(esp32 "--esp-flash-bootloader=${CMAKE_BINARY_DIR}/zephyr/${CONFIG_KERNE…
/Zephyr-Core-3.5.0/soc/xtensa/espressif_esp32/esp32s2/
DCMakeLists.txt36 SOURCE_DIR ${espidf_components_dir}/bootloader/subproject
37 BINARY_DIR ${espidf_build_dir}/bootloader
40 -S ${espidf_components_dir}/bootloader/subproject
41 -B ${espidf_build_dir}/bootloader -DSDKCONFIG=${espidf_build_dir}/sdkconfig
69 …board_finalize_runner_args(esp32 "--esp-flash-bootloader=${espidf_build_dir}/bootloader/bootloader…
88 …board_finalize_runner_args(esp32 "--esp-flash-bootloader=${CMAKE_BINARY_DIR}/zephyr/${CONFIG_KERNE…
/Zephyr-Core-3.5.0/soc/xtensa/espressif_esp32/esp32s3/
DCMakeLists.txt30 SOURCE_DIR ${espidf_components_dir}/bootloader/subproject
31 BINARY_DIR ${espidf_build_dir}/bootloader
34 -S ${espidf_components_dir}/bootloader/subproject
35 -B ${espidf_build_dir}/bootloader -DSDKCONFIG=${espidf_build_dir}/sdkconfig
63 …board_finalize_runner_args(esp32 "--esp-flash-bootloader=${espidf_build_dir}/bootloader/bootloader…
82 …board_finalize_runner_args(esp32 "--esp-flash-bootloader=${CMAKE_BINARY_DIR}/zephyr/${CONFIG_KERNE…
/Zephyr-Core-3.5.0/boards/xtensa/esp32s2_franzininho/doc/
Dindex.rst57 ESP-IDF bootloader
60 The board is using the ESP-IDF bootloader as the default 2nd stage bootloader.
64 MCUboot bootloader
67 User may choose to use MCUboot bootloader instead. In that case the bootloader
77 User can select the MCUboot bootloader by adding the following line
99 By default, the ESP32 sysbuild creates bootloader (MCUboot) and application
120 With ``--sysbuild`` option the bootloader will be re-build and re-flash
136 Remember that bootloader (MCUboot) needs to be flash at least once.
/Zephyr-Core-3.5.0/samples/subsys/usb/dfu/
DREADME.rst19 partition layout. You SoC must run MCUboot as the stage 1 bootloader.
20 This sample is built as an application for the MCUboot bootloader.
43 -DCONFIG_MCUBOOT_SIGNATURE_KEY_FILE=\"bootloader/mcuboot/root-rsa-2048.pem\"
45 Build and flash MCUboot bootloader for Zephyr project as it is described in
57 …-DCONFIG_BOOTLOADER_MCUBOOT=y '-DCONFIG_MCUBOOT_SIGNATURE_KEY_FILE="bootloader/mcuboot/root-rsa-20…
83 I: Starting bootloader
88 I: Bootloader chainload address offset: 0xc000
100 I: Starting bootloader
106 I: Bootloader chainload address offset: 0xc000
132 …-DCONFIG_BOOTLOADER_MCUBOOT=y '-DCONFIG_MCUBOOT_SIGNATURE_KEY_FILE="bootloader/mcuboot/root-rsa-20…
[all …]
/Zephyr-Core-3.5.0/tests/boot/test_mcuboot/
Dtestcase.yaml7 - "I: Starting bootloader"
13 bootloader.mcuboot:
23 bootloader.mcuboot.assert:
/Zephyr-Core-3.5.0/soc/arm/atmel_sam0/common/
Dbossa.c14 * Magic value that causes the bootloader to stay in bootloader mode instead of
22 #error Unsupported BOSSA bootloader variant
36 * bootloader. in bossa_reset()
/Zephyr-Core-3.5.0/share/sysbuild/images/bootloader/
DKconfig13 choice BOOTLOADER choice
14 prompt "Bootloader support"
21 Do not Include a bootloader in the build
27 Include MCUboot (Zephyr port) as the bootloader to use
/Zephyr-Core-3.5.0/tests/boot/mcuboot_recovery_retention/
Dtestcase.yaml20 - "Starting bootloader"
24 bootloader.mcuboot.recovery.retention:
30 bootloader.mcuboot.recovery.retention.mem:
/Zephyr-Core-3.5.0/boards/arm/bl654_usb/
DKconfig.defconfig11 # To let the nRF5 bootloader load an application, the application
14 # Nordic nRF5 bootloader exists outside of the partitions specified in the
17 # the bootloader at the end of flash.
/Zephyr-Core-3.5.0/boards/xtensa/heltec_wifi_lora32_v2/doc/
Dindex.rst45 ESP-IDF bootloader
48 The board is using the ESP-IDF bootloader as the default 2nd stage bootloader.
52 MCUboot bootloader
55 User may choose to use MCUboot bootloader instead. In that case the bootloader
65 User can select the MCUboot bootloader by adding the following line
87 By default, the ESP32 sysbuild creates bootloader (MCUboot) and application
108 With ``--sysbuild`` option the bootloader will be re-build and re-flash
124 Remember that bootloader (MCUboot) needs to be flash at least once.
/Zephyr-Core-3.5.0/boards/arm/nrf52840_mdk_usb_dongle/
Dfstab-stock.dtsi7 /* Flash partition table compatible with Nordic nRF5 bootloader */
41 /* Nordic nRF5 bootloader <0xe0000 0x1c000>
44 * are used by the nRF5 bootloader and MBR to store settings.
DKconfig15 bool "Board has nRF5 bootloader"
19 nRF5 bootloader.
/Zephyr-Core-3.5.0/boards/arm/nrf52840dongle_nrf52840/
Dfstab-stock.dtsi7 /* Flash partition table compatible with Nordic nRF5 bootloader */
38 /* Nordic nRF5 bootloader <0xe0000 0x1c000>
41 * are used by the nRF5 bootloader and MBR to store settings.
DKconfig.defconfig12 # To let the nRF5 bootloader load an application, the application
15 # Nordic nRF5 bootloader exists outside of the partitions specified in the
22 # the bootloader Kconfig option has been disabled.
DKconfig19 bool "Board has nRF5 bootloader"
23 nRF5 bootloader.
/Zephyr-Core-3.5.0/boards/arm/adafruit_itsybitsy_nrf52840/doc/
Dindex.rst134 The ItsyBitsy ships with the BOSSA compatible UF2 bootloader. The
135 bootloader can be entered by quickly tapping the reset button twice.
139 Some versions of this board were shipped with a buggy bootloader.
140 Ensure that the bootloader is up to date by following the
141 `Adafruit UF2 Bootloader update`_ tutorial. Note that this tutorial
143 the bootloader are the same for the ItsyBitsy. The files for the
144 ItsyBitsy bootloader can be found in the `Adafruit nRF52 Bootloader repo`_.
147 release 0.7.0 of the UF2 bootloader.
165 #. Tap the reset button twice quickly to enter bootloader mode
188 .. _Adafruit UF2 Bootloader update:
[all …]
/Zephyr-Core-3.5.0/doc/develop/flash_debug/
Dhost-tools.rst24 bootloader and both extensions from Arduino and Adafruit. Full support was
37 .. tab:: With ROM bootloader
42 .. tab:: Without ROM bootloader
46 1. Define flash partitions required to accommodate the bootloader and
52 3. Build and flash the SAM-BA bootloader on the device.
54 .. tab:: With compatible SAM-BA bootloader
58 1. Define flash partitions required to accommodate the bootloader and
68 to select the right compatible SAM-BA bootloader mode.
70 3. Build and flash the SAM-BA bootloader on the device.
75 as last resource. Try configure first with Devices without ROM bootloader.
[all …]
/Zephyr-Core-3.5.0/boards/arm/sparkfun_pro_micro_rp2040/
Dsparkfun_pro_micro_rp2040.dts36 * the second stage bootloader
45 /* Reserved memory for the second stage bootloader */
54 * Usable flash. Starts at 0x100, after the bootloader. The partition
55 * size is 16MB minus the 0x100 bytes taken by the bootloader.

12345678910>>...16