mcuboot/samples/zephyr
Carles Cufi b791138c0c samples: zephyr: Use BOOTLOADER_MCUBOOT
Instead of manually setting the text section offset and the overlay
file, use the now readily available BOOTLOADER_MCUBOOT Kconfig option to
provide that automatically.

Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2018-03-27 10:09:18 -03:00
..
bad-keys zephyr: Move testplan into sample Makefile 2017-09-14 16:10:50 -06:00
hello-world samples: zephyr: Use BOOTLOADER_MCUBOOT 2018-03-27 10:09:18 -03:00
.gitignore samples: Add .gitignore to ignore output files 2017-07-20 14:55:50 -06:00
Makefile zephyr: port build system to CMake 2017-11-20 18:10:29 -07:00
README.md samples: zephyr: use unified application 2017-08-03 07:19:06 -06:00
build-boot.sh zephyr: port build system to CMake 2017-11-20 18:10:29 -07:00
build-hello.sh zephyr: port build system to CMake 2017-11-20 18:10:29 -07:00
run-tests.go zephyr: Create a test runner for the samples 2018-01-29 14:29:48 -07:00
run-tests.sh zephyr: add script for running mcuboot tests 2017-11-20 18:10:29 -07:00

README.md

Zephyr sample application.

In order to successfully deploy an application using mcuboot, it is necessary to build at least one other binary: the application itself. It is beyond the scope of this documentation to describe what an application is able to do, however a working example is certainly useful.

Please see the comments in the Makefile in this directory for more details on how to build and test this application.