Out of date: This is not the most recent version of this page. Please see the most recent version
The block device API provides an interface for access to block-based storage. You can use a block device to back a full file system or write to it directly.
You can find the full C++ API here.
Here is an example that uses a block device:
Block device operations
A block device can perform three operations on a block in a device:
- Read a block from storage.
- Erase a block in storage.
- Program a block that has previously been erased.
Note: The state of an erased block is undefined. NOR flash devices typically set an erased block to all 0xff, but for some block devices such as the SD card, erase is a NOOP. If a deterministic value is required after an erase, the consumer of the block device must verify this.
Some storage technologies have different sized blocks for different operations. For example, NAND flash can be read and programmed in 256-byte pages, but must be erased in 4-kilobyte sectors.
Block devices indicate their block sizes through the
get_erase_size functions. The erase size must be a multiple of the program size, and the program size must be a multiple of the read size. Some devices may even have a read/program size of a single byte.
As a rule of thumb, you can use the erase size for applications that use a single block size (for example, the FAT file system).
Utility block devices
mbed OS contains several utility block devices to give you better control over the allocation of storage.
- With the slicing block device, you can partition storage into smaller block devices that you can use independentally.
- With the chaining block device, you can chain multiple block devices together and extend the usable amount of storage.
- mbed OS comes with support for storing partitions on disk with a Master Boot Record (MBR). The MBR block device provides this functionality and supports creating partitions at runtime or using preformatted partitions configured separately from outside the application.