Implement the utop module #822
Open
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
Signed-off-by: Daniël van de Giessen <[email protected]>
Signed-off-by: Daniël van de Giessen <[email protected]>
DvdGiessen
force-pushed
the
utop_esp32
branch
from
065316c
to
41c8127
Compare
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.
Implements a new module,
utop, as suggested in micropython/micropython#12732 (comment).Currently only works on the
esp32port, and requires micropython/micropython#12732.An animated GIF to demonstrate what the output looks like:
Opted to give it a generic name instead of ESP32-specific, as there was mention of other platforms also having options to retrieve runtime performance data, which might be nice to support at a later time.
Compared to the version posted in that
esp32MR (here) this version is a few lines longer to make it a bit easier to read and expand later.First commit implements the functionality as demo'd in the other MR. The second commit adds two lines of information about the current state of the ESP-IDF heap, as an example of how we could expand this later to be a more useful development utility.