doc/readme-zephyr:
Zephyr-port has switched to use DT node labels instead of
label properties for partition assignment.
Also usage of west is recommended way to work with the project.
Documentation was actualized to reflect these principles.
Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
Co-authored-by: Francesco Domenico Servidio <francesco.servidio@nordicsemi.no>
diff --git a/docs/readme-zephyr.md b/docs/readme-zephyr.md
index ea18fe9..d7b6f73 100644
--- a/docs/readme-zephyr.md
+++ b/docs/readme-zephyr.md
@@ -13,21 +13,21 @@
partitions defined in its device tree. These partitions are:
- `boot_partition`: for MCUboot itself
-- `image_0_primary_partition`: the primary slot of Image 0
-- `image_0_secondary_partition`: the secondary slot of Image 0
+- `slot0_partition`: the primary slot of Image 0
+- `slot1_partition`: the secondary slot of Image 0
- `scratch_partition`: the scratch slot
Currently, the two image slots must be contiguous. If you are running
MCUboot as your stage 1 bootloader, `boot_partition` must be configured
so your SoC runs it out of reset. If there are multiple updateable images
then the corresponding primary and secondary partitions must be defined for
-the rest of the images too (e.g. `image_1_primary_partition` and
-`image_1_secondary_partition` for Image 1).
+the rest of the images too (for example, `slot2_partition` and
+`slot3_partition` for Image 1).
The flash partitions are typically defined in the Zephyr boards folder, in a
file named `boards/<arch>/<board>/<board>.dts`. An example `.dts` file with
flash partitions defined is the frdm_k64f's in
-`boards/arm/frdm_k64f/frdm_k64f.dts`. Make sure the labels in your board's
+`boards/arm/frdm_k64f/frdm_k64f.dts`. Make sure the DT node labels in your board's
`.dts` file match the ones used there.
## Installing requirements and dependencies
@@ -53,9 +53,7 @@
```
cd boot/zephyr
- mkdir build && cd build
- cmake -GNinja -DBOARD=<board> ..
- ninja
+ west build -b <board>
```
In addition to the partitions defined in DTS, some additional
@@ -67,9 +65,8 @@
After building the bootloader, the binaries should reside in
`build/zephyr/zephyr.{bin,hex,elf}`, where `build` is the build
-directory you chose when running `cmake`. Use the Zephyr build
-system `flash` target to flash these binaries, usually by running
-`make flash` (or `ninja flash`, etc.) from the build directory. Depending
+directory you chose when running `west build`. Use `west flash`
+to flash these binaries from the build directory. Depending
on the target and flash tool used, this might erase the whole of the flash
memory (mass erase) or only the sectors where the bootloader resides prior to
programming the bootloader image itself.