Yes, it can be a Windows driver problem. Try to install it on a clean system if you can or, try a Live Linux distribution CD/DVD (just to be sure the problem is not from your microcontroller)... If my version of library do not differ from your, then what you saw in a loop is commented in the header. But read and write functions use that function and never read or write if USB connection is not available.
Vasi On Nov 22, 4:26 pm, phalox <[email protected]> wrote: > I had a look within the USB library, and there it also a check for > usb_cdc_line_status() but this time in a while loop. > That means that the entire library wouldn't do anything as long as te > status isn't ready. > > Are there means to debug the usb on the windows side? I heard today in > class that the drivers are harder to implement than the firmware on > the PIC is, which could mean that the problem is most probably on the > windows side... > > On 21 nov, 15:54, phalox <[email protected]> wrote: > > > I tried the commenting, but it still does the same... > > > In my terminal program there isn't any echo when I send it a char. > > Neither I'm getting the welcome message (but that's normal now, since > > I commented it...) > > > Any other suggestions? -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
