-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
dts: arm: st: standardize pwm default property st,prescaler to 0 #31290
Comments
+1 |
In that case where all |
Should this be extended to all the PWM prescaler : stm32f1, stm32f0 , stm32f3, stm32f4, stm32f7, stm32g4 , stm32h7, stm32l4, stm32wb soc devices which still have |
Point is to define default value to 0 in soc.dtsi files, which can be then be configured later on at board/application level.
This is indeed the request. |
Any updates on this or the related pr #32646 ? The issue still seems to persist. The PWM LED fade sample works with prescaler value of 10000 but when mapping values between using EDIT: this seems to be for all stm32 parts. I have tested it between some stm32f0 and stm32f4 variants |
@ric96 nothing has been done for now. But I plan to get this fixed for v2.7.0 |
As you may have seen in discord @erwango @FRASTM. BoardSTM32 Nucleo H743ZI2 ProblemI did this to set the period frequency
when setting the period to 10kHz (100µsec) i get no pwm output anymore
whenever i set it to 1kHz (1ms) it works. SolutionThere's still a prescaler set in dts... default: 10000...(/zephyr/boards/arm/nucleo_h743zi/nucleo_h743zi.dts).. i reset it to 0... no problems now.
In case someone encounters this issue. |
Looking at pwm property
st,prescaler
accross STM32 dtsi files,it appears that for some timer instances, value is 0, for other instances it is 10000.
It seems that there is no reason to have either 0 or 10000, just some inheritance.
Proposal is to harmonize this default value for all instances, and set 0 to give the maximum speed.
Warning: this change may impact user applications,
and this is the reason why we propose to do that after next LTS release,
i.e. do that for release 3.0
The text was updated successfully, but these errors were encountered: