LittleFS v2 on mbedOS 5.15.4

Hello,

I was testing mbedOS 6.1 and litteFSv2 on my custom nrf52840 board. While littleFSv2 is working great on 6.1, I am running into serious troubles with all I2C devices that are interrupt driven. With the same source on mbedOS 5.15.4 I am getting the opposite behaviour - while all I2C devices and interrupts are working as expected I can not get littleFS to work properly. This might be also related to the fact that I am using littleFS-fuse which is based on littleFSv2.

With this being said I was looking for an option to get littleFSv2 working on mbedOS 5.15. Looking at the information on Github (https://github.com/ARMmbed/mbed-littlefs) it should work but when compiling I am always running into the following errors:

[Error] LittleFileSystem2.cpp@28,34: ‘CrcMode’ was not declared in this scope
[Error] LittleFileSystem2.cpp@28,48: wrong number of template arguments (3, should be at least 0)
[Error] LittleFileSystem2.cpp@28,81: expression list treated as compound expression in initializer [-fpermissive]
[Warning] LittleFileSystem2.cpp@28,53: left operand of comma operator has no effect [-Wunused-value]
[Warning] LittleFileSystem2.cpp@28,81: right operand of comma operator has no effect [-Wunused-value]
[Warning] LittleFileSystem2.cpp@28,81: right operand of comma operator has no effect [-Wunused-value]
[Error] LittleFileSystem2.cpp@30,8: request for member ‘compute’ in ‘ct’, which is of non-class type ‘int’

Has anyone ever had any luck with littleFS v2 on mbedOS 5.15 yet? Is there anything I am not aware of? Thank you very much for helping me with solving this.

Hi Ben,

littleFSv2 is only supported in Mbed 6 onwards, it has not been ported to or officially tested with Mbed 5.15 I’m afraid. So your choices are either use 5.15 with LittleFS v1 or migrate to Mbed 6 and use LittleFS v2.

Regards
Anna

Hi Anna,

I am very sorry for the late response. Thank you for the clarification and additional information. Makes perfectly sense. I will try to migrate to Mbed 6 if I can figure out the cause of the issues I am facing with I2C.

All the best,
B