1
0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
RIOT/tests/pkg/fatfs_vfs
Gunar Schorcht c93f0a70d4 tests/pkg/fatfs_vfs: replace external mtd0 declaration
Since the `extern mtd_dev_t *` declarations were removed from board definitions, `mtd_dev_get` has to be used instead.
2023-12-07 15:32:49 +01:00
..
tests-with-config tests: move pkg_ application to tests/pkg subdirectory 2023-05-06 07:55:01 +02:00
create_fat_image_file.sh tests: move pkg_ application to tests/pkg subdirectory 2023-05-06 07:55:01 +02:00
main.c tests/pkg/fatfs_vfs: replace external mtd0 declaration 2023-12-07 15:32:49 +01:00
Makefile tests: move pkg_ application to tests/pkg subdirectory 2023-05-06 07:55:01 +02:00
Makefile.ci examples and tests: add atmega8 to relevent Makefile.ci 2023-07-11 21:22:02 +02:00
README.md tests: move pkg_ application to tests/pkg subdirectory 2023-05-06 07:55:01 +02:00
riot_fatfs_disk.tar.gz tests: move pkg_ application to tests/pkg subdirectory 2023-05-06 07:55:01 +02:00

Using FatFs (with VFS) 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.

make flash test-with-config

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. To use the automated test in pkg_fatfs_vfs you need to copy the generated image to your storage device (e.g. your SD-card). To copy the image onto the card you can use something like make image && dd if=bin/riot_fatfs_disk.img of=/dev/<your_sdcard>. After that you can connect the card to your RIOT device and check the test output via terminal.

make flash test-with-config