Skip to content

Add support for write unprotection - #96

Merged
florisla merged 1 commit into
florisla:masterfrom
ademuri:write-protect
Mar 5, 2026
Merged

florisla merged 1 commit into
florisla:masterfrom
ademuri:write-protect

Conversation

@ademuri

@ademuri ademuri commented Mar 4, 2026

Copy link
Copy Markdown

No description provided.

@florisla florisla left a comment •

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a very welcome addition.

I think the WRITE_PROTECT_SECTOR_SIZE info should be moved.

Let me know if you can do that or if you prefer me to have a go at it.

Comment thread src/stm32loader/devices.py Outdated
Comment thread src/stm32loader/devices.py Outdated
@florisla florisla added feature approved Will be included in the next release needs-work labels Mar 4, 2026
@ademuri

ademuri commented Mar 5, 2026

Copy link
Copy Markdown
Author

Sounds good, I'll make the suggested changes. However, this is more complicated than I initially thought. Some families have mixed sector sizes, and some don't use sectors at all. So, I changed this pull request to only implement write unprotection. I'm going to work on implementing write protection in a separate change.

@ademuri
ademuri marked this pull request as ready for review March 5, 2026 04:16
@florisla florisla changed the title Add support for write protection and unprotection Add support for write unprotection Mar 5, 2026
@florisla

florisla commented Mar 5, 2026

Copy link
Copy Markdown
Owner

Note: I would welcome write-protection even it was only implemented for certain families or devices.

@florisla
florisla merged commit 2409475 into florisla:master Mar 5, 2026
20 checks passed
@florisla florisla added this to the v1.0.0 milestone Mar 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Will be included in the next release feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants