Replies: 1 comment 1 reply
-
If you want to provide a way for users to interactivity experiment with the new Peripheral Manager prototype on Wokwi so they can provide feedback / want to test the prototype on Wokwi, please ping me and I'll be happy to assist. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Why
The ESP32 Family of chips have a large set of peripherals, that can provide different features, while not being bound to particular GPIOs. Some peripherals can provide more than one functionality and there are functionalities that can be provided by different peripherals at the same time (ex.
LEDC
can providePWM
,Servo
andTone
, so canRMT
, butRMT
can also provideNeoPixel
and others). Different chips have different subset of peripherals and peripherals themselves have different number of channels, limits, etc.With Peripheral Manager we hope to provide tracking of available GPIOs, peripherals and channels, in order to have a cleaner and easy to use API with more features on more pins, as well as preventing some common mistakes, like using pins reserved for Flash and PSRAM.
Targets
analogWrite
on more channelsServo
on more channelsTone
on more channelsNeoPixel
,OneWire
, etc.)Feature Ideas
RMT
will provide betterServo
thanLEDC
)Servo
channel fromRMT
toLEDC
if channel forNeoPixel
is needed)LEDC
select an already configured timer, if it matches the requirements (ex. allanalogWrite
channels can use the same timer. Same goes forServo
)LEDC
and have already predefined channel)Beta Was this translation helpful? Give feedback.
All reactions