[Bluez-users] SCO syncronization taking down USB dongle

[Gareth Bradley <gareth.bradley.nz@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]

Hello. I am currently writing code for voice connections using a Motorla
HS850 headset and the BlueZ stack on a Intrinsyc Cerf 255PXA board (a small
form mobile PC). I can currently make successful SCO connections to the
headset, but they sometimes crash, and take the whole USB dongle with it.
(Running 'hciconfig hci0 up' fixes it).

Here is the crash printout:
usb.c: USB disconnect on device 2
Receive failed: Broken pipe
hub.c: USB new device connect on bus1/2, assigned device number 3

I have a stream of incoming voice (from a Windows PDA) which is buffered. I
read from the SCO connection stream (and consistently get 48 byte packets),
and write in an amount from the receive buffer into the headset. This coice
connection works fine.

I've tried using FD_ZERO, FD_SET and FD_ISSET before all read and writes,
but still to no avail. I am able to get it to crash within a minute if I
deliberately write data chunks slightly out with the amount read from the
device (read 48, then write 47, or 46, or 49...).

I notice that flow (and error) control appear on the Todo list, but is there
some way to guard against the whole dongle being taken down?

[-- Attachment #2: Type: text/html, Size: 1232 bytes --]