You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our use of the ESP32-S3, we are enabling the secure boot option in the bootloader which increases the size of the bootloader such that it overflows into default location of the partition table at 0x8000. We've had to move our partition table to 0xA000 via the sdkconfig, but this appears to break our usage of cargo-espflash flash.
What would be the best way to support this change in the partition table location? A few ideas:
Detect the partition table location via the sdkconfig or esp-idf-sys output
Allow the partition table location to be explicitly specified via command-line option to cargo-espflash and espflash
Add a partition type to the .csv file that allows the location and size of the partition table in flash to be define just like other partitions. (Maybe the bootloader should be added to the csv as well. We know the bootloader must be located at 0x0, but it might be useful to specify the size of the bootloader in the .csv)
The text was updated successfully, but these errors were encountered:
In our use of the ESP32-S3, we are enabling the secure boot option in the bootloader which increases the size of the bootloader such that it overflows into default location of the partition table at 0x8000. We've had to move our partition table to 0xA000 via the
sdkconfig
, but this appears to break our usage ofcargo-espflash flash
.What would be the best way to support this change in the partition table location? A few ideas:
sdkconfig
oresp-idf-sys
outputcargo-espflash
andespflash
.csv
file that allows the location and size of the partition table in flash to be define just like other partitions. (Maybe the bootloader should be added to the csv as well. We know the bootloader must be located at 0x0, but it might be useful to specify the size of the bootloader in the .csv)The text was updated successfully, but these errors were encountered: