2018-07-12 04:43 AM
Hi, I am trying to use CRYP_AES_GCM example from STM32Cube_FW_F7_V1.11.0 for stm32f769I-eval. I see, stm32f7xx_hal_cryp.c has two set of APIs. By default the APIs under ' &sharpif defined (CRYP) ' are enabled. and these APIs seem not supporting GCM mode as HAL_CRYP_Init() is not even setting chaining mode. but
HAL_CRYP_Init() under
'
&sharpif defined (AES) ' has some code to set chaining mode.
Are APIs under
'
&sharpif defined (AES) ' are also well tested?
But Other extended APIs for AES GCM mode are under '
&sharpif defined (CRYP) ' in stm32f7xx_hal_cryp_ex.c file.
So I could not conclude which one is right option either '
&sharpif defined (CRYP) ' or '
&sharpif defined (AES) '. Can any one help if some one has used these APIs.
Thanks,
#stm32f7-hal #crypto #crypto-aes-encrypt-stm32 #stm32f769i2018-07-12 05:16 AM
You would need an F779 part which support crypto hardware, the F769 is the part without it.
The STM32F769I-EVAL board and the STM32F779I-EVAL share a common BSP and examples.