2025-12-20 1:12 AM - last edited on 2025-12-20 1:28 AM by Andrew Neil
Hello,
I'm facing an issue in CubeMX with the AES IV in CTR Mode
The IV is not saved in the IOC file and is discarded from the generated code, replaced with a full 0 value.
The AES content inside the IOC file:
AES.Algorithm=CRYP_AES_CTR
AES.DataType=CRYP_DATATYPE_8B
AES.DataWidthUnit=CRYP_DATAWIDTHUNIT_BYTE
AES.IPParameters=KeySize,DataType,DataWidthUnit,pKey,Algorithm
AES.KeySize=CRYP_KEYSIZE_256B
AES.pKey=-------- -------- -------- -------- -------- -------- -------- --------
MCU: STM32F423VHT
CubeMX: Latest version 6.16.1
AES Settings
Algorithm
Data encryption type AES CTR
Parameters
Data type 8b(byte swapping)
KeySize 256b
Encryption/Decryption key -------- -------- -------- -------- -------- -------- -------- --------
Initialization vector E467824C 805348FF 4CE1DF70 566ED4A9
Data width unit Byte
Key and IV configuration skip Always
Solved! Go to Solution.
2025-12-22 1:35 AM
Hello @zeboss49 ,
The behavior described was not reproduced by my side, knowing that I am using STM32CubeMX 6.16.1.
I will be waiting for your feedback.
Thanks.
Mahmoud
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2025-12-20 3:53 AM
Hello,
thanks for the change :)
You're right, the previous title was a rubbish.
2025-12-22 12:38 AM
Hello @zeboss49 ,
Let me thank you for posting.
I am currently checking this behavior, and I will get back to ASAP.
Thanks.
Mahmoud
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2025-12-22 1:35 AM
Hello @zeboss49 ,
The behavior described was not reproduced by my side, knowing that I am using STM32CubeMX 6.16.1.
I will be waiting for your feedback.
Thanks.
Mahmoud
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2025-12-22 4:20 AM
Hello,
the issue no longer exists with CubeMX 6.16.1.
I upgraded recently and did not check the issue after upgrading.
Sorry for the inconvenience.
Thanks
Didier