-
Notifications
You must be signed in to change notification settings - Fork 119
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
Implement different reset strategies based on host OS and communication method #349
Comments
I had implemented this, but it doesn't actually seem to solve any problems. Given the additional code and bump in MSRV required, I'm not sure this is even worth implementing at this point. |
This reset strategy seems to be added to EspTool to fix espressif/esptool#712. It looks like it all about the timing of setting the RTS and DTR pins which appears to differ depending on the combination of OS, USB ports and USB-Serial converter chip. I'm getting the impression it is (mostly?) and issue with usb 3.x ports and/or usb-c serial converters, so it might well become more common over time. I think I can come up with a fix which at least doesn't need the MSRV bump, and might end up being a bit more compact. I'll create a pull request once I've tested and cleaned it. |
Adds a reset approach for *nix called UnixTight reset by Espressif to avoid timing issues with USB-serial connections on Linux and macOS. See espressif/esptool#712 for details.
Add a #[cfg(unix)] I forgot (so it actually builds on windows).
I created a pull request: #387 |
Keep comments consistent.
Fix #[cfg(unix)] (and windows build).
Can anyone affected by this issue check if #487 fixes the issue?
|
This is a newer feature in
esptool
, see: https://github.com/espressif/esptool/blob/cc062082fb8ba0ca40cdd32e14fc673562b7b38f/esptool/reset.pyThe text was updated successfully, but these errors were encountered: