Skip to content

Conversation

@jessebraham
Copy link
Member

@jessebraham jessebraham commented May 26, 2022

Closes #185

When the esp-idf-sys package is built, we store the paths to the already-compiled bootloader.bin and partition-table.bin files. If no alternatives have been specified via either command-line arguments and/or Cargo package metadata, then these binaries will be used instead of the defaults included with espflash.

When users are not building esp-idf-sys, (ie. bare-metal) then the behaviour does not change.

@MabezDev @bjoernQ @ivmarkov @N3xed will this cause any issues which I have not thought of?

@jessebraham jessebraham requested a review from MabezDev May 26, 2022 20:40
@jessebraham jessebraham marked this pull request as draft May 26, 2022 20:41
Copy link
Member

@MabezDev MabezDev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! Thanks for looking into this!

@MabezDev MabezDev marked this pull request as ready for review May 30, 2022 10:08
@MabezDev MabezDev merged commit 2d5b08c into esp-rs:master May 30, 2022
@jessebraham jessebraham deleted the feature/idf-detect branch May 30, 2022 20:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Detect and use bootloader/partition table from ESP-IDF when able

2 participants