Open lurch opened 3 years ago
The absence of a picotool list
command also makes it "tricky" to use the picotool reboot
command (added by #23 ) when you've got two Picos plugged in 😉
If both Picos are in BOOTSEL mode, then picotool info
tells you e.g.
Multiple RP2040 devices in BOOTSEL mode found:
Device at bus 2, address 16:
----------------------------
Program Information
name: hello_usb
web site: https://github.com/raspberrypi/pico-examples/tree/HEAD/hello_world/usb
features: USB stdin / stdout
Device at bus 2, address 19:
----------------------------
Program Information
name: hello_usb
web site: https://github.com/raspberrypi/pico-examples/tree/HEAD/hello_world/usb
features: USB stdin / stdout
and if both Picos are in USB-CDC mode, then picotool info
(in this example, on Windows) tells you:
No accessible RP2040 devices in BOOTSEL mode were found.
but:
Device at bus 2, address 20 appears to be a RP2040 device with a USB serial connection, not in BOOTSEL mode. You can force reset it into BOOTSEL mode via 'picotool reboot -f -u' first.
Device at bus 2, address 21 appears to be a RP2040 device with a USB serial connection, not in BOOTSEL mode. You can force reset it into BOOTSEL mode via 'picotool reboot -f -u' first.
However if one Pico is in USB-CDC mode and the other is in BOOTSEL mode, then picotool info
(and any other picotool command?) seems to "only see" the device that's in BOOTSEL mode and just tells you:
Program Information
name: hello_usb
web site: https://github.com/raspberrypi/pico-examples/tree/HEAD/hello_world/usb
features: USB stdin / stdout
I wonder if a
picotool list
command might be useful? Consider the following scenario:if I then plug in a Pico with a blank Flash chip (wiped using
flash_nuke.uf2
) I get:In this latter case it would be nice if e.g. a
./picotool list
could tell me:For bonus points, it could even include the other VID/PID combos from https://github.com/raspberrypi/usb-pid ? :wink: