neopixel behaves oddly on esp32-s3-devkitm-1 #5679
Comments
Merged
dhalbert
pushed a commit
that referenced
this issue
Jan 20, 2022
This tweaks the RMT timing to better match the 1/3 and 2/3 of 800khz guideline for timing. It also ensures a delay of 300 microseconds with the line low before reset. Pin reset is now changed to the IDF default which pulls the pin up rather than CircuitPython's old behavior of floating the pin. Fixes #5679
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CircuitPython version
Code/REPL
# noneBehavior
The initial 3 flashes of the onboard neopixel work, but then after that the LED sometimes blinks random colors.
Description
No response
Additional information
This problem affects the 1 ESP32-S3-DevKitM-1 I have, but neither of the ESP32S3-DevKitC-1 (both with PSRAM) that I have.
The LED attachment is the same in both schematics, with no pull up/down to ensure the neopixel's input doesn't fluctuate. However, this seems to be typical of how neopixels are wired.
If the GPIO is placed in InputEnable mode (without pull up or down, i.e., just create a DigitalinOut object for the pin), it happens to stop the flickering. But since the neopixel pin is usually freed by the supervisor between color settings, it is normally placed in input disabled / output disabled / no pulls mode.
It's possible that this is just specific to the board and other boards are fine, however, I only had one board to test.
Affected module on the left:
PXL_20211207_192903939.mp4.2.mp4
The text was updated successfully, but these errors were encountered: