[4.0.0-beta1] ESP32 -- File system infinite loop

[henrygab]

--------- Instructions - Delete this ---------
Please provide answers directly below each section.
--------- Instructions - Delete to here ---------
ESPixelStick Firmware Version
4.0.0-Beta1 (7083637)

Hardware Version
TwilightLord ESP32 16MB

Binary release or compiled yourself?
Binary release

Operating System
N/A

Access Point
Ubiquiti Nanostation M2 Loco

Describe the bug

Bare, fresh module -- nothing attached to any pins. Fully erased flash just before flashing this beta, choosing Generic ESP32 4MB (should just ignore the extra 12MB).

Gets into an infinite cycle, and appears to have errors saving its own config to the internal flash?

The following output lines may be of particular interest:

./components/esp_littlefs/src/littlefs/lfs.c:495:error: No more free space 50
...
[FileMgr] ***Configuration File: '/input_config.json' Deserialzation Error. Error code = EmptyInput***
[InputMgr] EEEE Error loading Input Manager Config File. EEEE

Attached an example log showing the infinitely looping output.

espixelstick_fs_error.txt

(The module itself is fine ... WLED works on this same module.)

[MartinMueller2003]

The File System on this device is in a bad state. It looks like it was not properly set up. This line is the key:
./components/esp_littlefs/src/littlefs/lfs.c:495:error: No more free space 50
We do not use anywhere near the total space available in a properly formatted FS.

[forkineye]

@henrygab
For this one, can you try this as well? #360 (comment)

[forkineye]

@henrygab
Normally, we just erase the filesystem area on flash. I just changed the flash tool to do a full erase, can you give this one a try - https://github.com/forkineye/ESPixelStick/actions/runs/1279404057

[forkineye]

I've tried on all my modules can still can't re-produce this. If you're still experiencing this in the newer builds, let us know.

[henrygab]

I apologize for the delayed response. (Real life is sometimes busy.)

I had been fully erasing the flash using espytool.py before loading any of the 4.0 builds. So, I don't think having the flash tool full erase would change the result.

However, it appears that ESPixelStick_Firmware-4.0-ci1282596145 no longer reproduces the issue, so OK to close.