Skip to content

Commit d783809

Browse files
carlescufid3zd3z
authored andcommitted
zephyr: doc: Mention the DT flash description
In order to build for a particular Zephyr board, the Device Tree definition for it in the Zephyr tree must include the flash description. Additionally mention that a .hex version of the image is available, useful for those flash tools that deal with Intel Hex files. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
1 parent f4d0e1a commit d783809

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

README-zephyr.rst

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,12 @@ There is a ``build_boot.sh`` script at the top level that can make
2424
building a bit easier. It assumes that the mcuboot tree is next to,
2525
at the same level, as the zephyr source tree. It takes a single
2626
argument, which is the target to build. This must match one of the
27-
targets in ``boot/zephyr/targets`` to be a supported board.
27+
targets in ``boot/zephyr/targets`` to be a supported board. Additionally,
28+
the Zephyr Device Tree board definition in ``dts/<arch>/<board>.dts`` must
29+
contain the flash partitions description.
2830

2931
Once this is finished building, the bootloader should reside in
30-
``outdir/targname/zephyr.bin``. Use the flashing tools you have to
32+
``outdir/targname/zephyr.[bin|hex]``. Use the flashing tools you have to
3133
install this image at the beginning of the flash.
3234

3335
Building Applications for the bootloader

0 commit comments

Comments
 (0)