I've added the MCUBoot stack to my project and configured it to remove the configurator errors. When I go to build it, I get the following error:
"..... /ra_gen/common_data.h:8:10: fatal error: tinycrypt/cbc_mode.h: No such file or directory"
The file cbc_mode.h does exist at ....ra\mcu-tools\MCUboot\ext\tinycrypt\lib\include\tinycrypt\cbc_mode.h. I could add an include path, but it seems like this should be taken care of by the configurator since it generated the dependency.
Attached is the configuration.xml.
Thanks for the help,
Actually, the include path was added to all languages and build configurations. So I'm stumped. Any help would be appreciated.
If you enable the "Validate Primary Image" option, you also need to change the "Signature type" from "None" to "ECDSA P-256"
Probably that's the reason.
If this response, or one provided by another user, answers your question, please verify the answer. Thank you!
Renesas Engineering Community Moderatorhttps://community.renesas.com/https://academy.renesas.com/https://en-support.renesas.com/knowledgeBase/
I can confirm that "Validate Primary Image: is enabled and "Signature type" is set to "ECDSA P-256". Any other ideas?
Is there an issue using tinycript in a c++ project? Is there a define missing? The files and include paths are there. I haven't done anything custom. The configurator shows no errors.
The same thing happens if I add tinycrypt as a separate stack on its own, so it doesn't appear to be related to MCUboot .
When you created the project was it created as a C++ project?
I have created a C++ project for an EK-RA2E1 with FSP 4.3.0 with MCUBoot with TinyCrypt (HW Accelerated) and it builds without any problems.
Ya I can create a new project and it builds fine. I also noticed that new projects offer tinycrypt SW only and tinycrypt accelerated as options but mine only offers SW only.
Hardware acceleration is only supported on RA2 devices.