Warning: Getting the pico device to work on windows can be an initially frustrating experience, but usually the problem resolves itself.
Recommended steps to resolve issues:
- Close out any programs that access serial ports as windows won't allow multiple apps to access a port.
- Once pulseview is installed, do a reboot.
- Possibly use zadig to map the USB device (I apologize that it's been so long I can't really remember if zadig is atually needed).
- Try plugging/unplugging the device and/or opening closing pulseview a few times.
- Close pulseview, and open a serial device apps (Terraterm/Putty etc). Send a "*" and then a "i" for identify and you should get a response. For some reason, other apps seem to have more success accessing the device than does the libserial code in pulseview.
- Go back and repeat any of the steps above. (Yeah, I know it's frustrating, but eventually it seems to work for most folks).
It is recommended that you read through the AnalyzerDetails.md for specifics on modes of the device, but if you just can't wait:
- Get some 1Kohm or greater resistors to put inline between the PICO inputs, you don't want to accidentally fry your PICO because you put in voltages <0V or >3.3V or accidentally jumpered ground to VCC.
- Get the sigrok-pico/pico_sdk_sigrok/build/pico_sdk_sigrok.uf2 file and program it to your PICO devices (examples are online, everywhere).
- Install Pulseview and skip to step 7, or sigrok-cli - follow descriptions from the sigrok pages for both.
- Replug the PICO to reset it, and then use sigrok-cli to scan for avaliable serial ports
sigrok-cli --list-serial
- Use sigrok-cli to scan for the device based on the serial port you found above. The baudrate doesn't matter because we are CDC serial.
sigrok-cli -l 2 -d raspberrypi-pico:conn=/dev/ttyACM0:serialcomm=115200/flow=0 --scan
- Do a first trace
~/github/sigrok-cli/sigrok-cli -l 2 -d raspberrypi-pico:conn=/dev/ttyACM0:serialcomm=115200/flow=0 --config samplerate=10000 --channels D2,D3,D4,D5 --samples 1000
- Aternatively to using sigrok-cli use Pulseview.
- Go read AnalyzerDetails.md like you should have to begin with....