ESP32 WLAN init and BT init Problem

[dvcam99]

Hello FC team,

if I do a init of ESP32 WLAN and BT component together I´ll get the follwing compiler message.

[5/7] Linking CXX executable esp-project.elf
[6/7] Generating binary image from built executable
esptool.py v3.3.4-dev
Creating esp32 image...
Merged 27 ELF sections
Successfully created esp32 image.
Generated C:/ESP32/YGE_DBU_Texy/YGE_DBU_Texy_V_1_8_3/build/esp-project.bin
[7/7] cmd.exe /C "cd /D C:\ESP32\YGE_DBU_Texy\YGE_DBU_Texy_V_1_8_3\build\esp-idf\esptool_py && C:\ESP-IDF\-tools\python_env\idf4.4_py3.7_env\Scripts\python.exe C:/Users/dirkb/Desktop/esp-idf/components/partition_table/check_sizes.py --offset 0x8000 partition --type app C:/ESP32/YGE_DBU_Texy/YGE_DBU_Texy_V_1_8_3/build/partition_table/partition-table.bin C:/ESP32/YGE_DBU_Texy/YGE_DBU_Texy_V_1_8_3/build/esp-project.bin"

FAILED: esp-idf/esptool_py/CMakeFiles/app_check_size C:/ESP32/YGE_DBU_Texy/YGE_DBU_Texy_V_1_8_3/build/esp-idf/esptool_py/CMakeFiles/app_check_size

cmd.exe /C "cd /D C:\ESP32\YGE_DBU_Texy\YGE_DBU_Texy_V_1_8_3\build\esp-idf\esptool_py && C:\ESP-IDF\-tools\python_env\idf4.4_py3.7_env\Scripts\python.exe C:/Users/dirkb/Desktop/esp-idf/components/partition_table/check_sizes.py --offset 0x8000 partition --type app C:/ESP32/YGE_DBU_Texy/YGE_DBU_Texy_V_1_8_3/build/partition_table/partition-table.bin C:/ESP32/YGE_DBU_Texy/YGE_DBU_Texy_V_1_8_3/build/esp-project.bin"
Error: app partition is too small for binary esp-project.bin size 0x13c100:
- Part 'factory' 0/0 @ 0x10000 size 0x100000 (overflow 0x3c100)
ninja: build stopped: subcommand failed.
ninja failed with exit code 1
Executing action: all (aliases: build)
Running ninja in directory C:\ESP32\YGE_DBU_Texy\YGE_DBU_Texy_V_1_8_3\build
Executing "ninja all"...

Is this a known issue?

BR
Dirk

[mnfisher]

Hi Dirk,

It's complaining that the app partition isn't large enough (though if all you are doing is initialising the WiFi and BT I would be surprised that this is the case)

You will need to define a custom partition table - and point to that using menuconfig - allocating more memory to the application.

Something like

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,     0x9000,  0x6000,
phy_init, data, phy,     0xf000,  0x1000,
factory,  app,  factory, 0x10000, 2M

Assuming you are using a 4MB (or above part).

Save as partition.csv (name to suit) and use menuconfig partition table to point to this.

Then recompile - and test again.

Might also be worth setting compiler options to 'size' (again using menuconfig)

Martin