commit | 65e1314058341cf01e61f605b892660668389e00 | [log] [tgz] |
---|---|---|
author | Marcin Niestroj <m.niestroj@emb.dev> | Wed Jun 15 21:01:17 2022 +0200 |
committer | David Brown <davidb@davidb.org> | Wed Jun 15 14:37:24 2022 -0600 |
tree | cf78bbf442a6e14ef29cad7c87c7b842e3352a5f | |
parent | 453b0dd790770ebcf062b3a0606a108cf80749c5 [diff] |
zephyr: remove MBEDTLS_ECP_MAX_BITS from mbedTLS configs According to mbedTLS' Changelog "Mbed TLS 3.0.0 branch released 2021-07-07" -> "Removals": MBEDTLS_ECP_MAX_BITS is no longer a configuration option because it is now determined automatically based on supported curves. Hence remove MBEDTLS_ECP_MAX_BITS from configuration files to fix build issues with Zephyr when there is unfortunate order of include statements, like: /__w/zephyr/zephyr/modules/mbedtls/zephyr_init.c In file included from /__w/zephyr/modules/crypto/mbedtls/include/mbedtls/ssl.h:30, from /__w/zephyr/modules/crypto/mbedtls/include/mbedtls/debug.h:27, from /__w/zephyr/zephyr/modules/mbedtls/zephyr_init.c:16: /__w/zephyr/modules/crypto/mbedtls/include/mbedtls/ecp.h:314: error: "MBEDTLS_ECP_MAX_BITS" redefined [-Werror] 314 | #define MBEDTLS_ECP_MAX_BITS 1 | In file included from /__w/zephyr/bootloader/mcuboot/boot/zephyr/include/mcuboot-mbedtls-cfg.h:25, from /__w/zephyr/modules/crypto/mbedtls/include/mbedtls/build_info.h:59, from /__w/zephyr/modules/crypto/mbedtls/include/mbedtls/debug.h:25, from /__w/zephyr/zephyr/modules/mbedtls/zephyr_init.c:16: /__w/zephyr/bootloader/mcuboot/boot/zephyr/include/config-rsa.h:72: note: this is the location of the previous definition 72 | #define MBEDTLS_ECP_MAX_BITS 2048 | cc1: all warnings being treated as errors Signed-off-by: Marcin Niestroj <m.niestroj@emb.dev>
This is MCUboot version 1.10.0-dev
MCUboot is a secure bootloader for 32-bits microcontrollers. It defines a common infrastructure for the bootloader and the system flash layout on microcontroller systems, and provides a secure bootloader that enables easy software upgrade.
MCUboot is not dependent on any specific operating system and hardware and relies on hardware porting layers from the operating system it works with. Currently, MCUboot works with the following operating systems and SoCs:
RIOT is supported only as a boot target. We will accept any new port contributed by the community once it is good enough.
See the following pages for instructions on using MCUboot with different operating systems and SoCs:
There are also instructions for the Simulator.
The issues being planned and worked on are tracked using GitHub issues. To give your input, visit MCUboot GitHub Issues.
You can find additional documentation on the bootloader in the source files. For more information, use the following links:
Developers are welcome!
Use the following links to join or see more about the project: