Hi there, I-m trying to compile a hello world sample with an encrypted bootloader
System build: Use sysbuild
I'm getting these errors:
In file included from C:/D/dev/nordicsemi/v2.7.0/bootloader/mcuboot/boot/bootutil/include/bootutil/enc_key.h:33,
from C:/D/dev/nordicsemi/v2.7.0/bootloader/mcuboot/boot/bootutil/src/image_validate.c:44:
C:/D/dev/nordicsemi/v2.7.0/bootloader/mcuboot/boot/bootutil/include/bootutil/crypto/aes_ctr.h:19:6: error: #error "One crypto backend must be defined: either MBED_TLS or TINYCRYPT"
19 | #error "One crypto backend must be defined: either MBED_TLS or TINYCRYPT"C:/D/dev/nordicsemi/v2.7.0/bootloader/mcuboot/boot/bootutil/include/bootutil/enc_key.h:45:5: error: unknown type name 'bootutil_aes_ctr_context'
45 | bootutil_aes_ctr_context aes_ctr;and
C:/D/dev/nordicsemi/v2.7.0/bootloader/mcuboot/ext/tinycrypt/lib/source/hmac.c:33:10: fatal error: tinycrypt/hmac.h: No such file or directory
33 | #include <tinycrypt/hmac.h>
I also tried all these settings in sysbuild/mcuboot.conf without success:
edit: I've got autogen-enckey.c & autogen-pubkey.c at build/mcuboot/zephyr
I also have zephyr.bin, zephyr.signed.bin & zephyr.signed.encrypted.bin at build/myapp/zephyr
I have not more configutration except for custom board, can you help?, thanks in advance.
Running nrf connect SDK 2.7.0 and toolchain 2.7.0, VSC 1.93.1, nRF Connect for VS Code v2024.9.87,nRF Connect for VS Code Extension Pack v2024.9.5