Well, I described my problem on Gitter, but there was no response yet, so I will explain it here, perhaps someone may help me.
The problem: I have a ESP32 app which adds an extra 256K file system s described in the documenttion, and it works fine. Now I have an ESP32 WROVER module which comes with 16MB, and and I have no chance to use the memory above 4MB. This is strange, because the mos tool (and/or flasher) detects the 16MB as you may see here:
Connecting to https://mongoose.cloud, user test Uploading sources (31974 bytes) Firmware saved to build/fw.zip Loaded Heydo-MQTT-GO/esp32 version 1.0 (20180628-164828/???) Opening /dev/cu.SLAB_USBtoUART @ 115200... Connecting to ESP32 ROM, attempt 1 of 10... Connecting to ESP32 ROM, attempt 2 of 10... Connected, chip: ESP32D0WDQ6 R1 Running flasher @ 0... Flasher is running ==> Flash size: 16777216, params: 0x0240 (dio,128m,40m) Deduping... 16384 @ 0x9000 -> 8192 8192 @ 0xd000 -> 4096 ...
... but as I increase the value of the file system size in this line above 256K (even in 256K sized values)
build_vars: ESP_IDF_EXTRA_PARTITION: fs_ext,data,spiffs,,256K
... this error pops up:
Partitions defined in '/mongoose-os/fw/platforms/esp32/src/partitions_mgos.csv' occupy <xyz> of flash (<xyz> bytes) which does not fit in configured flash size 4MB. Change the flash size in menuconfig under the 'Serial Flasher Config' menu.
I tried a lot of things to change the configuration to 16MB (with buildvars as
FLASH_SIZE or even adding SDK settings, but nothing helped.
So the question is: what do I have to do to use the full available flash size?
Addendum: as I remark now, the creating of a filesystem with
FS.Mkfsfails completely on the ESP WROVER module ... even with the small size ...