Add clock_configure_mhz function #2244
Open
+45
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
As per new code in #2225 we should catch cases where the divider between 1 and 2. |
kilograham
reviewed
Feb 7, 2025
I guess that means you can't overclock the Pico to 66 GHz? 🤣 |
|
See also #2255 |
Trades off accuracy (only gets to +/- 1MHz) for reduced code size as it doesn't need 64 bit division
will-v-pi
force-pushed
the
clock-configure-mhz
branch
from
ca9e63e to
6728e7e
Compare
Fixup for dividers 1.0-2.0 on RP2040 Improve docs
That's better than the normal clock_configure, which only lets you overclock to 4.3GHz 🤣 |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a
clock_configure_mhzfunction, which trades off accuracy compared toclock_configure(only gets to +/- 1MHz) for reduced code size as it doesn't need 64 bit division.It takes the source and target frequencies in MHz as 16-bit numbers, to ensure they fit within the 32-bit division.
This is useful for example if you want to calibrate the ROSC using an XOSC and then run off the ROSC, in which case you don't need a very accurate frequency as the ROSC frequency isn't accurate.