Sounds like you want to flash the Pocket Reform keyboard? (the post is in the general category).
If you pull the latest code in the main branch the warnings and errors are solved.
You must put your keyboard in flashing mode, open the keyboard OLED menu and press X. This will disable keyboard input so you will need to invoke the flash command from a remote session or via a USB keyboard.
Also, I do not have a Pocket Reform, so I cannot test this myself but I uploaded version 2.0 of the package picotool to unstable today and your line No accessible RP2040/RP2350 looks like you are using this new version of picotool that i just uploaded a few hours ago. It is thus entirely possible that there is a bug somewhere that needs to be fixed. Maybe somebody else who has done this before can try it out?
Yes, I am using the version of picotool from unstable. Hopefully we can isolate any issues I might have so we know the source. I’m working on the other aspects of it tonight.
You can put the keyboard into programming mode by pressing the X key when the OLED menu is opened. […] So only do this when the flashing script asks you to do so. You can recover from a stuck keyboard by toggling Pocket Reform’s Standby Power Switch off and on.
Am I reading that right, that I run picotool, and during that flashing process, I’ll be asked to put the keyboard into programming mode? If so, I get the above error before I’m ever prompted. If I need to get the keyboard into programming mode before running picotool, then this is straight user error on my part (possibly with an assist from the docs).
For the classic Reform keyboard before RP2040, where one uses dfu-programmer to flash it, there exists an interactive script that uses udevadm to allow to flash the keyboard firmware without a second keyboard:
I do not own the RP2040 keyboards yet, so somebody who does would have to adapt this script for use with it.
Ultimately though, the flashing process is something that should be done using fwupd.