LittleFS support — official support status and OCTOSPI integration references

[CJ007]

Hi,

I'm working on a data-logging application using the STM32U575VGT6Q. I'm evaluating filesystem options for this.

I have a few questions for the community/ST team:

1. Is LittleFS officially supported on the STM32U575 series (or any STM32U5 platform)? Is there any official ST support, reference implementation, or roadmap for LittleFS on STM32U5, or on any STM32 series in general?
2. I'm targeting an external OCTOSPI  flash chip . Is there any official or community GitHub repo, example project, or app note demonstrating LittleFS's using OCTOSPI HAL driver on STM32U5?
3. If anyone has done this integration themselves, could you share a reference implementation or point me to one?
4. For an append-heavy, sequential data-logging use case on external NOR flash, which filesystem would you recommend between LittleFS, FatFS, and FileX+LevelX on this platform, and why?

Any pointers — official documentation, GitHub repos, forum threads, or app notes — would be greatly appreciated.

Thanks in advance.

[Pavel A.]

As you can see here LittleFS is not in the ST curated offering. 

Integration with a OCTOSPI flash or other specific storage medium is up to you. 

> For an append-heavy, sequential data-logging use case on external NOR flash, which filesystem would you recommend 

Do you need to expose the data *on the medium* to external system (PC and so on)? Do you need to log simultaneously to several “files” or “streams”?  If not, you don’t need a standard filesystem. Choose a flash memory that allows appending with minimal granularity.

Some memories have internal ECC or other integrity protection. (This usually works when you write by units of specific size (16 bytes or so). Appending lesser blocks invalidates this ECC.)

 

[CJ007]

Thanks for the clarification and the questions — that's helpful context.

The logged data doesn't need to be directly exposed on the medium to an external system like a PC. It will be retrieved and sent out over a communication interface through the MCU when needed.

Given that, I take your point that a full standard filesystem may not be strictly necessary , still I'd still like to explore a LittleFS integration on an STM32 board.
 

Since LittleFS isn't part of the curated Cube offering, could you or anyone in the community point me toward:

1. Any guidelines or best practices for integrating LittleFS on an STM32 board — particularly around designing the block-device HAL layer (read/prog/erase/sync) and handling erase-granularity/alignment for external  flash.
2. Any GitHub repos or reference projects showing a working LittleFS integration on an STM32 board (SPI, QSPI, or OCTOSPI — whichever example is available).
3. Any known caveats, pitfalls, or lessons learned from doing this kind of integration, especially with external flash and its erase-before-write constraints.