CubeMX HW crypto-callback tests (cubeaes + cubecrypto)#16
Open
dgarske wants to merge 2 commits into
Open
Conversation
dgarske
force-pushed
the
stm32_cubemx_aes_cb
branch
from
July 22, 2026 17:27
17cb7aa to
1f300ff
Compare
dgarske
changed the title
dgarske
force-pushed
the
stm32_cubemx_aes_cb
branch
from
July 22, 2026 17:55
1f300ff to
50426e6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds two CubeMX/HAL test targets that validate the wolfSSL STM32 crypto-callback device (companion wolfSSL PR) under
WOLF_CRYPTO_CB_ONLY_AES/_ECCon the STM32U385.Changes
src/main_cubeaes.c+cubeaestarget: AES-GCM KATs (McGrew TC3/TC4) with a plaintext key viawc_Stm32_CubeAesRegisterunderWOLF_CRYPTO_CB_ONLY_AES.src/main_cubecrypto.c+cubecryptotarget: HW ECDSA sign + verify (normal P-256 key -> PKA), CCB-protected ECDSA, and AES-GCM, all through the callback underWOLF_CRYPTO_CB_ONLY_ECC+WOLF_CRYPTO_CB_ONLY_AES. Brings up the ST HAL PKA (hpka+HAL_PKA_Init) the PKA path needs.Makefile/user_settings.h: the two targets +STM32_CUBE_AES_ONLY/STM32_CUBE_CRYPTO_ONLYpresets;cubecryptolinks the HAL PKA + CCB drivers.Testing
On NUCLEO-U385RG-Q:
make BOARD=u3 BUILD=cubemx TARGET=cubecrypto CONFIG=bare flashandTARGET=cubeaesboth reportResult: 0 (PASS). (CCB on-chip provisioning is a soft-pass underCB_ONLY_ECC-- it needs software keygen; CCB sign works with a pre-provisioned blob.)