We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I need to write a custom USB controller to communicate with a PC. Over the USB we will perform firmware upgrades, upload new operating parameters, download device performance data, etc. The PC side will use WinUSB mechanism to manage the USB device. I need to implement the USB control using a single interface with 2 bulf transfer endpoints, input and output. Have experimented with the USB CDC device example that came with the Keil toolset. I was thinking of taking that example and modify the descriptors and remove any unneeded logic that implemeted the CDC device and add what I need for my project.
Does this seem like a reasonebly place to start? For example, are the handling of the control endpoint esentially the same regardless of device class type?
"I have been trying to find a place to download the WdfCoInstaller01005.dll."
WdfCoInstaller01005.dll is included in the old release of WDK. But for new design, use the latest version. The number after "WdfCoInstaller" shows the version.
Tsuneo
Thanks for all the valuable information over time.
If I may, I do have a related, more generic question. If a new USB device is being developed what sort of analysis would you suggest as to determine if it should support a standard or custom device class?
In general the types of devices I would deal with would: (1) Generally perform some osrt of control or measurement (1) not clearly fall into a standard device (2) Not data intensive, that is they would not be required to send out large volumes of data with critical timing constraints (3) Need to be able to update the device firmware over USB (4) Need to work with a variety of Window OS's
It sounds like HID can be streteched to fit a wide variety of devices, with the advantage if existing HID drivers for the PC end of things.