Repository navigation
Firmware page: how to put a native-USB board in download mode - #28
Merged
Merged
Conversation
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
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.
One text fix to the esptool write step on the firmware page.
Boards whose USB port goes straight to the chip (the LilyGO T-Embed S3, the native port of the ESP32-S3-Touch-LCD-7) need download mode before esptool can reach them. The step now says: hold BOOT, press and release RESET, then release BOOT, and that the port's COM number can change in download mode. Boards with a USB-serial bridge chip do not need this. The board data has no native-USB field, so it is one general sentence with those two boards named.
Targets the
firmware-page-stagedbranch, which is not served. Rendered locally: the sentence appears in the esptool steps for the T-Embed S3, no console errors.