Lock picotool version on master to 2.1.1 #2401
Open
Conversation
This file contains hidden or 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
The master SDK branch (and the SDK release tags eg 2.1.1) should point to specific picotool tags, to ensure you get a compatible picotool
will-v-pi
added a commit
to raspberrypi/picotool
that referenced
this pull request
May 29, 2025
This is required due to 2.1.0 and 2.1.1 SDK releases pointing at picotool develop branch rather than the respective picotool releases (raspberrypi/pico-sdk#2401)
kilograham
added a commit
to raspberrypi/picotool
that referenced
this pull request
May 29, 2025
…key shares instead of just the AES key (#207) Note: this is not the final commit for this functionality, so use with caution for now * Use 4-way key shares for AES private keys The privateaes.bin key file is now 4x256bit numbers (A,B,C,D), and the AES key X is A^B^C^D * Remove check that ELF segments are between metadata blocks This is not required, as you can still load data outside of the region between the metadata blocks which contain the binary - for example, loading code into scratch memory. * Add enc_bootloader binary You can now use `picotool encrypt --embed ...` to create a self-decrypting binary, using enc_bootloader * Specify file types where useful for untyped files (json, pem, bin) * Implement FIB workaround by storing inverse of row n in row n+32 of each OTP page * Only delete existing load_maps when encrypting These only cause issues when encrypting, as the old block needs to be included in the new load_map When signing, the old load_map can be used again without issue * Throw clearer error when using picotool >2.1.1 with SDK <=2.1.1 This is required due to 2.1.0 and 2.1.1 SDK releases pointing at picotool develop branch rather than the respective picotool releases (raspberrypi/pico-sdk#2401) --------- Co-authored-by: Graham Sanderson <[email protected]>
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.
The master SDK branch (and the SDK release tags eg 2.1.1) should point to specific picotool tags, to ensure you get a compatible picotool - currently it points to the
developbranch of picotoolThis has been set to
developfor the 2.1.0 and 2.1.1 releases, so those releases may break in the future ifpicotoolloses backwards compatibility (eg SDK header movement, or changes topicotoolcommands)