Implement use_global_block_protection_lock for write-enabling flash. #10249
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
Fix mis-placed conditional in circuitpy_mpconfig.h.
This was
linked to
issues
Apr 14, 2025
This was referenced Apr 14, 2025
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.
For most flash memory parts, the sector protection mechanism can be disabled by clearing the part's status register. The Microchip SST26VFxxxB parts do not use status register bits to control sector protection. Instead, they require issue of a global block protection unlock (0x98) to disable sector protection. This PR does the following:
use_global_protection_lockto indicate that the flash part requires use of the global block protection unlock command to write-enable the part.Fixes issues #10172 and #8047.