Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support flashing partition table at custom location #458

Closed
jnross opened this issue Aug 15, 2023 · 1 comment · Fixed by #516
Closed

Support flashing partition table at custom location #458

jnross opened this issue Aug 15, 2023 · 1 comment · Fixed by #516
Labels
enhancement New feature or request

Comments

@jnross
Copy link
Contributor

jnross commented Aug 15, 2023

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:

  1. Detect the partition table location via the sdkconfig or esp-idf-sys output
  2. Allow the partition table location to be explicitly specified via command-line option to cargo-espflash and espflash
  3. 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)
@jnross
Copy link
Contributor Author

jnross commented Nov 22, 2023

Nice! Thanks for bringing this change in, @thetek42.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants