Remove elf2uf2-rs in favour of picotool #947
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
elf2uf2-rs seems to be unmaintained, and as of Rust 1.89 rejects valid ELF files due to an overly strict check of the ELF header. Picotool is maintained by Raspberry Pi and does not have this problem.
This commit changes guide-level explanation in the root and RP2040 examples READMEs, and the runner in .cargo/config.toml files, to picotool.
Some wording around the flashing process as "creating a UF2 file" was changed as picotool can flash directly from an ELF file with the appropriate command-line flag. Information about deliberately creating a UF2 file has been kept.
In addition, the root README now directs people to rp-binary-info rather than stating that picotool compatible "binary info" is unsupported.
A question: Previously the root README said:
I have removed this explicit recommendation as the paragraph above it directs people to use picotool if they are not using a debug probe (or otherwise wish to flash over USB). Is this acceptable, or should an explicit recommendation (to use picotool over USB) be included?