-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Peripheral Clock enabling before writing registers #14727
Comments
Closed/reopened to retrigger the github action for issue handling. |
Hi I would say there is unfortunately no generic and automatic method to detect if the peripheral clock is missing... @ARMmbed/team-st-mcd |
ST_INTERNAL_REF 108872 |
Hi |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of defect
In some targets the registers for peripherals were written before the clock to the peripherals was activated. Therefore the changes to the registers were not done.
See #14724 and #14720
The remaining question is if this kind of defect can be detected automatically. It can be tedious to look through the start code of all devices by hand, in the case of the STM32L552 this was detected "by accident".
I would appreciate any input on this subject. Maybe some sort of guide on peripheral initialization?
Target(s) affected by this defect ?
STM32, maybe others as well
Toolchain(s) (name and version) displaying this defect ?
any
What version of Mbed-os are you using (tag or sha) ?
mbed-os-6.11.0
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
any
How is this defect reproduced ?
Write a register and see if it actually changed something.
The text was updated successfully, but these errors were encountered: