-
Notifications
You must be signed in to change notification settings - Fork 41
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
Unable to change I2S_DEVICE from 0 to 1 #21
Comments
Thanks, this code comes from Yves, I'll check with him. |
Thanks, this is the last item before I'm fully able to switch over from arduino-esp32 to a full esp-idf environment. Let me know if I can help at all or share my audio codec configuration. EDIT: In theory, running an audio codec on i2s bus 0 alongside fastled running on bus 1 should be possible, right? |
Hi @bbulkow, just wondering if you ever heard back from Yves? Would this issue be better suited on one of his github repos? Let me know if I can help at all -- thanks. |
+1 on this one. I think there's gotta be something in |
Left a comment on FastLED#1165 as well, but it looks like this may just be a limitation of I2S1: in the technical reference manual--page 303, section 12.1, note 1: "... (note that I2S1 does not support 24-bit width)." Bummer! |
Hi @bbulkow, thanks again for this port and for the quality of maintenance. I've found it a breeze to work with so far and the readme is above and beyond.
I'm using this port in a project that uses the SGTL5000 audio codec on I2S bus 0 (which this port uses by default). BT audio stream comes in and is handled by I2S bus 0, pumped through a filter bank for audio analysis, and sent to the SGTL5000 using GPIO 0 for main clock.
I see that you should be able to change the default I2S bus in platforms/esp/32/clockless_i2s_esp32.h line 127, but when I set this to 1, nothing shows on the WS2811 strip I'm using. I understand i2s at a high level, but I'm not sure how to debug this, nor do I have access to a scope.
Is there something I'm missing here about which pins are usable with each i2s bus? I ask because I know i2s bus 0 must use GPIO 0 for its main clock, so maybe I'm just using the wrong pins? (I was running the included sketch on pin 13)
Steps to reproduce:
idf.py menuconfig
, and saveidf.py flash monitor
and ensure includedblinkWithFx_test
fxn renders animations as expected#define I2S_DEVICE 1
to very top of main.cppidf.py flash monitor
again and observe that none of the animations are displayedIt would be great to have the flexibility to run FastLED using i2s bus 1, and all audio on i2s bus 0. That being said, is there anything I should watch out for here? Theoretically I should be able to do this, right? I remember earlier this summer when I was using this port and its RMT interface, outputting LED data completely killed my audio. It was all scrambled as if the RMT was interrupting the main clock or something. But it was way beyond my experience level and I didn't feel opening an issue was necessary. But now that the i2s interface has been ironed out in this port, I thought maybe this is again a good time to see if this port plays well with my audio pipeline. Happy to share code samples, too. Thanks!
Versions:
The text was updated successfully, but these errors were encountered: