On Sat, Jan 26, 2013 at 8:41 PM, Wander Lairson Costa <wander.lair...@gmail.com> wrote: > I have been playing with (my modified version) benchmark firmware > regarding this question. After I change it to use the mBDT_GetLength > to get the number of bytes transfered (diff bellow), it now always > transmit only 16 bytes per packet when the number of bytes is 16 or > more: > > Despite the fact libusb says it transmitted 32 bytes, mBDT_GetLength > reports that only 16 were actually read.
I will need to take a look at the firmware again. I admit I have not touched much about the Microchip stack over the past several years. And this is even more true for the isochronous transfer. The last time I really deeply look into isochronous transfer was back in 2007 where a few of us struggled to get a simple isoc transfer example working on both the firmware side and more so on the host side. http://www.microchip.com/forums/m270049.aspx -- Xiaofan ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel