37e4223413
Signed-off-by: honglin leng <a909204013@gmail.com> |
||
|---|---|---|
| .. | ||
| bad-keys | ||
| hello-world | ||
| mcutests | ||
| .gitignore | ||
| Makefile | ||
| README.md | ||
| build-boot.sh | ||
| build-hello.sh | ||
| overlay-ecdsa-p256.conf | ||
| overlay-rsa.conf | ||
| overlay-skip-primary-slot-validate.conf | ||
| overlay-upgrade-only.conf | ||
| run-tests.go | ||
| run-tests.sh | ||
| test-compile.go | ||
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.
Note that this sample uses the "ninja" build tool, which can be installed on most systems using the system package manager, e.g., for a Debian-based distro:
$ sudo apt-get install ninja
or in Fedora:
$ sudo dnf install ninja