mcuboot/samples/zephyr
David Brown 8e0016eb14 zephyr: Create a test runner for the samples
Enhance the test runner so that it can verify the output of the tests by
itself.  This needs the console to be logged to a file, but otherwise
works the same as the current test runner.

Also, the build results are placed in a log file, so that it is easier
to see what is happening.

Signed-off-by: David Brown <david.brown@linaro.org>
2018-01-29 14:29:48 -07:00
..
bad-keys zephyr: Move testplan into sample Makefile 2017-09-14 16:10:50 -06:00
hello-world zephyr: hello-world: Samples should not define default boards 2018-01-29 16:19:37 -02: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.