From efc63a301f96e31438ac856726daba88ef91856d Mon Sep 17 00:00:00 2001 From: Daniel M'BOUYOU Date: Tue, 11 Aug 2026 21:12:28 +0000 Subject: [PATCH 1/4] Fix two outdated facts in BUILDING.md --- BUILDING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/BUILDING.md b/BUILDING.md index 326eb8f7..e047bceb 100644 --- a/BUILDING.md +++ b/BUILDING.md @@ -8,7 +8,7 @@ git submodule update --init lib/mbedtls You also need to install `libusb-1.0` if you want to use the USB functionality. -> If libusb-1.0 is not installed, picotool still builds, but it omits all options that deal with managing a pico via USB (load, save, erase, verify, reboot). Builds that do not include USB support can be identified by running `picotool version`, which will state `This version of picotool was compiled without USB support. Some commands are not available.`. Additionally, the unsupported commands won't appear in the output of the help command, and if you attempt to execute an invalid command you will get an error message. The build output message `libUSB is not found - no USB support will be built` also appears in the build logs. +> If libusb-1.0 is not installed, picotool still builds, but it omits all options that deal with managing a pico via USB (load, save, erase, verify, reboot, bdev). Builds that do not include USB support can be identified by running `picotool version`, which will state `This version of picotool was compiled without USB support. Some commands are not available.`. Additionally, the unsupported commands won't appear in the output of the help command, and if you attempt to execute an invalid command you will get an error message. The build output message `libUSB is not found - no USB support will be built` also appears in the build logs. ### Linux / macOS @@ -103,7 +103,7 @@ In order for the SDK to find `picotool` in this custom folder, you will usually The `picotool` build has some CMake variables you can use to customise how the build works, and how `picotool` functions: -- `GENERATE_FIXED_DOCS_WIDTH`: By default the width of the output from `picotool` adjusts to the width of the terminal. Setting this to `true` fixes the width to 140, which is used when generating the [README](README.md). +- `GENERATE_FIXED_DOCS_WIDTH`: By default the width of the output from `picotool` adjusts to the width of the terminal. Setting this to `true` fixes the width to 95, which is used when generating the [README](README.md). - `DEFAULT_BOOTSEL_LED`: This can be used to set the default value for the `--bootsel-led` argument, so `picotool` always reboots devices to BOOTSEL with that LED used as the activity indicator. - `PICOTOOL_NO_LIBUSB`: By default `picotool` is compiled with USB support if libusb is found. Setting this to `true` explicitly compiles without USB support, which is used when the Pico SDK builds picotool. - `USE_PRECOMPILED`: By default the build uses pre-compiled ELF/BIN files for code that is run on the device (enc_bootloader, xip_ram_perms, and picoboot_flash_id). Setting this to `false` re-compiles these files instead. From b99db6da98e8e535cd0335992f4fac031b6fadec Mon Sep 17 00:00:00 2001 From: will-v-pi <108662275+will-v-pi@users.noreply.github.com> Date: Wed, 12 Aug 2026 10:11:11 +0100 Subject: [PATCH 2/4] Fix otp permissions output in README --- README.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index d3ec328f..6e9bb9a2 100644 --- a/README.md +++ b/README.md @@ -1568,8 +1568,8 @@ OPTIONS: ``` ```text -$ picotool otp permissions --sign private.pem --tx 46 sample-permissions.json -Picking file ./xip_ram_perms.elf +$ picotool otp permissions --sign private.pem sample-permissions.json +Picking file /usr/local/share/picotool/xip_ram_perms.elf page10 page10 = 0 setting page10 -> 4063233 @@ -1578,11 +1578,8 @@ page11 = 0 setting page11 -> 4128781 page12 page12 = 0 -setting page12 -> 4128781 -tx_pin = 0 -setting tx_pin -> 46 +setting page12 -> 4128768 Loading into XIP RAM: [==============================] 100% ->>> using flash update boot of 13ffc000 The device was rebooted to start the application. ``` From 468b6882371d4f8aa31398aacf5b23c1cf02e713 Mon Sep 17 00:00:00 2001 From: will-v-pi <108662275+will-v-pi@users.noreply.github.com> Date: Wed, 12 Aug 2026 12:20:00 +0200 Subject: [PATCH 3/4] Update BUILDING.md --- BUILDING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/BUILDING.md b/BUILDING.md index e047bceb..6503c831 100644 --- a/BUILDING.md +++ b/BUILDING.md @@ -8,7 +8,7 @@ git submodule update --init lib/mbedtls You also need to install `libusb-1.0` if you want to use the USB functionality. -> If libusb-1.0 is not installed, picotool still builds, but it omits all options that deal with managing a pico via USB (load, save, erase, verify, reboot, bdev). Builds that do not include USB support can be identified by running `picotool version`, which will state `This version of picotool was compiled without USB support. Some commands are not available.`. Additionally, the unsupported commands won't appear in the output of the help command, and if you attempt to execute an invalid command you will get an error message. The build output message `libUSB is not found - no USB support will be built` also appears in the build logs. +> If libusb-1.0 is not installed, picotool still builds, but it omits all options that deal with managing a pico via USB (load, save, reboot, etc.). Builds that do not include USB support can be identified by running `picotool version`, which will state `This version of picotool was compiled without USB support. Some commands are not available.`. Additionally, the unsupported commands won't appear in the output of the help command, and if you attempt to execute an invalid command you will get an error message. The build output message `libUSB is not found - no USB support will be built` also appears in the build logs. ### Linux / macOS From 674fc861cfe0d75da39cc35751847a46c9960bac Mon Sep 17 00:00:00 2001 From: Daniel M'BOUYOU Date: Wed, 12 Aug 2026 12:20:15 +0200 Subject: [PATCH 4/4] Capitalise Pico in the libusb note --- BUILDING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/BUILDING.md b/BUILDING.md index 6503c831..ff34c679 100644 --- a/BUILDING.md +++ b/BUILDING.md @@ -8,7 +8,7 @@ git submodule update --init lib/mbedtls You also need to install `libusb-1.0` if you want to use the USB functionality. -> If libusb-1.0 is not installed, picotool still builds, but it omits all options that deal with managing a pico via USB (load, save, reboot, etc.). Builds that do not include USB support can be identified by running `picotool version`, which will state `This version of picotool was compiled without USB support. Some commands are not available.`. Additionally, the unsupported commands won't appear in the output of the help command, and if you attempt to execute an invalid command you will get an error message. The build output message `libUSB is not found - no USB support will be built` also appears in the build logs. +> If libusb-1.0 is not installed, picotool still builds, but it omits all options that deal with managing a Pico via USB (load, save, reboot, etc.). Builds that do not include USB support can be identified by running `picotool version`, which will state `This version of picotool was compiled without USB support. Some commands are not available.`. Additionally, the unsupported commands won't appear in the output of the help command, and if you attempt to execute an invalid command you will get an error message. The build output message `libUSB is not found - no USB support will be built` also appears in the build logs. ### Linux / macOS