ESP-IDF Partition table problems

lg.lindstrom
Posts: 47
Joined: Fri Sep 17, 2021 4:02 pm

ESP-IDF Partition table problems

Postby lg.lindstrom » Wed Dec 01, 2021 4:30 pm

Hi

My application is getting bigger and bigger so I purchased samples of ESP32-WROOM-32D (16M). This should give me more storage for the application compare to the device I had before.

Until now, I have only tested parts of my application which independent works as expected.

First time putting all parts of the application together and trying to FLASH I got a error telling me that the partition table was to small for the application.

So far I have used the default partition table which I think look like 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,     ,        0x6000,
phy_init, data, phy,     ,        0x1000,
factory,  app,  factory, ,        1M,
I have copied this to a custom file and did a small change. I changed from IM to 2M in the "factory" line.

No more errors about the size of the application size and it flashes okay but .....

When running I get all kind of, for me, unknown errors .........

Code: Select all

V (1152) memory_layout: Examining memory region 0x40070000 - 0x40078000
V (1159) memory_layout: Region 0x40070000 - 0x40078000 inside of reserved 0x40070000 - 0x40078000
V (1168) memory_layout: Examining memory region 0x40078000 - 0x40080000
0x40080000: _WindowOverflow4 at C:/Users/lglin/esp/esp-idf/components/freertos/port/xtensa/xtensa_vectors.S:1730

V (1174) memory_layout: Region 0x40078000 - 0x40080000 inside of reserved 0x40078000 - 0x40080000
0x40080000: _WindowOverflow4 at C:/Users/lglin/esp/esp-idf/components/freertos/port/xtensa/xtensa_vectors.S:1730

0x40080000: _WindowOverflow4 at C:/Users/lglin/esp/esp-idf/components/freertos/port/xtensa/xtensa_vectors.S:1730

V (1183) memory_layout: Examining memory region 0x40080000 - 0x40082000
0x40080000: _WindowOverflow4 at C:/Users/lglin/esp/esp-idf/components/freertos/port/xtensa/xtensa_vectors.S:1730

0x40082000: gpio_isr_loop at C:/Users/lglin/esp/esp-idf/components/driver/gpio.c:422
 (inlined by) gpio_intr_service at C:/Users/lglin/esp/esp-idf/components/driver/gpio.c:444

V (1190) memory_layout: Region 0x40080000 - 0x40082000 inside of reserved 0x40080000 - 0x4009ea64
0x40080000: _WindowOverflow4 at C:/Users/lglin/esp/esp-idf/components/freertos/port/xtensa/xtensa_vectors.S:1730

0x40082000: gpio_isr_loop at C:/Users/lglin/esp/esp-idf/components/driver/gpio.c:422
 (inlined by) gpio_intr_service at C:/Users/lglin/esp/esp-idf/components/driver/gpio.c:444

0x40080000: _WindowOverflow4 at C:/Users/lglin/esp/esp-idf/components/freertos/port/xtensa/xtensa_vectors.S:1730

V (1199) memory_layout: Examining memory region 0x40082000 - 0x40084000
0x40082000: gpio_isr_loop at C:/Users/lglin/esp/esp-idf/components/driver/gpio.c:422
 (inlined by) gpio_intr_service at C:/Users/lglin/esp/esp-idf/components/driver/gpio.c:444

0x40084000: ea_get_current_elt at ??:?

I somehow says to me that the change in the partition table was not OKAY,,, but how should it look ?????

ESP_igrr
Posts: 2067
Joined: Tue Dec 01, 2015 8:37 am

Re: ESP-IDF Partition table problems

Postby ESP_igrr » Wed Dec 01, 2021 8:37 pm

Hi lg.lindstrom,

Is this the only thing you see on the console? Does the application boot successfully after these messages, or is this the last thing it prints?

If it boots okay, the messages themselves don't indicate any issue... Since you have verbose log output enabled, parts of the startup code are printing various addresses (like 0x40080000). The IDF monitor automatically decodes these addresses into function names and source code locations. Some of the function names (like _WindowOverflow4, which is located at 0x40080000) may sound scary but the fact that these messages are printed doesn't mean that these functions are executed and doesn't mean that there is any error.

lg.lindstrom
Posts: 47
Joined: Fri Sep 17, 2021 4:02 pm

Re: ESP-IDF Partition table problems

Postby lg.lindstrom » Thu Dec 02, 2021 9:50 am

ahhh ,, my mistake,,, I was to impatient and never let the log printout pass the startup sequence before breaking ,,,,,, Sorry.

Who is online

Users browsing this forum: ESP_rrtandler and 110 guests