Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Littlefs Alternatives
Similar projects and alternatives to littlefs
-
-
MicroPython
MicroPython - a lean and efficient Python implementation for microcontrollers and constrained systems
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
-
zephyr
Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
FatFs
FatFs is a generic FAT file system module for small embedded systems. The FatFs is written in compliance with ANSI C and completely separated from the disk I/O layer. Therefore it is independent of hardware architecture.
-
-
Raspberry-PICO2040-Flash-Storage
The Following C Coded Library is used to perform Flash Write, Read and Erase functions on Raspberry Pico 2040.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better littlefs alternative or higher similarity.
littlefs reviews and mentions
Posts with mentions or reviews of littlefs.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-10.
- LittleFS Design (CObW) – Combining advantages of COW and log-structures
- LittleFS Design
-
Littlefs – a little fail-safe filesystem designed for microcontrollers
Pointers correctly round-trip through unrelated pointer types, provided the alignment for both types is compatible.
At least one bit does look a bit questionable: lfs_mlist is treated as the common initial sequence of lfs_dir and lfs_file, even though it isn't, and common initial sequences only apply to union fields anyway. Example cast of struct dir * to struct lfs_mlist * (probably valid of itself, assuming the alignment is compatible): https://github.com/littlefs-project/littlefs/blob/c733d9ec57... then use struct dir as if it were actually a struct lfs_mlist: https://github.com/littlefs-project/littlefs/blob/c733d9ec57...
(There's other occurrences of the same kind of thing.)
Strictly speaking, I think this might be unfixable without a bunch of work, but so much stuff does this kind of operation that any compiler that doesn't do what you expect will have been fixed by now. (Assuming you're not one of those people who is going to pop up and tell us with a straight face that what we should expect is for the compiler to do absolutely anything - except, perhaps, for having it generate correct code, which would be defective behaviour that should be eliminated.) Maybe improve the odds by using lfs_mlist as the common initial sequence of both structs, and fingers crossed that the compiler considers the union rules to apply to this case too. Or compile with -fno-strict-aliasing.
-
I made a tachometer/hour meter for my outboard engine using the PIO
Also, it looks like you're writing to the flash every second the engine is running. Do you have an idea of what the endurance of that might be? I'm not too familiar with this but supposedly the flash on the Pico is good for at least 100K program/erase cycles and Micropython uses LittleFS on RP2040 which does wear leveling. I looked for more official info and the rp2 port code backs that up with a note: "the flash requires the programming size to be aligned to 256 bytes". And the littlefs readme does say it does wear leveling and other good stuff.
- GitHub - littlefs-project/littlefs: A little fail-safe filesystem designed for microcontrollers
-
nRF Connect SDK file writes gives -22 error after many files
Maybe first go and localize which assumption has been voided, i.e. what of the many places in littlefs that raise this error actually raise it? And... erm... what littlefs are you talking about? https://github.com/littlefs-project/littlefs doesn't seem to have a fs_close() function...
- SPI Flash file system vs writing my own fifo?
-
Small MicroSD module for project
Rather easy to add LittleFS for file storage onto the NOR flash. https://github.com/littlefs-project/littlefs
- CircuitPython – The easiest way to program microcontrollers
-
A note from our sponsor - InfluxDB
www.influxdata.com | 23 Apr 2024
Stats
Basic littlefs repo stats
29
4,764
8.2
6 days ago
littlefs-project/littlefs is an open source project licensed under BSD 3-clause "New" or "Revised" License which is an OSI approved license.
The primary programming language of littlefs is C.
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com