-
Notifications
You must be signed in to change notification settings - Fork 42
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
New version has GPIO5 connected to RST of A7670E #10
Comments
The module is reset with or without these lines of code. I think this may have to do with the fact that the RESET pin of A7670 is connected to GPIO 5 of ESP32 which is pulled up at boot. Then GPIO 5 goes to 0, and this is like a reset. Is there a way to remove connection between GPIO 5 and the RESET pin of A7670? Do you have a sample code where ESP32 goes from deep sleep to normal mode without resetting A7670 (A7670 is ON while ESP32 is in deep sleep)? This setup used to work great with the previous version of this board where GPIO 5 was not connected to the RESET pin of A7670. |
To confirm my claim above in my previous post, I pulled up externally GPIO 5, and there is no reset anymore. So, my question is: Is there any software or hardware way to disconnect GPIO 5 from the RESET pin of A7670? I need to resolve both the bounce issue, and I need this GPIO 5 to connect a sensor (I have run out of pins). Is there anything I can solder / desolder on that board to achieve that? Your previous version of the product did NOT use GPIO 5 and 12, and that was great! |
Thanks a lot for that info! However, I have several boards which are version 1.0 (2021-12-18) and not 1.1 (2022-2-28). Could you please confirm that the location of the resistor for GPIO 5 is the same for 1.0 as for 1.1? Thanks |
same |
I have a nasty problem with A7670E resetting each time ESP32 WROVER-E exits deep sleep. My program flow is the following:
Is there a way to avoid that? The previous version of this board did not have GPIO5 connected to A7670's RST.
The text was updated successfully, but these errors were encountered: