Partitions.csv Offset values, needed or not
Posted: Fri Aug 11, 2023 7:58 pm
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:
The Second is this:
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,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