Tools: Switch from elf2uf2 to modern picotool #21269
Open
+125
−55
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
Area: doc
AnnsAnns
changed the title
picotool: start elf2uf2 migration picotool: Replace elf2uf2 usage with picotool picotool: Fix incorrect filename for flash utility picotool: fix compilation when arm g++ is installed picotool: picotool-ify flash process picotool: Adjust documentation to new workflow
|
I have tested this working properly on a Pi Pico 1 now. I am not too confident in my understanding of the RIOT packages makefile system so I am happy to hear feedback 😄 |
|
Wouldn't it be easier to use the precompiled binaries of picotool instead of compiling it on demand: https://github.com/raspberrypi/pico-sdk-tools/releases ? |
|
Given the way elf2uf2 worked and looking into other packages + the documentation I would have assumed that the preference is to avoid binaries when possible |
AnnsAnns
changed the title
|
I gave this a try now and unfortunately there seems to be an issue with the CMake configuration of the picotool that others have run into as well: https://www.reddit.com/r/embedded/comments/1els7zl/armnoneeabig_not_working/ Build log:This seems to be an issue with MBedTLS using the wrong compiler, but I couldn't really pinpoint the issue and how to solve it. I wondered if it would be possible to check for |
|
I can confirm that this also happened for me but after tinkering a bit with the Makefile it didn't happen again, I'll investigate if I can reproduce it again, thank you for testing it, I thought this was a local one-off issue |
crasbe
reviewed
Mar 13, 2025
|
Furthermore it would be good to add For example: - echo "[INFO] compiling picotool from source now"
+ @echo "[INFO] compiling picotool from source now" |
|
Thank you for the review, I will adjust the PR based on your suggestions as soon as I can |
crasbe
reviewed
Mar 13, 2025
Teufelchen1
reviewed
Mar 19, 2025
crasbe
added
Type: enhancement
|
Was able to verify it flashing and building for the raspberry pi pico 2 |
crasbe
reviewed
Mar 27, 2025
|
The patch for the The red warning message is also not shown because of the indentations in the |
crasbe
reviewed
Mar 27, 2025
crasbe
reviewed
Mar 27, 2025
|
Tested, is able to flash to rpi pico 1 and 2 |
crasbe
reviewed
Mar 27, 2025
|
Thank you for your thorough review 😄 |
|
Thanks, the double colons makefile syntax definitely feels absolutely wrong, the more I learn about Makefiles the less I understand Makefiles 😆 |
crasbe
reviewed
Mar 27, 2025
| all: $(CURDIR)/picotool | ||
|
|
||
| clean:: | ||
| rm picotool |
There was a problem hiding this comment.
Suggested change
| rm picotool | |
| rm picotool |
Speaking of Makefile oddities, this has to be a tabulator, spaces don't work.
There was a problem hiding this comment.
Suggested change
| rm picotool | |
| rm -f picotool |
It would be also good to add the -f option again so that rm won't complain if there is no picotool binary.
I wanted to be "more gentle" with the rm, but that was wrong apparently. Sorry for the wrong suggestion (again).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Contribution description
The Pi Pico 2 requires a more modern version of elf2uf2 called picotool, in a first effort to get the Raspberry Pi Pico 2 to be compatible with Riot I thus needed to update it.
While this PR is intended to allow me to work on the Pi Pico 2, picotool also offers advantages for the Pico 1 such as easier device detection, loading/flashing and the ability to easily verify the integrity of a file after loading it onto the device. I have incorporated these advantages into the existing workflow so hopefully the flashing process should have become easier for everyone 😄
Testing procedure
I verified it working with examples using the pi pico 1, the expected outcome is that the user should not experience any differences while flashing (aside from the tool being different)
Issues/PRs references