We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I found the issue of gpio refusing to reset after a set. (with stm32l151xc variant)
The issue and its cause is explain in the st community forum: https://community.st.com/s/question/0D50X0000AldbDt/bug-in-stm32l151-and-others-driver-code-these-chips-dont-have-a-brr-register
That means we need to have the STM32Cube driver fixed.
There is nothing wrong with not the board definition nor the stm32duino core.
As a workaround, I set a #undef GPIO_BRR_BR_0 inside variant.h . Of course it's only to proove that this is the issue.
#undef GPIO_BRR_BR_0
Do you plan to open a PR to upstream these board definitions?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I found the issue of gpio refusing to reset after a set. (with stm32l151xc variant)
The issue and its cause is explain in the st community forum: https://community.st.com/s/question/0D50X0000AldbDt/bug-in-stm32l151-and-others-driver-code-these-chips-dont-have-a-brr-register
That means we need to have the STM32Cube driver fixed.
There is nothing wrong with not the board definition nor the stm32duino core.
As a workaround, I set a
#undef GPIO_BRR_BR_0
inside variant.h . Of course it's only to proove that this is the issue.Do you plan to open a PR to upstream these board definitions?
The text was updated successfully, but these errors were encountered: