Maybe describe the details and/or provide photographs of what you have.I believe that I have attached the wires correct.
Given only '/dev/ttyACM0' shows I would guess you have the following, though the PSU could be a phone charger (no data) cable back to the Pi's USB -
Code:
____________ ____ .----------------. | ::::::::: | | _____ | | | |____| USB | | | .------------|-. _____ | | |_______| D |- | | _| | | | |__| | U |----' | |_|---| PSU | | | | |_____| | | |_____| |______________|__| `--------------' Raspberry Pi Debug Probe Pico 2W- The Debug Probe "U" connector must connect to the correct Pico 2W UART pins
- The Pico 2W must be powered
- The Pico 2W must not be in BOOTSEL mode
- The Pico 2W must be running custom MicroPython firmware
- That custom MicroPython must have been build with REPL over UART enabled
I can think of reasons it might work at the command line but not when using VS Code. That would rest with how VS Code expects to interact with the Pico 2W and would depend on exactly what tools were being used. Are you using the official Raspberry Pi Pico VS Code Extension or something else ?
Statistics: Posted by hippy — Sat Jul 19, 2025 11:31 am