Skip to content

Commit e033a43

Browse files
committed
Remove references to picotool sign
Fixes #218
1 parent ce1e6b9 commit e033a43

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -576,7 +576,7 @@ OPTIONS:
576576

577577
## encrypt
578578

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`.
580580

581581
The encrypted binary will have the following structure:
582582

@@ -850,10 +850,10 @@ These commands will set/get specific rows of OTP. By default, they will write/re
850850

851851
### load
852852

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)
854854
For example, if you wish to sign a binary and then test secure boot with it, you can run the following set of commands:
855855
```text
856-
$ picotool sign hello_world.elf hello_world.signed.elf private.pem otp.json
856+
$ picotool seal --sign hello_world.elf hello_world.signed.elf private.pem otp.json
857857
$ picotool load hello_world.signed.elf
858858
$ picotool otp load otp.json
859859
$ picotool reboot

0 commit comments

Comments
 (0)