Skip to content
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

Auto-reset support for NodeMCU devkit as well as esprog,etc. #30

Merged
merged 1 commit into from
Apr 26, 2015
Merged

Auto-reset support for NodeMCU devkit as well as esprog,etc. #30

merged 1 commit into from
Apr 26, 2015

Conversation

projectgus
Copy link
Contributor

The NodeMCU dev-kit board has a similar auto-reset circuit to previous
ones (RTS drives reset, DTR drives GPIO0), but with a quirk - if both
RTS & DTR are asserted at once, neither nRESET nor GPIO0 are asserted.

This commit changes the reset order so RTS,DTR are asserted one at a
time instead of simultaneously. This should still work with the
traditional configuration as well.

This problem was mentioned in #26.

The NodeMCU dev-kit board has a similar auto-reset circuit to previous
ones (RTS drives reset, DTR drives GPIO0), but with a quirk - if both
RTS & DTR are asserted at once, neither nRESET nor GPIO0 are asserted.

This commit changes the reset order so RTS,DTR are asserted one at a
time instead of simultaneously. This should still work with the
traditional configuration as well.

This problem was mentioned in #26.
@themadinventor
Copy link
Collaborator

Great, thanks!

themadinventor added a commit that referenced this pull request Apr 26, 2015
Auto-reset support for NodeMCU devkit as well as esprog,etc.
@themadinventor themadinventor merged commit 6374ad4 into espressif:master Apr 26, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants