Custom partitioning

[altmind]

Hi. I'm using ESP32 M5stack basic with only 4mb of storage. Default firmware build barely fits the partitions.
I know how to configure/resize partitions when using the esp-idf toolset, but how do i supply a custom partitions.csv to lvlg_micropython toolset?

python-venv make.py esp32 BOARD=ESP32_GENERIC DISPLAY=ili9341 --flash-size=4 --optimize-size --ccache

...
Partition table binary generated. Contents:
*******************************************************************************
# ESP-IDF Partition Table
# Name, Type, SubType, Offset, Size, Flags
nvs,data,nvs,0x9000,24K,
phy_init,data,phy,0xf000,4K,
factory,app,factory,0x10000,2384K,
vfs,data,fat,0x264000,1648K,
*******************************************************************************
...
micropython.bin binary size 0x253c70 bytes. Smallest app partition is 0x254000 bytes. 0x390 bytes (0%) free.
Warning: The smallest app partition is nearly full (0% free space left)!
[7/8] Completed 'bootloader'
Project build complete. To flash, run:
idf.py flash
python -m esptool --chip esp32 -b 460800 --before default_reset --after no_reset write_flash --flash_mode dio --flash_size 4MB --flash_freq 40m 0x1000 build-ESP32_GENERIC/bootloader/bootloader.bin 0x8000 build-ESP32_GENERIC/partition_table/partition-table.bin 0x10000 build-ESP32_GENERIC/micropython.bin
or from the "/home/alt/lvgl_micropython/lib/micropython/ports/esp32/build-ESP32_GENERIC" directory
python -m esptool --chip esp32 -b 460800 --before default_reset --after no_reset write_flash "@flash_args"
bootloader  @0x001000    22592  (    6080 remaining)
partitions  @0x008000     3072  (    1024 remaining)
application @0x010000  2440304  (     912 remaining)
total                  2505840

Do i have to create a new board definition/toml? I would prefer to just use a custom partitions.csv.

[kdschlosser]

The firmware fits just fine with the partition size that is made. Take note of the partition size and then If you edit /lib/lv_config.h and turn off a bunch of the widgets and compile again you are going to notice that the partition size is smaller. The build system sizes the application partition so it fits the binary with a little wasted space as possible. It does this because only the firmware gets written to that partition and it's not accessible from user code at all. Having a bunch of space on that partition is a waste because it is never going to be able to be used.

It's a good thing that the build system does this because it makes sure that you have the ability to use as much of the resources as possible. That is the reason why I wrote the build system that way..

However if you want to manually control the partition size then you should read over the README.MD file located in the root of the repository. I lists all of the build options that are available. There are a couple of build options available for the partitions and there is also an option to be able to make a custom board where you would have a partition file that is supplied by you that gets used.