ESP32 Forum

Posted: **Wed Jul 11, 2018 9:26 am**

Following Partitiontable works fine in V3.0

#Name,Type,SubType,Offset,Size
#boot,data,0,0x1000,4K
#reserved,0,0,0x2000,24K
partition,data,0,0x8000,4K
nvs,data,nvs,0x9000,12K
otadata,data,ota,0xC000,8K
free,data,0x40,0xE000,8K
factory,app,factory,0x10000,1344K
ota_0,app,ota_0,0x160000,1344K
flash,data,0x40,0x2B0000,64K
js_code,data,0,0x2C0000,256K
storage,data,0,0x300000,1024K

but gives this error in V3.1
Partitions defined in '/home/esp32/V3_1_prerelease/template/partitions_espruino.csv' occupy 4.1MB of flash (4259840 bytes) which does not fit in configured flash size 4MB.

Calling gen_esp32.py directly gives this
../esp-idf/components/partition_table/gen_esp32part.py partitions_espruino.csv partitions_espruino.bin
Parsing CSV input...
WARNING: 0x8000 address in the partition table is below 0x9000
WARNING: 0x9000 address in the partition table is below 0xa000
WARNING: 0xc000 address in the partition table is below 0xd000
WARNING: 0xe000 address in the partition table is below 0xf000
WARNING: 0x10000 address in the partition table is below 0x11000
WARNING: 0x160000 address in the partition table is below 0x170000
WARNING: 0x2b0000 address in the partition table is below 0x2c0000
WARNING: 0x2c0000 address in the partition table is below 0x2d0000
WARNING: 0x300000 address in the partition table is below 0x310000

Looks like partition should not be defined in partitiontable anymore (?)

Posted: **Thu Jul 12, 2018 1:24 am**

jumjum123 wrote: Looks like partition should not be defined in partitiontable anymore (?)

That's right, in ESP-IDF we haven't considered the partition table to be a partition so it doesn't need to be mentioned in the partition table.

The V3.0 partition tool didn't check that the first partition didn't clobber the partition table, so it will happily generate a binary partition table that includes an entry for the table itself. The V3.1 generator tool thinks that this partition will clobber the partition table, hence the warning (this is more important in V3.1 as you can change the offset of the partition table now, to allow a bigger bootloader).

At the moment the behaviour is to print a warning and modify the offsets so that they don't overlap, this is what caused the partition table to not fit in the flash. I'm going to change this so it's a hard error, to avoid people getting unexpected offsets in the binary tables.

ESP32 Forum

Partitiontable works fine in V3.0, has problem in V3.1 prerelease

Partitiontable works fine in V3.0, has problem in V3.1 prerelease

Re: Partitiontable works fine in V3.0, has problem in V3.1 prerelease