Skip to content
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

Added ESP32 S2 mini #481

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

BastiMu
Copy link

@BastiMu BastiMu commented Nov 11, 2024

I use a ESP32 S2 mini for my project so I added it to the devices.

Unfortunately there is no GPIO27 for the LEDs, so I added a if/else to define GPIO16 for all ESP32 S2.

@nikolai2111
Copy link
Contributor

nikolai2111 commented Dec 5, 2024

@dbambus is there a way you could specify like some defines in the platform.ini that you could specify the pins used of the MCU in it, something like

[env:esp32c3dev]
platform = espressif32
board = esp32-c3-devkitc-02
...
pins = 
  LEDS:24
  SDA:5
  SCL:6
  RTC:7

Or another easy way to add and change MCU and their pins, because I have seen, since you upgraded to the ESP32 there are a lot of other MCU to migrate to, or do you only want to support a handful of MCUs?

@dbambus
Copy link
Collaborator

dbambus commented Dec 6, 2024

Hey @BastiMu and @nikolai2111,

for your contribution and your input. So far I've added the support for ESP32 as a testcase, it works, but not a 100% yet. There are still problems to solve, and you can help me with that, for example look for potential bugs in combination with ESP32. For example with the time, it takes up to 90 secs to get a correct time on the ESP32 in comparison to the ESP8266.

The Idea behind this is also to support a variety of MCUs, including a Rpi Pico. The only constraint here are the supported MCUs of the Neopixelbus library.

@nikolai2111 is your suggestion already in use in some other project ?

David

@BastiMu
Copy link
Author

BastiMu commented Dec 6, 2024

@dbambus I did not experienced any restrictions with the ESP32-S2 mini, here the time is updated instant with wifi connection. Unfortunately I don't have a ESP32 laying around here (just an ESP32-C3 super mini), so I cannot help here.

@nikolai2111 That's a good idea. But I think it would be best to be able to specify the pin in the settings (e.g. like in WLED).

@nikolai2111
Copy link
Contributor

nikolai2111 commented Dec 8, 2024

I understand, I would also support this variant of being a little bit caution about the MCU we support at the moment and rule out the bugs. Currently, my clocks (I purchased 5 pcs.) aren't deployed in the wild, but I will look forward to record every bug they will find.

For the ESP32-C3 I also did not noticed some problems with the time update.

I would also recommend to look forward to support the latest ESPs, like the ESP32-C3 or S2 and for legacy only the ESP8266, because the other aren't recommended for new designs anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants