Crate embedded_sdmmc

source ·
Expand description

§embedded-sdmmc

An SD/MMC Library written in Embedded Rust

This crate is intended to allow you to read/write files on a FAT formatted SD card on your Rust Embedded device, as easily as using the SdFat Arduino library. It is written in pure-Rust, is #![no_std] and does not use alloc or collections to keep the memory footprint low. In the first instance it is designed for readability and simplicity over performance.

§Using the crate

You will need something that implements the BlockDevice trait, which can read and write the 512-byte blocks (or sectors) from your card. If you were to implement this over USB Mass Storage, there’s no reason this crate couldn’t work with a USB Thumb Drive, but we only supply a BlockDevice suitable for reading SD and SDHC cards over SPI.

use embedded_sdmmc::{Error, Mode, SdCard, SdCardError, TimeSource, VolumeIdx, VolumeManager};

fn example<S, D, T>(spi: S, delay: D, ts: T) -> Result<(), Error<SdCardError>>
where
    S: embedded_hal::spi::SpiDevice,
    D: embedded_hal::delay::DelayNs,
    T: TimeSource,
{
    let sdcard = SdCard::new(spi, delay);
    println!("Card size is {} bytes", sdcard.num_bytes()?);
    let mut volume_mgr = VolumeManager::new(sdcard, ts);
    let mut volume0 = volume_mgr.open_volume(VolumeIdx(0))?;
    println!("Volume 0: {:?}", volume0);
    let mut root_dir = volume0.open_root_dir()?;
    let mut my_file = root_dir.open_file_in_dir("MY_FILE.TXT", Mode::ReadOnly)?;
    while !my_file.is_eof() {
        let mut buffer = [0u8; 32];
        let num_read = my_file.read(&mut buffer)?;
        for b in &buffer[0..num_read] {
            print!("{}", *b as char);
        }
    }
    Ok(())
}

§Features

  • log: Enabled by default. Generates log messages using the log crate.
  • defmt-log: By turning off the default features and enabling the defmt-log feature you can configure this crate to log messages over defmt instead.

You cannot enable both the log feature and the defmt-log feature.

Modules§

  • Traits and types for working with Block Devices.
  • FAT16/FAT32 file system implementation
  • Generic File System structures
  • Implements the BlockDevice trait for an SD/MMC Protocol over SPI.

Structs§

  • Indicates whether a directory entry is read-only, a directory, a volume label, etc.
  • A standard 512 byte block (also known as a sector).
  • The a number of blocks (or sectors).
  • The linear numeric address of a block (or sector).
  • Identifies a cluster on disk.
  • A directory entry, which tells you about other files and directories.
  • A handle for an open directory on disk, which closes on drop.
  • Identifies a FAT16 or FAT32 Volume on the disk.
  • A handle for an open file on disk, which closes on drop.
  • A handle for an open directory on disk.
  • A handle for an open file on disk.
  • A partition with a filesystem within it.
  • Driver for an SD Card on an SPI bus.
  • An MS-DOS 8.3 filename. 7-bit ASCII only. All lower-case is converted to upper-case by default.
  • A Gregorian Calendar date/time, in the local time zone.
  • An open volume on disk, which closes on drop.
  • A number which identifies a volume (or partition) on a disk.
  • Wraps a block device and gives access to the FAT-formatted volumes within it.

Enums§

  • All the ways the functions in this crate can fail.
  • Various filename related errors that can occur.
  • The different ways we can open a file.
  • The possible errors this crate can generate.
  • This enum holds the data for the various different types of filesystems we support.

Constants§

Traits§

  • A block device - a device which can read and write blocks (or sectors). Only supports devices which are <= 2 TiB in size.
  • Things that impl this can tell you the current time.