PICOTOOL-OTP-GET(1)
π PICOTOOL-OTP-GET π
okay bestie, welcome to picotool-otp-get from the picotool manual (that's section 1, User Commands, for the record) β and literally all it does is get the value of one or more OTP registers/fields. that's it, that's the whole vibe. β¨
β¨ NAME β¨
picotool-otp-get β get the value of one or more OTP registers/fields π«Ά
πΈ SYNOPSIS πΈ
picotool otp get [-c <copies>] [-r] [-e] [-n] [-i <filename>]
[device-selection] [-z] [<selector>..]
π OPTIONS π
π Row/field options
-c <copies>β read a bunch of redundant values at once, multiple copies bestie π-r,--rawβ hand over the raw 24-bit values, no glow-up applied π₯-e,--eccβ use error correction, we love a self-healing queen π-n,--no-descriptionsβ don't show the descriptions, keep it mysterious π-i <filename>β include an extra otp definition from<filename>β¨
π¦ Row/Field Selection
-z,--fuzzyβ allow fuzzy name searches in the selector instead of demanding an exact match π<selector>β the row/field selector!! each one of these can select a whole row:
so like. ROW_NAME selects a whole row by name. ROW_NUMBER selects a whole row by number. PAGE:PAGE_ROW_NUMBER selects a whole row by page, plus its number within that page. iconic.
...or it can select a single field / a subset of a row β and for all of these, ROW_SEL is one of the row selectors from up there βοΈ:
ROW_SEL.FIELD_NAME selects a field within a row by name. ROW_SEL.n-m selects a range of bits within a row. ROW_SEL.n selects a single bit within a row. .FIELD_NAME selects any row's field by name β yes, any row, main character energy fr fr π
..or you can select multiple rows by using a blank, or *, for PAGE or PAGE_ROW_NUMBER β
π TARGET SELECTION π
π Target device selection
--bus <bus>β filter devices by USB bus number π--address <addr>β filter devices by USB device address--vid <vid>β filter by vendor id--pid <pid>β filter by product id--ser <ser>β filter by serial number-f,--forceβ force a device that is not in BOOTSEL mode, but is running compatible code, to reset so the command can actually run. and after executing the command (unless the command itself is areboot), the device will be rebooted back to application mode. no cap π-F,--force-no-rebootβ same deal: force a device that is not in BOOTSEL mode, but running compatible code, to reset so the command can be executed. after executing the command (unless the command itself is areboot), the device will be left connected and accessible to picotool, but without the USB drive mounted. so close yet so far π
heads up bestie: both-f/--forceand-F/--force-no-rebootare about devices not in BOOTSEL mode but running compatible code β they get reset, and then things happen after the command runs unless the command itself is areboot. don't say i didn't warn you π«Ά
aaaand that's the whole page, periodt. π this lil manual lives in picotool 2.2.0-a4+dfsg, dated December 2025 β mwah, bye, go read your OTPs bestie π¦πβ¨
π¦ where this page comes from
- ubuntu stonking: picotool 2.2.0-a4+dfsg-3 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms