-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
STM32WB: add support for AES #63768
Conversation
Hello @hlukasz, and thank you very much for your first pull request to the Zephyr project! |
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]>
2668358
to
81f6816
Compare
Hi @hlukasz! 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! 🪁 |
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.