1 Reply by ClarkS

(3 replies, posted in wolfBoot)

Hello @degarske,

Updating the submodule fixed it. I've a bad cold and my brain is minimally functional this week.  I should have figured this out myself. Now everything builds...keytools, and make.

I can't help compare this process, even including my bumbling, with the pain of trying to get SBSFU or TF-M apps working on macOS. Without running on Windows, which I resist, getting those apps to build is a long process....real long.

Thank you for rapidly helping! I have to admit, this is exciting.

@embhorn. I'm refactoring an old X-CUBE-SBSFU project used for an IOT industrial control project. It's no longer in service due to persistent communication problems, but I've resolved them. Now I'm replacing the SBSFU boot loader with either MCUBoot or WolfBoot. And later adding an RTOS. I'm in Hot Springs Village, AR.

Clark

Go to forum: wolfBoot

2 Topic by ClarkS

(3 replies, posted in wolfBoot)

I am following this YouTube video: https://www.youtube.com/watch?v=dzcmscEyrKM

I have entered the following in macOS terminal:

git clone https://github.com/wolfSSL/wolfboot.git

cd wolfboot

cp ./config/examples/stm32u5.config .config && make

After this I receive the following error:

[CC-ARM] src/string.o
In file included from include/image.h:35,
                 from src/string.c:45:
include/wolfboot/wolfboot.h:167:13: fatal error: wolfssl/wolfcrypt/sha256.h: No such file or directory
  167 | #   include "wolfssl/wolfcrypt/sha256.h"
      |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make: *** [src/string.o] Error 1

I'm pretty lost here as I'm not familiar with Make or with WolfBoot. I hope someone can give me some advice.

Go to forum: wolfBoot