Hi list, In testing syncing using a Blackberry 8700 with OS v4.5.0.180, I've found that occasionally the device stops responding to "get command table" commands.
Here's a usbmon capture of the issue: // Open the desktop mode f69b5600 200.496628 S Bo:1:015:4 - 24 = 00 00 18 00 07 ff 00 07 52 49 4d 20 44 65 73 6b ........ RIM Desk 6f 70 00 00 00 00 00 op..... f69b5600 200.497588 C Bo:1:015:4 0 24 > f69b5600 200.497616 S Bi:1:015:3 - 16384 < f69b5600 200.520640 C Bi:1:015:3 0 44 = 00 00 2c 00 08 05 00 07 52 49 4d 20 44 65 73 6b ..,..... RIM Desk 6f 70 00 00 00 00 00 00 00 00 00 01 00 04 00 op...... ....... f69b5600 200.520670 S Bi:1:015:3 - 16384 < f69b5600 200.521637 C Bi:1:015:3 0 12 = 00 00 0c 00 13 05 01 00 00 00 00 00 ........ .... // Open new socket f69b5600 200.521685 S Bo:1:015:4 - 8 = 00 00 08 00 0a 05 01 08 ........ f69b5600 200.522586 C Bo:1:015:4 0 8 > f69b5600 200.522614 S Bi:1:015:3 - 16384 < f69b5600 200.523637 C Bi:1:015:3 0 8 = 00 00 08 00 10 05 01 08 ........ // Load command table f69b5600 200.523681 S Bo:1:015:4 - 10 = 05 01 0a 00 40 00 00 01 00 00 ....@... .. f69b5600 200.524585 C Bo:1:015:4 0 10 > f69b5600 200.524639 S Bi:1:015:3 - 16384 < // 30 second timeout here f69b5600 230.527107 C Bi:1:015:3 -2 0 // I hacked the library to clearhalt at this point and try again f69b5600 230.527461 S Co:1:015:0 s 02 01 0000 0083 0000 0 f69b5600 230.529053 C Co:1:015:0 0 0 f69b5600 230.529075 S Co:1:015:0 s 02 01 0000 0004 0000 0 f69b5600 230.530053 C Co:1:015:0 0 0 // second try: f69b5600 230.530100 S Bo:1:015:4 - 10 = 05 01 0a 00 40 00 00 01 00 00 ....@... .. f69b5600 230.531055 C Bo:1:015:4 0 10 > f69b5600 230.531187 S Bi:1:015:3 - 16384 < // another 30 second timeout f69b5600 260.533573 C Bi:1:015:3 -2 0 // amazingly, the device responds to "close socket" efae6b80 260.627881 S Bo:1:015:4 - 8 = 00 00 08 00 0b 05 01 08 ........ efae6b80 260.629521 C Bo:1:015:4 0 8 > efae6b80 260.629588 S Bi:1:015:3 - 16384 < efae6b80 260.630565 C Bi:1:015:3 0 8 = 00 00 08 00 0c 05 01 08 ........ This has me very puzzled. It doesn't always happen, and it usually happens at the end of a sync where barry-sync is updating dirty flags. As this is the usbmon log, I'm fairly sure (!) the messages are getting to the device. So it seems that the firmware just decides not to respond at this point. The screen is not in the desktop mode when this happens, but I can use the device. This is odd, since in other testing, immediately after the following "open socket" command: 00 00 08 00 0a 05 01 08 ........ the screen changes to "connecting to desktop". This not the case when the firmware stops responding, yet the firmware seems to respond with a successful open command. I figured I'd post this just to record my progress, and in case folks have any brainwaves. :-) Thanks, - Chris ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
