![]() When I use the new driver that you built I still see that the class is 2 and the subclass is 0xFF, could you double-check that file? Hi for getting back to me and sorry for the delay in my response. This post also suggests that for Windows 10 this feature needs to use class 2 and subclass 2. Here’s a web post on the Microchip forum which describes the same problem that I have run into with Windows 10. I have this working very well already on Windows 7, but it doesn’t work on Windows 10. This is way more convenient for end users than grappling with WinUSB. The function driver in causes Windows to load the usbser.sys driver, which creates a virtual COM port which can then be opened by any terminal client on the PC by opening a port with a name like “COM40”. The topic I was discussing with in this thread is about, which is different from the. There is a page elsewhere on the Toradex site that talks about how to do this: I have created a DLL for my customers which hides the complexity of WinUSB from them and provides a simple API. This works well, but using WinUSB is really only practical in my code and it’s not something that most of my end-customers want to deal with in their own code. I then use the low-level WinUSB driver in Windows to open a USB end-point on the PC which is connected to COM0 on the Colibri module. What I do is disable ActiveSync on the Colibri and then I wrote an inf file for Windows to recognize my VID and PID. I already have working for both Windows 7 and Windows 10 with my own VID and PID. Hi for your answer, but I think your answer is for a different question than the one I asked. Therefore I would appreciate your feedback whether this is a good solution or if there are any important things I missed in my description. Please refer to the following article how to disable ActiveSync:Īctually we never used the serial connection like this before. ![]() So if you open a terminal program on the PC, you will see some messages CLIENTCLIENTCLIENT or similar. So maybe there’s a better way to configure the combination Colibri / PC.Īnyway, WinCe still attaches WMDC to this interface. ![]() It seems to be a bug in the driver that this setting is required at all (The driver sets the Product ID to a fixed value of 0x0079, then overwrites it with the mandatory registry setting idProduct). The idProduct setting instructs the Windows 10 PC to load a different driver - “Palm Treo Modem”.The DeviceArrayIndex actually changes the behavior of the driver.However, I found another setting which could work: This was expected, as the subclass defines the CDC control model (0x02 = Abstract Control Model, 0xff = vendor specific control model). show originalĭear modified the driver to test changing the Interface Class / Subclass to 0x02 / 0x02, and it didn’t work. ServiceName="Microsoft USB Serial Driver"ĬlassGuid=ĭriverPackageDisplayName=%DriverPackageDisplayName% inf file from someone else which worked with my T20: pololu/p-star-examples/blob/master/drivers/p-star-serial.inf Copyright (C) 2016 Pololu CorporationĭriverPackageDisplayName="P-Star Virtual COM Port Drivers" How to use or to reference the Usbser.sys driver from universal serial bus (USB) modem. I found this article from Microsoft which contained some clues but was not very specific: inf file for Windows to tell it which driver to load. Changing the registry on the T20 was the easy part, the hard part was creating a.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |