B4R Question LittleFS compile errors when Arduino board updated to v3

[RJB]

If I update the esp32 board from v1.0.6 to v3.0.1 in the Arduino board manager I get littleFS errors on compile
The rLittleFS library version is 1.11 and no online version is shown in the Libraries manager.
Is there/ should there be an updated version of the library to work with the updated arduino board?
The errors are:

Compiling (ESP32 Dev Module)    Error
C:\Users\robin\Documents\Arduino\libraries\LittleFS_esp32\src\LITTLEFS.cpp: In member function 'virtual bool LITTLEFSImpl::exists(const char*)':
C:\Users\robin\Documents\Arduino\libraries\LittleFS_esp32\src\LITTLEFS.cpp:44:18: error: no matching function for call to 'LITTLEFSImpl::open(const char*&, const char [2])'
   44 |     File f = open(path, "r");
      |              ~~~~^~~~~~~~~~~
In file included from C:\Users\robin\Documents\Arduino\libraries\LittleFS_esp32\src\LITTLEFS.cpp:17:
C:\Users\robin\AppData\Local\Arduino15\packages\esp32\hardware\esp32\3.0.1\libraries\FS\src/vfs_api.h:37:15: note: candidate: 'virtual fs::FileImplPtr VFSImpl::open(const char*, const char*, bool)'
   37 |   FileImplPtr open(const char *path, const char *mode, const bool create) override;
      |               ^~~~
C:\Users\robin\AppData\Local\Arduino15\packages\esp32\hardware\esp32\3.0.1\libraries\FS\src/vfs_api.h:37:15: note:   candidate expects 3 arguments, 2 provided
Error during build: exit status 1

Thanks

 

[peacemaker]

Some news: https://github.com/espressif/arduino-esp32/releases/

 

[Erel]

You will need to keep using v1 for now.

 

[RJB]

OK thanks.

 

[RJB]

Some news: https://github.com/espressif/arduino-esp32/releases/

Thanks

 

[peacemaker]

using v1 for now

3.0.0 is previous. It seems it was OK before recently, i compiled.

 

[RJB]

Catch 22 at the moment: need v3.0.1 for logging on esp32 C3 but can't use it on existing code with littleFS built in, has to be V1.0.6 for that.

 

[peacemaker]

need v3.0.1 for logging on esp32 C3

Is v.3.0.0 not OK for esp32 C3 ?

 

[RJB]

Not for logging: see https://www.b4x.com/android/forum/threads/esp32c3-logging.161449/

 

[RJB]

You will need to keep using v1 for now.

Hi,
Will you be providing updates for the latest Arduino IDE and ESP32 boards? Just need to know for forward planning.
Thanks

 

[peacemaker]

providing updates

Updates of what ? B4R is just transpiller (from B4X language to C-code) over the Arduino ecosystem that is aggregator of MCUs SDK's. We cannot update SDK of chipsets

 

[RJB]

Possibly I'm wrong but I think that b4r/ libraries have to be updated to work with the updates on the Arduino side.
I assumed "You will need to keep using v1 for now" indicated that there would be an update at some point.

 

[peacemaker]

I guess, Erel meant that it's to be used those old version which allows usage without a stuck. But SDK of the MCU for sure can update the vendor only, IMHO.

 

[RJB]

Hopefully Erel will see this and can clarify what the position is. Even if there is no resolution for the problems it would help me understand what is going on!

 

[Erel]

The library needs to be updated to support the updated SDK: https://www.b4x.com/android/forum/threads/rlittlefs-for-b4r.130630/#content

 

[candide]

first B4R test with rLittleFS on esp32 with sdk 3.0.2 was NOK
library LittleFS in 3.0.x is exactly the same as it was before, no change => i see nothing to change in rLittelFS

B4R test with sdk 2.0.27 and rLittleFS was OK

Arduino test with sdk 3.0.0 and LittleFS was OK
B4R test with sdk 3.0.0 and rLittleFS was OK

Arduino test with sdk 3.0.2 and LittleFS was OK
B4R test with sdk 3.0.2 and rLittleFS is now OK

all B4R tests with sdk 3.0.2 and rLittleFS are now OK

i suppose we have in sdk 3.0.x some parameters added for esp32 configuration and checked with LittleFS. in my case, Correct parameters are set up with Arduino and after it is OK for B4R

 

[peacemaker]

some parameters added

It would be good to find how to list these settings, to compare with other SDK versions and for ... any other MCUs.

 

[RJB]

Correct parameters are set up with Arduino and after it is OK for B4R

I don't understand what this means either!

 

[candide]

I don't understand what this means either!

can you share an example of code with rLittleFS not working for you ?

 

[RJB]

can you share an example of code with rLittleFS not working for you ?

I'll check if that's feasible!
In the mean time can you help with what 'Correct parameters are set up with Arduino' and where they are set up?
I presume you made some changes somewhere as you said 'B4R test with sdk 3.0.2 and rLittleFS is now OK?
Thanks