Unexpected Behavior of the STM32 CRYP Module I'm recently working on benchmarking a various implementations and configurations of cryptographic algorithms such AES-GCM on STM32. Two of these tested function are the following :void test_aes_hardware(void)
{
uint32_t plaintext[DATA_SIZE/4];
uint32_t ciphertext[DATA_SIZE/4];
uint32_t decrypted[DATA_SIZE/4];
uint8_t key_bytes[32];
uint8_t iv_bytes[16];
uint32_t key[8];
uint32_t iv[4];
uint8_t ikm[4];
uint8_t salt[4];
uint8_t info1[] = "HW_AES_KEY";
uint8_t info2[] = "HW_AES_IV";
uint32_t rnd;
/* RNG */
HAL_RNG_GenerateRandomNumber(&hrng, &rnd);
memcpy(ikm, &rnd, 4);
HAL_RNG_GenerateRandomNumber(&hrng, &rnd);
memcpy(salt, &rnd, 4);
/* KDF */
xkdfBlake(key_bytes, 32, ikm, 4, salt, 4, info1, sizeof(info1));
xkdfBlake(iv_bytes, 16, ikm, 4, salt, 4, info2, sizeof(info2));
memcpy(key, key_bytes, 32);
memcpy(iv, iv_bytes, 16);
for (int i = 0; i < DATA_SIZE / 4; i++) {
uint32_t w
