unable to find a matching CMSIS-DAP device
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c
- Domain
- devtools, embedded-iot
Research direction
Start by reproducing the reported USB enumeration, pyocd list result, and OpenOCD command against the Pico1/Pico2 setup. Compare the detected USB interfaces with the CMSIS-DAP interface expected by pyOCD and OpenOCD; done means the adapter is recognized and can connect to the RP2350 target.
Written by the indexing model from the issue text.
Description
I'm using Pico1 to debug Pico2. The adapter isn't detected.
[ 6595.254937] usb 1-5.2: USB disconnect, device number 50
[ 6597.994980] usb 1-5.2: new full-speed USB device number 51 using xhci_hcd
[ 6598.233024] usb 1-5.2: New USB device found, idVendor=2e8a, idProduct=000c, bcdDevice= 2.23
[ 6598.233030] usb 1-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6598.233032] usb 1-5.2: Product: Debugprobe on Pico (CMSIS-DAP)
[ 6598.233034] usb 1-5.2: Manufacturer: Raspberry Pi
[ 6598.233035] usb 1-5.2: SerialNumber: E660B440072C1A2A
[ 6598.267448] cdc_acm 1-5.2:1.1: ttyACM0: USB ACM device
pyocd list
No available debug probes are connected
openocd -f interface/cmsis-dap.cfg -f target/rp2350.cfg -c "adapter speed 5000"
Open On-Chip Debugger 0.12.0+dev-00002-gcd4873400 (2025-10-18-05:11)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : [rp2350.cm0] Hardware thread awareness created
Info : [rp2350.cm1] Hardware thread awareness created
ocd_process_reset_inner
adapter speed: 5000 kHz
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: unable to find a matching CMSIS-DAP device
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 363
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/debugprobe
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
raspberrypi/debugprobe#210 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
raspberrypi/debugprobe#206 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
raspberrypi/debugprobe#202 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
raspberrypi/debugprobe#196 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 30/100
raspberrypi/debugprobe#177 · 1 reaction ·
All issues in raspberrypi/debugprobe
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
libsdl-org/SDL#16372 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
corazawaf/coraza-nginx#140 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
jamesstringer90/appsandbox#160 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100