ARMmbed / ARMmbed/DAPLink

How to Achieve Dual WinUSB Vender Class

Open
#1,107 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
2.8k
Forks
1.1k
Avg merge
3d 12h
Merged PRs (30d)
1

Description

I'm trying to achieve a dual vender class in a single device and successes, one's interface is 3 and the other is 4, and dual are recognized by PC. One interface string is "**ZPLINK CMSIS-DAP**", and the other is "**ZPLINK-WL CMSIS-DAP**"(See Picture)

And I did some test, both of them can be accessed by there IN or OUT endpoints.

But when I use Keil or IAR, they only can recognize one WinUSB device and only access the last interface's **ZPLINK-WL CMSIS-DAP,** which interface is 4. After I deleted the interface 4, then Keil can recognize interface 3's **ZPLINK CMSIS-DAP**.

Is Keil or IAR can only access one WinUSB in a single device at once? Always choose the last one?

Image

Contributor guide

Open the contributing guide

Research direction

No source file, test, or entry point is named. Start by reproducing the dual-interface device with interfaces 3 and 4, then compare how Keil and IAR recognize and access the two WinUSB interfaces; done means establishing and documenting the expected behavior or a confirmed project change.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
embedded-iot
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.