Platformio 3.4.3 ffat no data file in Build Filesystem image

[maxgerhardt]

@whogarden

The next line is missing, I expected to see the file \stationslist.txt. Correct?

No, no such line would be printed.

$ pio run -t buildfs
Processing esp32dev (platform: espressif32; board: esp32dev; framework: arduino)
--------------------------------------------------------------------------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp32dev.html
PLATFORM: Espressif 32 (6.0.0) > Espressif ESP32 Dev Module
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
DEBUG: Current (cmsis-dap) External (cmsis-dap, esp-bridge, esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES: 
 - framework-arduinoespressif32 @ 3.20006.221224 (2.0.6) 
 - tool-esptoolpy @ 1.40400.0 (4.4.0) 
 - tool-mkfatfs @ 2.0.1 
 - toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch5
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 33 compatible libraries
Scanning dependencies...
No dependencies
Building in release mode
Building FS image from 'data' directory to .pio/build/esp32dev/fatfs.bin
=================[SUCCESS] Took 0.49 seconds =================

Irregardless, in a minimum reproduction of the project, my data/test.txt and content is perfectly there in the generated fatfs.bin.

$ hexdump -C .pio/build/esp32dev/fatfs.bin 
00000000  eb fe 90 4d 53 44 4f 53  35 2e 30 00 10 01 01 00  |...MSDOS5.0.....|
00000010  01 00 02 5f 01 f8 01 00  3f 00 ff 00 00 00 00 00  |..._....?.......|
00000020  00 00 00 00 80 00 29 86  76 9a 56 4e 4f 20 4e 41  |......).v.VNO NA|
00000030  4d 45 20 20 20 20 46 41  54 20 20 20 20 20 00 00  |ME    FAT     ..|
00000040  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00001000  f8 ff ff ff 0f 00 00 00  00 00 00 00 00 00 00 00  |................|
00001010  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00002000  54 45 53 54 20 20 20 20  54 58 54 20 18 00 86 76  |TEST    TXT ...v|
00002010  9a 56 00 00 00 00 86 76  9a 56 02 00 12 00 00 00  |.V.....v.V......|
00002020  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00006000  53 6f 6d 65 20 74 65 73  74 20 63 6f 6e 74 65 6e  |Some test conten|
00006010  74 0a 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |t...............|
00006020  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00007000  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
*
0015f000

The most reasonable explanation is that you have

@whogarden

// You only need to format FFat the first time you run a test
#define FORMAT_FFAT true

So it’ll format the partition, erasing the previous content…

@whogarden

    if (FORMAT_FFAT) FFat.format();
    if(!FFat.begin()){
        Serial.println("FFat Mount Failed");
        return;
    }

You need to absolutely set this macro to false, reupload the firmware and reupload the filesystem.