Prepare an ESP32 pin and PWM configuration
Check a declared board configuration before building firmware. Choose the exact module revision: exposed pins, reserved memory pins and LEDC resources differ between ESP32 families.
Board profiles and fixed clocks
- ESP32-DevKitC V4 / WROOM-32E-N4 · APB 80 MHz · esp32:esp32 3.3.8 / ESP-IDF 5.5.4
- ESP32-S3-DevKitC-1 v1.1 / WROOM-1-N16R8 · XTAL 40 MHz · esp32:esp32 3.3.8 / ESP-IDF 5.5.4
- ESP32-C3-DevKitM-1 / MINI-1-N4X · XTAL 40 MHz · esp32:esp32 3.3.8 / ESP-IDF 5.5.4
Describe the signals you need
Enter GPIO and channel numbers, frequency in Hz and resolution in bits. Set either pulse width in microseconds or duty in percent. Peripheral pin lists follow the displayed signal order; USB and other fixed routes cannot be moved arbitrarily.
From board to checked configuration
- Select the board, enable the peripherals you intend to use and check their actual pins.
- Add PWM outputs and enter the requested timing. Resolve pin conflicts and review shared timer use.
- Read the nominal frequency, pulse quantization error and findings before downloading code.
Downloads and compilation
Save the project, JSON report or channel CSV. When the necessary checks are clear, download a sketch or ZIP engineering package containing the source, board settings and pinned versions. Compile arbitrary configurations externally; the linked classic ESP32 example is a separate simulation.
What this check cannot establish
Clocks and timer behavior follow the pinned driver model; dynamic frequency independence is not promised. S3 and C3 are configuration/export targets. Offline checks do not verify wiring, servo travel or supply conditions, and the page does not flash hardware.
Worked PWM configurations
Follow a fixed-version input through the offline checker. Nominal timing is calculated, not measured on a board.
Offline configuration checks do not verify physical hardware or safety. These synthetic reference cases are separate from the settings above. Import an example to check its inputs again; a saved verdict is not trusted.
Two outputs share one timer
Do two channel numbers guarantee independent frequency changes?
Version baseline: Microduck rules 2026-11-12.2 · Arduino-ESP32 3.3.8 · ESP-IDF 5.5.4
Inputs and steps
ESP32-DevKitC V4 / WROOM-32E-N4; APB 80 MHz; GPIO18/channel 0 and GPIO19/channel 1; 50 Hz, 14 bits; 1500 µs and 1000 µs.
- Select the named Classic board and keep the example peripheral reservations.
- Add both outputs with the same frequency and resolution, but different channels and pulse widths.
- Inspect group 0 / timer 0 for both outputs and the nominal pulse errors in the report.
Reference check result
No known configuration conflict
No known configuration conflict. Both outputs share timer 0; their nominal pulse errors are about +0.244141 µs and −0.244141 µs.
Inspect inputs and reference JSON
{
"inputs": {
"profileId": "esp32-devkitc-v4-wroom32e-n4",
"peripherals": {
"uart0": true,
"usb": false,
"i2c": false,
"spi": false,
"jtag": false,
"onboardLed": true
},
"peripheralPins": {
"uart0": [
1,
3
],
"usb": [],
"i2c": [
21,
22
],
"spi": [
5,
23,
19,
18
],
"jtag": [
12,
13,
14,
15
],
"onboardLed": []
},
"allowStrapping": false,
"dynamicFrequency": false,
"outputs": [
{
"gpio": 18,
"channel": 0,
"frequencyHz": 50,
"resolutionBits": 14,
"mode": "pulse",
"pulseUs": 1500
},
{
"gpio": 19,
"channel": 1,
"frequencyHz": 50,
"resolutionBits": 14,
"mode": "pulse",
"pulseUs": 1000
}
]
},
"status": "no_known_conflict",
"findings": [],
"outputs": {
"board": "ESP32-DevKitC V4 / WROOM-32E-N4",
"clock": {
"source": "APB",
"hz": 80000000,
"unit": "Hz",
"sourceRef": "arduino-ledc"
},
"channels": [
{
"index": 0,
"gpio": 18,
"header": "J3.9",
"channel": 0,
"group": 0,
"timer": 0,
"frequencyHz": 50,
"resolutionBits": 14,
"dividerRaw": 25000,
"divider": 97.65625,
"actualFrequencyHz": 50,
"readbackFrequencyHz": 50,
"periodUs": 20000,
"precision": 16384,
"mode": "pulse",
"targetHighUs": 1500,
"duty": 1229,
"effectiveTicks": 1229,
"actualHighUs": 1500.244140625,
"pulseErrorUs": 0.244140625,
"actualDutyPercent": 7.501220703125,
"sharedChannel": false
},
{
"index": 1,
"gpio": 19,
"header": "J3.8",
"channel": 1,
"group": 0,
"timer": 0,
"frequencyHz": 50,
"resolutionBits": 14,
"dividerRaw": 25000,
"divider": 97.65625,
"actualFrequencyHz": 50,
"readbackFrequencyHz": 50,
"periodUs": 20000,
"precision": 16384,
"mode": "pulse",
"targetHighUs": 1000,
"duty": 819,
"effectiveTicks": 819,
"actualHighUs": 999.755859375,
"pulseErrorUs": -0.244140625,
"actualDutyPercent": 4.998779296875,
"sharedChannel": false
}
],
"enabledResources": [
{
"resource": "uart0",
"pins": [
1,
3
]
},
{
"resource": "onboardLed",
"pins": []
}
],
"timerUse": [
{
"group": 0,
"used": 1,
"maximum": 4
},
{
"group": 1,
"used": 0,
"maximum": 4
}
],
"simulatorSupported": true,
"fixedFrequencyOnly": true,
"codeReady": true
}
}
What this case does not establish
- Different channels can share a timer. Later frequency changes are outside this fixed-frequency example.
- These pulse widths do not establish safe servo travel. Compile arbitrary projects externally; the website does not flash hardware.
Reference prepared:
Specification sources
The links below retain the technical sources’ original titles. Read each version and review date with the case assumptions.
- Espressif ESP32-DevKitC V4 user guideesp-dev-kits 1b4c83b · reviewed
- Arduino-ESP32 LEDC implementationArduino-ESP32 3.3.8 b4f85baa · reviewed
- ESP-IDF LEDC divider implementationESP-IDF 5.5.4 73550728 · reviewed
- ESP-IDF Classic ESP32 hardware capabilitiesESP-IDF 5.5.4 73550728 · reviewed
An exposed pin reserved for memory
Why is GPIO35 rejected on this S3 board?
Version baseline: Microduck rules 2026-11-12.2 · Arduino-ESP32 3.3.8 · ESP-IDF 5.5.4
Inputs and steps
ESP32-S3-DevKitC-1 v1.1 / WROOM-1-N16R8; GPIO35/channel 0; 50 Hz, 14 bits, 1500 µs.
- Choose the exact N16R8 profile and enter GPIO35.
- Read pin_reserved: this module uses GPIO35–37 for its memory connection.
- Change only the output pin to GPIO18 and check the adjusted report.
Reference check result
Cannot use this configuration
The original input is blocked because the pin is reserved.
Inspect inputs and reference JSON
{
"inputs": {
"profileId": "esp32s3-devkitc1-v1.1-n16r8",
"peripherals": {
"uart0": true,
"usb": false,
"i2c": false,
"spi": false,
"jtag": false,
"onboardLed": true
},
"peripheralPins": {
"uart0": [
43,
44
],
"usb": [
19,
20
],
"i2c": [
8,
9
],
"spi": [
10,
11,
13,
12
],
"jtag": [
39,
40,
41,
42
],
"onboardLed": [
38
]
},
"allowStrapping": false,
"dynamicFrequency": false,
"outputs": [
{
"gpio": 35,
"channel": 0,
"frequencyHz": 50,
"resolutionBits": 14,
"mode": "pulse",
"pulseUs": 1500
}
]
},
"status": "blocked",
"findings": [
{
"code": "pin_reserved",
"severity": "blocked",
"fieldPath": "outputs.0.gpio",
"messageKey": "pinReserved",
"details": {
"gpio": 35,
"reason": "octal_psram"
},
"sourceRef": "s3-board"
}
],
"outputs": {
"board": "ESP32-S3-DevKitC-1 v1.1 / WROOM-1-N16R8",
"clock": {
"source": "XTAL",
"hz": 40000000,
"unit": "Hz",
"sourceRef": "arduino-ledc"
},
"channels": [],
"enabledResources": [
{
"resource": "uart0",
"pins": [
43,
44
]
},
{
"resource": "onboardLed",
"pins": [
38
]
}
],
"timerUse": [
{
"group": 0,
"used": 0,
"maximum": 4
}
],
"simulatorSupported": false,
"fixedFrequencyOnly": true,
"codeReady": false
}
}
Adjust and check again
GPIO18 removes this declared conflict; the adjusted configuration has no known conflict.
No known configuration conflict
Inspect the adjusted reference JSON
{
"inputs": {
"profileId": "esp32s3-devkitc1-v1.1-n16r8",
"peripherals": {
"uart0": true,
"usb": false,
"i2c": false,
"spi": false,
"jtag": false,
"onboardLed": true
},
"peripheralPins": {
"uart0": [
43,
44
],
"usb": [
19,
20
],
"i2c": [
8,
9
],
"spi": [
10,
11,
13,
12
],
"jtag": [
39,
40,
41,
42
],
"onboardLed": [
38
]
},
"allowStrapping": false,
"dynamicFrequency": false,
"outputs": [
{
"gpio": 18,
"channel": 0,
"frequencyHz": 50,
"resolutionBits": 14,
"mode": "pulse",
"pulseUs": 1500
}
]
},
"status": "no_known_conflict",
"findings": [],
"outputs": {
"board": "ESP32-S3-DevKitC-1 v1.1 / WROOM-1-N16R8",
"clock": {
"source": "XTAL",
"hz": 40000000,
"unit": "Hz",
"sourceRef": "arduino-ledc"
},
"channels": [
{
"index": 0,
"gpio": 18,
"header": "J1.11",
"channel": 0,
"group": 0,
"timer": 0,
"frequencyHz": 50,
"resolutionBits": 14,
"dividerRaw": 12500,
"divider": 48.828125,
"actualFrequencyHz": 50,
"readbackFrequencyHz": 50,
"periodUs": 20000,
"precision": 16384,
"mode": "pulse",
"targetHighUs": 1500,
"duty": 1229,
"effectiveTicks": 1229,
"actualHighUs": 1500.244140625,
"pulseErrorUs": 0.244140625,
"actualDutyPercent": 7.501220703125,
"sharedChannel": false
}
],
"enabledResources": [
{
"resource": "uart0",
"pins": [
43,
44
]
},
{
"resource": "onboardLed",
"pins": [
38
]
}
],
"timerUse": [
{
"group": 0,
"used": 1,
"maximum": 4
}
],
"simulatorSupported": false,
"fixedFrequencyOnly": true,
"codeReady": true
}
}
What this case does not establish
- This restriction belongs to the named module and memory variant, not every S3 board.
- S3 projects can be exported for external compilation; this site does not emulate S3 firmware or verify wiring.
Reference prepared:
Specification sources
The links below retain the technical sources’ original titles. Read each version and review date with the case assumptions.
- Espressif ESP32-S3-DevKitC-1 v1.1 user guidev1.1; esp-dev-kits 1b4c83b · reviewed
- Espressif ESP32-S3-WROOM-1 module datasheetv1.8; ESP32-S3-WROOM-1-N16R8 · reviewed
- Arduino-ESP32 LEDC implementationArduino-ESP32 3.3.8 b4f85baa · reviewed
A low frequency needs a feasible divider
Why does 50 Hz fail at 8 bits on the C3 profile?
Version baseline: Microduck rules 2026-11-12.2 · Arduino-ESP32 3.3.8 · ESP-IDF 5.5.4
Inputs and steps
ESP32-C3-DevKitM-1 / MINI-1-N4X; XTAL 40 MHz; GPIO4/channel 0; 50 Hz, 8 bits, 1500 µs.
- Enter the 8-bit input without changing the fixed clock.
- Read divider_out_of_range before trying to export usable code.
- Change resolution to 14 bits and compare the resulting timing.
Reference check result
Cannot use this configuration
The 8-bit combination is blocked by the divider limit.
Inspect inputs and reference JSON
{
"inputs": {
"profileId": "esp32c3-devkitm1-n4x",
"peripherals": {
"uart0": true,
"usb": false,
"i2c": false,
"spi": false,
"jtag": false,
"onboardLed": true
},
"peripheralPins": {
"uart0": [
21,
20
],
"usb": [
18,
19
],
"i2c": [
8,
9
],
"spi": [
7,
6,
5,
4
],
"jtag": [
4,
5,
6,
7
],
"onboardLed": [
8
]
},
"allowStrapping": false,
"dynamicFrequency": false,
"outputs": [
{
"gpio": 4,
"channel": 0,
"frequencyHz": 50,
"resolutionBits": 8,
"mode": "pulse",
"pulseUs": 1500
}
]
},
"status": "blocked",
"findings": [
{
"code": "divider_out_of_range",
"severity": "blocked",
"fieldPath": "outputs.0.frequencyHz",
"messageKey": "frequencyUnavailable",
"details": {
"frequency": 50,
"bits": 8
},
"sourceRef": "idf-ledc"
}
],
"outputs": {
"board": "ESP32-C3-DevKitM-1 / MINI-1-N4X",
"clock": {
"source": "XTAL",
"hz": 40000000,
"unit": "Hz",
"sourceRef": "arduino-ledc"
},
"channels": [],
"enabledResources": [
{
"resource": "uart0",
"pins": [
21,
20
]
},
{
"resource": "onboardLed",
"pins": [
8
]
}
],
"timerUse": [
{
"group": 0,
"used": 0,
"maximum": 4
}
],
"simulatorSupported": false,
"fixedFrequencyOnly": true,
"codeReady": false
}
}
Adjust and check again
At 14 bits the nominal result is 50 Hz, with a 1500.244140625 µs high pulse.
No known configuration conflict
Inspect the adjusted reference JSON
{
"inputs": {
"profileId": "esp32c3-devkitm1-n4x",
"peripherals": {
"uart0": true,
"usb": false,
"i2c": false,
"spi": false,
"jtag": false,
"onboardLed": true
},
"peripheralPins": {
"uart0": [
21,
20
],
"usb": [
18,
19
],
"i2c": [
8,
9
],
"spi": [
7,
6,
5,
4
],
"jtag": [
4,
5,
6,
7
],
"onboardLed": [
8
]
},
"allowStrapping": false,
"dynamicFrequency": false,
"outputs": [
{
"gpio": 4,
"channel": 0,
"frequencyHz": 50,
"resolutionBits": 14,
"mode": "pulse",
"pulseUs": 1500
}
]
},
"status": "no_known_conflict",
"findings": [],
"outputs": {
"board": "ESP32-C3-DevKitM-1 / MINI-1-N4X",
"clock": {
"source": "XTAL",
"hz": 40000000,
"unit": "Hz",
"sourceRef": "arduino-ledc"
},
"channels": [
{
"index": 0,
"gpio": 4,
"header": "J3.11",
"channel": 0,
"group": 0,
"timer": 0,
"frequencyHz": 50,
"resolutionBits": 14,
"dividerRaw": 12500,
"divider": 48.828125,
"actualFrequencyHz": 50,
"readbackFrequencyHz": 50,
"periodUs": 20000,
"precision": 16384,
"mode": "pulse",
"targetHighUs": 1500,
"duty": 1229,
"effectiveTicks": 1229,
"actualHighUs": 1500.244140625,
"pulseErrorUs": 0.244140625,
"actualDutyPercent": 7.501220703125,
"sharedChannel": false
}
],
"enabledResources": [
{
"resource": "uart0",
"pins": [
21,
20
]
},
{
"resource": "onboardLed",
"pins": [
8
]
}
],
"timerUse": [
{
"group": 0,
"used": 1,
"maximum": 4
}
],
"simulatorSupported": false,
"fixedFrequencyOnly": true,
"codeReady": true
}
}
What this case does not establish
- The low-frequency boundary depends on clock and resolution; this is not a universal C3 minimum frequency.
- This is a calculated reference, not a waveform measurement. C3 firmware must be compiled and tested outside this simulator.
Reference prepared:
Specification sources
The links below retain the technical sources’ original titles. Read each version and review date with the case assumptions.
- Espressif ESP32-C3-DevKitM-1 user guideesp-dev-kits 1b4c83b · reviewed
- ESP-IDF ESP32-C3 hardware capabilitiesESP-IDF 5.5.4 73550728 · reviewed
- ESP-IDF LEDC divider implementationESP-IDF 5.5.4 73550728 · reviewed
- Arduino-ESP32 LEDC implementationArduino-ESP32 3.3.8 b4f85baa · reviewed
A valid number can still need review
Why is GPIO0 not an automatic pass?
Version baseline: Microduck rules 2026-11-12.2 · Arduino-ESP32 3.3.8 · ESP-IDF 5.5.4
Inputs and steps
Classic ESP32 profile; GPIO0/channel 0; 50 Hz, 14 bits, 1500 µs; allowStrapping=false.
- Enter GPIO0 and leave the strapping acknowledgement off.
- Read pin_strapping and keep the needs_review result.
- Save the reference project for inspection; check the real reset-level conditions before changing that declaration.
Reference check result
Needs review
Timing can be calculated, but codeReady remains false while the strapping condition is unconfirmed.
Inspect inputs and reference JSON
{
"inputs": {
"profileId": "esp32-devkitc-v4-wroom32e-n4",
"peripherals": {
"uart0": true,
"usb": false,
"i2c": false,
"spi": false,
"jtag": false,
"onboardLed": true
},
"peripheralPins": {
"uart0": [
1,
3
],
"usb": [],
"i2c": [
21,
22
],
"spi": [
5,
23,
19,
18
],
"jtag": [
12,
13,
14,
15
],
"onboardLed": []
},
"allowStrapping": false,
"dynamicFrequency": false,
"outputs": [
{
"gpio": 0,
"channel": 0,
"frequencyHz": 50,
"resolutionBits": 14,
"mode": "pulse",
"pulseUs": 1500
}
]
},
"status": "needs_review",
"findings": [
{
"code": "pin_strapping",
"severity": "needs_review",
"fieldPath": "outputs.0.gpio",
"messageKey": "pinStrapping",
"details": {
"gpio": 0
},
"sourceRef": "classic-board"
}
],
"outputs": {
"board": "ESP32-DevKitC V4 / WROOM-32E-N4",
"clock": {
"source": "APB",
"hz": 80000000,
"unit": "Hz",
"sourceRef": "arduino-ledc"
},
"channels": [
{
"index": 0,
"gpio": 0,
"header": "J3.14",
"channel": 0,
"group": 0,
"timer": 0,
"frequencyHz": 50,
"resolutionBits": 14,
"dividerRaw": 25000,
"divider": 97.65625,
"actualFrequencyHz": 50,
"readbackFrequencyHz": 50,
"periodUs": 20000,
"precision": 16384,
"mode": "pulse",
"targetHighUs": 1500,
"duty": 1229,
"effectiveTicks": 1229,
"actualHighUs": 1500.244140625,
"pulseErrorUs": 0.244140625,
"actualDutyPercent": 7.501220703125,
"sharedChannel": false
}
],
"enabledResources": [
{
"resource": "uart0",
"pins": [
1,
3
]
},
{
"resource": "onboardLed",
"pins": []
}
],
"timerUse": [
{
"group": 0,
"used": 1,
"maximum": 4
},
{
"group": 1,
"used": 0,
"maximum": 4
}
],
"simulatorSupported": true,
"fixedFrequencyOnly": true,
"codeReady": false
}
}
What this case does not establish
- A checkbox is a declaration, not a measurement of external pull resistors or reset levels.
- This example leaves the question open. It does not prove that a connected servo or board will boot safely.
Reference prepared:
Specification sources
The links below retain the technical sources’ original titles. Read each version and review date with the case assumptions.
- Espressif ESP32-DevKitC V4 user guideesp-dev-kits 1b4c83b · reviewed
- Espressif ESP32-WROOM-32E module datasheetv2.1; ESP32-WROOM-32E-N4 · reviewed
- Arduino-ESP32 LEDC implementationArduino-ESP32 3.3.8 b4f85baa · reviewed