Re: debug with mcuboot
Marti Bolivar <marti@...>
On Fri, Mar 1, 2019 at 9:12 AM David Brown <firstname.lastname@example.org> wrote:
I somehow have trouble believing the date stamp on the original email.
Clogged internet pipes, perhaps.
Multi-image build is a build system issue, not a west issue. Nordic is
working on this, for reference:
Also just FYI, west already supports building, signing, and flashing
MCUboot images. For example:
# Build and flash MCUboot itself for reel_board
west build -b reel_board -s mcuboot/boot/zephyr/ -d build-mcuboot
west flash -d build-mcuboot/
# Build and flash hello_world as an MCUboot chain-loadable image
west build -b reel_board -s zephyr/samples/hello_world/ -d build-hello
west sign -t imgtool -d build-hello/ -- --key mcuboot/root-rsa-2048.pem
west flash --hex-file zephyr.signed.hex -d build-hello/
The above assumes your runner prefers flashing .hex files, which is
true of nrfjprog and pyocd at least. You can do it with .bin files too
but it's a little more annoying and I'd like to deprecate some of the
command line flags.
The value of "west sign -t imgtool" compared to using imgtool directly
is that it pulls the values for the --align, --header-size, and
--slot-size options out of the build directory by inspecting Kconfig
and device tree output files.
Hopefully something like the above can continue working in these
contexts, suitably extended if necessary.