Had a similar problem – here is a solution.

PROBLEM

First of all – it is an ESP-IDF defaults problem – not VisualGDB. Albeit, I would argue that for something like that VisualGDB could have provided a user-friendly configuration override

1. The way partition writing logic is controlled is first esptool_py tool creates partition command skeleton using a fixed template
2. Then, individual components which are interested in adding to partitions (eg spiffs, nvs, etc), add their own entries
3. To support various tools within toolchain, the logic is then used to generate a number of configuration files overlapping in functionality
4. To add rules for writing to partition, one typically uses  either esptool_py_flash_target_image() or esptool_py_flash_to_partition() CMAKE functions. The two functions do the same thing, except that the first one expects you to provide all details (offset, etc), while the second one tries to extract those details from configuration

CONCEPTUAL FIX

So, to fix the problem, we need to do two things:

1. We need to disable the default partition logic which writes the project main binary to the first ‘app’ partition which happened to be mentioned in partition table – which is typically ‘factory’
2. Add explicit partition writing rules to write binaries we want to each project directory

This has the benefit that we keep core ESP-IDF project-neutral and allow each project to define what it likes

STEP-BY-STEP FIX

The default partition logic is located in %ESP_IDF_HOME%\components\esptool_py\CMakeLists.txt

if(CONFIG_APP_BUILD_GENERATE_BINARIES)
partition_table_get_partition_info(app_partition_offset “–partition-boot-default” “offset”)
esptool_py_custom_target(app-flash app “app”)`</div>

# esptool_py_flash_target_image(app-flash app “${app_partition_offset}” “${build_dir}/${PROJECT_BIN}”)
# esptool_py_flash_target_image(flash app “${app_partition_offset}” “${build_dir}/${PROJECT_BIN}”)
endif()

to disable it – comment out the last two lines, as shown</div>

To add your own rules, create a new cmake file – lets call it “custom.flash.config.cmake”
Inside, specify something like that (I am using “esptool_py_flash_to_partition”, as it is cleaner)

esptool_py_flash_to_partition(flash “factory” “${CMAKE_BINARY_DIR}/factory.bin”)
esptool_py_flash_to_partition(flash “app0” “${CMAKE_BINARY_DIR}/MyApp.bin”)
esptool_py_flash_to_partition(flash “app1” “${CMAKE_BINARY_DIR}/MyApp.bin”)

Finally, reference the new CMAKE file from your add the following to your root CMakeLists.txt (assuming that your custom cmake file is in project root directory

include(custom.flash.config.cmake)

That is it.

• This reply was modified 3 months, 2 weeks ago by AnatoliKrassavine.
• This reply was modified 3 months, 2 weeks ago by AnatoliKrassavine.