- Fri Sep 28, 2018 3:29 pm
#78434
I am using an ESP12F module (4M/1M SPIFFS) running core 2.4.2 SDK 2.2.1(cfd48f3) and am experiencing a corrupt flash file. A segment of the file cannot be read from that portion of the file return 0 bytes. However, I can read data on either side of that segment. Any ideas/help would be appreciated! Unfortunately, I can't turn on SPIFFS_DBG without running out of iram.
For illustration, the application supports a command-line interface and an fdump command that seeks to the specified offset of a file and hex dumps the specified number of bytes in 16-byte chunks. The output showing the problem is below:\
readBytes(my16ByteBuffer,16) fails for everything between file offsets 0x67DF (26591) and 0x69E4 (27108), but works for everything outside this range
The directory and file information reports the file size as 75888 and the fdump function works right up to the end of the file.
For illustration, the application supports a command-line interface and an fdump command that seeks to the specified offset of a file and hex dumps the specified number of bytes in 16-byte chunks. The output showing the problem is below:\
Code: Select all
>fdump /report.log 26564
000067C4: FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000067D4: 73 FD C9 A2 04 23 17 17 17 70 02 00 00 00 00 EF
000067E4: read failed (0 bytes returned)
000067F4: read failed (0 bytes returned)readBytes(my16ByteBuffer,16) fails for everything between file offsets 0x67DF (26591) and 0x69E4 (27108), but works for everything outside this range
Code: Select all
>fdump /report.log 27072
000069C0: read failed (0 bytes returned)
000069D0: read failed (0 bytes returned)
000069E0: read failed (0 bytes returned)
000069F0: 67 76 6A EF 1F 17 00 00 F0 4B 00 3F 00 00 00 00The directory and file information reports the file size as 75888 and the fdump function works right up to the end of the file.
