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

57 lines
1.7 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
Make mcuboot less mynewt style Remove most of mynewt specific stuff to a separate port package. This should make mcuboot less "mynewt'y" and slightly easier to port to. - Mynewt specific stuff moved to boot/mynewt. - Sample app moved from apps/boot to boot/mynewt. - Use MYNEWT_VAL macro only on mynewt port. - BOOTUTIL_* and MYNEWT_VAL() usage moved to MCUBOOT_ defines.
2017-05-12 03:19:36 +08:00
CFLAGS += -DMCUBOOT_SIGN_RSA -DMCUBOOT_USE_MBED_TLS
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: Add support for RSA-PSS The PKCS#1 standards, which define RSA signatures, are currently at version 2.2. Starting in v2.1, the standard defines a new signature method RSA-PSS, which has a stronger security proof than the signature method used in earlier versions. The standard recommends that RSA-PSS be used in new designs, instead of the older algorithm. This patch implements RSA-PSS verification for a specific set of parameters: - RSA-2048 - SHA256 for both the message digest and the internal hash - 32-byte salt - 2047 bit message Although RSA-PSS supports other parameters, due to size constraints, this verificatino code only supports these specific parameters, and signatures with other parameters will be considered invalid. To encourage the use of the more secure algorithm, the default build configuration is RSA-PSS. BOOTUTIL_RSA_PKCS1_15 needs to be defined in order to support the older signature algorithm.
2017-06-01 03:21:39 +08:00
# Newer uses should use the RSA-PSS signature algorithm. This define
# enables (and requires) this type of signature.
#CFLAGS += -DMCUBOOT_RSA_PKCS1_15
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
# ECDSA P-256
#CONF_FILE = boot/zephyr/prj-p256.conf
Make mcuboot less mynewt style Remove most of mynewt specific stuff to a separate port package. This should make mcuboot less "mynewt'y" and slightly easier to port to. - Mynewt specific stuff moved to boot/mynewt. - Sample app moved from apps/boot to boot/mynewt. - Use MYNEWT_VAL macro only on mynewt port. - BOOTUTIL_* and MYNEWT_VAL() usage moved to MCUBOOT_ defines.
2017-05-12 03:19:36 +08:00
#CFLAGS += -DMCUBOOT_SIGN_EC256 -DMCUBOOT_USE_TINYCRYPT
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
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.
Make mcuboot less mynewt style Remove most of mynewt specific stuff to a separate port package. This should make mcuboot less "mynewt'y" and slightly easier to port to. - Mynewt specific stuff moved to boot/mynewt. - Sample app moved from apps/boot to boot/mynewt. - Use MYNEWT_VAL macro only on mynewt port. - BOOTUTIL_* and MYNEWT_VAL() usage moved to MCUBOOT_ defines.
2017-05-12 03:19:36 +08:00
CFLAGS += -DMCUBOOT_VALIDATE_SLOT0
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
bootutil: optionally use flash_area_get_sectors() Add a typedef which lets us use flash_sector or flash_area to contain the sectors within the boot_data global. When MCUBOOT_USE_FLASH_AREA_GET_SECTORS is defined, this is struct flash_sector. Also add struct boot_loader_state accessors to handle this case, and make the appropriate changes to where the sectors are allocated to use the new typedef. Finally, ensure MCUBOOT_USE_FLASH_AREA_GET_SECTORS is defined in the Zephyr Makefile, since flash_area_get_sectors() is already provided there. This lets mcuboot users convert to the new flash API gradually. Signed-off-by: Marti Bolivar <marti.bolivar@linaro.org>
2017-06-14 21:35:40 +08:00
# Enabling this option uses newer flash map APIs. This saves RAM and
# avoids deprecated API usage.
#
# (This can be deleted when flash_area_to_sectors() is removed instead
# of simply deprecated.)
CFLAGS += -DMCUBOOT_USE_FLASH_AREA_GET_SECTORS
Add "upgrade only" support Add a configuration option "BOOTUTIL_OVERWRITE_ONLY" that avoids using the image swap code. Instead, when an upgrade is detected in slot 1, it is copied directly onto slot 0. As long as the image in slot 1 is valid, this should work robustly (it will redo it if power is lost during the upgrade). This doesn't protect against the case of deploying an image that fails to boot on some devices. But, the behavior is similar to the swap upgrade approach when the slot 1 image is marked initially as "image ok", but without the complexity (or need of a swap partition) of the swap code.
2017-05-05 23:41:34 +08:00
# Enable this option to not use the swapping code and just overwrite
# the image on upgrade.
Fix some leftovers after mynewt move (PR #52) - caps.c was now updated (missed this one!). - *_OVERWRITE_ONLY flag was now also updated.
2017-06-12 21:25:43 +08:00
#CFLAGS += -DMCUBOOT_OVERWRITE_ONLY
Add "upgrade only" support Add a configuration option "BOOTUTIL_OVERWRITE_ONLY" that avoids using the image swap code. Instead, when an upgrade is detected in slot 1, it is copied directly onto slot 0. As long as the image in slot 1 is valid, this should work robustly (it will redo it if power is lost during the upgrade). This doesn't protect against the case of deploying an image that fails to boot on some devices. But, the behavior is similar to the swap upgrade approach when the slot 1 image is marked initially as "image ok", but without the complexity (or need of a swap partition) of the swap code.
2017-05-05 23:41:34 +08:00
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
Makefile: update location of target-specific .conf arduino_101.conf was moved up a level, but the toplevel Makefile was not updated so that it can be located. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-03-17 05:39:04 +08:00
CONF_FILE += $(wildcard boot/zephyr/$(BOARD).conf)
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
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