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?
Thanks. Perhaps physical detection on connect/disonnect will suffice. These should be detectable events correct? I experimented with this in the past, setting breakpoints at the ISR and seeing what get executed when I physically connect and disconnect USB. This was sometimes problematic as it seems that Keil debugger has problems hitting breakpoinrs in ISR.