Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[STM32L471]: Cannot set option byte #1128

Closed
seeseemelk opened this issue Apr 15, 2021 · 3 comments · Fixed by #1102
Closed

[STM32L471]: Cannot set option byte #1128

seeseemelk opened this issue Apr 15, 2021 · 3 comments · Fixed by #1102

Comments

@seeseemelk
Copy link
Contributor

When attempting to unset the BFB2 bit from FLASH_OPTCR register, I get the following error:

$ st-flash --area=option read
st-flash 1.6.1-109-g781557d
2021-04-15T15:00:02 INFO common.c: L4xx: 96 KiB SRAM, 512 KiB flash in at least 2 KiB pages.
fffff8aa
$ st-flash --area=option write 0xFFEFF8AA
st-flash 1.6.1-109-g781557d
2021-04-15T15:00:13 INFO common.c: L4xx: 96 KiB SRAM, 512 KiB flash in at least 2 KiB pages.
attempting to set option byte to 0, abort.

It seems that the st-flash utility is not quite correctly parsing its command line arguments, preventing the modification of special registers.

@seeseemelk
Copy link
Contributor Author

This issue has been fixed by eff18d8, but as of writing this isn't yet in a released version which is why I encountered it.

@Nightwalker-87
Copy link
Member

@seeseemelk: Please follow #906 before opening new tickets in future.

@Nightwalker-87 Nightwalker-87 added this to the v1.7.0 milestone Apr 15, 2021
@Nightwalker-87 Nightwalker-87 linked a pull request Apr 15, 2021 that will close this issue
@Nightwalker-87 Nightwalker-87 self-assigned this Apr 15, 2021
@stlink-org stlink-org locked as resolved and limited conversation to collaborators Apr 15, 2021
@Nightwalker-87
Copy link
Member

Fixed by #1102.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants