I have the same issue, Linux Mint 22.
Except I know to copy the uf2 file, rather than the elf file, and the blinking works fine (as does revised with a different blink rate).
Bur VS Code says:
RP2350 device at bus 1, address 4 appears to be in BOOTSEL mode, but picotool was
unable to connect. Maybe try 'sudo' or check your permissions.
The terminal process "/home/f/.pico-sdk/picotool/2.1.1/picotool/picotool 'load', '/home/f/Desktop/HW/PiPico/VSCbuild/blink/build/blink.elf', '-fx'" failed to launch (exit code: 249).
The pico is clearly in bootsel and has been automatically mounted at /media/f/RP2350 where I can copy (or paste) a uf2 file and everything works. Both the files in the directory and the directory show as owned by the user running VS Code and are writable.
One possibility is that it can't find that mount path, so running as root wouldn't help.
Thoughts?
Except I know to copy the uf2 file, rather than the elf file, and the blinking works fine (as does revised with a different blink rate).
Bur VS Code says:
RP2350 device at bus 1, address 4 appears to be in BOOTSEL mode, but picotool was
unable to connect. Maybe try 'sudo' or check your permissions.
The terminal process "/home/f/.pico-sdk/picotool/2.1.1/picotool/picotool 'load', '/home/f/Desktop/HW/PiPico/VSCbuild/blink/build/blink.elf', '-fx'" failed to launch (exit code: 249).
The pico is clearly in bootsel and has been automatically mounted at /media/f/RP2350 where I can copy (or paste) a uf2 file and everything works. Both the files in the directory and the directory show as owned by the user running VS Code and are writable.
One possibility is that it can't find that mount path, so running as root wouldn't help.
Thoughts?
Statistics: Posted by ke1g — Tue Apr 08, 2025 9:02 pm