-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[STM32F446]: Wrong chip definition #1228
Milestone
Comments
maybe dupe of #1156 |
It should be ok to leave this open, even if it's a duplicate. |
Nightwalker-87
changed the title
[STM32 device name]: STM32F446 wrong chip definition
[STM32F446]: Wrong chip definition
Feb 27, 2022
6 tasks
Nightwalker-87
added
status/resolved
status/resolved-verified
status/no-bug
and removed
needs/investigation
labels
Dec 29, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Thank you for giving feedback to the stlink project.
NOTE: In order to offer sufficient and the best possible support, please read /CONTRIBUTING.md and follow the given instructions before submitting a ticket.
Bug reports and/or feature requests will be deleted, if they violate our contribution guidelines and if no issue-template is used! Thank you for your support.
In order to allow developers to isolate and target your respective issue, please take some time to select the check boxes below and fill out each of the following items appropriate to your specific problem.
st-info
,st-flash
,st-trace
,st-util
)Further we kindly ask you to describe the detected problem as detailed as possible and to add debug output if available, by using the following template:
Commandline output:
Expected/description:
Introduced in this commit e62b9e1 the option byte area has been changed. This leads to a read-out of 0x40023c14 which is somwhere in the AHB1 area.
Please change back option area to 0x1FFFC000 with a size of 16bytes, as shown in the datasheet and the attached images.
The text was updated successfully, but these errors were encountered: