mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2024-12-29 04:50:03 +01:00
28 lines
1.2 KiB
Markdown
28 lines
1.2 KiB
Markdown
Using FatFs on RIOT
|
|
=======================================
|
|
|
|
# native
|
|
|
|
To use this test on native you can either use a FAT-formatted image file or
|
|
directly use the mkfs command from the RIOT shell. Use `make image` to extract
|
|
a prepared image file that already contains a simple test.txt file. This is
|
|
only a convenience function to allow testing against a "default linux"
|
|
formatted fat volume without the need to call mount or other stuff that may
|
|
require super user privileges. Optionally `make compressed-image` can be used
|
|
to generate the compressed image that is in turn used by `make image`.
|
|
|
|
To tell RIOT where your image file is located you can use the define
|
|
`MTD_NATIVE_FILENAME`.
|
|
|
|
NOTE: You shouldn't leave the image mounted while you use it in RIOT, the
|
|
abstraction layer between FatFs and the image file mimics a dumb block device
|
|
(i.e. behaves much like the devices that are actually meant to be used with
|
|
FAT) That implies it doesn't show any modifications in RIOT that you perform on
|
|
your OS and the other way round. So always remember to mount/unmount correctly
|
|
or your FS will probably get damaged.
|
|
|
|
# Real Hardware
|
|
|
|
Currently the test defaults to sdcard_spi on real hardware. But generally any
|
|
device that supports the mtd-interface can be used with FatFs.
|