Skip to content

Conversation

@MCUdude
Copy link
Contributor

@MCUdude MCUdude commented Jan 31, 2020

The system clock is now running at 96 MHz (and not 100 MHz) to keep compatibility with USB, which requires a 48 MHz clock. The expected external crystal/clock frequency can now be redefined at compile time.

System clock is now running at 96 MHz (and not 100 MHz) to keep compatibility with USB, that requires a 48 MHz clock. The expected external crystal/clock frequency can now be redefined at compile time.
@fpistm fpistm self-requested a review February 3, 2020 07:19
@fpistm fpistm added enhancement New feature or request fix 🩹 Bug fix labels Feb 3, 2020
@fpistm fpistm added this to the 1.9.0 milestone Feb 3, 2020
@fpistm fpistm merged commit 6e76ffa into stm32duino:master Feb 3, 2020
@fpistm
Copy link
Member

fpistm commented Feb 3, 2020

@MCUdude
Thanks, note that you changed only the F411Rx not the F411Cx as mentioned in your OP.

@MCUdude MCUdude changed the title Change clock setup for Generic F411's Change clock setup for Generic F411Rx Feb 3, 2020
@MCUdude
Copy link
Contributor Author

MCUdude commented Feb 3, 2020

Thanks, note that you changed only the F411Rx, not the F411Cx as mentioned in your OP.

Sorry about this. I've been struggling to get Git todo what I want. Will add a PR for the F411Cx's soon.

@fpistm
Copy link
Member

fpistm commented Feb 3, 2020

Sorry about this. I've been struggling to get Git todo what I want. Will add a PR for the F411Cx's soon.

No worry. 😉
I've made it in #905

@MCUdude
Copy link
Contributor Author

MCUdude commented Feb 3, 2020

Great! I'll apply the appropriate changes to #877!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request fix 🩹 Bug fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants