I can't use the official Raspberry Pi VS Code Pico Extension because it doesn't support my Raspberry Pi Bookworm OS so I looked up MicroPico and thought I'd give a whirl.Note that the extension "MicroPico" is already installed by default in VS Code.
Ho hum -
And the same for every '>micropico:' command I have tried. And I have tried closing and restarting VS Code but no joy. How anything can install itself then not find what it's installed is beyond me. I don't suppose it's worth asking if anyone has any ideas for making it work ?
I guess I'll give it a go under Windows.
Seems I already had 'MicroPico' installed and it's working okay under Windows. And I probably can't blame it that when I opened a project folder with a Python file in it VS Code brought up some 'copilot' enshittification which locked my PC solid and required a power-cycle reboot.
Luckily nothing locked up when I tried again and ">hide copilot" brought up some command which then disabled it.
Anyway, it looks to me like it's nothing but an alternative to Thonny. The auto-connect is perhaps nicer but the "No COM device found", which has to be manually closed when the Pico isn't plugged in, is just plain annoying. I can't imagine MicroPico is going to last long on any of my systems without getting uninstalled.
If that's what the OP is using, or the VS Code Pico Extension is invoking it, it seems it is looking for a Pico presenting a virtual serial port. It just works when connected via USB when using stock MicroPython, but doesn't and can't when not connected via USB, using Debug Probe to connect to a pico UART using stock MicroPython.
Statistics: Posted by hippy — Sat Jul 19, 2025 9:34 pm