ota data partition info error

[Ritesh]

Is it possible to create custom OTA partitions for more than 1 MB? Do I need to change bootloader for that?

I have tried but not got any success for that.

[ESP_Sprite]

Yes, you should; up to 16MB should work just fine. What is the trouble you're running into?

[Ritesh]

Hi,

I am getting following warnings while using "Factory APP, Two OTA Definitions" at boot time.

I (31) boot: Espressif ESP32 2nd stage bootloader v. V0.1
I (40) boot: compile time 14:22:28
I (62) boot: SPI Speed : 40MHz
I (62) boot: SPI Mode : DIO
I (62) boot: SPI Flash Size : 16MB
I (64) boot: Partition Table:
I (70) boot: ## Label Usage Type ST Offset Length
I (81) boot: 0 nvs WiFi data 01 02 00009000 00004000
I (92) boot: 1 otadata OTA data 01 00 0000d000 00002000
I (103) boot: 2 phy_init RF data 01 01 0000f000 00001000
I (114) boot: 3 factory factory app 00 00 00010000 00100000
I (125) boot: 4 ota_0 OTA app 00 10 00110000 00100000
I (137) boot: 5 ota_1 OTA app 00 11 00210000 00100000
I (148) boot: End of partition table
I (155) boot: Loading app partition at offset 00010000
I (1172) boot: segment 0: paddr=0x00010018 vaddr=0x00000000 size=0x0ffe8 ( 65512)
I (1173) boot: segment 1: paddr=0x00020008 vaddr=0x3f400010 size=0x41338 (267064) map
I (1181) boot: segment 2: paddr=0x00061348 vaddr=0x3ffc1740 size=0x0903c ( 36924) load
I (1209) boot: segment 3: paddr=0x0006a38c vaddr=0x40080000 size=0x00400 ( 1024) load
I (1210) boot: segment 4: paddr=0x0006a794 vaddr=0x40080400 size=0x1c608 (116232) load
I (1275) boot: segment 5: paddr=0x00086da4 vaddr=0x400c0000 size=0x00000 ( 0) load
I (1276) boot: segment 6: paddr=0x00086dac vaddr=0x00000000 size=0x0925c ( 37468)
I (1283) boot: segment 7: paddr=0x00090010 vaddr=0x400d0018 size=0x3efcc (257996) map
I (1296) boot: segment 8: paddr=0x000cefe4 vaddr=0x50000000 size=0x00008 ( 8) load
I (1311) heap_alloc_caps: Initializing. RAM available for dynamic allocation:
I (1320) heap_alloc_caps: At 3FFCA77C len 00015884 (86 KiB): DRAM
I (1330) heap_alloc_caps: At 3FFE8000 len 00018000 (96 KiB): D/IRAM
I (1341) heap_alloc_caps: At 4009CA08 len 000035F8 (13 KiB): IRAM
I (1351) cpu_start: Pro cpu up.
I (1356) cpu_start: Single core mode
I (1363) cpu_start: Pro cpu start user code
W (1467) cpu_start: failed to load RF calibration data, falling back to full calibration
I (2860) phy: phy_version: 258, Nov 29 2016, 15:51:07, 0, 2
I (3009) cpu_start: Starting scheduler on PRO CPU.

Does anyone has any idea for this type of warning and does it will create any impact on WiFi test?