I was astonished by all the subpackages pulled in with the pico vscode extension -- so I uninstalled them. (see: viewtopic.php?t=390203)
The VSCode extension is only needed for visual debugging. VSCode will build for the pico without it. Then just manually upload with openocd from the terminal in vscode, done. To each his own, but I found running VSCode with nothing but the C++ and CMake extensions was much preferable to trying to use the 8+ extensions pulled in by the pico extension.
That's always an option if you are finding the extensions a bit heavy on top of vscode, I did.
The VSCode extension is only needed for visual debugging. VSCode will build for the pico without it. Then just manually upload with openocd from the terminal in vscode, done. To each his own, but I found running VSCode with nothing but the C++ and CMake extensions was much preferable to trying to use the 8+ extensions pulled in by the pico extension.
That's always an option if you are finding the extensions a bit heavy on top of vscode, I did.
Statistics: Posted by drankinatty — Thu Oct 16, 2025 12:25 am