Partitions.csv Offset values, needed or not

[username]

I have seen 2 styles of partiton.csv files in the example folder which I would like clarification on please.
Some have an offset value and some do not. Obviously, the ones that don't work, so why do some examples use them and others do not?
Is there any reason why we would need to add them ?

One style is this:

Code: Select all

# Name,   Type, SubType, Offset,  Size, Flags
# Note: if you have increased the bootloader size, make sure to update the offsets to avoid overlap

nvs,      data, nvs,     ,        0x4000,
otadata,  data, ota,     ,        0x2000,
phy_init, data, phy,     ,        0x1000,
ota_0,    app,  ota_0,   ,        1500K,
ota_1,    app,  ota_1,   ,        1500K,

The Second is this:

Code: Select all

# Name,   Type, SubType,  Offset,   Size,  Flags
nvs,      data, nvs,      0x9000,   16k
otadata,  data, ota,      0xd000,   8k
phy_init, data, phy,      0xf000,   4k
ota_0,    app,  ota_0,    0x10000,  1920k
ota_1,    app,  ota_1,    ,         1920k
coredump, data, coredump, ,         64K
reserved, data, 0xfe,     ,         128K

[ESP_Sprite]

If you don't specify an offset, by default it takes the place where the previous partition ends as the offset.

[username]

Thanks, but for the version that all are empty. There is nothing before nvs, so how does it know where to start ?

[MicroController]

https://docs.espressif.com/projects/esp ... ffset-size:

"Partitions with blank offsets in the CSV file will start after the previous partition, or after the partition table in the case of the first partition."