<![CDATA[wolfSSL - Embedded SSL Library — STM32U5A5 HASH seems to not works as expected]]> https://www.wolfssl.com/forums/topic2174-stm32u5a5-hash-seems-to-not-works-as-expected.html Tue, 24 Sep 2024 19:10:49 +0000 PunBB <![CDATA[Re: STM32U5A5 HASH seems to not works as expected]]> https://www.wolfssl.com/forums/post7889.html#p7889 Hi Rickou,

Congratulations! I am happy to hear you got it working. Let us know if anything else comes up.

Thanks,
David Garske, wolfSSL

]]> Tue, 24 Sep 2024 19:10:49 +0000 https://www.wolfssl.com/forums/post7889.html#p7889 <![CDATA[Re: STM32U5A5 HASH seems to not works as expected]]> https://www.wolfssl.com/forums/post7888.html#p7888 OK, i found it !
it was a mistake during copying the project files.
The main expect to use/init the CRYP module instance (linked to AES) but the HAL_MSP source expect SAES...
so you're right, the module was not clocked !

Now all is fine
Thank you for the help !

]]> Tue, 24 Sep 2024 19:06:56 +0000 https://www.wolfssl.com/forums/post7888.html#p7888 <![CDATA[Re: STM32U5A5 HASH seems to not works as expected]]> https://www.wolfssl.com/forums/post7887.html#p7887 dgarske wrote:

Is it the same version of the CubeMX HAL for AES?

Hum, yes, both projects generated in same way..

dgarske wrote:

Are you using the same AES GHASH build options, example: GCM_SMALL or GCM_TABLE_4BIT? The actual AES GCM test happens later. If it also fails then you might check to make sure the clock for the AES peripheral is enabled (__HAL_RCC_AES_CLK_ENABLE();).

I will check this, but i'm pretty sure clock is enabled

]]> Tue, 24 Sep 2024 14:56:22 +0000 https://www.wolfssl.com/forums/post7887.html#p7887 <![CDATA[Re: STM32U5A5 HASH seems to not works as expected]]> https://www.wolfssl.com/forums/post7886.html#p7886 Hi Rickou,

That's odd. Is it the same version of the CubeMX HAL for AES? Are you using the same AES GHASH build options, example: GCM_SMALL or GCM_TABLE_4BIT? The actual AES GCM test happens later. If it also fails then you might check to make sure the clock for the AES peripheral is enabled (__HAL_RCC_AES_CLK_ENABLE();).

Thanks,
David Garske, wolfSSL

]]> Tue, 24 Sep 2024 14:37:51 +0000 https://www.wolfssl.com/forums/post7886.html#p7886 <![CDATA[Re: STM32U5A5 HASH seems to not works as expected]]> https://www.wolfssl.com/forums/post7883.html#p7883 i just made a test on my board with U5A5 (same config file, same lib version, same patch)

i just works as expected without errors .. hum...

So it's OK for me, but i'm currious why it works on 1 target and not on another one..

Tested again on U545 using the lib provided main.c example..
same error during GMAC test.

I haven't seen any differences between the 2 MCU crypto... but as i said i'm a newbee in Crypto world..

]]> Tue, 24 Sep 2024 06:20:11 +0000 https://www.wolfssl.com/forums/post7883.html#p7883 <![CDATA[Re: STM32U5A5 HASH seems to not works as expected]]> https://www.wolfssl.com/forums/post7882.html#p7882 yes sure, found it attached.
I have just modified it for handling U545 MCU

I generated a blank project
I just configured the project using cubeIDE to enable RNG, EAES, PKA, HASH & RTC modules.
then i added this config file and linked the library from a v5.7.2 git clone patched with the STM32 HW fix

run on NUCLEO U545-REQ board.

i will try on my own U5A5 board (but it's a little bit harder because of lack of USART)

]]> Tue, 24 Sep 2024 06:09:13 +0000 https://www.wolfssl.com/forums/post7882.html#p7882 <![CDATA[Re: STM32U5A5 HASH seems to not works as expected]]> https://www.wolfssl.com/forums/post7878.html#p7878 Hi Rickou,

GMAC is the integrity portion of AES GCM and can be used like a hashing function. I suspect you won't need GMAC, but I will investigate the root cause with AES GCM HW crypto.

Can you share me your build settings to try and reproduce? With the CubeMX generated code the settings are usually in a wolfSSL/wolfSSL.I-CUBE-wolfSSL_conf.h.

Thanks,
David Garske, wolfSSL

]]> Mon, 23 Sep 2024 16:17:54 +0000 https://www.wolfssl.com/forums/post7878.html#p7878 <![CDATA[Re: STM32U5A5 HASH seems to not works as expected]]> https://www.wolfssl.com/forums/post7874.html#p7874 ok, i just tested on nucleo U545 board (my own board doesn't have UART on board)
the HASH  test passed..
but i get GMAC error
GMAC     test failed!
error L=15541
[fiducial line numbers: 8773 27740 43402 55860]
Crypt Test: Return code -1

when undefining NO_STM32_CRYPTO
if i'm right this MCU also have crypto module as well as my U5A5..

if i do not undefined NO_STM32_CRYPTO all tests passed..

]]> Mon, 23 Sep 2024 15:40:48 +0000 https://www.wolfssl.com/forums/post7874.html#p7874 <![CDATA[Re: STM32U5A5 HASH seems to not works as expected]]> https://www.wolfssl.com/forums/post7869.html#p7869 Hi dgarske,

thank for the info. i'm currently using v5.7.2-stable

ok i will try to patch it

thank you !

]]> Mon, 23 Sep 2024 06:22:41 +0000 https://www.wolfssl.com/forums/post7869.html#p7869 <![CDATA[Re: STM32U5A5 HASH seems to not works as expected]]> https://www.wolfssl.com/forums/post7868.html#p7868 Hi Rickou,

This issue was fixed in PR https://github.com/wolfSSL/wolfssl/pull/7787 on July 29, 2024.

Please confirm you are using the latest master or patch your code with this PR.

If you continue to have any issues please let us know.

Thanks,
David Garske, wolfSSL

]]> Fri, 20 Sep 2024 16:50:48 +0000 https://www.wolfssl.com/forums/post7868.html#p7868 <![CDATA[STM32U5A5 HASH seems to not works as expected]]> https://www.wolfssl.com/forums/post7867.html#p7867 Hi there!

i'm a newbee regarding Crypto/SSL/etc world..

I use a STM32U5A5 MCU.

I implemented the WolfSSL library successfuly.

BUT, if it try to use STM32 hardware HASH acceleration, i have failure to communicate with TLS1.2 and/or TLS1.3.

so i tryed the provided unit tests and i get same results..
if STM32 HASH is enabled, most tests fail.. starting with:
RANDOM   test failed!

if i disable HASH HW acceleration,
all tests succeed...

is someone have any clue about this problem ?

]]> Fri, 20 Sep 2024 16:47:49 +0000 https://www.wolfssl.com/forums/post7867.html#p7867