-
Notifications
You must be signed in to change notification settings - Fork 1.6k
i2s transmit (GIT8266O-747) #1169
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
Comments
I found it because I found no errors on the initial runs, but no data/clock coming out any gpio.
This will throw an error in a log or on screen when monitoring :
That would at least send out some notification as to where to look.
Hope this helps. Thanks for all your efforts! |
Too long time for this issue .... |
ESP8266_RTOS_SDK/components/esp8266/driver/i2s.c
Line 750 in 83517ba
When I tried the example code for i2s, the esp8266 would hang. After much gnashing of teeth, I finally found the culprit.
In the subroutine, esp_err_t i2s_write(), the line :
if (xQueueReceive(p_i2s_obj[i2s_num]->tx->queue, &p_i2s_obj[i2s_num]->tx->curr_ptr, ticks_to_wait) == pdFALSE) {
should be :
if (xQueueSend(p_i2s_obj[i2s_num]->tx->queue, &p_i2s_obj[i2s_num]->tx->curr_ptr, ticks_to_wait) == pdFALSE) {
The text was updated successfully, but these errors were encountered: