Hi list,
I try to run an HAMA BT Headset connected through a Linksys BT USB
adapter on my notebook.
I got to install alsa modules and the other BT softs. My outputs are:
dmesg [...]
Bluetooth: L2CAP ver 2.6
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM ver 1.3
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
snd-bt-sco revision 1.4 $
snd-bt-sco: snd-bt-scod thread starting
nomade:/home/dh#
nomade:~# hciconfig -a
hci0: Type: USB
BD Address: 00:0C:41:E2:4C:B0 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:2539 acl:39 sco:0 events:103 errors:0
TX bytes:1246 acl:38 sco:0 commands:41 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'nomade-0'
Class: 0x000100
Service Classes: Unspecified
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP
Subver: 0x20d
Manufacturer: Cambridge Silicon Radio (10)
nomade:~# hcitool info 00:0b:2e:06:01:2e
Requesting information ...
BD Address: 00:0b:2e:06:01:2e
Device Name: BT1000
LMP Version: 1.1 (0x1) LMP Subversion: 0x405
Manufacturer: Transilica, Inc. (24)
Features: 0xff 0xf9 0x31 0x00 0x00 0x00 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot
offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <SCO link> <HV2 packets> <HV3 packets>
<u-law log> <A-law log> <CVSD>
I launch btsco
nomade:/home/dh# btsco 00:0b:2e:06:01:2e
Device is 1:0
Voice setting: 0x0060
RFCOMM channel 6 connected
and that's all. Hcidump -X outputs are (notice the unexpected errors):
nomade:/home/dh# hcidump -X
HCIDump - HCI packet analyzer ver 1.12
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
0000: 2e 01 06 2e 0b 00 18 cc 02 00 00 00 01 .............
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 05 04 ....
> HCI Event: Link Key Request (0x17) plen 6
0000: 2e 01 06 2e 0b 00 ......
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
0000: 2e 01 06 2e 0b 00 e3 29 89 d3 51 2c 66 c5 d2 16 .......)..Q,f...
0010: 20 fa 9e 46 f3 73 ..F.s
> HCI Event: Command Complete (0x0e) plen 10
0000: 01 0b 04 00 2e 01 06 2e 0b 00 ..........
> HCI Event: Connect Complete (0x03) plen 11
0000: 00 29 00 2e 01 06 2e 0b 00 01 00 .).........
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
0000: 29 00 0f 00 )...
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 0
> HCI Event: Command Complete (0x0e) plen 6
0000: 01 0d 08 00 29 00 ....).
> HCI Event: Max Slots Change (0x1b) plen 3
0000: 29 00 05 )..
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
> ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
MTU 48
< ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
< ACL data: handle 0x0029 flags 0x02 dlen 24
L2CAP(d): cid 0x0040 len 20 [psm 1]
SDP SSA Req: tid 0x0 len 0xf
pat uuid-16 0x1108 (Headset)
max 0xffff
aid(s) 0x0000 - 0xffff
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 27
> ACL data: handle 0x0029 flags 0x01 dlen 24
L2CAP(d): cid 0x0040 len 47 [psm 1]
SDP SSA Rsp: tid 0x0 len 0x2a
cnt 0x26
srv rec #0
aid 0x0000 (SrvRecHndl)
uint 0x20000
aid 0x0001 (SrvClassIDList)
< uuid-16 0x1108 (Headset) uuid-16 0x1203 (Audio) >
aid 0x0004 (ProtocolDescList)
< < uuid-16 0x0100 (L2CAP) > <
uuid-16 0x0003 (RFCOMM) null null > >
cont
< ACL data: handle 0x0029 flags 0x02 dlen 25
L2CAP(d): cid 0x0040 len 21 [psm 1]
SDP SSA Req: tid 0x1 len 0x10
pat uuid-16 0x1108 (Headset)
max 0xffff
aid(s) 0x0000 - 0xffff
cont 01 01
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 27
> ACL data: handle 0x0029 flags 0x01 dlen 22
L2CAP(d): cid 0x0040 len 45 [psm 1]
SDP SSA Rsp: tid 0x1 len 0x28
cnt 0x24
ERROR: Unexpected syntax
0000: 06 09 00 05 35 03 19 10 02 09 00 06 35 09 09 65
....5.......5..e
0010: 6e 09 00 6a 09 01 00 09 01 00 25 07 48 65 61 64
n..j......%.Head
0020: 73 65 74 01 02 set..
cont 06 09 00 05 35 03 19 10 02 09 00 06 35 09 09 65 6E 09 00
6A 09 01 00 09 01 00 25 0748 65 61 64 73 65 74 01 02
< ACL data: handle 0x0029 flags 0x02 dlen 25
L2CAP(d): cid 0x0040 len 21 [psm 1]
SDP SSA Req: tid 0x2 len 0x10
pat uuid-16 0x1108 (Headset)
max 0xffff
aid(s) 0x0000 - 0xffff
cont 01 02
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 1]
SDP SSA Rsp: tid 0x2 len 0x8
cnt 0x5
ERROR: Unexpected syntax
0000: 03 02 28 01 00 ..(..
cont 03 02 28 01 00
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< HCI Command: Read Voice Setting (0x03|0x0025) plen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> HCI Event: Command Complete (0x0e) plen 6
0000: 01 25 0c 00 60 00 .%..`.
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0041
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0041 result 0 status 0
< ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0041 flags 0x0000 result 0 clen 4
MTU 1024
> ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0041 flags 0x0000 clen 4
MTU 317
< ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
< ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 0x0029 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 12 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 312 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 18
L2CAP(d): cid 0x0041 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 12 frame_type 0 credit_flow 14 pri 1 ack_timer 0
frame_size 312 max_retrans 0 credits 7
< ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 12 pf 1 ilen 0 fcs 0x43
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 12 pf 1 ilen 0 fcs 0x88
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 12 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x0041 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 12 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 12 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x0041 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 12 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
< ACL data: handle 0x0029 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 12 pf 1 ilen 0 fcs 0x53 credits 33
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0041 scid 0x0040
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
< HCI Command: Disconnect (0x01|0x0006) plen 3
0000: 29 00 13 )..
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 06 04 ....
> HCI Event: Disconn Complete (0x05) plen 4
0000: 00 29 00 16 .)..
< HCI Command: Read Local Name (0x03|0x0014) plen 0
> HCI Event: Command Complete (0x0e) plen 252
0000: 01 14 0c 00 6e 6f 6d 61 64 65 2d 30 00 00 00 00 ....nomade-0....
0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 ............
< HCI Command: Read Class of Device (0x03|0x0023) plen 0
> HCI Event: Command Complete (0x0e) plen 7
0000: 01 23 0c 00 00 01 00 .#.....
< HCI Command: Read Local Version Information (0x04|0x0001) plen 0
> HCI Event: Command Complete (0x0e) plen 12
0000: 01 01 10 00 01 0d 02 01 0a 00 0d 02 ............
< HCI Command: Read Local Name (0x03|0x0014) plen 0
> HCI Event: Command Complete (0x0e) plen 252
0000: 01 14 0c 00 6e 6f 6d 61 64 65 2d 30 00 00 00 00 ....nomade-0....
0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 ............
< HCI Command: Read Class of Device (0x03|0x0023) plen 0
> HCI Event: Command Complete (0x0e) plen 7
0000: 01 23 0c 00 00 01 00 .#.....
< HCI Command: Read Local Version Information (0x04|0x0001) plen 0
> HCI Event: Command Complete (0x0e) plen 12
0000: 01 01 10 00 01 0d 02 01 0a 00 0d 02 ............
< HCI Command: Create Connection (0x01|0x0005) plen 13
0000: 2e 01 06 2e 0b 00 18 cc 02 00 00 00 01 .............
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 05 04 ....
> HCI Event: Link Key Request (0x17) plen 6
0000: 2e 01 06 2e 0b 00 ......
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
0000: 2e 01 06 2e 0b 00 e3 29 89 d3 51 2c 66 c5 d2 16 .......)..Q,f...
0010: 20 fa 9e 46 f3 73 ..F.s
> HCI Event: Command Complete (0x0e) plen 10
0000: 01 0b 04 00 2e 01 06 2e 0b 00 ..........
> HCI Event: Connect Complete (0x03) plen 11
0000: 00 29 00 2e 01 06 2e 0b 00 01 00 .).........
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
0000: 29 00 0f 00 )...
> HCI Event: Command Complete (0x0e) plen 6
0000: 01 0d 08 00 29 00 ....).
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
0000: 2e 01 06 2e 0b 00 02 00 00 00 ..........
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 19 04 ....
> HCI Event: Max Slots Change (0x1b) plen 3
0000: 29 00 05 )..
> HCI Event: Remote Name Req Complete (0x07) plen 255
0000: 00 2e 01 06 2e 0b 00 42 54 31 30 30 30 00 00 00 .......BT1000...
0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...............
< HCI Command: Read Remote Version Information (0x01|0x001d) plen 2
0000: 29 00 ).
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 1d 04 ....
> HCI Event: Read Remote Ver Info Complete (0x0c) plen 8
0000: 00 29 00 01 18 00 05 04 .)......
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
0000: 29 00 ).
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 1b 04 ....
> HCI Event: Read Remote Supported Features (0x0b) plen 11
0000: 00 29 00 ff f9 31 00 00 00 00 00 .)...1.....
< HCI Command: Disconnect (0x01|0x0006) plen 3
0000: 29 00 13 )..
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 06 04 ....
> HCI Event: Disconn Complete (0x05) plen 4
0000: 00 29 00 16 .)..
and nothing more. Pairing was done.
Thanks for your help.
--
Daniel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Marcel Holtmann a =E9crit :
>Hi Daniel,
>
> =20
>
>>>what is in /proc/bus/usb/devices? I think that this dongle don't has t=
he
>>>needed USB ISOC endpoints for SCO data.
>>>=20
>>>
>>> =20
>>>
>>This is not a dongle output, it's the headset one. Here is the output o=
f=20
>>devices.
>> =20
>>
>
>then forget what I said. You have a CSR dongle with HCI 16.4 and this
>should work fine.
> =20
>
Then is it normal that hcitool scan <btaddr> doesn't find the headset as=20
hcitool info <btaddr> is ok? Meanwhile, I CVS the latest btsco, rebuild=20
everything and tested with the mpg123 sample with a2play. Here the=20
result from output:
MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo
subbands =3D 1
allocation method =3D 1
channel_mode =3D 2
blocks =3D 3
sampling frequency =3D 2
bitpool =3D 32
frame len =3D 72
Using address: 00:0b:2e:06:01:2e
Can't connect to 2E:01:06:2E:0B:00. Invalid argument(22)
cannot open psm_cmd =3D 0
Many thanks for your help.
--=20
Daniel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Daniel,
> >what is in /proc/bus/usb/devices? I think that this dongle don't has the
> >needed USB ISOC endpoints for SCO data.
> >
> >
> This is not a dongle output, it's the headset one. Here is the output of
> devices.
then forget what I said. You have a CSR dongle with HCI 16.4 and this
should work fine.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Marcel Holtmann a =E9crit :
>Hi Daniel,
> =20
>
Hi Marcel,
> =20
>
>>I check further and still I can't get it work. If I do a hcitool scan n=
o
>>device is found. But the info command is working:
>>
>>nomade:/etc/bluetooth# hcitool info 00:0b:2e:06:01:2e
>>Requesting information ...
>> BD Address: 00:0b:2e:06:01:2e
>> Device Name: BT1000
>> LMP Version: 1.1 (0x1) LMP Subversion: 0x405
>> Manufacturer: Transilica, Inc. (24)
>> Features: 0xff 0xf9 0x31 0x00 0x00 0x00 0x00 0x00
>> <3-slot packets> <5-slot packets> <encryption> <slot of=
fset>
>> <timing accuracy> <role switch> <hold mode> <sniff mode=
>
>> <park state> <SCO link> <HV2 packets> <HV3 packets>
>> <u-law log> <A-law log> <CVSD>
>> =20
>>
>
>what is in /proc/bus/usb/devices? I think that this dongle don't has the
>needed USB ISOC endpoints for SCO data.
> =20
>
This is not a dongle output, it's the headset one. Here is the output of=20
devices.
nomade:/home/dh# cat /proc/bus/usb/devices
T: Bus=3D04 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D480 M=
xCh=3D 6
B: Alloc=3D 0/800 us ( 0%), #Int=3D 0, #Iso=3D 0
D: Ver=3D 2.00 Cls=3D09(hub ) Sub=3D00 Prot=3D01 MxPS=3D 8 #Cfgs=3D 1
P: Vendor=3D0000 ProdID=3D0000 Rev=3D 2.06
S: Manufacturer=3DLinux 2.6.10custom.2 ehci_hcd
S: Product=3DSilicon Integrated Systems [SiS] USB 2.0 Controller
S: SerialNumber=3D0000:00:03.3
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3De0 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driver=
=3Dhub
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 2 Ivl=3D256ms
T: Bus=3D03 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D12 M=
xCh=3D 2
B: Alloc=3D 0/900 us ( 0%), #Int=3D 0, #Iso=3D 0
D: Ver=3D 1.10 Cls=3D09(hub ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D 1
P: Vendor=3D0000 ProdID=3D0000 Rev=3D 2.06
S: Manufacturer=3DLinux 2.6.10custom.2 ohci_hcd
S: Product=3DSilicon Integrated Systems [SiS] USB 1.0 Controller (#3)
S: SerialNumber=3D0000:00:03.2
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3Dc0 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driver=
=3Dhub
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 2 Ivl=3D255ms
T: Bus=3D02 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D12 M=
xCh=3D 2
B: Alloc=3D 43/900 us ( 5%), #Int=3D 1, #Iso=3D 2
D: Ver=3D 1.10 Cls=3D09(hub ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D 1
P: Vendor=3D0000 ProdID=3D0000 Rev=3D 2.06
S: Manufacturer=3DLinux 2.6.10custom.2 ohci_hcd
S: Product=3DSilicon Integrated Systems [SiS] USB 1.0 Controller (#2)
S: SerialNumber=3D0000:00:03.1
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3Dc0 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driver=
=3Dhub
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 2 Ivl=3D255ms
T: Bus=3D02 Lev=3D01 Prnt=3D01 Port=3D01 Cnt=3D01 Dev#=3D 3 Spd=3D12 M=
xCh=3D 0
D: Ver=3D 1.10 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 MxPS=3D64 #Cfgs=3D 1
P: Vendor=3D0a12 ProdID=3D0001 Rev=3D 5.25
C:* #Ifs=3D 3 Cfg#=3D 1 Atr=3Dc0 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 3 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 16 Ivl=3D1ms
E: Ad=3D02(O) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms
E: Ad=3D82(I) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms
I: If#=3D 1 Alt=3D 0 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 0 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 0 Ivl=3D1ms
I: If#=3D 1 Alt=3D 1 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 9 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 9 Ivl=3D1ms
I: If#=3D 1 Alt=3D 2 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 17 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 17 Ivl=3D1ms
I: If#=3D 1 Alt=3D 3 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 25 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 25 Ivl=3D1ms
I: If#=3D 1 Alt=3D 4 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 33 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 33 Ivl=3D1ms
I: If#=3D 1 Alt=3D 5 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 49 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 49 Ivl=3D1ms
I: If#=3D 2 Alt=3D 0 #EPs=3D 0 Cls=3Dfe(app. ) Sub=3D01 Prot=3D00 Driver=
=3D(none)
T: Bus=3D01 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D12 M=
xCh=3D 2
B: Alloc=3D 0/900 us ( 0%), #Int=3D 0, #Iso=3D 0
D: Ver=3D 1.10 Cls=3D09(hub ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D 1
P: Vendor=3D0000 ProdID=3D0000 Rev=3D 2.06
S: Manufacturer=3DLinux 2.6.10custom.2 ohci_hcd
S: Product=3DSilicon Integrated Systems [SiS] USB 1.0 Controller
S: SerialNumber=3D0000:00:03.0
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3Dc0 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driver=
=3Dhub
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 2 Ivl=3D255ms
Many thanks for your help
--=20
Daniel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Daniel,
> I check further and still I can't get it work. If I do a hcitool scan no
> device is found. But the info command is working:
>
> nomade:/etc/bluetooth# hcitool info 00:0b:2e:06:01:2e
> Requesting information ...
> BD Address: 00:0b:2e:06:01:2e
> Device Name: BT1000
> LMP Version: 1.1 (0x1) LMP Subversion: 0x405
> Manufacturer: Transilica, Inc. (24)
> Features: 0xff 0xf9 0x31 0x00 0x00 0x00 0x00 0x00
> <3-slot packets> <5-slot packets> <encryption> <slot offset>
> <timing accuracy> <role switch> <hold mode> <sniff mode>
> <park state> <SCO link> <HV2 packets> <HV3 packets>
> <u-law log> <A-law log> <CVSD>
what is in /proc/bus/usb/devices? I think that this dongle don't has the
needed USB ISOC endpoints for SCO data.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Does really nobody have an idea on what is wrong here?
Thanks for any hint.
Daniel.
Sebastian Roth a =E9crit :
> Hi Daniel,
>
>> nomade:/home/dh# btsco 00:0b:2e:06:01:2e
>> Device is 1:0
>> Voice setting: 0x0060
>> RFCOMM channel 6 connected
>
> You have to press the headset button now!
I check further and still I can't get it work. If I do a hcitool scan no
device is found. But the info command is working:
nomade:/etc/bluetooth# hcitool info 00:0b:2e:06:01:2e
Requesting information ...
BD Address: 00:0b:2e:06:01:2e
Device Name: BT1000
LMP Version: 1.1 (0x1) LMP Subversion: 0x405
Manufacturer: Transilica, Inc. (24)
Features: 0xff 0xf9 0x31 0x00 0x00 0x00 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offs=
et>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <SCO link> <HV2 packets> <HV3 packets>
<u-law log> <A-law log> <CVSD>
Here is a hcidump -x when launching btsco with the given channel:
nomade:/home/dh#btsco 00:0b:2e:06:01:2e 1
Device is 1:0
Voice setting: 0x0060
RFCOMM channel 1 connected
HCIDump - HCI packet analyzer ver 1.12
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Read Voice Setting (0x03|0x0025) plen 0
> HCI Event: Command Complete (0x0e) plen 6
01 25 0C 00 60 00
< HCI Command: Create Connection (0x01|0x0005) plen 13
2E 01 06 2E 0B 00 18 CC 02 00 00 00 01
> HCI Event: Command Status (0x0f) plen 4
00 01 05 04
> HCI Event: Link Key Request (0x17) plen 6
2E 01 06 2E 0B 00
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
2E 01 06 2E 0B 00 98 0F 70 E7 AD EE 4B 1A 93 1C BA 18 77 0C
19 00
> HCI Event: Command Complete (0x0e) plen 10
01 0B 04 00 2E 01 06 2E 0B 00
> HCI Event: Connect Complete (0x03) plen 11
00 29 00 2E 01 06 2E 0B 00 01 00
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
29 00 0F 00
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> HCI Event: Max Slots Change (0x1b) plen 3
29 00 05
> HCI Event: Command Complete (0x0e) plen 6
01 0D 08 00 29 00
> ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
< ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> ACL data: handle 0x0029 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 4
MTU 1024
> ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
MTU 317
< ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
< ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 0x0029 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 312 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> ACL data: handle 0x0029 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 2 frame_type 0 credit_flow 14 pri 1 ack_timer 0
frame_size 312 max_retrans 0 credits 7
< ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
< ACL data: handle 0x0029 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 2 pf 1 ilen 0 fcs 0x86 credits 33
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
< ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 2 pf 1 ilen 0 fcs 0xb8
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
29 00 13
> HCI Event: Command Status (0x0f) plen 4
00 01 06 04
> HCI Event: Disconn Complete (0x05) plen 4
00 29 00 16
And here the output from snd-bt-sco
snd-bt-sco: prepare ok bps: 16000 size: 8000 count: 2000
snd-bt-sco: playback_trigger 1
snd-bt-sco: setting playback to bspcm
snd-bt-sco: playback_trigger 0
snd-bt-sco: setting playback to NULL
Pairing is done, so what could be the problem?
I would really appreciate any help to debug this problem.
Thanks
--=20
Daniel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Sebastian Roth a =E9crit :
> Hi Daniel,
>
>> nomade:/home/dh# btsco 00:0b:2e:06:01:2e
>> Device is 1:0
>> Voice setting: 0x0060
>> RFCOMM channel 6 connected
>
> You have to press the headset button now!
I check further and still I can't get it work. If I do a hcitool scan no=20
device is found. But the info command is working:
nomade:/etc/bluetooth# hcitool info 00:0b:2e:06:01:2e
Requesting information ...
BD Address: 00:0b:2e:06:01:2e
Device Name: BT1000
LMP Version: 1.1 (0x1) LMP Subversion: 0x405
Manufacturer: Transilica, Inc. (24)
Features: 0xff 0xf9 0x31 0x00 0x00 0x00 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offs=
et>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <SCO link> <HV2 packets> <HV3 packets>
<u-law log> <A-law log> <CVSD>
Here is a hcidump -x when launching btsco with the given channel:
nomade:/home/dh#btsco 00:0b:2e:06:01:2e 1
Device is 1:0
Voice setting: 0x0060
RFCOMM channel 1 connected
HCIDump - HCI packet analyzer ver 1.12
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Read Voice Setting (0x03|0x0025) plen 0
> HCI Event: Command Complete (0x0e) plen 6
01 25 0C 00 60 00
< HCI Command: Create Connection (0x01|0x0005) plen 13
2E 01 06 2E 0B 00 18 CC 02 00 00 00 01
> HCI Event: Command Status (0x0f) plen 4
00 01 05 04
> HCI Event: Link Key Request (0x17) plen 6
2E 01 06 2E 0B 00
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
2E 01 06 2E 0B 00 98 0F 70 E7 AD EE 4B 1A 93 1C BA 18 77 0C
19 00
> HCI Event: Command Complete (0x0e) plen 10
01 0B 04 00 2E 01 06 2E 0B 00
> HCI Event: Connect Complete (0x03) plen 11
00 29 00 2E 01 06 2E 0B 00 01 00
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
29 00 0F 00
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> HCI Event: Max Slots Change (0x1b) plen 3
29 00 05
> HCI Event: Command Complete (0x0e) plen 6
01 0D 08 00 29 00
> ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
< ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> ACL data: handle 0x0029 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 4
MTU 1024
> ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
MTU 317
< ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
< ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 0x0029 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 312 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> ACL data: handle 0x0029 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 2 frame_type 0 credit_flow 14 pri 1 ack_timer 0
frame_size 312 max_retrans 0 credits 7
< ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
< ACL data: handle 0x0029 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 2 pf 1 ilen 0 fcs 0x86 credits 33
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
< ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 2 pf 1 ilen 0 fcs 0xb8
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
< ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> HCI Event: Number of Completed Packets (0x13) plen 5
01 29 00 01 00
> ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
29 00 13
> HCI Event: Command Status (0x0f) plen 4
00 01 06 04
> HCI Event: Disconn Complete (0x05) plen 4
00 29 00 16
And here the output from snd-bt-sco
snd-bt-sco: prepare ok bps: 16000 size: 8000 count: 2000
snd-bt-sco: playback_trigger 1
snd-bt-sco: setting playback to bspcm
snd-bt-sco: playback_trigger 0
snd-bt-sco: setting playback to NULL
Pairing is done, so what could be the problem?
I would really appreciate any help to debug this problem.
Thanks
--=20
Daniel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
stefan,
that's good sleuthing, but rfcomm.conf is used to bind a character
device in /dev (eg /dev/rfcomm1) to a bluetooth device. btsco does not
try to use a character device to interact with the headset... it makes a
straight l2cap connection for control signals and later a sco connection
for audio transport.
brad
Stefan Bellon wrote:
> Sebastian Roth wrote:
>
>
>>>nomade:/home/dh# btsco 00:0b:2e:06:01:2e
>>>Device is 1:0
>>>Voice setting: 0x0060
>>>RFCOMM channel 6 connected
>>
>>You have to press the headset button now!
>
>
> Sorry to hi-jack this thread, but I just noticed something regarding my
> problem when I read this.
>
> When I issue the above, the line "RFCOMM channel x connected" doesn't
> appear at all. You wrote that afterwards I have to press the headset
> button. That means, if that line doesn't appear, the problem isn't with
> the headset, but still with my Bluetooth/rfcomm configuration of the
> computer?
>
> In that case I got an idea. As I use Bluetooth in order to connect my
> SonyEricsson P900 to the computer as well, I have got set up a
> /etc/bluetooth/rfcomm.conf which looks like this:
>
> rfcomm1 {
> bind yes;
> device 00:0A:D9:E9:BB:0A;
> channel 1;
> comment "P900 Serial Protocol connection";
> }
>
> rfcomm11 {
> bind yes;
> device 00:0A:D9:E9:BB:0A;
> channel 11;
> comment "P900 p3nfsd connection";
> }
>
> Do I have to add something like ...
>
> rfcomm2 {
> bind yes;
> device 00:07:A4:21:1D:86;
> channel 2;
> comment "Jabra BT800";
> }
>
> ... in order to make it work with btsco? In any case, adding the above
> channel 2 configuration doesn't work. Or don't I have to touch the
> rfcomm.conf at all?
>
> Perhaps this gives some clues what I'm doing wrong?
>
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Sebastian Roth wrote:
> > nomade:/home/dh# btsco 00:0b:2e:06:01:2e
> > Device is 1:0
> > Voice setting: 0x0060
> > RFCOMM channel 6 connected
> You have to press the headset button now!
Sorry to hi-jack this thread, but I just noticed something regarding my
problem when I read this.
When I issue the above, the line "RFCOMM channel x connected" doesn't
appear at all. You wrote that afterwards I have to press the headset
button. That means, if that line doesn't appear, the problem isn't with
the headset, but still with my Bluetooth/rfcomm configuration of the
computer?
In that case I got an idea. As I use Bluetooth in order to connect my
SonyEricsson P900 to the computer as well, I have got set up a
/etc/bluetooth/rfcomm.conf which looks like this:
rfcomm1 {
bind yes;
device 00:0A:D9:E9:BB:0A;
channel 1;
comment "P900 Serial Protocol connection";
}
rfcomm11 {
bind yes;
device 00:0A:D9:E9:BB:0A;
channel 11;
comment "P900 p3nfsd connection";
}
Do I have to add something like ...
rfcomm2 {
bind yes;
device 00:07:A4:21:1D:86;
channel 2;
comment "Jabra BT800";
}
... in order to make it work with btsco? In any case, adding the above
channel 2 configuration doesn't work. Or don't I have to touch the
rfcomm.conf at all?
Perhaps this gives some clues what I'm doing wrong?
--
Stefan Bellon
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Sebastian Roth a =E9crit :
> Hi Daniel,
Hi Sebastian
>
>> nomade:/home/dh# btsco 00:0b:2e:06:01:2e
>> Device is 1:0
>> Voice setting: 0x0060
>> RFCOMM channel 6 connected
>
> You have to press the headset button now!
Headset was already on ;-) The only other information I receive when
plying with alsamixer is "speaker volume: 10 mic volume: 10" I also
tried to switch on the headset after launching btsco, same result.
Do you know what's the meaning of this 2 errors in hcidump?
>
> If this does not help please post the outputs of
> hciconfig hci0 revision (as root)
hci0: Type: USB
BD Address: 00:0C:41:E2:4C:B0 ACL MTU: 192:8 SCO MTU: 64:8
HCI 16.4
Chip version: BlueCore02
Max key size: 56 bit
SCO mapping: HCI
dh@nomade:~$
> and
> cat /proc/bus/usb/devices
dh@nomade:~/music$ cat /proc/bus/usb/devices
T: Bus=3D04 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D480 M=
xCh=3D 6
B: Alloc=3D 0/800 us ( 0%), #Int=3D 0, #Iso=3D 0
D: Ver=3D 2.00 Cls=3D09(hub ) Sub=3D00 Prot=3D01 MxPS=3D 8 #Cfgs=3D 1
P: Vendor=3D0000 ProdID=3D0000 Rev=3D 2.06
S: Manufacturer=3DLinux 2.6.10custom.2 ehci_hcd
S: Product=3DSilicon Integrated Systems [SiS] USB 2.0 Controller
S: SerialNumber=3D0000:00:03.3
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3De0 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driver=
=3Dhub
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 2 Ivl=3D256ms
T: Bus=3D03 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D12 M=
xCh=3D 2
B: Alloc=3D 0/900 us ( 0%), #Int=3D 0, #Iso=3D 0
D: Ver=3D 1.10 Cls=3D09(hub ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D 1
P: Vendor=3D0000 ProdID=3D0000 Rev=3D 2.06
S: Manufacturer=3DLinux 2.6.10custom.2 ohci_hcd
S: Product=3DSilicon Integrated Systems [SiS] USB 1.0 Controller (#3)
S: SerialNumber=3D0000:00:03.2
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3Dc0 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driver=
=3Dhub
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 2 Ivl=3D255ms
T: Bus=3D02 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D12 M=
xCh=3D 2
B: Alloc=3D 43/900 us ( 5%), #Int=3D 1, #Iso=3D 2
D: Ver=3D 1.10 Cls=3D09(hub ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D 1
P: Vendor=3D0000 ProdID=3D0000 Rev=3D 2.06
S: Manufacturer=3DLinux 2.6.10custom.2 ohci_hcd
S: Product=3DSilicon Integrated Systems [SiS] USB 1.0 Controller (#2)
S: SerialNumber=3D0000:00:03.1
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3Dc0 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driver=
=3Dhub
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 2 Ivl=3D255ms
T: Bus=3D02 Lev=3D01 Prnt=3D01 Port=3D01 Cnt=3D01 Dev#=3D 3 Spd=3D12 M=
xCh=3D 0
D: Ver=3D 1.10 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 MxPS=3D64 #Cfgs=3D 1
P: Vendor=3D0a12 ProdID=3D0001 Rev=3D 5.25
C:* #Ifs=3D 3 Cfg#=3D 1 Atr=3Dc0 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 3 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 16 Ivl=3D1ms
E: Ad=3D02(O) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms
E: Ad=3D82(I) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms
I: If#=3D 1 Alt=3D 0 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 0 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 0 Ivl=3D1ms
I: If#=3D 1 Alt=3D 1 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 9 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 9 Ivl=3D1ms
I: If#=3D 1 Alt=3D 2 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 17 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 17 Ivl=3D1ms
I: If#=3D 1 Alt=3D 3 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 25 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 25 Ivl=3D1ms
I: If#=3D 1 Alt=3D 4 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 33 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 33 Ivl=3D1ms
I: If#=3D 1 Alt=3D 5 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 49 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 49 Ivl=3D1ms
I: If#=3D 2 Alt=3D 0 #EPs=3D 0 Cls=3Dfe(app. ) Sub=3D01 Prot=3D00 Driver=
=3D(none)
T: Bus=3D01 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D12 M=
xCh=3D 2
B: Alloc=3D 0/900 us ( 0%), #Int=3D 0, #Iso=3D 0
D: Ver=3D 1.10 Cls=3D09(hub ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D 1
P: Vendor=3D0000 ProdID=3D0000 Rev=3D 2.06
S: Manufacturer=3DLinux 2.6.10custom.2 ohci_hcd
S: Product=3DSilicon Integrated Systems [SiS] USB 1.0 Controller
S: SerialNumber=3D0000:00:03.0
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3Dc0 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driver=
=3Dhub
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 2 Ivl=3D255ms
dh@nomade:~/music$
Thanks a lot for your help.
--=20
Daniel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Sebastian Roth a =E9crit :
> Hi Daniel,
Hi Sebastian
>
>> nomade:/home/dh# btsco 00:0b:2e:06:01:2e
>> Device is 1:0
>> Voice setting: 0x0060
>> RFCOMM channel 6 connected
>
> You have to press the headset button now!
Headset was already on ;-) The only other information I receive when=20
plying with alsamixer is "speaker volume: 10 mic volume: 10" I also=20
tried to switch on the headset after launching btsco, same result.
Do you know what's the meaning of this 2 errors in hcidump?
>
> If this does not help please post the outputs of
> hciconfig hci0 revision (as root)
hci0: Type: USB
BD Address: 00:0C:41:E2:4C:B0 ACL MTU: 192:8 SCO MTU: 64:8
HCI 16.4
Chip version: BlueCore02
Max key size: 56 bit
SCO mapping: HCI
dh@nomade:~$
> and
> cat /proc/bus/usb/devices
dh@nomade:~/music$ cat /proc/bus/usb/devices
T: Bus=3D04 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D480 M=
xCh=3D 6
B: Alloc=3D 0/800 us ( 0%), #Int=3D 0, #Iso=3D 0
D: Ver=3D 2.00 Cls=3D09(hub ) Sub=3D00 Prot=3D01 MxPS=3D 8 #Cfgs=3D 1
P: Vendor=3D0000 ProdID=3D0000 Rev=3D 2.06
S: Manufacturer=3DLinux 2.6.10custom.2 ehci_hcd
S: Product=3DSilicon Integrated Systems [SiS] USB 2.0 Controller
S: SerialNumber=3D0000:00:03.3
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3De0 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driver=
=3Dhub
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 2 Ivl=3D256ms
T: Bus=3D03 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D12 M=
xCh=3D 2
B: Alloc=3D 0/900 us ( 0%), #Int=3D 0, #Iso=3D 0
D: Ver=3D 1.10 Cls=3D09(hub ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D 1
P: Vendor=3D0000 ProdID=3D0000 Rev=3D 2.06
S: Manufacturer=3DLinux 2.6.10custom.2 ohci_hcd
S: Product=3DSilicon Integrated Systems [SiS] USB 1.0 Controller (#3)
S: SerialNumber=3D0000:00:03.2
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3Dc0 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driver=
=3Dhub
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 2 Ivl=3D255ms
T: Bus=3D02 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D12 M=
xCh=3D 2
B: Alloc=3D 43/900 us ( 5%), #Int=3D 1, #Iso=3D 2
D: Ver=3D 1.10 Cls=3D09(hub ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D 1
P: Vendor=3D0000 ProdID=3D0000 Rev=3D 2.06
S: Manufacturer=3DLinux 2.6.10custom.2 ohci_hcd
S: Product=3DSilicon Integrated Systems [SiS] USB 1.0 Controller (#2)
S: SerialNumber=3D0000:00:03.1
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3Dc0 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driver=
=3Dhub
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 2 Ivl=3D255ms
T: Bus=3D02 Lev=3D01 Prnt=3D01 Port=3D01 Cnt=3D01 Dev#=3D 3 Spd=3D12 M=
xCh=3D 0
D: Ver=3D 1.10 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 MxPS=3D64 #Cfgs=3D 1
P: Vendor=3D0a12 ProdID=3D0001 Rev=3D 5.25
C:* #Ifs=3D 3 Cfg#=3D 1 Atr=3Dc0 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 3 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 16 Ivl=3D1ms
E: Ad=3D02(O) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms
E: Ad=3D82(I) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms
I: If#=3D 1 Alt=3D 0 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 0 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 0 Ivl=3D1ms
I: If#=3D 1 Alt=3D 1 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 9 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 9 Ivl=3D1ms
I: If#=3D 1 Alt=3D 2 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 17 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 17 Ivl=3D1ms
I: If#=3D 1 Alt=3D 3 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 25 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 25 Ivl=3D1ms
I: If#=3D 1 Alt=3D 4 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 33 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 33 Ivl=3D1ms
I: If#=3D 1 Alt=3D 5 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 49 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 49 Ivl=3D1ms
I: If#=3D 2 Alt=3D 0 #EPs=3D 0 Cls=3Dfe(app. ) Sub=3D01 Prot=3D00 Driver=
=3D(none)
T: Bus=3D01 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D12 M=
xCh=3D 2
B: Alloc=3D 0/900 us ( 0%), #Int=3D 0, #Iso=3D 0
D: Ver=3D 1.10 Cls=3D09(hub ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D 1
P: Vendor=3D0000 ProdID=3D0000 Rev=3D 2.06
S: Manufacturer=3DLinux 2.6.10custom.2 ohci_hcd
S: Product=3DSilicon Integrated Systems [SiS] USB 1.0 Controller
S: SerialNumber=3D0000:00:03.0
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3Dc0 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driver=
=3Dhub
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 2 Ivl=3D255ms
dh@nomade:~/music$=20
Thanks a lot for your help.
--=20
Daniel Huhardeaux ______ _____ _____ ______ ______ __
enum +48 32 285 5276 /_ _// _ // _ //_ _// __ // /
IAX FWD +1 7009 422493 / / / // // // / / / / /_/ // /
sip:101 h323:121 @voip./_/ /____//____/ /_/ /_/ /_//_/.com
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Daniel,
> nomade:/home/dh# btsco 00:0b:2e:06:01:2e
> Device is 1:0
> Voice setting: 0x0060
> RFCOMM channel 6 connected
You have to press the headset button now!
If this does not help please post the outputs of
hciconfig hci0 revision (as root)
and
cat /proc/bus/usb/devices
Regards,
Sebastian
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Sebastian Roth a =E9crit :
> Hi Daniel,
Hi Sebastian
>> 2.6.10 (debian) + patch swsusp2 & bluez-utils 2.10-5 (debian sid)
>
> As I said before please give it a try and update your kernel with the
> current patch from bluez.org and install the latest versions of
> utils and lib (source is also available at bluez.org)
nomade:/etc# uname -r
2.6.10-mh3-custom.3
nomade:/usr/lib# ls /usr/lib/libblu*
/usr/lib/libbluetooth.a /usr/lib/libbluetooth.so =20
/usr/lib/libbluetooth.so.1.0.15
/usr/lib/libbluetooth.la /usr/lib/libbluetooth.so.1
Utils also upgraded.
>
> Haven't seen any output of the SCO module in your dmesg. Make sure
> you have enabled CONFIG_BT_SCO and CONFIG_BT_HCIUSB_SCO in your kernel
> config and loaded the module 'sco'!
nomade:/etc# lsmod
Module Size Used by
sco 15108 0
snd_bt_sco 13728 0
snd_hwdep 9540 1 snd_bt_sco
ndiswrapper 114264 0
rfcomm 41116 0
l2cap 27140 3 rfcomm
nomade:/usr/src/linux# hciconfig -a
hci0: Type: USB
BD Address: 00:0C:41:E2:4C:B0 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:1851 acl:49 sco:0 events:89 errors:0
TX bytes:1287 acl:47 sco:0 commands:29 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'BlueZ (0)'
Class: 0x3e0100
Service Classes: Networking, Rendering, Capturing
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver:=20
0x20d
Manufacturer: Cambridge Silicon Radio (10)
>> #sdptool search --bdaddr 00:0b:2e:06:01:2e 0x1108
>
> [...]
>
>> Channel: 6
>
> [...]
>
>> nomade:/etc/waproamd/keys# btsco 00:0b:2e:06:01:2e
>> Device is 1:0
>> Voice setting: 0x0060
>> RFCOMM channel 6 connected
>> speaker volume: 10 mic volume: 10
>
> Channel should be ok. Now where are the new message from? Does it
> work now?
speaker volume message: I always get it the first time I run btsco=20
*after* having loaded snd-bt-sco. The hcidump is below. Still this 2=20
ERROR unexpected syntax.
nomade:/usr/src/linux# hcidump -X
HCIDump - HCI packet analyzer ver 1.12
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
0000: 2e 01 06 2e 0b 00 18 cc 02 00 00 00 01 .............
> HCI Event: Command Status (0x0f) plen 4
0000: 00 01 05 04 ....
> HCI Event: Link Key Request (0x17) plen 6
0000: 2e 01 06 2e 0b 00 ......
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
0000: 2e 01 06 2e 0b 00 98 0f 70 e7 ad ee 4b 1a 93 1c ........p...K...
0010: ba 18 77 0c 19 00 ..w...
> HCI Event: Command Complete (0x0e) plen 10
0000: 01 0b 04 00 2e 01 06 2e 0b 00 ..........
> HCI Event: Connect Complete (0x03) plen 11
0000: 00 29 00 2e 01 06 2e 0b 00 01 00 .).........
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
0000: 29 00 0f 00 )...
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> HCI Event: Max Slots Change (0x1b) plen 3
0000: 29 00 05 )..
> HCI Event: Command Complete (0x0e) plen 6
0000: 01 0d 08 00 29 00 ....).
> ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
> ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
MTU 48
< ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
< ACL data: handle 0x0029 flags 0x02 dlen 24
L2CAP(d): cid 0x0040 len 20 [psm 1]
SDP SSA Req: tid 0x0 len 0xf
pat uuid-16 0x1108 (Headset)
max 0xffff
aid(s) 0x0000 - 0xffff
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 27
> ACL data: handle 0x0029 flags 0x01 dlen 24
L2CAP(d): cid 0x0040 len 47 [psm 1]
SDP SSA Rsp: tid 0x0 len 0x2a
cnt 0x26
srv rec #0
aid 0x0000 (SrvRecHndl)
uint 0x20000
aid 0x0001 (SrvClassIDList)
< uuid-16 0x1108 (Headset) uuid-16 0x1203 (Audio) >
aid 0x0004 (ProtocolDescList)
< < uuid-16 0x0100 (L2CAP) > <
uuid-16 0x0003 (RFCOMM) null null > >
cont
< ACL data: handle 0x0029 flags 0x02 dlen 25
L2CAP(d): cid 0x0040 len 21 [psm 1]
SDP SSA Req: tid 0x1 len 0x10
pat uuid-16 0x1108 (Headset)
max 0xffff
aid(s) 0x0000 - 0xffff
cont 01 01
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 27
> ACL data: handle 0x0029 flags 0x01 dlen 22
L2CAP(d): cid 0x0040 len 45 [psm 1]
SDP SSA Rsp: tid 0x1 len 0x28
cnt 0x24
ERROR: Unexpected syntax
0000: 06 09 00 05 35 03 19 10 02 09 00 06 35 09 09 65 =20
....5.......5..e
0010: 6e 09 00 6a 09 01 00 09 01 00 25 07 48 65 61 64 =20
n..j......%.Head
0020: 73 65 74 01 02 set..
cont 06 09 00 05 35 03 19 10 02 09 00 06 35 09 09 65 6E 09 00=20
6A 09 01 00 09 01 00 25 0748 65 61 64 73 65 74 01 02
< ACL data: handle 0x0029 flags 0x02 dlen 25
L2CAP(d): cid 0x0040 len 21 [psm 1]
SDP SSA Req: tid 0x2 len 0x10
pat uuid-16 0x1108 (Headset)
max 0xffff
aid(s) 0x0000 - 0xffff
cont 01 02
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 1]
SDP SSA Rsp: tid 0x2 len 0x8
cnt 0x5
ERROR: Unexpected syntax
0000: 03 02 28 01 00 ..(..
cont 03 02 28 01 00
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< HCI Command: Read Voice Setting (0x03|0x0025) plen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> HCI Event: Command Complete (0x0e) plen 6
0000: 01 25 0c 00 60 00 .%..`.
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
< ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 4
MTU 1024
> ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
MTU 317
< ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
< ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 0x0029 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 12 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 312 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 12 frame_type 0 credit_flow 14 pri 1 ack_timer 0
frame_size 312 max_retrans 0 credits 7
< ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 12 pf 1 ilen 0 fcs 0x43
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 8
L2CAP(d): cid 0x0040 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 12 pf 1 ilen 0 fcs 0x88
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 12 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 12 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 12 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(d): cid 0x0040 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 12 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
< ACL data: handle 0x0029 flags 0x02 dlen 9
L2CAP(d): cid 0x0040 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 12 pf 1 ilen 0 fcs 0x53 credits 33
> HCI Event: Number of Completed Packets (0x13) plen 5
0000: 01 29 00 01 00 .)...
Thanks for your help
--=20
Daniel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Daniel,
>>> nomade:/home/dh# btsco 00:0b:2e:06:01:2e
>>> Device is 1:0
>>> Voice setting: 0x0060
>>> RFCOMM channel 6 connected
>>
>>
>> You have to press the headset button now!
I wanted to say that you have to press the button like on a cd-player.
First turn on your cd-player or headset ;-) then start btsco and now
push the button once more!
> I check further and still I can't get it work. If I do a hcitool scan no
> device is found. But the info command is working:
My headset has a so called "scan mode". I have to turn it off and press
the button for a long time. Now the LED is blinking alternately red and
green. Only in this mode it show's up on hcitool scan! btw no address
is needed when scanning for devices.
$ hcitool scan
Regards,
Sebastian
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users