eFuse write support #962
Open
eFuse write support #962
+2,182
−113
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
kyrias
force-pushed
the
efuse-write
branch
9 times, most recently
from
1a099f0 to
f54b621
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 pull requests add support for writing eFuses to all currently supported chips. From reading both the relevant TRMs and the
espefuseflashing process I believe that this should be correct for all of them, though I only have ESP32-S3 and ESP32-C3 devkits to test this out with. In particular I think it would be good if it could be explicitly tested on at least an ESP32 as well since its eFuse controller is structured completely differently from the rest, as well as ESP32-S2 just to be sure since it has rather different timing parameters from the rest.Since I only have a couple of devkits on hand that limits the number of tests that can be done for this feature, so I would appreciate a review and at least a tentative approval before I perform my final tests.