Which binaries should be provided to off-shore manufacturers?

[fevang]

I am using an off-shore manufacturer for an esp32 product that can only be updated via OTA updates after the initial flash. For security reasons we are providing a limited firmware that we will subsequently use to load the proper firmware via an OTA update.

I believe the following files and information are required

• firmware.bin
• partition-table.bin
• bootloader.bin
• partition table offset (0x9000)

Is there anything else I should provide?
From my testing, the partition table needs to be moved from the default 0x8000 to make room for a new bootloader.bin I will upload via OTA update that enables flash encryption and secure boot. I should specify the partition table offset(0x9000) then so I don't need to move that via an OTA update after.

This is my first time using a manufacturer, I am unsure of the process. If anyone has experience they can share, I will be very appreciative. Thank-you

[doglike]

Also interested in...

[chegewara]

When you issue in cmd/terminal "make" or "idf.py build" you will see at the end nice command line to flash esp32. In that long command you will find all files with paths and addresses.

Then you can use flash download tool to merge all files into 1 binary file.