Tim Lowery
2003-04-08 03:23:43 UTC
Hi All,
I've been trying the characterize the problem with the serial
communications on the Mac. It's not uncommon for the serial connection
to fail after "Get Phone Data" the first time the application is
launched. Below is a portion of the protocol log for a successful
switch to Brew mode.
/dev/tty.usbserial0: Writing - Data 5 bytes
00000000 59 0c c4 c1 7e
/dev/tty.usbserial0: Begin reading until - Data 1 bytes
00000000 7e
/dev/tty.usbserial0: Read completed - Data 10 bytes
00000000 59 0c 00 b0 28 1f 00 4e 3c 7e
Here's the same portion of the protocol log for a failed switch to Brew
mode.
/dev/tty.usbserial0: Writing - Data 5 bytes
00000000 59 0c c4 c1 7e
/dev/tty.usbserial0: Begin reading until - Data 1 bytes
00000000 7e
/dev/tty.usbserial0: Read completed - Data 9 bytes
00000000 0c 00 b0 28 1f 00 4e 3c 7e
Note the last two lines of each log. It appears that the first byte
(hex 59) is dropped in the response from the phone.
This is my observation with all the serial failures I've encountered in
my testing. After the serial connection fails (displaying 8-6-2
alert), it almost always succeeds the 2nd time. And, without altering
the port setting on the phone. It doesn't seem to matter how the port
is selected on the phone. I'm able to consistently establish serial
connection whether it's in RS232, USB, or Closed.
My practice is to power-off the phone before connecting or
disconnecting to the cable.
Any thoughts on the above? How reliable is the serial communication on
the Windows side?
Tim
I've been trying the characterize the problem with the serial
communications on the Mac. It's not uncommon for the serial connection
to fail after "Get Phone Data" the first time the application is
launched. Below is a portion of the protocol log for a successful
switch to Brew mode.
/dev/tty.usbserial0: Writing - Data 5 bytes
00000000 59 0c c4 c1 7e
/dev/tty.usbserial0: Begin reading until - Data 1 bytes
00000000 7e
/dev/tty.usbserial0: Read completed - Data 10 bytes
00000000 59 0c 00 b0 28 1f 00 4e 3c 7e
Here's the same portion of the protocol log for a failed switch to Brew
mode.
/dev/tty.usbserial0: Writing - Data 5 bytes
00000000 59 0c c4 c1 7e
/dev/tty.usbserial0: Begin reading until - Data 1 bytes
00000000 7e
/dev/tty.usbserial0: Read completed - Data 9 bytes
00000000 0c 00 b0 28 1f 00 4e 3c 7e
Note the last two lines of each log. It appears that the first byte
(hex 59) is dropped in the response from the phone.
This is my observation with all the serial failures I've encountered in
my testing. After the serial connection fails (displaying 8-6-2
alert), it almost always succeeds the 2nd time. And, without altering
the port setting on the phone. It doesn't seem to matter how the port
is selected on the phone. I'm able to consistently establish serial
connection whether it's in RS232, USB, or Closed.
My practice is to power-off the phone before connecting or
disconnecting to the cable.
Any thoughts on the above? How reliable is the serial communication on
the Windows side?
Tim