MicroPython Forum (Archive)

... but I'm worried it will be only a matter of time before the file system falls over again. Is there a way to tell if release='1.17.0' uses FAT or littleFS? Is there a stable upython out there that uses littleFS by default?

... filesystems : https://docs.micropython.org/en/latest/reference/filesystem.html Anyway, it seems the only filesystem available on STM32L432 is LittleFS v1 (probably due to memory constraints on that tiny board). Then, here's how I solved the problem : import os, pyb os.VfsLfs1.mkfs(pyb.Flash(start=0)) ...

... Multiple devices may share an SPI bus to form a single logical RAM. It is possible to use the RAM as a (huge) bytearray or to implement a littlefs or FAT filesystem on it. This may be mounted and used like flash or SD card devices. If used as an array, supports slice operations. The driver ...

This is an old thread and thus things have changed: to check for littlefs on recent micropython builds this works: def check_for_littlefs(): from flashbdev import bdev buf = bytearray(16) bdev.readblocks(0, buf) return buf[8:16] == b"littlefs" check_for_littlefs() ...

Thank you very much @mattyt for taking the time to provide these details. It is indeed very interesting to understand the pros and cons of LittleFS vs Fat. And also TinyUSB (I didn' know it) is a great project. What would we do without everyone from the Open Source who works for us! And as ...

... USB mass storage for example. MicroPython supports the concept of a virtual filesystem of which there are currently two implementations: FatFS and LittleFS. FatFS is the venerable Microsoft filesystem - it's not particularly robust but it is required for USB mass storage. LittleFS was designed ...

... store files on it. The question about minimum sizes only makes sense in the context of specific filesystems. FAT requires 512 byte sectors (IIRC). Littlefs can go down to 128 bytes, but I have only tested 512 bytes. In practice the number of sectors is set by the hardware device. As for your mention ...

... (which is 2MiB). - In ports/rp2/rp2_flash.c we define the rp2.Flash object using those two macros. - In ports/rp2/modules/_boot.py we construct a LittleFS filesystem using the entire rp2.Flash object. The flash object (a block device) provides an ioctl that returns the size, and the filesystem ...

... so even though these two different approaches feel different, they're really the same thing. ALso worth noting that on RP2040, MicroPython uses LittleFS which does automatic wear-levelling etc. Others have commented about using json, which I think is a good idea, but the other approach I've ...

... ESP32 access that filesystem to write a small file that can persist between reboots? I'm still learning, so a simple example would be helpful. A littlefs filesystem is automatically mounted when you load in the images on the download page. What I ended up doing, so I wouldn't lose import datalogging ...