Lines Matching full:zephyr

1 # Building and using MCUboot with Zephyr
4 acquired the ability to be used as a bootloader for Zephyr as well.
6 for Zephyr, and these are documented here.
12 The first step required for Zephyr is making sure your board has flash
33 The flash partitions are typically defined in the Zephyr boards folder, in a
50 The bootloader is an ordinary Zephyr application, at least from
51 Zephyr's point of view.  There is a bit of configuration that needs to
53 the `CMakeLists.txt` file in boot/zephyr.  There are comments there for
57 To build MCUboot, create a build directory in boot/zephyr, and build
61   cd boot/zephyr
68 `boot/zephyr/include/target.h`. Depending on the board, this information
73 `build/zephyr/zephyr.{bin,hex,elf}`, where `build` is the build
85 This is handled internally by the Zephyr configuration system and is wrapped
89 The directory `samples/zephyr/hello-world` in the MCUboot tree contains
92 application; see samples/zephyr/README.md for a tutorial.
94 The Zephyr `CONFIG_BOOTLOADER_MCUBOOT` configuration option
111 to look at `samples/zephyr/Makefile` for examples on how to use this.
156 The generated public key is saved in `build/zephyr/autogen-pubkey.h`, which is included
157 by the `boot/zephyr/keys.c`.
159 Currently, the Zephyr RTOS port limits its support to one keypair at the time,
177 `<zephyr>/boards/nordic/nrf52dk/nrf52dk_nrf52832.dts` with:
209 erasing the secondary slot from the zephyr application returns an error
220 - `zephyr,console` - If a hardware serial port is used.
221 - `zephyr,cdc-acm-uart` - If a virtual serial port is used.