michaelh/zephyr
1
0
Fork 0
Code Releases Activity

docs: Improve documentation of bootloader usage

Browse source 
Describes the necessity to specify the code partition as the chosen one.

Signed-off-by: Benedikt Schmidt <benedikt.schmidt@embedded-solutions.at>
This commit is contained in:
Benedikt Schmidt 2021-08-24 17:51:05 +02:00 • committed by Anas Nashif
commit 6e7f93a5a3
1 changed files with 13 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

16
doc/guides/device_mgmt/dfu.rst
View file

@ -36,11 +36,21 @@ In order to use MCUboot with Zephyr you need to take the following into account:
1. You will need to define the flash partitions required by MCUboot; see 1. You will need to define the flash partitions required by MCUboot; see
:ref:`flash_map_api` for details. :ref:`flash_map_api` for details.
2. Your application's :file:`.conf` file needs to enable the 2. You will have to specify your flash parition as the chosen code partition
.. code-block:: devicetree
/ {
chosen {
zephyr,code-partition = &slot0_partition;
};
};
3. Your application's :file:`.conf` file needs to enable the
:kconfig:`CONFIG_BOOTLOADER_MCUBOOT` Kconfig option in order for Zephyr to :kconfig:`CONFIG_BOOTLOADER_MCUBOOT` Kconfig option in order for Zephyr to
be built in an MCUboot-compatible manner be built in an MCUboot-compatible manner
3. You need to build and flash MCUboot itself on your device 4. You need to build and flash MCUboot itself on your device
4. You might need to take precautions to avoid mass erasing the flash and also 5. You might need to take precautions to avoid mass erasing the flash and also
to flash the Zephyr application image at the correct offset (right after the to flash the Zephyr application image at the correct offset (right after the
bootloader) bootloader)