> Harold Hallikainen wrote: >> Is CDC the most appropriate class to use in such an application? I'm >> just sending ascii commands and getting responses. > > CDC will make your device look like a COM port. It has the advantage that > the driver is built into the OS, but comes with hassles too. The > application has to let the user chose the COM port, since there is no way > to > know what it is ahead of time. Then there's the hassle of figuring out > which COM port number the system picked for your device. > > It would be nice if there was a standard USB device type that presented > like > a bidirection stream of bytes to the application. Until we have something > like that, I use my own conventions and driver to go with them. Endpoints > 0 > are used for private communication with the driver and the OS, and > endpoints > 1 implement the application visible bidirection stream of bytes. The > USBProg PIC programmer, for example, is layered on this mechanism. > Thanks for the comments! It would indeed be really great if there were a simple bidirectional stream of bytes implemented (just like a uart!). We could identify the device by VID/PID or the ID string. I see Microchip includes a "Generic" USB demo. I'll play with this when I get back to work. On another issue I'm having with the PIC32, I copied the demo files in to a new directory to build my own project. I set the directories to search the files in the /Microchip Solutions directories. The code compiles fine, downloads in to the PIC32 starter board fine, runs fine, EXCEPT it appears that variables that are initialized in their declaration are not initialized. Using the debugger on the PIC32 Starter Board, I can look at a couple strings that are initialized in their declarations. They are null strings. I can't find any compiler option to enable or disable initialization during declaration (I recall C18 had several startup files, some of which skipped variable initialization). Ideas? Thanks! Harold -- FCC Rules Updated Daily at http://www.hallikainen.com - Advertising opportunities available! -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist