-
Notifications
You must be signed in to change notification settings - Fork 51
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SDIO and set_sys_clock_khz #81
Comments
It's on my list of things to do to make the SDIO clock rate configurable in the H/W config. It is currently hard coded in
so you would have to modify that directly.
The
Note that the PIO state machine effectively divides the clock rate by 4. When I get around to making the SDIO baud rate configurable in the H/W config., I should use a scheme like that used in the SDK's |
I am able to run reliably with system clock at 252000 and SDIO baud rate 5 MHz. |
Thanks Carl! |
(my background is software. I'm a newbie to most hardware stuff. Forgive my ignorance and if this seems strange or silly)
I'm trying to combine SDIO from your project and this: https://github.com/Wren6991/PicoDVI
I've been able to make my sd card work over SPI, and I can make SDIO work alone but as soon as I add this line:
set_sys_clock_khz(252000, true);
it quits working with error "A hard error occurred in the low level disk I/O"
My (limited) understanding is that 252000khz is related to the output DVI/TMDS clock.
via trial and error I've discovered that 206000khz works and seems to make both SDIO and DVI (or at least my monitor) happy.
so I'm curious: is there a tweak to the SDIO code that I can make which will make it work at 252mhz? i suspect that I'm pushing the DVI timing pretty far outside spec and I'd like to bump that back up to maybe make this work on less forgiving monitors.
The text was updated successfully, but these errors were encountered: