Partition table without factory partition

[TypingRabbit]

Hello,

in the current project I am currently trying to realize we need as much NVS memory as possible and as much memory as possible for each OTA partition.

Now my question is if there is anything to consider when simply removing the factory partition from the partition table "Factory app, two OTA definitions"?

Here is my current partition table:

Code: Select all

# Espressif ESP32 Partition Table
# Name,     Type,   SubType,    Offset,     Size, Flags
nvs,        data,   nvs,        0x9000,     0xF3000,
otadata,    data,   ota,        0xFD000,    0x2000,
phy_init,   data,   phy,        0xFF000,    0x1000,
ota_0,      0,      ota_0,      0x100000,   0x180000,
ota_1,      0,      ota_1,      0x280000,   0x180000,

Many greetings
TypingRabbit

[ESP_Sprite]

If there is no factory app, the bootloader will normally just always boot from the active OTA app.

[eriksl]

Currently it doesn't work:

[ 0%] Generating ../../partition_table/partition-table.bin
[ 0%] Built target _project_elf_src
[ 0%] Built target memory_ld
Error at line 6: Value 'factory' is not valid. Known keywords: ota, phy, nvs, coredump, nvs_keys, efuse, undefined, esphttpd, fat, spiffs, littlefs
Please check extra_partition_subtypes.inc file in build/config directory

[ESP_Sprite]

That's a different issue. Suggest you start your own post for that, and make sure you also post the partitions.csv file you have.

[eriksl]

Thanks for your help. It appeared to be a f*up of myself, fixed it. It works now.
I now even have OTA update over Bluetooth working, which was a bit of a challenge as the S3 doesn't have BT "classic" so no SPP support and even very little support for (large) streams of data. Also I must say the documentation of Nimble leaves a lot to be desired.