[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bluetooth-dev] bluetooth.c USB driver won't recognize Ericssondevice




Hello Greg,

I ignored the error messages described in my previous posting and
recompiled the OpenBT tree from the beginning of May with the
CONFIG_BLUETOOTH_USBMODULE defined instead of CONFIG_BLUETOOTH_ERICSSON.
(I also ignored the comment beside the #define statement saying that this
option is not implemented).

I was able to run "cat /dev/ttyUB0" without getting "no such device"
message.

However, I got response timeouts when running "bti -u /dev/ttyUB0" or "btd
-u /dev/ttyUB0 -m".  I attached the dmesg logs below.

Ilguiz

=======================================================================
>
> BT (driver) bt_open on line 7
> BT (driver) Registering tty on line 7
> BT SYS: Now 1 open fd:s for ttyBTC
> BT (driver) bt_close on line 7
> BT (driver) Unregistering tty on line 7
> bluetooth.c: bluetooth_ioctl - cmd 0x5401
> bluetooth.c: bluetooth_ioctl - cmd 0x5402
> bluetooth.c: bluetooth_set_termios
> bluetooth.c: bluetooth_ioctl - cmd 0x5401
> bluetooth.c: bluetooth_chars_in_buffer - returns 0
> bluetooth.c: bluetooth_chars_in_buffer - returns 0
> BT (ldisc) bt_tty_open
> BT SYS: Setting BT driver to use serial tty
> BT (driver) bt_open on line 7
> BT (driver) Registering tty on line 7
> BT SYS: Now 1 open fd:s for ttyBTC
> BT SYS: Initialising Bluetooth Stack
> BT SYS: Current HW: USB
> BT SYS: hci_init, Initialising HCI
> BT SYS: HCI emulator off
> BT SYS: hci_init, Initialising HCI inbuffers [800]
> BT SYS: hci_init, Reading buffer sizes in the module...
> bluetooth.c: bluetooth_write_room
> bluetooth.c: bluetooth_write_room - returns 3072
> bluetooth.c: bluetooth_write - 4 byte(s)
> bluetooth.c: bluetooth_write - length = 4, data = 01 05 10 00
> cmd_pkt from interrupt!
> cmd_timeout, Timeout when waiting for command response
> BT SYS: ERROR :hci_read_firmware_rev_info [Generic] not supported.
> BT SYS: hci_init, Host flow control not enabled
> BT SYS: M/S switch disabled
> BT SYS: Initialising L2CAP
> bluetooth.c: bluetooth_write_room
> bluetooth.c: bluetooth_write_room - returns 3072
> bluetooth.c: bluetooth_write - 4 byte(s)
> bluetooth.c: bluetooth_write - length = 4, data = 01 09 10 00
> cmd_pkt from interrupt!
> cmd_timeout, Timeout when waiting for command response
> BT SYS: ERROR :l2cap_init: Failed to get local BD addr
> BT SYS: Initialising RFCOMM
> BT SYS: Initialising SDP
> BT SYS: sdp_init, Init sdp as server
> BT SYS: Initialising TCS
> BT SYS: Initialising BTMEM [2500 bytes]
> bluetooth.c: bluetooth_write_room
> bluetooth.c: bluetooth_write_room - returns 3072
> bluetooth.c: bluetooth_write - 7 byte(s)
> bluetooth.c: bluetooth_write - length = 7, data = 01 24 0c 03 00 03 02
> cmd_pkt from interrupt!
> cmd_timeout, Timeout when waiting for command response
> bluetooth.c: bluetooth_write_room
> bluetooth.c: bluetooth_write_room - returns 3072
> bluetooth.c: bluetooth_write - 252 byte(s)
> bluetooth.c: bluetooth_write - length = 252, data = 01 13 0c f8 41 58 49 53 20
> 28 74 65 73 74 62 65 64 29 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00
> cmd_pkt from interrupt!
> cmd_timeout, Timeout when waiting for command response
> BT (driver) setting write scan enable : [0x3]
> bluetooth.c: bluetooth_write_room
> bluetooth.c: bluetooth_write_room - returns 3072
> bluetooth.c: bluetooth_write - 5 byte(s)
> bluetooth.c: bluetooth_write - length = 5, data = 01 1a 0c 01 03
> cmd_pkt from interrupt!
> cmd_timeout, Timeout when waiting for command response
> BT (driver) setting write page scan activity : [0x800,0x12]
> bluetooth.c: bluetooth_write_room
> bluetooth.c: bluetooth_write_room - returns 3072
> bluetooth.c: bluetooth_write - 8 byte(s)
> bluetooth.c: bluetooth_write - length = 8, data = 01 1c 0c 04 00 08 12 00
> cmd_pkt from interrupt!
> cmd_timeout, Timeout when waiting for command response
> bluetooth.c: bluetooth_write_room
> bluetooth.c: bluetooth_write_room - returns 3072
> bluetooth.c: bluetooth_write - 7 byte(s)
> bluetooth.c: bluetooth_write - length = 7, data = 01 05 0c 03 4c fa ff
> cmd_pkt from interrupt!
> cmd_timeout, Timeout when waiting for command response
> BT (driver) bt_open on line 7
> BT (driver) Registering tty on line 7
> BT SYS: Now 2 open fd:s for ttyBTC
> BT (driver) bt_close on line 7
> BT (driver) Unregistering tty on line 7
> BT (driver) bt_open on line 7
> BT (driver) Registering tty on line 7
> BT SYS: Now 2 open fd:s for ttyBTC
> BT (driver) bt_ioctl: HCIREADLOCALBDADDR
> bluetooth.c: bluetooth_write_room
> bluetooth.c: bluetooth_write_room - returns 3072
> bluetooth.c: bluetooth_write - 4 byte(s)
> bluetooth.c: bluetooth_write - length = 4, data = 01 09 10 00
> cmd_pkt from interrupt!
> cmd_timeout, Timeout when waiting for command response
> BT (driver) bt_ioctl: HCINQUIRY
>
> hci_inquiry (9)
>    0x01 0x01 0x04 0x05 0x33 0x8b 0x9e 0x03 0x01
> bluetooth.c: bluetooth_write_room
> bluetooth.c: bluetooth_write_room - returns 3072
> bluetooth.c: bluetooth_write - 9 byte(s)
> bluetooth.c: bluetooth_write - length = 9, data = 01 01 04 05 33 8b 9e 03 01
> cmd_pkt from interrupt!
> inq_timeout, Timeout when waiting for inquiry response
> BT (driver) bt_close on line 7
> BT (driver) Unregistering tty on line 7
>
=======================================================================

On Tue, 5 Jun 2001, Greg KH wrote:

> The device was found, and attached to ttyUB0.  The other 4 messages are
> the driver complaining about the fact that it doesn't know how to talk
> to the SCO interfaces that the Ericsson device exports.  Since the Axis
> stack also doesn't know how to use SCO, there isn't a problem.
>
>
> > usb.c: USB disconnect on device 5
> > bluetooth.c: Bluetooth converter now disconnected from ttyUB0
>
> Now you removed the device.
>
> So have you tried using the device?  Or just stopped when you saw the
> "driver not bound." messages?




-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com