Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

STM32WB: add support for AES #63768

Merged
merged 3 commits into from
Oct 20, 2023

Conversation

hlukasz
Copy link
Contributor

@hlukasz hlukasz commented Oct 10, 2023

STM32WB MCUs have two AES peripherals: AES1 for application use and AES2 dedicated for network stack. This patch allows to use AES1 in Zephyr. Tested on nucleo-wb55rg board with drivers/crypto sample.

*** Booting Zephyr OS build v3.5.0-rc2-72-g4f57614cbddc ***
I: Cipher Sample
I: ECB Mode
I: Output length (encryption): 16
I: ECB mode ENCRYPT - Match
I: Output length (decryption): 16
I: ECB mode DECRYPT - Match
I: CBC Mode
I: Output length (encryption): 80
I: CBC mode ENCRYPT - Match
I: Output length (decryption): 64
I: CBC mode DECRYPT - Match
I: CTR Mode
I: Output length (encryption): 64
I: CTR mode ENCRYPT - Match
I: Output length (decryption): 64
I: CTR mode DECRYPT - Match
I: CCM Mode
E: Unsupported mode
I: GCM Mode
E: Unsupported mode

@github-actions
Copy link

Hello @hlukasz, and thank you very much for your first pull request to the Zephyr project!
Our Continuous Integration pipeline will execute a series of checks on your Pull Request commit messages and code, and you are expected to address any failures by updating the PR. Please take a look at our commit message guidelines to find out how to format your commit messages, and at our contribution workflow to understand how to update your Pull Request. If you haven't already, please make sure to review the project's Contributor Expectations and update (by amending and force-pushing the commits) your pull request if necessary.
If you are stuck or need help please join us on Discord and ask your question there. Additionally, you can escalate the review when applicable. 😊

STM32WB MCUs have two AES peripherals: AES1 for application use and AES2
dedicated for network stack. This patch modifies stm32 crypto driver to
use AES1 peripheral when building for STM32WB.

Signed-off-by: Lukasz Hawrylko <[email protected]>
STM32WB MCUs has two AES peripeherals. Add AES1 definition, AES2 must not
be used by application CPU core.

Signed-off-by: Lukasz Hawrylko <[email protected]>
Enable AES1 peripheral by default to add support for drivers/crypto sample.

Signed-off-by: Lukasz Hawrylko <[email protected]>
@hlukasz hlukasz force-pushed the stm32wb_aes_support branch from 2668358 to 81f6816 Compare October 11, 2023 08:11
@carlescufi carlescufi merged commit a422e1d into zephyrproject-rtos:main Oct 20, 2023
17 checks passed
@github-actions
Copy link

Hi @hlukasz!
Congratulations on getting your very first Zephyr pull request merged 🎉🥳. This is a fantastic achievement, and we're thrilled to have you as part of our community!

To celebrate this milestone and showcase your contribution, we'd love to award you the Zephyr Technical Contributor badge. If you're interested, please claim your badge by filling out this form: Claim Your Zephyr Badge.

Thank you for your valuable input, and we look forward to seeing more of your contributions in the future! 🪁

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants