[riot-notifications] [RIOT-OS/RIOT] nrfusb: Fix data stage handling of control writes (#12269)

benpicco notifications at github.com
Wed Sep 25 16:47:04 CEST 2019


I'm trying to run this on Windows (together with #12269) - it's more involved than I would have thought!
Windows does not simply bind a driver based on the class, but expects you to have a driver that matches the USB ID. There doesn't seem to be a generic CDC ACM driver.

After some google search I found [Silabs-CDC_Install.zip](https://www.silabs.com/content/usergenerated/asi/cloud/attachments/siliconlabs/en/community/mcu/32-bit/forum/_jcr_content/content/primary/qna/usb_cdc_and_virtualc-xz9d/i_think_if_you_updat-kSkx/Silabs-CDC_Install.zip). I selected the first VID/PID combination from the `.inf` file and compiled RIOT with that.

The driver binds to the device, I can connect to it with [hterm](http://www.der-hammer.info/terminal/), but send some data to it, I get no response.

I'm not sure if this is due to the sketchy driver or due to RIOT.

![usb](https://user-images.githubusercontent.com/1301112/65611947-d65bef00-dfb3-11e9-98d6-f9b84e0e44b6.png)

On Linux everything works out of the box.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/12269#issuecomment-535058705
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190925/05dfd7bc/attachment.htm>


More information about the notifications mailing list