IMO there is very little we can do in this case. https://arm-software.github.io/CMSIS_5/DAP/html/group__DAP__ConfigUSB__gr.html reads "... Product String to indicate the Debug Unit. Note that "CMSIS-DAP" must be part of that string to allow identification by debuggers (or part of interface string for USB composite device)." It doesn't say explicitly that CMSIS-DAP string cannot be used for other interfaces in a composite device, but looks like a very stupid practice with respect to autodetection. Yes, we can exclude DCI interface because it has wrong class number. Unfortunately doing so would prevent the autodetection of Cypress KitProg in CMSIS-DAP mode, because it uses wrong class number for CMSIS-DAP v2 interface.
--- ** [tickets:#327] can't connect cmsis-dap v2 device. ** **Status:** new **Milestone:** 0.11.0 **Created:** Mon Dec 20, 2021 09:29 AM UTC by Qinfeng Chen **Last Updated:** Fri Dec 24, 2021 02:02 PM UTC **Owner:** OpenOCD-Gerrit **Attachments:** - [log.txt](https://sourceforge.net/p/openocd/tickets/327/attachment/log.txt) (8.8 kB; text/plain) Version: Open On-Chip Debugger 0.11.0+dev-00542-gfdf17dba5 (2021-12-17-19:05) Env: MacOsx 11.6 intel version. description: can't connect cmsis-dap v2 device. detail: see the trace log below. --- Sent from sourceforge.net because openocd-devel@lists.sourceforge.net is subscribed to https://sourceforge.net/p/openocd/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/openocd/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
