Bug - I2S communication disrupted by arbitrary function call following I2C initialization. #14009
Replies: 1 comment
-
Thanks @ajbradburn -- converting this to an issue (#14050), we'll need to try and repro it and investigate. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Bug - I2S communication disrupted by arbitrary function call following I2C initialization.
I have discovered that I2S communication is somehow disrupted by initializing I2C, and then calling any function.
A work-around is to do something as simple a call ‘print’ after the arbitrary function call.
Here is an example of a script that demonstrates the bug:
I have tested this with blocking, and non blocking I2S implementation with the same result.
I discovered this while trying to operate a PCA9685 and a Max98357 on an ESP32-S3-WROOM-1 using Micropython v1.22.2 (2024-02-22).
Files can be found here:
https://github.com/ajbradburn/ESP32-PuppetRemote/blob/main/code/sound_test.py
https://github.com/ajbradburn/ESP32-PuppetRemote/blob/main/code/sound_test2.py
https://github.com/ajbradburn/ESP32-PuppetRemote/blob/main/code/snake.wav
Beta Was this translation helpful? Give feedback.
All reactions