preliminary support for ESP32 (e.g. LOLIN32 Lite) #47
Conversation
This file contains 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.
NodeMCU for ESP32 (dev-esp32) lacks
node.info()which is used to determine NodeMCU firmware on the ESP device, this patch stills keeps probingnode.info(), if it fails it tries to probenode.chipid()and if the response is hex with prefix '0x' then it's very likely an ESP32, and then I set the data as far I know (no flashID or flashsize etc).Result is,
nodemcu-toolrecognizes the ESP32 device anduploadworks. I added a new field 'arch' which contains 'esp8266' or 'esp32'.