Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork213
Change the FMC frequency source to HCLK#995
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Change the FMC frequency source to HCLK, freeing up PLL2 for other uses. On Portenta, the frequency will be same. On giga it will be higher but still within spec, and I timings should get recalculated based on MICROPY_HW_SDRAM_FREQUENCY.
CLAassistant commentedNov 10, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Had to do a small change, should be in a final form now though. |
Applied this PR to my GIGA and ran its SDRAM intensive workload for 90mins or so. Nil impact. I will continue running with these changes and report any issues |
That's great to hear!! From my testing I was now able to set PLL2 to any frequency while using ram, which is great as I can now use it to have ADCs run as I want them to. (Though this will be useful for anyone who wants to use PLL2 at different frequencies) Speed wise with transfers couldn't see any decrease. |
Uh oh!
There was an error while loading.Please reload this page.
Change the FMC frequency source to HCLK, freeing up PLL2 for other uses. On Portenta, the frequency will be same. On giga it will be higher but still within spec, and timings should get recalculated based on MICROPY_HW_SDRAM_FREQUENCY.