FatFs

FatFs is designed to be a Filesystem Layer that is agnostic to the platform and storage media it is used with. This is achieved by providing a media access interface that is used to communicate with the storage device control module which is provided by the implementer.{{cite web |url=https://www.st.com/resource/en/user_manual/um1721-developing-applications-on-stm32cube-with-fatfs-stmicroelectronics.pdf |title=Developing applications on STM32Cube with FatFs |publisher=STMicroelectronics |access-date=22 June 2022}} This means that FatFs can work with any physical device such as an SD card or a hard disk on any platform that can run plain C code if the implementer provides a control module interface.

File:FatFs Architecture.jpg

FatFs library architecture logically separates the abstractions of the user app and the platform-dependent code. The user application and the low level disk I/O layer (driver) must be added by the implementer.{{rp|11}} Also, the architecture of the library implies that the system can have several storage devices with different drivers and the library can work in a multi-threaded operating system. At the application level it is hidden which physical media is used.

In the minimum implementation, the driver layer must support at least these 3 interfaces:{{rp|14}}

• disk_status — return block device status (not initialized, missing, protected, ready)
• disk_initialize — initialize the physical disk
• disk_read — read block from physical disk

This level of abstraction allows implementers to write an application once, and then port it on different platforms, changing only the implementation of the driver.{{Cite book

|first=Jacob

|last=Beningo

|url=https://books.google.com/books?id=wzVCDwAAQBAJ&pg=PA255

|title=Reusable Firmware Development; A Practical Approach to APIs, HALs and Drivers

|date=2017

|page=255

|isbn=9781484232972

|oclc=1484232976

}}

FatFs has its own minimalistic license {{Cite web|title=FatFs License|url=http://elm-chan.org/fsw/ff/doc/appnote.html#license|access-date=2022-06-17|website=elm-chan.org}} similar to the BSD license. It allows usage in commercial products without disclosing the source code.{{rp|12}} The only condition is to keep the copyright notice in case of redistribution of the source code. The conditions of FatFs license do not cover any redistributions in binary form, such as embedded code and hex files.

• Arduino (STM32Duino) — port of Arduino platform for STM32 MCU's{{Cite web|title=FatFs Library description on Arduino platform documentation|url=https://www.arduino.cc/reference/en/libraries/fatfs/|access-date=2022-06-17|website=Arduino Official Website}}
• ChibiOS/RT — open-source real-time operating system (RTOS) for microcontrollers
• Flipper Zero — open source portable multi-tool device
• Marlin (firmware) — open source firmware for 3D printers and CNC machines
• ESP-IDF — official IoT Development Framework for the ESP32 series SoC's{{Cite web |title=FAT Filesystem Support - ESP32 - — ESP-IDF Programming Guide latest documentation |url=https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/storage/fatfs.html |access-date=2022-06-27 |website=docs.espressif.com}}
• Prusa Mini — open-source firmware for low cost 3D printer
• RT-Thread — open-source real-time operating system for embedded systems{{Cite web|title=FatFs File System Configuration in rt-thread operating system|url=https://www.rt-thread.io/document/site/programming-manual/filesystem/filesystem/#elm-fatfs-file-system-configuration-option|access-date=2022-06-26|website=www.rt-thread.io}}
• Zephyr — real-time operating system for embedded systems supporting multiple architectures
• ErlendOS — an open source minimal UNIX-like operating system for embedded systems
• EZ-Flash Omega - Family of flashcarts for the Nintendo Game Boy Advance.

{{Reflist}}

Category:Computer libraries

Category:Microcontroller software