Support STM32H5 Debug Authentication
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
STM32H5 controller family uses so-called Product State for Readout protection among other benefits.
See https://wiki.st.com/stm32mcu/index.php?title=Security:Product_state_for_STM32H5&oldid=49661
For closing/opening STM32H5 controllers, a special protocol is used (see p.40 https://www.st.com/content/ccc/resource/training/technical/product_training/group1/08/1e/b9/6d/c9/e9/47/3f/STM32H5-Security-Architecture-overview/files/stm32h5-security-architecture-overview.pdf/jcr:content/translations/en.stm32h5-security-architecture-overview.pdf ).
Tutorial with ST tools: https://community.st.com/t5/stm32-mcus/implementing-debug-authentication-on-stm32h5-using-cli-tools/ta-p/622308
Are there any plans for supporting Provisioning/Debug Authentication on STM32H5 controllers?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files, tests, or entry points. Start by reviewing the linked STM32H5 Product State, Security Architecture, and ST CLI documentation alongside existing pyOCD support for related authentication workflows. Done would require an agreed scope and verified support for STM32H5 provisioning or debug authentication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100