-
Notifications
You must be signed in to change notification settings - Fork 7.3k
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
adc_continuous_read returning ESP_ERR_TIMEOUT (IDFGH-10857) #12053
Comments
I re-checked the code and did some testings, and found out it's because the dma interrupt stops generating during heavy load. I created a PR, it works fine for me, atleat now. Could you help to review it? |
Hello, I have the same problem, what is the cause of this problem? |
A PR with similar changes have been accepted before. Sorry for the late reply.
You may upgrade to use a newer version. |
You did not ever read the PR, right? This PR is based on the one you referenced. Issue can still be reproduced by applying below patch to idf v5.0.4:
nvs_1 is something like this in partiton.csv: |
If the PR was merged then why do I still have this problem? I have esp-idf v5.1.2. Any ideas why this is happening. Thanks in advance |
Answers checklist.
IDF version.
v5.0.3
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
esp32-s3-wroom-1
Power Supply used.
External 5V
What is the expected behavior?
adc_continuous_read is quite easy (80% possibility) to return ESP_ERR_TIMEOUT
What is the actual behavior?
adc_continuous_read is quite easy (80% possibility) to always return ESP_ERR_TIMEOUT (conv_frame_size set to 512), after power on reset, and s_adc_dma_intr is then never being called.
This occurs when running v5.0.3, but never occurs on v5.0.2.
I checked the history, seems this bug was introduced by commit 5da5e18 and d8ee45c.
Wish you guys can confirm this.
I tried below patch, and seems can fix:
Steps to reproduce.
running continuous_read_main.c
Debug Logs.
No response
More Information.
No response
The text was updated successfully, but these errors were encountered: