5 years, 1 month ago.

Can littlefs build size be reduced for read-only support?

Our team is developing a custom firmware update feature with a custom bootloader. We are investigating the use of littlefs as a filesystem abstraction to manage storage on a SPI-connected flash chip. Our main application will use the full read and write features of littlefs, but we are trying to reduce the size of our separate bootloader app by building in only those portions of littlefs needed to READ from the filesystem. So far, after a bit of basic hacking, we've only been able to save a few hundred bytes.

Has anyone else ever tried something like this? Does anyone think it is feasible to expect the size difference to be more than just a few hundred bytes, or is this the only savings we should expect to see?

Hints/tips are appreciated.

Be the first to answer this question.