PICOTOOL-CONFIG(1)

πŸ“¦ version 2.2.0-a4, in ubuntu stonking

πŸ’– PICOTOOL-CONFIG πŸ’–

okay so bestie, welcome to the picotool-config manual page, section 1 (User Commands, obviously), and it's literally just about looking at or changing your program's configuration settings β€” either on the target device(s) or inside a file. that's the whole vibe. πŸŽ€


✨ NAME ✨

picotool-config β€” display or change program configuration settings from the target device(s) or file. no cap, that's it, that's the job. πŸ’…


🌸 SYNOPSIS 🌸

picotool config [-s <key> <value>] [-g <group>] [device-selection]

picotool config [-s <key> <value>] [-g <group>] <filename> [-t <type>]

like, two whole moods: device mode and file mode. pick ur fighter. πŸ¦‹


πŸ‘‘ OPTIONS πŸ‘‘

  • <key> β€” this is the variable name, aka which setting you're poking at. 🫢
  • <value> β€” the new value you want that key to hold. glow-up for ur config.
  • -g <group> β€” filter stuff by feature group. only the groupies u asked for. πŸŽ€

πŸ”₯ TARGET SELECTION πŸ”₯

targeting device(s) 🌈

if you wanna target one or more connected RP-series device(s) sittin' in BOOTSEL mode β€” and yes, that's the default, main character energy fr fr β€” here's ur filter menu:

  • --bus <bus> β€” filter devices by their USB bus number.
  • --address <addr> β€” filter devices by USB device address.
  • --vid <vid> β€” filter by vendor id. iykyk.
  • --pid <pid> β€” filter by product id.
  • --ser <ser> β€” filter by serial number.
  • -f, --force β€” this one's spicy: it forces a device that is not in BOOTSEL mode, but is running compatible code, to reset so the command can actually run. and after the command executes β€” unless the command itself happens to be a reboot β€” the device gets rebooted back into application mode. it's giving "let me in, i promise i'll put it back". 😭
  • -F, --force-no-reboot β€” same rescue mission: forces a device that's not in BOOTSEL mode but running compatible code to reset so the command can run. BUT here's the difference β€” after executing (again, unless the command itself is a reboot), the device is left connected and accessible to picotool, just without the USB drive mounted. no reboot home, it stays out here with us. πŸ’€

targeting a file πŸ“

  • <filename> β€” the file name. that's the whole description bestie, it's the name of the file. πŸ™ˆ
  • -t <type> β€” specify the file type explicitly β€” uf2 | elf | bin β€” and it just straight up ignores the file extension. icon-level decisiveness. ⭐

πŸ’œ reminder: -f and -F both reset a device that isn't in BOOTSEL mode, and both skip rebooting when the command itself is reboot. the only difference is where the device ends up after β€” rebooted to application mode (-f) or left connected without the USB drive mounted (-F). don't mix 'em up, queen. πŸ‘‘

🧚 SEE ALSO 🧚

nothing here bestie, the original page doesn't list any. slay with what u got. ✨


and that's the tea, gorgeous. this was picotool-config, section 1 of the User Commands manual, from picotool 2.2.0-a4+dfsg, dated December 2025. go forth and configure, periodt. πŸ’…πŸ’–πŸŽ€

πŸ“¦ where this page comes from