embedded-sdmmc-rs
embedded-sdmmc-rs copied to clipboard
A SD/MMC library with FAT16/FAT32 support, suitable for Embedded Rust systems
Looked at the init sequence and saw `0xFF` issued before `CMD0`, this [PR](https://github.com/rust-embedded-community/embedded-sdmmc-rs/pull/32) fixes the issue for me. Thanks!
This PR attempts to fix closing `Files` and `Directories`. The working principle is that each new `File` and `Directory` is assigned a unique `SearchId`. To close/delete them, instead of looking...
I've found an issue when trying to close files and open them again. Basically what ends up happening is that upon opening the file, the [`starting_cluster` of the File initialized...
Looking at #32 and #33, at least some cards get stuck in `TimeoutWaitNotBusy` when trying to initialize them. #32 provides a fix, however it seems to break other cards' init...
The current `BlockSpi` API makes it quite difficult to pass ownership around because it borrows the underlying `SdMmcSpi`. This is especially unergonomic e.g. in RTIC, where a `Controller` could be...
Currently SdMmcSpi::acquire returns a BlockSpi object which contains a mutable reference to the SdMmcSpi. This is a construct that is very hard to work with. I'm reading parts of a...
Commit https://github.com/rust-embedded-community/embedded-sdmmc-rs/commit/566f2023653dace195a43b05a6429f47e6be8a50 added two const generic parameters `MAX_DIRS` and `MAX_FILES` to `Controller`. Those parameters have default values equal to the values used before, and the new docs say: "By default...
Currently, `BlockDevice::read` and `BlockDevice::write` (and practically all functions in `SdMmcSpi` and `BlockSpi`) receive `&self`. Why is this done? In my opinion, they should receive `&mut self`, so that responsibility of...
I am currently experimenting with the nRF52 and using the [embassy](https://embassy.dev/embassy/dev/index.html) project. I intend to use an SD Card in the project. However, this library does not appear to support...