8000 esp32: After hard reset PWM always has a duty of 512 of frequencies < 611Hz. · Issue #8306 · micropython/micropython · GitHub
[go: up one dir, main page]
Skip to content

esp32: After hard reset PWM always has a duty of 512 of frequencies < 611Hz. #8306

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.

Sign up for GitHub

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

Jump to bottom
Closed
robert-hh opened this issue Feb 15, 2022 · 1 comment
Closed

esp32: After hard reset PWM always has a duty of 512 of frequencies < 611Hz. #8306

robert-hh opened this issue Feb 15, 2022 · 1 comment
Labels
port-esp32

Comments

@robert-hh
Copy link
Contributor
robert-hh commented Feb 15, 2022 •
edited
Loading

This is another variant of the <611Hz issue. After hard reset, for the first PWM object the duty rate is always 50% for frequencies < 611Hz, regardless of what has been set in the constructor. Setting the duty rate in a second command works. Further new instantiated PWM objects have the right duty rate. For frequencies >=611 it works well.
@Dreagonmon Dreagonmon mentioned this issue Feb 26, 2022
Closed
robert-hh added a commit to robert-hh/micropython that referenced this issue Feb 27, 2022
@robert-hh
esp32: Always set the duty cycle when setting the frequency.
076b961 
If setting the frequency to a value used already by an existing timer,
this timer will be used. But still, the duty cycle for that channel
may have to be changed.

Fixes micropython#8306 as well.
@robert-hh robert-hh mentioned this issue Feb 27, 2022
Closed
robert-hh added a commit to robert-hh/micropython that referenced this issue Mar 1, 2022
@robert-hh
esp32: Always set the duty cycle when setting the frequency.
28030a8 
If setting the frequency to a value used already by an existing timer,
this timer will be used. But still, the duty cycle for that channel
may have to be changed.

Fixes micropython#8306 as well.
robert-hh added a commit to robert-hh/micropython that referenced this issue Mar 1, 2022
@robert-hh
esp32: Always set the duty cycle when setting the frequency.
2ea391f 
If setting the frequency to a value used already by an existing timer,
this timer will be used. But still, the duty cycle for that channel
may have to be changed.

Fixes micropython#8306 as well.
@robert-hh robert-hh mentioned this issue Mar 3, 2022
Closed
robert-hh added a commit to robert-hh/micropython that referenced this issue Mar 4, 2022
@robert-hh
esp32: Always set the duty cycle when setting the frequency.
7d0bb77 
If setting the frequency to a value used already by an existing timer,
this timer will be used. But still, the duty cycle for that channel
may have to be changed.

Fixes micropython#8306 as well.
dpgeorge pushed a commit that referenced this issue Mar 7, 2022
@robert-hh @dpgeorge
esp32/machine_pwm: Always set the duty cycle when setting the frequency.
55a0125 
If setting the frequency to a value used already by an existing timer, this
timer will be used.  But still, the duty cycle for that channel may have to
be changed.

Fixes issues #8306 and #8345.
@dpgeorge
Copy link
Member
dpgeorge commented Mar 7, 2022

Fixed by 55a0125

@dpgeorge dpgeorge closed this as completed Mar 7, 2022
tannewt pushed a commit to tannewt/circuitpython that referenced this issue Aug 24, 2023
@dhalbert
Merge pull request micropython#8306 from jepler/setsockopt-constants-…
a15d139 
…for-todbot

Add several constants needed to use multicast UDP
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
port-esp32
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dpgeorge @robert-hh
0