Topic: Packages 5.8.0 and 5.8.2 cause compilation errors on Keil uVision

Hi,

I'm trying to integrate WolfSSL into a project using Keil uVision EDK, but trying to use the packages 5.8.0 or 5.8.2 cause a compilation error because the project is being asked to compile two files that are not present:

  • %LocalAppData%\Arm\Packs\wolfSSL\wolfSSL\5.8.2\wolfssl\wolfcrypt\src\port\arm\thumb2-kyber-asm_c.c

  • %LocalAppData%\Arm\Packs\wolfSSL\wolfSSL\5.8.2\wolfssl\wolfcrypt\src\ext_kyber.c

The packages were downloaded from http://www.wolfssl.com/files/ide/wolfSS … 5.8.0.pack, and http://www.wolfssl.com/files/ide/wolfSS … 5.8.2.pack.

The package for 5.7.6 had no issues and let me compile without issues, but I would need the 5.8.2 version for some of the fixes to the STM32 Hardware crypto.

Do you know if there is a way to tell uVision to ignore the file (since it is part of a package, and directly part of WolfCrypt:CORE, uVision doesn't really let me remove the file), or is it possible to have a version of the .pack file that doesn't point to these two removed files?

Best regards,
David

Share

Re: Packages 5.8.0 and 5.8.2 cause compilation errors on Keil uVision

Hi David,

I noticed you've had past tickets on our support system.  Can you please send the same message to support@wolfssl.com ?

Warm regards, Anthony

Share

Re: Packages 5.8.0 and 5.8.2 cause compilation errors on Keil uVision

Oof, looks like they forgot to update the .pdsc file for the 5.8.x release. To bypass it, just rename the .pack to .zip, open the .pdsc file in a text editor, and delete the <file> tags for those two missing Kyber files. Re-zip it, rename back, and you're set. Navigating Keil's rigid pack manager is honestly as stressful as trying to keep the ball from flying off the edge in SL at max speed. If that's too much of a hassle, just pull the raw source files into your project instead!

Share