Spi memory lock #1415
Open
Spi memory lock #1415
+722
−32
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
Beerosagos
force-pushed
the
spi-memory-lock
branch
2 times, most recently
from
28dc7c4 to
950a314
Compare
Beerosagos
commented
Apr 17, 2025
| // set the top/bottom protection bit. | ||
| // This is an OTP bit,so the write will have an effect | ||
| // only the first time. | ||
| reg[1] = reg[1] | CR1_TB_BIT_BOTTOM; |
There was a problem hiding this comment.
Not sure if it is ok to add this here, or if we want to do it inside the driver during the init function.
Beerosagos
force-pushed
the
spi-memory-lock
branch
2 times, most recently
from
1ba0527 to
050dd3e
Compare
Beerosagos
force-pushed
the
spi-memory-lock
branch
2 times, most recently
from
c1a7ab8 to
49badb6
Compare
This adds api calls to lock/unlock and write a protected area of the memory.
Beerosagos
force-pushed
the
spi-memory-lock
branch
from
49badb6 to
b29fa51
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.
This adds api calls to lock/unlock and write a protected area of the memory.
This PR includes a test function to be removed before merging