Add 'cargo espflash' subcommand - #1
Merged
Merged
Conversation
icewind1991
approved these changes
Sep 9, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This creates a cargo subcommand which compiles and flashes applications to ESP-based devices in a single command. It's still pretty rough around the edges, but has worked so far in my limited testing.
Usage:
$ cargo espflash [--ram] [--release] [--example EXAMPLE] --chip {esp32,esp8266} <serial>Currently it requires xargo for cross-compilation, and I have only tested it on the ESP8266. I will do some more testing, but I just wanted to get some more eyes on it as well. Let me know if there's anything you'd like to see changed, or if you have any questions about anything.