Home
last modified time | relevance | path

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

12345678910>>...21

/Zephyr-latest/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-latest/soc/ti/simplelink/cc23x0/
DKconfig23 menu "Bootloader Configuration"
27 prompt "Pointer to user bootloader vector table"
31 bool "ROM serial bootloader"
34 bool "No bootloader invoked"
45 bool "Bootloader commands"
47 If n, bootloader ignores all commands.
49 endmenu # "Bootloader Configuration"
/Zephyr-latest/soc/ti/simplelink/cc13x2x7_cc26x2x7/
DKconfig35 bool "ROM bootloader"
37 Enable the serial bootloader which resides in ROM on CC13xx / CC26xx
41 bool "ROM bootloader backdoor"
44 Enable the ROM bootloader backdoor which starts the bootloader if the
48 int "ROM bootloader backdoor pin"
53 Set the pin that is level checked if the bootloader backdoor is
57 int "ROM bootloader backdoor level"
62 Set the active level of the pin selected for the bootloader backdoor.
/Zephyr-latest/soc/ti/simplelink/cc13x2_cc26x2/
DKconfig34 bool "ROM bootloader"
36 Enable the serial bootloader which resides in ROM on CC13xx / CC26xx
40 bool "ROM bootloader backdoor"
43 Enable the ROM bootloader backdoor which starts the bootloader if the
47 int "ROM bootloader backdoor pin"
52 Set the pin that is level checked if the bootloader backdoor is
56 int "ROM bootloader backdoor level"
61 Set the active level of the pin selected for the bootloader backdoor.
/Zephyr-latest/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-latest/soc/st/stm32/stm32f0x/
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-latest/boards/adafruit/itsybitsy/doc/
Dindex.rst89 The ItsyBitsy ships with the BOSSA compatible UF2 bootloader. The
90 bootloader can be entered by quickly tapping the reset button twice.
94 Some versions of this board were shipped with a buggy bootloader.
95 Ensure that the bootloader is up to date by following the
96 `Adafruit UF2 Bootloader update`_ tutorial. Note that this tutorial
98 the bootloader are the same for the ItsyBitsy. The files for the
99 ItsyBitsy bootloader can be found in the `Adafruit nRF52 Bootloader repo`_.
102 release 0.7.0 of the UF2 bootloader.
120 #. Tap the reset button twice quickly to enter bootloader mode
143 .. _Adafruit UF2 Bootloader update:
[all …]
/Zephyr-latest/tests/boot/test_mcuboot/
Dtestcase.yaml8 - "I: Starting bootloader"
14 bootloader.mcuboot:
50 bootloader.mcuboot.assert:
55 bootloader.mcuboot.swap_using_offset:
/Zephyr-latest/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-latest/soc/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-latest/dts/bindings/options/
Dopenthread,config.yaml13 bootloader-gpios = <&gpio0 1 GPIO_ACTIVE_HIGH>;
26 bootloader-gpios:
29 This enables resetting to bootloader by triggering given GPIO pin. Property represents
/Zephyr-latest/tests/boot/mcuboot_recovery_retention/
Dtestcase.yaml18 - "Starting bootloader"
22 bootloader.mcuboot.recovery.retention:
28 bootloader.mcuboot.recovery.retention.mem:
/Zephyr-latest/boards/nordic/nrf52840dongle/
DKconfig.defconfig9 # To let the nRF5 bootloader load an application, the application
12 # Nordic nRF5 bootloader exists outside of the partitions specified in the
19 # the bootloader Kconfig option has been disabled.
DKconfig9 bool "Board has nRF5 bootloader"
13 nRF5 bootloader.
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.
/Zephyr-latest/boards/ezurio/bl654_usb/
DKconfig.defconfig8 # To let the nRF5 bootloader load an application, the application
11 # Nordic nRF5 bootloader exists outside of the partitions specified in the
14 # the bootloader at the end of flash.
/Zephyr-latest/boards/others/promicro_nrf52840/
DKconfig.defconfig10 # To let the nRF5 bootloader load an application, the application
13 # Nordic nRF5 bootloader exists outside of the partitions specified in the
20 # the bootloader Kconfig option has been disabled.
DKconfig7 bool "Board has nRF5 bootloader"
11 nRF5 bootloader.
/Zephyr-latest/boards/franzininho/esp32s2_franzininho/doc/
Dindex.rst53 The board could be loaded using the single binary image, without 2nd stage bootloader.
60 MCUboot bootloader
63 User may choose to use MCUboot bootloader instead. In that case the bootloader
73 User can select the MCUboot bootloader by adding the following line
96 By default, the ESP32 sysbuild creates bootloader (MCUboot) and application
117 With ``--sysbuild`` option the bootloader will be re-build and re-flash
133 Remember that bootloader (MCUboot) needs to be flash at least once.
/Zephyr-latest/modules/openthread/platform/
Dmisc.c21 "`bootloader-gpios` property missing from `openthread,config` compatible node");
53 * To enable resetting to bootloader by triggering gpio pin, in otPlatResetToBootloader()
56 * `compatible = "openthread,config"` property and `bootloader-gpios` property, in otPlatResetToBootloader()
63 * bootloader-gpios = <&gpio0 0 GPIO_ACTIVE_HIGH>; in otPlatResetToBootloader()
69 * Configuring pin flags in `bootloader-gpios` allows to choose in otPlatResetToBootloader()
/Zephyr-latest/boards/ezurio/bl654_usb/doc/
Dbl654_usb.rst77 The board supports programming using the built-in bootloader.
80 open bootloader from Nordic's nRF5x SDK. With this option, you'll use
82 bootloader and flash them to the device. Before proceeding, make sure:
87 #. With the adapter plugged in, reset the board into the bootloader by pressing
96 The blue LED should start a fade pattern, signalling the bootloader is
106 #. Package the application for the bootloader using ``nrfutil``:
158 .. _Creating a secure bootloader image: https://www.ezurio.com/documentation/application-note-creat…
/Zephyr-latest/boards/seeed/xiao_esp32c3/doc/
Dindex.rst55 The board could be loaded using the single binary image, without 2nd stage bootloader.
62 MCUboot bootloader
65 User may choose to use MCUboot bootloader instead. In that case the bootloader
75 User can select the MCUboot bootloader by adding the following line
98 By default, the ESP32 sysbuild creates bootloader (MCUboot) and application
119 With ``--sysbuild`` option the bootloader will be re-build and re-flash
135 Remember that bootloader (MCUboot) needs to be flash at least once.
/Zephyr-latest/boards/m5stack/stamp_c3/doc/
Dindex.rst36 The board could be loaded using the single binary image, without 2nd stage bootloader.
43 MCUboot bootloader
46 User may choose to use MCUboot bootloader instead. In that case the bootloader
56 User can select the MCUboot bootloader by adding the following line
79 By default, the ESP32 sysbuild creates bootloader (MCUboot) and application
100 With ``--sysbuild`` option the bootloader will be re-build and re-flash
116 Remember that bootloader (MCUboot) needs to be flash at least once.
/Zephyr-latest/soc/espressif/esp32s3/
Dmemory.h21 /** Simplified memory map for the bootloader.
22 * Make sure the bootloader can load into main memory without overwriting itself.
30 * The 2nd stage bootloader can take space up to the end of ROM shared
48 /* For safety margin between bootloader data section and startup stacks */
67 * This address is where 2nd stage bootloader starts allocating memory,
69 * When there is no 2nd stage bootloader the bootstrapping is done
/Zephyr-latest/boards/makerdiary/nrf52840_mdk_usb_dongle/
DKconfig8 bool "Board has nRF5 bootloader"
13 nRF5 bootloader.

12345678910>>...21