esp-idf/examples/mesh/ip_internal_network/partitions.csv

# 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,     0x9000,  0x6000,
phy_init, data, phy,     0xf000,  0x1000,
factory,  app,  factory, 0x10000, 1200K,
esp-mesh: Added example showing internal IP capable mesh network 2020-02-13 09:51:24 -05:00			`# 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, 0x9000, 0x6000,`
			`phy_init, data, phy, 0xf000, 0x1000,`
fix(partition_table): Check partition size for type APP The size of partition of type APP should be multiple of 4 KB. Partition generation tool now make this as a mandatory requirement. This is minimum flash erase size. If the size of the APP type partition is not aligned to 4 KB then the last erase operation could go beyond the allocated partition and hence may fail. This issue would only be observed when the firmware size grows very close to the allocated partition size, and hence causing the OTA update to fail. For already deployed devices on-field with the size of APP partition not aligned to flash sector boundary, it is best to ensure that firmware size always remains within the lower 4 KB boundary of the total allocated space. While migrating to ESP-IDF 5.3 release, partition table for an existing project can be adjusted accordingly for the build to succeed. Found during discussion in https://github.com/espressif/esp-idf/pull/12460 2023-10-30 08:34:25 -04:00			`factory, app, factory, 0x10000, 1200K,`