I would recommend getting rid of '/home/pi/bin/picotool' and whatever else related you have and follow -
viewtopic.php?p=2144302#p2144302
The '~/pico' is the parent directory of wherever you have placed the Pico SDK, for example, '~/pico/pico-sdk'.
That works for me and should provide a system-wide 'picotool' in '/usr/local/bin' linked to the '~/pico/picotool/build/picotool' executable and the 'sudo make install' should have command line and VS Code builds recognise it is already installed, stop it from downloading each and every clean build.
This keeps cropping up so it seems the documentation is deficient. It would probably be best to raise that as an issue.
viewtopic.php?p=2144302#p2144302
The '~/pico' is the parent directory of wherever you have placed the Pico SDK, for example, '~/pico/pico-sdk'.
That works for me and should provide a system-wide 'picotool' in '/usr/local/bin' linked to the '~/pico/picotool/build/picotool' executable and the 'sudo make install' should have command line and VS Code builds recognise it is already installed, stop it from downloading each and every clean build.
This keeps cropping up so it seems the documentation is deficient. It would probably be best to raise that as an issue.
Statistics: Posted by hippy — Wed Feb 26, 2025 2:34 pm