Skip to content

ESP32-S3 Ledc different resolutions cause wrong duty update #11373

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

Open
1 task done
handmade0octopus opened this issue May 17, 2025 · 1 comment
Open
1 task done

ESP32-S3 Ledc different resolutions cause wrong duty update #11373

handmade0octopus opened this issue May 17, 2025 · 1 comment
Assignees
Labels
Status: Awaiting triage Issue is waiting for triage Status: Test needed Issue needs testing

Comments

@handmade0octopus
Copy link

Board

Custom ESP32-S3 board

Device Description

Custom Gauge.S board

Hardware Configuration

[    123][I][esp32-hal-ledc.c:166] ledcAttachChannel(): LEDC attached to pin 10 (channel 0, resolution 8)
[  1791][I][esp32-hal-ledc.c:166] ledcAttachChannel(): LEDC attached to pin 3 (channel 1, resolution 14)

Version

v3.2.0

IDE Name

PlatformIO

Operating System

W11

Flash frequency

80mhz

PSRAM enabled

yes

Upload speed

Default

Description

When setting different resolutions on different channels, second one called disrupts duty resolution calculation and frequency.

Basically I set first one to pin 10 to control backlight LED at 500hz frequency and 8 bit resolution.

Then I use 400Hz PWM output on 14 bit resolution.

After second one is setup the first one goes from very well working to 29 Hz at ~1% duty cycle (measured with scope).

Sketch

not relevant

Debug Message

Got scope trace but its not very interesting.

Other Steps to Reproduce

No response

I have checked existing issues, online documentation and the Troubleshooting Guide

  • I confirm I have checked existing issues, online documentation and Troubleshooting guide.
@handmade0octopus handmade0octopus added the Status: Awaiting triage Issue is waiting for triage label May 17, 2025
@P-R-O-C-H-Y P-R-O-C-H-Y self-assigned this May 19, 2025
@P-R-O-C-H-Y P-R-O-C-H-Y added the Status: Test needed Issue needs testing label May 19, 2025
@P-R-O-C-H-Y
Copy link
Member

Hi @handmade0octopus, Thank you for reporting that. I will try to reproduce and will keep you updated about next steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Awaiting triage Issue is waiting for triage Status: Test needed Issue needs testing
Projects
None yet
Development

No branches or pull requests

2 participants