Add PLL to control clocks #607
Draft
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
Signed-off-by: Robert Szczepanski <[email protected]>
Signed-off-by: Robert Szczepanski <[email protected]>
robertszczepanski
force-pushed
the
33342-dynamic-clock-control-pll
branch
from
f095fd1 to
dc81db2
Compare
Signed-off-by: Robert Szczepanski <[email protected]>
Signed-off-by: Robert Szczepanski <[email protected]>
Signed-off-by: Robert Szczepanski <[email protected]>
robertszczepanski
force-pushed
the
33342-dynamic-clock-control-pll
branch
from
dc81db2 to
626b4bb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 introduces PLL into HPS design with an additional option to enable/disable output clocks. It makes power consumption much higher. Initial tests with multimeter result in 70mW when CFU is disabled. It's ~30mW higher than version with DCC only presented in #597.
CI will fail because
nextpnr-nexusrequires a small fix to work. There is not needed tile generated into output.fasm. If you want to test it locally, build it as usual,prjoxidewill fail to generate a bitstream with an error:thread 'main' panicked at 'No enum named PLL_LLC.MODE in tilegroup R28C1_PLL_LLC.Then go to generated
.fasmand just search forPLL_LLC.MODEand remove a line that contains it. Run againprjoxideand it should generate a bitstream just fine: