Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebUSB sample not recognized correctly in Windows 10 #59457

Closed
maxd-nordic opened this issue Jun 20, 2023 · 6 comments
Closed

WebUSB sample not recognized correctly in Windows 10 #59457

maxd-nordic opened this issue Jun 20, 2023 · 6 comments
Assignees
Labels
area: USB Universal Serial Bus area: Windows Support Related to building Zephyr on Windows bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug Stale

Comments

@maxd-nordic
Copy link
Contributor

Describe the bug
Automatic driver installation does not work for the WebUSB sample. It just gets assigned the null GUID and is shown with a warning triangle. Zadig also shows that the device did not get the correct WICD. On Linux, the WebUSB stuff seems to work fine, so I presume this is mostly related to the MS OS 2.0 descriptors / BOS entry. The MS OS 1.0 stuff seems to be irrelevant for anything newer than Windows 7.

To Reproduce

  • Build the WebUSB sample with an nRF52 or nRF53 DK. (I don't think this is hardware-related.)
  • Plug into a Windows 10 machine or VM

Expected behavior
The WinUSB driver should be installed automatically, the device should not be should with a warning symbol in the device manager. The GUID should be reported correctly.

Impact
This is a showstopper for me since it prevents me from implementing my current project: A Zephyr implementation of CMSIS-DAP v2. The automatic driver installation part is mandatory to conform to the spec.

Environment (please complete the following information):

  • Windows 10
  • Zephyr 3.3.0
@maxd-nordic maxd-nordic added the bug The issue is a bug, or the PR is fixing a bug label Jun 20, 2023
@github-actions
Copy link

Hi @maxd-nordic! We appreciate you submitting your first issue for our open-source project. 🌟

Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙

@nordicjm nordicjm added area: USB Universal Serial Bus area: Windows Support Related to building Zephyr on Windows labels Jun 21, 2023
@carlescufi
Copy link
Member

This is a showstopper for me since it prevents me from implementing my current project: A Zephyr implementation of CMSIS-DAP v2. The automatic driver installation part is mandatory to conform to the spec.

Have you seen this? #53798

@carlescufi carlescufi added the priority: low Low impact/importance bug label Jun 21, 2023
@maxd-nordic
Copy link
Contributor Author

Yes, I'm trying to finish that one for Johann. :)

@tmon-nordic
Copy link
Contributor

The problem is definitely in MS OS 2.0 descriptor. One of the issue is that

0x02, /* Index of first interface this subset applies to. */

hardcodes the first interface index to 0x02 while the sample when built for nrf52840dk_nrf52840 has only one interface with number 0.

Changing the index itself doesn't seem to be enough though.

@maxd-nordic
Copy link
Contributor Author

This fixes the issue: #59758

@github-actions
Copy link

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: USB Universal Serial Bus area: Windows Support Related to building Zephyr on Windows bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug Stale
Projects
None yet
Development

No branches or pull requests

4 participants