OrgZephyr/mcuboot
OrgZephyr
/
mcuboot
mirror of https://github.com/zephyrproject-rtos/mcuboot.git
1
0
Fork 0
Code Issues Releases Wiki Activity
mcuboot/Makefile

42 lines
1.1 KiB
Makefile
Raw Normal View History

zephyr: Support RSA, and ECDSA P-256 signing Make it clear in the top-level Makefile how to configure mcuboot for Zephyr for a particular signing algorithm. Currently supported, are the RSA signatures, and ECDSA with the P-256 curve. These configuration lines will select the code built in the bootloader, as well as which public key gets included with the image. This also adds a demo public key for the P-256 signatures.
2017-02-02 23:10:23 +08:00
# Makefile for building mcuboot as a Zephyr project.
zephyr: Make makefile clearer about configuration Separate the signature selection blocks, so that it is clearer to add another config option for the boot verification.
2017-02-02 23:23:57 +08:00
# Configuration choices.
#####################
# Signature algorithm
#####################
# Choose one of RSA or ECDSA P-256 blocks, and uncomment the config
# lines there, and comment out any other blocks.
zephyr: Support RSA, and ECDSA P-256 signing Make it clear in the top-level Makefile how to configure mcuboot for Zephyr for a particular signing algorithm. Currently supported, are the RSA signatures, and ECDSA with the P-256 curve. These configuration lines will select the code built in the bootloader, as well as which public key gets included with the image. This also adds a demo public key for the P-256 signatures.
2017-02-02 23:10:23 +08:00
# RSA
zephyr: Move code under 'boot' directory The Zephyr build systems makes some assumptions about the directory layout, and encounters problems if the necessary path contains "../..". To help this, place the zephyr directory next to the bootutil directory so that the Makefile can just refer to "../bootutil". This keeps all of the build artifacts under the proper top-level directory.
2017-01-11 00:49:47 +08:00
CONF_FILE = boot/zephyr/prj.conf
zephyr: Support RSA, and ECDSA P-256 signing Make it clear in the top-level Makefile how to configure mcuboot for Zephyr for a particular signing algorithm. Currently supported, are the RSA signatures, and ECDSA with the P-256 curve. These configuration lines will select the code built in the bootloader, as well as which public key gets included with the image. This also adds a demo public key for the P-256 signatures.
2017-02-02 23:10:23 +08:00
CFLAGS += -DBOOTUTIL_SIGN_RSA
# ECDSA P-256
#CONF_FILE = boot/zephyr/prj-p256.conf
#CFLAGS += -DBOOTUTIL_SIGN_EC256
zephyr: Make makefile clearer about configuration Separate the signature selection blocks, so that it is clearer to add another config option for the boot verification.
2017-02-02 23:23:57 +08:00
# Enable this option to have the bootloader verify the signature of
# the primary image upon every boot. Without it, signature
# verification only happens on upgrade.
CFLAGS += -DBOOTUTIL_VALIDATE_SLOT0
zephyr: Support RSA, and ECDSA P-256 signing Make it clear in the top-level Makefile how to configure mcuboot for Zephyr for a particular signing algorithm. Currently supported, are the RSA signatures, and ECDSA with the P-256 curve. These configuration lines will select the code built in the bootloader, as well as which public key gets included with the image. This also adds a demo public key for the P-256 signatures.
2017-02-02 23:10:23 +08:00
##############################
# End of configuration blocks.
##############################
# The board should be set to one of the targets supported by
# mcuboot/Zephyr. These can be found in ``boot/zephyr/targets``
BOARD ?= qemu_x86
zephyr: look for board-specific configuration To build Zephyr as a bootloader will typically require overriding the default flash regions where the binary lives, and possibly other board-specific configuration directives. Look for boot/zephyr/targets/$(BOARD).conf and include it in the kernel configuration if it exists. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-03-16 00:50:30 +08:00
# Additional board-specific Zephyr configuration
CONF_FILE += $(wildcard boot/zephyr/targets/$(BOARD).conf)
zephyr: Support RSA, and ECDSA P-256 signing Make it clear in the top-level Makefile how to configure mcuboot for Zephyr for a particular signing algorithm. Currently supported, are the RSA signatures, and ECDSA with the P-256 curve. These configuration lines will select the code built in the bootloader, as well as which public key gets included with the image. This also adds a demo public key for the P-256 signatures.
2017-02-02 23:10:23 +08:00
# The source to the Zephyr-specific code lives here.
zephyr: Move code under 'boot' directory The Zephyr build systems makes some assumptions about the directory layout, and encounters problems if the necessary path contains "../..". To help this, place the zephyr directory next to the bootutil directory so that the Makefile can just refer to "../bootutil". This keeps all of the build artifacts under the proper top-level directory.
2017-01-11 00:49:47 +08:00
SOURCE_DIR = boot/zephyr
zephyr: Bring in the Zephyr build Add support for building mcuboot as a Zephyr application. This is copied from the iotboot repo with some minor reorganization to work with the mcuboot directory layout.
2017-01-07 02:16:53 +08:00
zephyr: Include mbedtls config file Rather than commit our specific mbedtls config file into the Zephyr tree, include it here, and add a path early in the make process so that it will get picked up when building the library.
2017-01-11 00:51:39 +08:00
# Needed for mbedtls config-boot.h file.
CFLAGS += -I$(CURDIR)/boot/zephyr/include
zephyr: Bring in the Zephyr build Add support for building mcuboot as a Zephyr application. This is copied from the iotboot repo with some minor reorganization to work with the mcuboot directory layout.
2017-01-07 02:16:53 +08:00
include ${ZEPHYR_BASE}/Makefile.inc