Feature Request: DAC support for ESP32-S2
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c, erlang
- Domain
- embedded-iot
Research direction
Start by reading the ESP-IDF DAC peripheral documentation linked in the issue and the existing ESP32-S2 support in AtomVM. The issue names no source files or tests, so first identify how the project exposes existing peripherals and what hardware support paths apply. Done means DAC support for ESP32-S2 is available; the issue does not define an API or acceptance tests.
Written by the indexing model from the issue text.
Description
I am really enjoying the AtomVM project and what it brings to the table! Such a cool project.
I would like to request support for the Digital To Analog Converter Peripheral on the esp32s2. I have not seen any work being done on it here, and I was hoping it would be possible for a hobby project I am building. If this is not possible, or maybe not practical, this issue can be closed. I understand that this project exists on the work of volunteers. I might try my hand at adding support, but this type of embedded work is all new to me.
Thanks for your work!
- Dominant language
- Erlang
- Stars
- 2.3k
- Forks
- 171
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from atomvm/AtomVM
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 3 days
-
lwIP sockets: a failed listen or connect leaves the socket lock held, a later close hangs foreverOpen
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 3 days
Similar issues
-
SPIDevice selects an active-high device as soon as it is createdPossibly taken @mikeysklar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
adafruit/circuitpython#11869 ·
Maintainers usually reply within 1 day
-
[Bug]: RFENCE rejects the architecturally defined full-range size when start_addr is nonzeroPossibly taken @hongwei-2026 claimed this today. OpenC-bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rustsbi/rustsbi#484 · 1 comment ·
Maintainers usually reply within 1 day
-
Fan percentage in Auto mode shows the night-mode speed cap (`nmdv`) while the fan is idle (`fnst: OFF`)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cmgrayb/hass-dyson#552 ·
Maintainers usually reply within 1 day
-
backlog bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EchoTools/nevr-runtime#2664 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
seven-lynx/HoundMind#108 ·
Maintainers usually reply within 1 day