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

[feature] Support for STM32F4 option bytes #1062

Merged

Conversation

timothytylee
Copy link
Collaborator

Allow the option bytes to be read/written to STM32F4. Tested on a STM32F405.

@Ant-ON
Copy link
Collaborator

Ant-ON commented Oct 27, 2020

@timothytylee how view from the already written code, the STM32_XX_OPTION_BYTES_BASE constants use the physical address of option bytes. For STM32F4 it is 0x1FFFC000 (dm00031020, p. 88)

@timothytylee
Copy link
Collaborator Author

Yet in section 3.7.2 (pg92), it says to use FLASH_OPTCR register to program the user option bytes. I have checked that the RDP feature does indeed come into effect after changing the FLASH_OPTCR. The values read back from 0x1fffc000 appear to be some random bytes.

@Ant-ON
Copy link
Collaborator

Ant-ON commented Oct 28, 2020

@timothytylee You're right

@Nightwalker-87
Copy link
Member

@timothytylee Does this close any open issues?

@timothytylee
Copy link
Collaborator Author

@Nightwalker-87 this is a new feature. I do not think there are issues related to it.

@Nightwalker-87 Nightwalker-87 merged commit 1dff591 into stlink-org:develop Nov 11, 2020
@Nightwalker-87 Nightwalker-87 changed the title [feature] support STM32F4 option bytes [feature] Support for STM32F4 option bytes Nov 11, 2020
@stlink-org stlink-org locked as resolved and limited conversation to collaborators Dec 5, 2020
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 this pull request may close these issues.

3 participants