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

[bluetooth-dev] SDP Problem with Mitsumi USB Dongle



Hi,

I got a little problem between OpenBT's SDP server and a Mitsumi USB Dongle.

Our demonstrator that uses OpenBT on a PowerPC works fine against some PCMCIA cards.
Now I tried a Mitsumi USB against the OpenBT box.

I got a strange behavior when the Mitsumi (Extended systems stack) soft tries to connect to
OpenBT. The USB dongle always connects to the wrong RFCOMM server channel.

Here is are some lines from my sdp.xml:

       <LANAccessUsingPPP ServiceRecordHandle = "0x0010ffff">
...
	    <RFCOMM type = "DES" Parameter0 = "0x0803">
             </RFCOMM>
...
       </LANAccessUsingPPP>

       <DialupNetworking ServiceRecordHandle = "0x0011ffff">
...
	    <RFCOMM type = "DES" Parameter0 = "0x0802">
             </RFCOMM>
...
       </DialupNetworking>

       <SerialPort ServiceRecordHandle = "0x0100ffff">
...
	    <RFCOMM type = "DES" Parameter0 = "0x0801">
             </RFCOMM>
...
       </SerialPort>

My btd application does a huge switch on the rfcomm channel the clients connects to:

	switch(rfcomm_chan):
	{
		case 1:
		start_my_special_serial_port_app();
		case 2:
		case 3:
		start_LAN_DUP_server():
	}

With the above settings multiple BT peers work fine.

The Mitsumi USB dongle connects to the following rfcomm channels:

	LAN: DLCI 2, RFCOMM channel 1
	DUP: DLCI 2, RFCOMM channel 1
	SPP: DLCI 4, RFCOMM channel 2

How can that happen ?? Is this a bug in the extended systems stack that is used by Mitsumi
or is this an OpenBT bug ?

Here is a SDP log when the USB dongle does service discovery:

Jan  1 01:01:17 (none) daemon.warn klogd:
Jan  1 01:01:17 (none) daemon.warn klogd: sdp_receive_data (21):
Jan  1 01:01:17 (none) daemon.warn klogd: 0x06 0x00 0x00 0x00 0x10 0x35 0x03 0x19 0x10 0x02 0x00 0x64 0x35 0x06 0x09 0x00
Jan  1 01:01:17 (none) daemon.warn klogd: 0x00 0x09 0x00 0x01 0x00
Jan  1 01:01:17 (none) daemon.warn klogd:           SDP sdp_database_write preparing to send 101 bytes data to sdp_con[0]
Jan  1 01:01:17 (none) daemon.warn klogd:
Jan  1 01:01:17 (none) daemon.warn klogd: Data to be sent to client: (101):
Jan  1 01:01:17 (none) daemon.warn klogd: 0x07 0x00 0x00 0x00 0x60 0x00 0x5d 0x36 0x00 0x5a 0x35 0x10 0x09 0x00 0x00 0x0a
Jan  1 01:01:17 (none) daemon.warn klogd: 0x00 0x00 0x00 0x00 0x09 0x00 0x01 0x35 0x03 0x19 0x10 0x00 0x35 0x10 0x09 0x00
Jan  1 01:01:17 (none) daemon.warn klogd: 0x00 0x0a 0x00 0x10 0x00 0x00 0x09 0x00 0x01 0x35 0x03 0x19 0x10 0x01 0x35 0x10
Jan  1 01:01:17 (none) daemon.warn klogd: 0x09 0x00 0x00 0x0a 0x00 0x10 0xff 0xff 0x09 0x00 0x01 0x35 0x03 0x19 0x11 0x02
Jan  1 01:01:17 (none) daemon.warn klogd: 0x35 0x10 0x09 0x00 0x00 0x0a 0x00 0x11 0xff 0xff 0x09 0x00 0x01 0x35 0x03 0x19
Jan  1 01:01:17 (none) daemon.warn klogd: 0x11 0x03 0x35 0x10 0x09 0x00 0x00 0x0a 0x01 0x00 0xff 0xff 0x09 0x00 0x01 0x35
Jan  1 01:01:17 (none) daemon.warn klogd: 0x03 0x19 0x11 0x01 0x00
Jan  1 01:01:17 (none) daemon.warn klogd:
Jan  1 01:01:17 (none) daemon.warn klogd: l2cap options:  (0):
Jan  1 01:01:17 (none) daemon.warn klogd:
Jan  1 01:01:17 (none) daemon.warn klogd: sdp_receive_data (20):
Jan  1 01:01:17 (none) daemon.warn klogd: 0x04 0x00 0x01 0x00 0x0f 0x00 0x10 0x00 0x00 0x00 0x64 0x35 0x06 0x09 0x00 0x00
Jan  1 01:01:17 (none) daemon.warn klogd: 0x09 0x00 0x01 0x00
Jan  1 01:01:17 (none) daemon.warn klogd:           SDP sdp_database_write preparing to send 26 bytes data to sdp_con[0]
Jan  1 01:01:17 (none) daemon.warn klogd:
Jan  1 01:01:17 (none) daemon.warn klogd: Data to be sent to client: (26):
Jan  1 01:01:17 (none) daemon.warn klogd: 0x05 0x00 0x01 0x00 0x15 0x00 0x12 0x35 0x10 0x09 0x00 0x00 0x0a 0x00 0x10 0x00
Jan  1 01:01:17 (none) daemon.warn klogd: 0x00 0x09 0x00 0x01 0x35 0x03 0x19 0x10 0x01 0x00
Jan  1 01:01:17 (none) daemon.warn klogd:
Jan  1 01:01:17 (none) daemon.warn klogd: HW module contains...
Jan  1 01:01:17 (none) daemon.warn klogd: 8 ACL buffers at 672 bytes
Jan  1 01:01:17 (none) daemon.warn klogd: 0 SCO buffers at 0 bytes
Jan  1 01:01:17 (none) daemon.warn klogd:

Any ideas are welcome.

Matthias


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