fixed in core littlefs v2.9.2, and subsequently in esp_littlefs v1.14.4

Based on huming2207 being able to reproduce it here: https://github.com/joltwallet/esp_littlefs/issues/183

I opened up a PR that may resolve the issue here: https://github.com/littlefs-project/littlefs/pull/966

Will update when it gets merged and and makes its way to esp_littlefs.

In this context, block_count is the number of blocks in the entire filesystem, not free ones remaining. In newer versions of littlefs, the lfs_config.block_count value can be set to 0 to be inferred from an existing filesystem; on mount lfs.block_count is then appropriately populated. If you can get...

@owenjames can you post the full log? I believe this is an upstream core littlefs issue (unexpected divide by zero); esp_littlefs should be reporting an appropriate error code. The log can help us raise an appropriate issue in https://github.com/littlefs-project/littlefs

I do basically exactly this, checkout my repo Jolt Wallet . I have a few different sdkconfig.defaults for a few different target boards here . Basically I first apply sdkconfig.defaults, followed by sdkconfig.defaults.${TARGET_BOARD}, followed by sdkconfig.defaults.personal. The logic for applying t...

Here's my port of LittleFS that has the same API as the esp-idf SPIFFS port. Basically it should just work if you replace all your "spiffs" calls with "littlefs". Only slight difference is in your configuration, you don't specify "max_files".

https://github.com/joltwallet/esp_littlefs

checkout my project here:

https://github.com/BrianPugh/cookiecutt ... -webserver

if you don't want to use the entire template, look mostly at the OTA route. Essentially it allows you to perform an OTA by making a POST request.

I was able to solve this by assigning a value to a cmake variable in idf_ext.py via an action callback via define_cache_entry. Then, in my CMakeList file I pass this along as a compile definition. Definitely seems round about, but hey it works.

I'm currently trying to migrate my build system from GNU make to Cmake. In my original Makefile, i had multiple different targets that were just invoking the `build` target with different flags controlling portions of the code. For example, i may have a target like: foo: CFLAGS='-DFOO=1' $(MAKE) all...

@ESP_Angus I was outputting raw binary; you're absolutely correct these failures are probably causes by the newlinereplacement. Thank you so much! I'll be running another test, but all the evidence suggests that this was the bug. @Markus Becker thank you so much for independently programming and tes...