littlefs
rshell
littlefs | rshell | |
---|---|---|
29 | 6 | |
4,769 | 896 | |
1.4% | - | |
8.2 | 4.3 | |
4 days ago | 18 days ago | |
C | Python | |
BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
littlefs
- 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
rshell
- Only way I can connect to micropython through serial connection is Arduino IDE
- VSCode - Micropython - Pi Pico (non W)
- MicroPython officially becomes part of the Arduino ecosystem
-
use pico without thonny ide
If you don't want a GUI, you can use rshell which was written for the original Pyboard and the very first MicroPython implemention. It is a simple tool that can copy files in/out of the pico filesystem, and gives you the REPL prompt too.
-
Raspberry Pi Pico w/ Python Working
inside pythonsdk, it recommends using either Thonny or rshell. Since I was pretty sure Thonny was gonna take a lot of work, I tried rshell; however it seemed rshell was gonna to work rshell issue. I was looking around for alternatives and landed on ampy.
-
CircuitPython – The easiest way to program microcontrollers
CircuitPython is a fork of MicroPython, and they periodically bring in commits from MicroPython to stay up to date.
One advantage of CircuitPython is that your board gets mounted as a volume like a USB drive, and you can just copy code.py onto it to install your program; it's just a more user-friendly experience. For comparison MicroPython only exposes a file system through a tool called rshell[1], that you need to use to copy code over. CircuitPython also seems to have a lot more libraries due to Adafruit's investment in this ecosystem, although I suspect that most of them could easily be adapted to work with both.
[1] https://github.com/dhylands/rshell
What are some alternatives?
spiffs - Wear-leveled SPI flash file system for embedded devices
ampy - MicroPython Tool - Utility to interact with a MicroPython board over a serial connection.
lvgl - Embedded graphics library to create beautiful UIs for any MCU, MPU and display type.
picotool
zephyr - Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
MicroPython - MicroPython - a lean and efficient Python implementation for microcontrollers and constrained systems
lwext4 - ext2/ext3/ext4 filesystem library for microcontrollers
Pico-Go - Raspberry Pi Pico support for VS Code
uf2 - UF2 file format specification
pymakr-vsc
STORfs - Open source file system for small embedded systems
rp2040js - A Raspberry Pi Pico Emulator in JavaScript