Replies: 5 comments
-
I've successfully used Neopixels on several ESP32-S3 devices. There may be a conflict or misconfiguration getting in the way here. To be able to help, some additional information is going to be needed:
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
I also tried G1 with a grove connector in Port A of the atom S3, same result - worth noting that I get the same for the core s3. But works really well on the feather tft esp32-s3 from adafruit. However as you noted Im probably missing some configuration. I note that at least by the code in the module I believe its supposed to be supported on esp32 using a * wildcard path. I'm very new to this and my my experience is limited. Hope that helps. |
Beta Was this translation helpful? Give feedback.
-
Hello. I tried the examples/drivers/neopixel app with esp32/m5atom_s3 pin 6. neopixels-m5atom_s3.mp4 |
Beta Was this translation helpful? Give feedback.
-
Ja, it works very well when you import the lib from manifest.json. 0__o such a silly thing to overlook. Thanks @mkellner |
Beta Was this translation helpful? Give feedback.
-
I asked chatgpt a similar question and its response was:
Which I feel must be nonsense right, surely these boards are using the same chip. Why would one not write the lib for all boards as these neopixel strips are external hardware devices that you connect via pins. It makes no sense to only support boards that have an on board neopixel.
Beta Was this translation helpful? Give feedback.
All reactions