We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
The device id for stm32l0 is pointed at 0x1FF8_0050 in this crate. This doesn't match the l0x0 version, as it is 0x1FF8_0050 + offset 0x14 here. See page 722 of the reference manual: https://www.st.com/resource/en/reference_manual/dm00443854-ultralowpower-stm32l0x0-advanced-armbased-32bit-mcus-stmicroelectronics.pdf
I haven't checked if the other l0 versions are affected the same, I just verified the _0050 offset to be not unique in my test hardware.
The text was updated successfully, but these errors were encountered:
Thank you for the information! Apparently, 0x1FF8_0050 address is correct, but device ID is stored in non-contiguous registers (offsets 0, 4, 0x14).
Sorry, something went wrong.
I found the same problem in L0 and L1 families. Seems like F0, F1, F3, F4, G0 and L4 are not affected.
No branches or pull requests
Hi,
The device id for stm32l0 is pointed at 0x1FF8_0050 in this crate. This doesn't match the l0x0 version, as it is 0x1FF8_0050 + offset 0x14 here.
See page 722 of the reference manual: https://www.st.com/resource/en/reference_manual/dm00443854-ultralowpower-stm32l0x0-advanced-armbased-32bit-mcus-stmicroelectronics.pdf
I haven't checked if the other l0 versions are affected the same, I just verified the _0050 offset to be not unique in my test hardware.
The text was updated successfully, but these errors were encountered: