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
stm32f405 has sdioio module as sdio #5344
Comments
Good catch @jerryneedell. This change was introduced in 9002f35, it is probably a mistake. |
Ah -- good -- I've been trying to find another port that has it enabled to compare, but have not found one yet. IT is in the "common-hal" for atmel-samd but it appears to be disabled in the build. |
Is it just this line
missing the "io" in the MP_QSTR_sdio |
Yup, that is the only line that needs to be changed. - MP_REGISTER_MODULE(MP_QSTR_sdio, sdioio_module, CIRCUITPY_SDIOIO);
+ MP_REGISTER_MODULE(MP_QSTR_sdioio, sdioio_module, CIRCUITPY_SDIOIO); |
I can do a PR later today, but it may be a lot quicker for someone else to do it. |
I just did a quick PR. |
Thanks -- it works! |
Call MICROPY_EVENT_POLL_HOOK even on very short delays so that busy loops that call sleep_ms still yield to events and other threads. See related issue #5344.
So that other threads get a chance to run when taskYIELD() is called. See issue #5344. Signed-off-by: Damien George <damien@micropython.org>
This helps the OS switch to and give other threads processing time during the sleep. It also ensures that pending events are handled, even when sleeping for 0ms. Fixes issue #5344. Signed-off-by: Damien George <damien@micropython.org>
Was the name of sdioio changed to sdio recently? the docs still refer to it as sdioio but in the rc.1 build for the STM32F405, it shows up (and works) as sdio instead of sdioio.
Is this correct?
this example works on the STM32F405
The text was updated successfully, but these errors were encountered: