On Mon, 17 Feb 2014, Phil Dibowitz wrote: > Great idea! We are getting them all here. Check this out (this is a stripped > down version of the debug). Note that I'm blindly printing the second byte in > any packet that comes in, not checking if it's one our response types or not. > > PHIL: hid_report_callback: seq: 11 > DEBUG (ReadFlash): Expected seq 11, got 11 > DEBUG (ReadFlash): Next expected seq 22 > PHIL: hid_report_callback: seq: 50 > PHIL: hid_report_callback: seq: 01 > DEBUG (ReadFlash): Expected seq 01, got 01 > DEBUG (ReadFlash): Next expected seq 12 > PHIL: hid_report_callback: seq: 12 > DEBUG (ReadFlash): Expected seq 12, got 12 > DEBUG (ReadFlash): Next expected seq 23 > PHIL: hid_report_callback: seq: 23 > DEBUG (ReadFlash): Expected seq 23, got 23 > DEBUG (ReadFlash): Next expected seq 34 > PHIL: hid_report_callback: seq: 34 > DEBUG (ReadFlash): Expected seq 34, got 34 > DEBUG (ReadFlash): Next expected seq 45 > PHIL: hid_report_callback: seq: 45 > DEBUG (ReadFlash): Expected seq 45, got 45 > DEBUG (ReadFlash): Next expected seq 56 > PHIL: hid_report_callback: seq: 56 > PHIL: hid_report_callback: seq: 67 > PHIL: hid_report_callback: seq: 78 > PHIL: hid_report_callback: seq: 89 > PHIL: hid_report_callback: seq: 9a > PHIL: hid_report_callback: seq: ab > PHIL: hid_report_callback: seq: bc > PHIL: hid_report_callback: seq: cd > PHIL: hid_report_callback: seq: de > DEBUG (ReadFlash): Expected seq 56, got 56 > DEBUG (ReadFlash): Next expected seq 67 > DEBUG (ReadFlash): Expected seq 67, got 67 > DEBUG (ReadFlash): Next expected seq 78 > DEBUG (ReadFlash): Expected seq 78, got 78 > DEBUG (ReadFlash): Next expected seq 89 > DEBUG (ReadFlash): Expected seq 89, got 89 > DEBUG (ReadFlash): Next expected seq 9A > DEBUG (ReadFlash): Expected seq 9A, got 9A > DEBUG (ReadFlash): Next expected seq AB > DEBUG (ReadFlash): Expected seq AB, got AB > DEBUG (ReadFlash): Next expected seq BC > DEBUG (ReadFlash): Expected seq BC, got BC > DEBUG (ReadFlash): Next expected seq CD > DEBUG (ReadFlash): Expected seq CD, got CD > DEBUG (ReadFlash): Next expected seq DE > DEBUG (ReadFlash): Expected seq DE, got DE > DEBUG (ReadFlash): Next expected seq EF > PHIL: hid_report_callback: seq: 11 > DEBUG (ReadFlash): Expected seq EF, got 11 > DEBUG (ReadFlash): Invalid sequence want: EF got: 11
So the packets are getting dropped before they even get to hid_report_callback. Darn. > DEBUG (ReadFlash): Next expected seq CD > DEBUG (ReadFlash): Expected seq CD, got CD > DEBUG (ReadFlash): Next expected seq DE > DEBUG (ReadFlash): Expected seq DE, got DE > DEBUG (ReadFlash): Next expected seq EF > PHIL: hid_report_callback: seq: 11 > DEBUG (ReadFlash): Expected seq EF, got 11 > DEBUG (ReadFlash): Invalid sequence want: EF got: 11 It's kind of weird that it is always the EF packet that is being dropped, though. I think you've shown dumps where other packets got dropped, though right? > I have a hard time believing this just blatanly doesn't work in Mac though... > as I said the official software manages to work. The official software doesn't do config dumping, though. ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
