|
From: Phani K. <pha...@gm...> - 2016-03-25 05:50:27
|
Thanks Alan. The code is working now and I am not resetting the toggle at all. 1. I assume I have to reset the toggle only when an endpoint halts for this device? 2. Usually in our code, we send reset toggle (by clearing halt feature) on every pipe initialize. All other devices work with this code. However this device is vendor defined and it is not accepting this behavior. How can I differentiate this behavior only for this device and how windows works in the same scenario? Any idea? Regards Phani On Wed, Mar 23, 2016 at 10:17 PM, Alan Stern <st...@ro...> wrote: > On Wed, 23 Mar 2016, Phani Kumar wrote: > > > Hi > > > > After debugging using USB analyzer, came to know its toggle endpoint > issue. > > However facing another issue because of toggle. > > Kindly help. > > > > My application has : > > > > write to endpoint 2 > > read from endpoint 81 > > > > First time it works successfully. If I run the application second time, > it > > fails again. > > > > Do I need to do reset the toggle bit after every transfer? Kindly help > > You do not need to reset the toggle bit after every transfer. > > Probably the problem is that your program is doing something to reset > the toggle when it shouldn't. For example, your program may issue an > unneeded Set-Interface or Set-Configuration request. > > Alan Stern > > |