SPIFFS format question [false alarm/solved]

[fly135]

We just produced a new version of our board and now the spiffs file system doesn't work the same. If I install the same software on the new board as the old, the old one works and the new one doesn't. Our latest design has wrover-b (16MB flash). The previous design seems to have a wrover-b, but it has a white sticker that says WROVER instead of the engraved cover. I really don't see what difference the module makes. I've tested with two boards that have the wrover-b and they exhibit the same problem. Since everything related to flash and storage is on the module I don't see how it's different. The application runs, so factory partition seems fine.

The file looks valid before I reboot. IOW I save the file, then read it back and print the contents, then reboot and it can't be opened. But I can use esptool to read the partition data, then look at it with a hex editor. The main difference I notice is that the data on the failing unit has 10 zeros at the beginning of the file, and the one that works has....

00 00 00 00 01 00 01 00 01 80 then a bunch of FFs until I get to valid looking text and data starting at 0x00FC.

I was wondering about the spiffs format and if the zeros in the beginning are the source of my problem.

John A

[fly135]

False alarm.... I have a factory reset button that is used to delete the configuration and ready the unit for provisioning. Just found out from the board designer that the button on the new board is accidentally wired normally closed by accident. So when the device boots, it sees the button pressed and deletes the configuration file.

John A