Closed opkaizen closed 6 months ago
Hi @opkaizen,
Thank you for this report. I will look into this.
Hi @opkaizen,
Can you give https://github.com/wolfSSL/wolfBoot/pull/441 a try? You would just have to add -DBUILD_IMAGE=yes
to your cmake command
About the failure on re-running cmake, it's an issue with the cache from the first run. If you delete build/CMakeCache.txt
, you should be able to re-run the cmake command and see it succeed
I'm closing this in favor of #441 (if I understand correctly this was initially handled in #427). Feel free to continue the discussion there.
Hi! I have issues when trying to build the bootloader firmware via cmake.
I tried to build the project using the following command:
It's the example command available in the README.md file without the -DTEST_APPS flag to avoid building the baremetal test application, as I only want the bootloader.bin. With this,
wolfboot.bin
andwolfboot.elf
are not being built (but they are in the Makefile version:cp config/examples/stm32h7.config .config && make wolfboot.bin
). How can I avoid building the test apps when I only want the wolfboot bootloader firmware using cmake?The logs are:
I also have issues when I try to reconfigure the project. Rerunning the cmake command above generates the following logs:
I guess cmake doesn't like the multiarch build between the static libs (arm-none-eabi) and the keytools.
Thanks,