mcuboot/samples/zephyr
David Brown 1d3f67d36e zephyr: Move testplan into sample Makefile
Instead of a bunch of patches that tend to become conflicting, use the
newly parameterized Makefile to make all of the test plans into make
targets.  Update the instructions to match this.

Signed-off-by: David Brown <david.brown@linaro.org>
2017-09-14 16:10:50 -06:00
..
bad-keys zephyr: Move testplan into sample Makefile 2017-09-14 16:10:50 -06:00
hello-world samples: zephyr: add hello-world 2017-08-03 07:19:06 -06:00
.gitignore samples: Add .gitignore to ignore output files 2017-07-20 14:55:50 -06:00
Makefile zephyr: Move testplan into sample Makefile 2017-09-14 16:10:50 -06:00
README.md samples: zephyr: use unified application 2017-08-03 07:19:06 -06:00
build-boot.sh samples: Create a zephyr sample 2017-07-10 11:16:25 -06:00
build-hello.sh samples: Create a zephyr sample 2017-07-10 11:16:25 -06: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.