You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -576,7 +576,7 @@ OPTIONS:
576
576
577
577
## encrypt
578
578
579
-
`encrypt` allows you to encrypt and sign a binary for use on the RP2350. By default, it will sign the encrypted binary, but that can be configured similarly to `picotool sign`.
579
+
`encrypt` allows you to encrypt and sign a binary for use on the RP2350. By default, it will sign the encrypted binary, but that can be configured similarly to `picotool seal`.
580
580
581
581
The encrypted binary will have the following structure:
582
582
@@ -850,10 +850,10 @@ These commands will set/get specific rows of OTP. By default, they will write/re
850
850
851
851
### load
852
852
853
-
This command allows loading of a range of OTP rows onto the device. The source can be a binary file, or a JSON file such as the one output by `picotool sign`. The schema for this JSON file is [here](json/schemas/otp-schema.json)
853
+
This command allows loading of a range of OTP rows onto the device. The source can be a binary file, or a JSON file such as the one output by `picotool seal`. The schema for this JSON file is [here](json/schemas/otp-schema.json)
854
854
For example, if you wish to sign a binary and then test secure boot with it, you can run the following set of commands:
0 commit comments