mcuboot/samples/zephyr
Marti Bolivar 08b8058b5c zephyr: hello-world: remove BUILD_TIMESTAMP from prj.conf
This feature has been deleted in Zephyr upstream. The project won't
build with this line in anymore due to Kconfig errors.

Signed-off-by: Marti Bolivar <marti@foundries.io>
2018-10-01 21:41:40 -03:00
..
bad-keys zephyr: Move testplan into sample Makefile 2017-09-14 16:10:50 -06:00
hello-world zephyr: hello-world: remove BUILD_TIMESTAMP from prj.conf 2018-10-01 21:41:40 -03:00
.gitignore samples: Add .gitignore to ignore output files 2017-07-20 14:55:50 -06:00
Makefile Fix multi-line script call 2018-07-10 09:51:06 -03: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
overlay-ecdsa-p256.conf zephyr: migrate signature type to Kconfig 2018-04-25 18:44:03 -03:00
overlay-rsa.conf zephyr: migrate signature type to Kconfig 2018-04-25 18:44:03 -03:00
overlay-skip-slot0-validate.conf zephyr: migrate slot 0 validation to Kconfig 2018-04-25 18:44:03 -03:00
overlay-upgrade-only.conf zephyr: migrate upgrade-only to Kconfig 2018-04-25 18:44:03 -03: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.