-
Notifications
You must be signed in to change notification settings - Fork 726
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
Why is the reset pin driven high instead of left floating when unasserted? #474
Comments
Makes sense, didn't think of it and it never came up as a problem... |
This is what I'm using currently: https://github.com/GMMan/esp-link/tree/v3.0.14-floating-reset My module is 4MB:512/512. |
that's exactly what I wanted to do :) (change reset pin to input when not used) |
Should I rebase it on the master branch? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I recently flashed esp-link to a D1 Mini clone and wired it into a consumer product that has an AllWinner R16 SoC and AXP233 PMIC. Everything worked fine out of the box except I had to issue a uC reset to get the SoC to actually enter FEL mode after setting it up to do so. I found that esp-link driving the RESET/PWROK line high was interfering with the SoC's watchdog reset. I changed all instances where esp-link drives the reset pin high to disabling output so it floats, and now the SoC is entering FEL mode as expected.
My question is why has esp-link been designed to drive reset high while idle? If a uC requires a specific powerup sequence, this would interfere with that. If the uC doesn't require a powerup sequence, the reset pin would have been pulled high on the board the uC is attached to anyway.
The text was updated successfully, but these errors were encountered: