* RE: [Bluez-devel] Cannot send through serial device rfcomm
@ 2005-10-03 20:42 Robert Wlaschin
2005-10-04 11:16 ` Marcel Holtmann
0 siblings, 1 reply; 10+ messages in thread
From: Robert Wlaschin @ 2005-10-03 20:42 UTC (permalink / raw)
To: 'bluez-devel@lists.sourceforge.net'
[-- Attachment #1: Type: text/plain, Size: 53802 bytes --]
Hi,
I'm cross-compiling for an Arm processor using a Debian 2.6.10 kernel with
bluez-utils/lib 2.21, and bluez-hcidump 2.25 w/ a brainbox usb adapter for
rs-232 replacement (CSR chipset)
I'm having a problem communicating through the /dev/rfcomm0 device. I
thought that once the device was connected it would be have like a serial
device and I could do this ...
cat /dev/rfcomm0 > myfile.dat
echo AT > /dev/rfcomm0
Am I assuming correctly? If not what am I missing? Do I need to use the
pppd or the dund to communicate? Am I in the wrong mode (master vs slave).
If this should work please look at my log files, I'm executing these
commands ...
hcid
sdpd
sdptool add SP
rfcomm bind 0 XX:XX ...
Also, I attempted to connect using Microcom because many examples used
Minicom but it was unable to create a connection.
I would appreciate any insight you can give me.
Thanks,
Robert
----------------------------- sys log
Oct 3 12:03:56 health-buddy kern.info hcid[1428]: link_key_request
(sba=00:0A:4F:00:41:84, dba=00:A0:96:0D:3B:80)
Oct 3 12:03:57 health-buddy user.notice root: Device /dev/rfcomm0 bound and
ready
Oct 3 12:03:57 health-buddy user.notice root: Executing script
00:A0:96:0D:3B:80.cmds
Oct 3 12:04:03 health-buddy kern.info hcid[1428]: link_key_request
(sba=00:0A:4F:00:41:84, dba=00:A0:96:0D:3B:80)
Oct 3 12:04:03 health-buddy user.notice root: Device /dev/rfcomm0 bound and
ready
Oct 3 12:04:03 health-buddy user.notice root: Executing script
00:A0:96:0D:3B:80.cmds
Oct 3 12:04:09 health-buddy kern.info hcid[1428]: link_key_request
(sba=00:0A:4F:00:41:84, dba=00:A0:96:0D:3B:80)
Oct 3 12:04:09 health-buddy user.notice root: Device /dev/rfcomm0 bound and
ready
Oct 3 12:04:09 health-buddy user.notice root: Executing script
00:A0:96:0D:3B:80.cmds
Oct 3 12:05:20 health-buddy kern.info hcid[1428]: link_key_request
(sba=00:0A:4F:00:41:84, dba=00:A0:96:0D:3B:80)
Oct 3 12:05:21 health-buddy user.notice root: Device /dev/rfcomm0 bound and
ready
Oct 3 12:05:21 health-buddy user.notice root: Executing script
00:A0:96:0D:3B:80.cmds
Oct 3 12:05:27 health-buddy kern.info hcid[1428]: link_key_request
(sba=00:0A:4F:00:41:84, dba=00:A0:96:0D:3B:80)
Oct 3 12:05:27 health-buddy user.notice root: Device /dev/rfcomm0 bound and
ready
Oct 3 12:05:27 health-buddy user.notice root: Executing script
00:A0:96:0D:3B:80.cmds
Oct 3 12:05:33 health-buddy kern.info hcid[1428]: link_key_request
(sba=00:0A:4F:00:41:84, dba=00:A0:96:0D:3B:80)
Oct 3 12:05:34 health-buddy user.notice root: Device /dev/rfcomm0 bound and
ready
Oct 3 12:05:34 health-buddy user.notice root: Executing script
00:A0:96:0D:3B:80.cmds
Oct 3 12:05:39 health-buddy kern.info hcid[1428]: link_key_request
(sba=00:0A:4F:00:41:84, dba=00:A0:96:0D:3B:80)
Oct 3 12:05:40 health-buddy user.notice root: Device /dev/rfcomm0 bound and
ready
Oct 3 12:05:40 health-buddy user.notice root: Executing script
00:A0:96:0D:3B:80.cmds
Oct 3 12:05:46 health-buddy kern.info hcid[1428]: link_key_request
(sba=00:0A:4F:00:41:84, dba=00:A0:96:0D:3B:80)
Oct 3 12:05:46 health-buddy user.notice root: Device /dev/rfcomm0 bound and
ready
Oct 3 12:05:46 health-buddy user.notice root: Executing script
00:A0:96:0D:3B:80.cmds
Oct 3 12:05:52 health-buddy kern.info hcid[1428]: link_key_request
(sba=00:0A:4F:00:41:84, dba=00:A0:96:0D:3B:80)
Oct 3 12:05:53 health-buddy user.notice root: Device /dev/rfcomm0 bound and
ready
Oct 3 12:05:53 health-buddy user.notice root: Executing script
00:A0:96:0D:3B:80.cmds
----------------------------- hcidump
> ACL data: handle 42 flags 0x02 dlen 12
L2CAP(d): cid 0x0041 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
< ACL data: handle 42 flags 0x02 dlen 12
L2CAP(d): cid 0x0043 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 12
L2CAP(d): cid 0x0041 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 1 ilen 0 fcs 0x29 credits 33
> ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0041 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 1 ilen 0 fcs 0xf3 credits 15
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0042
< ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0042
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 82
L2CAP(d): cid 0x0041 len 78 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 0 ilen 74 fcs 0xef
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0041 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 1 ilen 0 fcs 0xf3 credits 8
> ACL data: handle 42 flags 0x02 dlen 10
L2CAP(d): cid 0x0041 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 1 ilen 1 fcs 0xf3 credits 3
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> ACL data: handle 42 flags 0x02 dlen 11
L2CAP(d): cid 0x0041 len 7 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 0 ilen 3 fcs 0xef
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0043 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 3 pf 1 ilen 0 fcs 0x7a
< ACL data: handle 42 flags 0x02 dlen 8
L2CAP(d): cid 0x0043 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 3 pf 1 ilen 0 fcs 0x50
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x0043 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 3 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 127 max_retrans 0 credits 7
> ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0041 scid 0x0043
< ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0043
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Disconn Complete (0x05) plen 4
> HCI Event: Connect Request (0x04) plen 10
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Link Key Request (0x17) plen 6
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
> HCI Event: Command Complete (0x0e) plen 10
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
> HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
> HCI Event: Max Slots Change (0x1b) plen 3
> HCI Event: Command Complete (0x0e) plen 6
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
> ACL data: handle 43 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0044
< ACL data: handle 43 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0044 result 0 status 0
Connection successful
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Connection Packet Type Changed (0x1d) plen 5
> ACL data: handle 43 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
MTU 48
< ACL data: handle 43 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0044 flags 0x00 result 0 clen 0
Success
< ACL data: handle 43 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0044 flags 0x00 clen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 43 flags 0x02 dlen 19
L2CAP(d): cid 0x0040 len 15 [psm 1]
SDP SS Req: tid 0x1 len 0xa
pat uuid-32 0x1101 (SP)
max 40
cont 00
< ACL data: handle 43 flags 0x02 dlen 26
L2CAP(d): cid 0x0044 len 22 [psm 1]
SDP SS Rsp: tid 0x1 len 0x11
count 3
handles 0x10000 0x10001 0x10002
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 21
L2CAP(d): cid 0x0040 len 17 [psm 1]
SDP SA Req: tid 0x2 len 0xc
handle 0x10000
max 38
aid(s) 0x0004 (ProtocolDescList)
cont 00
< ACL data: handle 43 flags 0x02 dlen 31
L2CAP(d): cid 0x0044 len 27 [psm 1]
SDP SA Rsp: tid 0x2 len 0x16
count 19
aid 0x0004 (ProtocolDescList)
< < uuid-16 0x0100 (L2CAP) > <
uuid-16 0x0003 (RFCOMM) uint 0x1 > >
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0045
< ACL data: handle 43 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0045 result 0 status 0
Connection successful
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
MTU 325
< ACL data: handle 43 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0045 flags 0x00 result 0 clen 0
Success
< ACL data: handle 43 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0045 flags 0x00 clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 4
Success
MTU 325
> ACL data: handle 43 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
< ACL data: handle 43 flags 0x02 dlen 8
L2CAP(d): cid 0x0045 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 18
L2CAP(d): cid 0x0041 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 0 ack_timer 0
frame_size 319 max_retrans 0 credits 0
< ACL data: handle 43 flags 0x02 dlen 8
L2CAP(d): cid 0x0045 len 4 [psm 3]
RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 43 flags 0x02 dlen 18
L2CAP(d): cid 0x0045 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 3 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 127 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 18
L2CAP(d): cid 0x0041 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 3 frame_type 0 credit_flow 14 pri 7 ack_timer 0
frame_size 127 max_retrans 0 credits 0
< ACL data: handle 43 flags 0x02 dlen 8
L2CAP(d): cid 0x0045 len 4 [psm 3]
RFCOMM(s): SABM: cr 0 dlci 3 pf 1 ilen 0 fcs 0xfa
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 0 dlci 3 pf 1 ilen 0 fcs 0x31
< ACL data: handle 43 flags 0x02 dlen 12
L2CAP(d): cid 0x0045 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
> ACL data: handle 43 flags 0x02 dlen 12
L2CAP(d): cid 0x0041 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
< ACL data: handle 43 flags 0x02 dlen 12
L2CAP(d): cid 0x0045 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 12
L2CAP(d): cid 0x0041 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0045 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 1 ilen 0 fcs 0x29 credits 33
> ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0041 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 1 ilen 0 fcs 0xf3 credits 15
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0044
< ACL data: handle 43 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0044
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 82
L2CAP(d): cid 0x0041 len 78 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 0 ilen 74 fcs 0xef
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0045 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0045 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0045 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0045 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0045 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0045 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0045 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0045 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0045 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0045 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0045 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0041 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 1 ilen 0 fcs 0xf3 credits 8
> ACL data: handle 43 flags 0x02 dlen 10
L2CAP(d): cid 0x0041 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 1 ilen 1 fcs 0xf3 credits 3
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0045 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> ACL data: handle 43 flags 0x02 dlen 11
L2CAP(d): cid 0x0041 len 7 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 0 ilen 3 fcs 0xef
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0045 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0045 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0045 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 3 pf 1 ilen 0 fcs 0x7a
< ACL data: handle 43 flags 0x02 dlen 8
L2CAP(d): cid 0x0045 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 3 pf 1 ilen 0 fcs 0x50
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 43 flags 0x02 dlen 18
L2CAP(d): cid 0x0045 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 3 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 127 max_retrans 0 credits 7
> ACL data: handle 43 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0041 scid 0x0045
< ACL data: handle 43 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0045
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Disconn Complete (0x05) plen 4
> HCI Event: Connect Request (0x04) plen 10
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Link Key Request (0x17) plen 6
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
> HCI Event: Command Complete (0x0e) plen 10
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
> HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
> HCI Event: Command Complete (0x0e) plen 6
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
> HCI Event: Max Slots Change (0x1b) plen 3
> HCI Event: Command Status (0x0f) plen 4
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0046
< ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0046 result 0 status 0
Connection successful
> HCI Event: Connection Packet Type Changed (0x1d) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
MTU 48
< ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0046 flags 0x00 result 0 clen 0
Success
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0046 flags 0x00 clen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 41 flags 0x02 dlen 19
L2CAP(d): cid 0x0040 len 15 [psm 1]
SDP SS Req: tid 0x1 len 0xa
pat uuid-32 0x1101 (SP)
max 40
cont 00
< ACL data: handle 41 flags 0x02 dlen 26
L2CAP(d): cid 0x0046 len 22 [psm 1]
SDP SS Rsp: tid 0x1 len 0x11
count 3
handles 0x10000 0x10001 0x10002
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 21
L2CAP(d): cid 0x0040 len 17 [psm 1]
SDP SA Req: tid 0x2 len 0xc
handle 0x10000
max 38
aid(s) 0x0004 (ProtocolDescList)
cont 00
< ACL data: handle 41 flags 0x02 dlen 31
L2CAP(d): cid 0x0046 len 27 [psm 1]
SDP SA Rsp: tid 0x2 len 0x16
count 19
aid 0x0004 (ProtocolDescList)
< < uuid-16 0x0100 (L2CAP) > <
uuid-16 0x0003 (RFCOMM) uint 0x1 > >
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0047
< ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0047 result 0 status 0
Connection successful
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
MTU 325
< ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0047 flags 0x00 result 0 clen 0
Success
< ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0047 flags 0x00 clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 4
Success
MTU 325
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0047 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 18
L2CAP(d): cid 0x0041 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 0 ack_timer 0
frame_size 319 max_retrans 0 credits 0
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0047 len 4 [psm 3]
RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 41 flags 0x02 dlen 18
L2CAP(d): cid 0x0047 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 3 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 127 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 18
L2CAP(d): cid 0x0041 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 3 frame_type 0 credit_flow 14 pri 7 ack_timer 0
frame_size 127 max_retrans 0 credits 0
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0047 len 4 [psm 3]
RFCOMM(s): SABM: cr 0 dlci 3 pf 1 ilen 0 fcs 0xfa
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 0 dlci 3 pf 1 ilen 0 fcs 0x31
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0047 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0041 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0047 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(d): cid 0x0041 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0047 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 1 ilen 0 fcs 0x29 credits 33
> ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0041 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 1 ilen 0 fcs 0xf3 credits 15
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0046
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0046
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 4
> ACL data: handle 41 flags 0x01 dlen 78
L2CAP(d): cid 0x0041 len 78 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 0 ilen 74 fcs 0xef
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0047 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0047 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0047 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0047 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0047 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0047 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0047 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0047 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0047 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0047 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0047 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0041 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 1 ilen 0 fcs 0xf3 credits 8
> ACL data: handle 41 flags 0x02 dlen 10
L2CAP(d): cid 0x0041 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 1 ilen 1 fcs 0xf3 credits 3
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0047 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> ACL data: handle 41 flags 0x02 dlen 11
L2CAP(d): cid 0x0041 len 7 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 0 ilen 3 fcs 0xef
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0047 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0047 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 41 flags 0x02 dlen 9
L2CAP(d): cid 0x0047 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 41 flags 0x02 dlen 4
> ACL data: handle 41 flags 0x01 dlen 4
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 3 pf 1 ilen 0 fcs 0x7a
< ACL data: handle 41 flags 0x02 dlen 8
L2CAP(d): cid 0x0047 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 3 pf 1 ilen 0 fcs 0x50
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 41 flags 0x02 dlen 18
L2CAP(d): cid 0x0047 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 3 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 127 max_retrans 0 credits 7
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0041 scid 0x0047
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0047
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Disconn Complete (0x05) plen 4
> HCI Event: Connect Request (0x04) plen 10
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Link Key Request (0x17) plen 6
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
> HCI Event: Command Complete (0x0e) plen 10
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
> HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
> HCI Event: Command Complete (0x0e) plen 6
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
> HCI Event: Max Slots Change (0x1b) plen 3
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Connection Packet Type Changed (0x1d) plen 5
> ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0048
< ACL data: handle 42 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0048 result 0 status 0
Connection successful
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
MTU 48
< ACL data: handle 42 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0048 flags 0x00 result 0 clen 0
Success
< ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0048 flags 0x00 clen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 42 flags 0x02 dlen 19
L2CAP(d): cid 0x0040 len 15 [psm 1]
SDP SS Req: tid 0x1 len 0xa
pat uuid-32 0x1101 (SP)
max 40
cont 00
< ACL data: handle 42 flags 0x02 dlen 26
L2CAP(d): cid 0x0048 len 22 [psm 1]
SDP SS Rsp: tid 0x1 len 0x11
count 3
handles 0x10000 0x10001 0x10002
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 21
L2CAP(d): cid 0x0040 len 17 [psm 1]
SDP SA Req: tid 0x2 len 0xc
handle 0x10000
max 38
aid(s) 0x0004 (ProtocolDescList)
cont 00
< ACL data: handle 42 flags 0x02 dlen 31
L2CAP(d): cid 0x0048 len 27 [psm 1]
SDP SA Rsp: tid 0x2 len 0x16
count 19
aid 0x0004 (ProtocolDescList)
< < uuid-16 0x0100 (L2CAP) > <
uuid-16 0x0003 (RFCOMM) uint 0x1 > >
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0049
< ACL data: handle 42 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0049 result 0 status 0
Connection successful
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
MTU 325
< ACL data: handle 42 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0049 flags 0x00 result 0 clen 0
Success
< ACL data: handle 42 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0049 flags 0x00 clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 4
Success
MTU 325
> ACL data: handle 42 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
< ACL data: handle 42 flags 0x02 dlen 8
L2CAP(d): cid 0x0049 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x0041 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 0 ack_timer 0
frame_size 319 max_retrans 0 credits 0
< ACL data: handle 42 flags 0x02 dlen 8
L2CAP(d): cid 0x0049 len 4 [psm 3]
RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x0049 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 3 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 127 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x0041 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 3 frame_type 0 credit_flow 14 pri 7 ack_timer 0
frame_size 127 max_retrans 0 credits 0
< ACL data: handle 42 flags 0x02 dlen 8
L2CAP(d): cid 0x0049 len 4 [psm 3]
RFCOMM(s): SABM: cr 0 dlci 3 pf 1 ilen 0 fcs 0xfa
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 0 dlci 3 pf 1 ilen 0 fcs 0x31
< ACL data: handle 42 flags 0x02 dlen 12
L2CAP(d): cid 0x0049 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
> ACL data: handle 42 flags 0x02 dlen 12
L2CAP(d): cid 0x0041 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
< ACL data: handle 42 flags 0x02 dlen 12
L2CAP(d): cid 0x0049 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 12
L2CAP(d): cid 0x0041 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0049 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 1 ilen 0 fcs 0x29 credits 33
> ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0041 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 1 ilen 0 fcs 0xf3 credits 15
> ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0048
< ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0048
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 82
L2CAP(d): cid 0x0041 len 78 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 0 ilen 74 fcs 0xef
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0049 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0049 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0049 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0049 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0049 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0049 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0049 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0049 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0049 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0049 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0049 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0041 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 1 ilen 0 fcs 0xf3 credits 8
> ACL data: handle 42 flags 0x02 dlen 10
L2CAP(d): cid 0x0041 len 6 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 1 ilen 1 fcs 0xf3 credits 3
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0049 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> ACL data: handle 42 flags 0x02 dlen 11
L2CAP(d): cid 0x0041 len 7 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 0 ilen 3 fcs 0xef
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0049 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0049 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0049 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 42 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): DISC: cr 1 dlci 3 pf 1 ilen 0 fcs 0x7a
< ACL data: handle 42 flags 0x02 dlen 8
L2CAP(d): cid 0x0049 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 3 pf 1 ilen 0 fcs 0x50
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x0049 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 3 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 127 max_retrans 0 credits 7
> ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0041 scid 0x0049
< ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0049
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Disconn Complete (0x05) plen 4
> HCI Event: Connect Request (0x04) plen 10
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Link Key Request (0x17) plen 6
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
> HCI Event: Command Complete (0x0e) plen 10
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
> HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
> HCI Event: Command Complete (0x0e) plen 6
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
> HCI Event: Max Slots Change (0x1b) plen 3
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Connection Packet Type Changed (0x1d) plen 5
> ACL data: handle 43 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x004a
< ACL data: handle 43 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x004a result 0 status 0
Connection successful
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
MTU 48
< ACL data: handle 43 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x004a flags 0x00 result 0 clen 0
Success
< ACL data: handle 43 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x004a flags 0x00 clen 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 43 flags 0x02 dlen 19
L2CAP(d): cid 0x0040 len 15 [psm 1]
SDP SS Req: tid 0x1 len 0xa
pat uuid-32 0x1101 (SP)
max 40
cont 00
< ACL data: handle 43 flags 0x02 dlen 26
L2CAP(d): cid 0x004a len 22 [psm 1]
SDP SS Rsp: tid 0x1 len 0x11
count 3
handles 0x10000 0x10001 0x10002
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 21
L2CAP(d): cid 0x0040 len 17 [psm 1]
SDP SA Req: tid 0x2 len 0xc
handle 0x10000
max 38
aid(s) 0x0004 (ProtocolDescList)
cont 00
< ACL data: handle 43 flags 0x02 dlen 31
L2CAP(d): cid 0x004a len 27 [psm 1]
SDP SA Rsp: tid 0x2 len 0x16
count 19
aid 0x0004 (ProtocolDescList)
< < uuid-16 0x0100 (L2CAP) > <
uuid-16 0x0003 (RFCOMM) uint 0x1 > >
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x004b
< ACL data: handle 43 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0041 scid 0x004b result 0 status 0
Connection successful
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
MTU 325
< ACL data: handle 43 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x004b flags 0x00 result 0 clen 0
Success
< ACL data: handle 43 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x004b flags 0x00 clen 4
MTU 1024
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 4
Success
MTU 325
> ACL data: handle 43 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
< ACL data: handle 43 flags 0x02 dlen 8
L2CAP(d): cid 0x004b len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 18
L2CAP(d): cid 0x0041 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 0 ack_timer 0
frame_size 319 max_retrans 0 credits 0
< ACL data: handle 43 flags 0x02 dlen 8
L2CAP(d): cid 0x004b len 4 [psm 3]
RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 43 flags 0x02 dlen 18
L2CAP(d): cid 0x004b len 14 [psm 3]
RFCOMM(s): PN CMD: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
dlci 3 frame_type 0 credit_flow 15 pri 7 ack_timer 0
frame_size 127 max_retrans 0 credits 7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 18
L2CAP(d): cid 0x0041 len 14 [psm 3]
RFCOMM(s): PN RSP: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 3 frame_type 0 credit_flow 14 pri 7 ack_timer 0
frame_size 127 max_retrans 0 credits 0
< ACL data: handle 43 flags 0x02 dlen 8
L2CAP(d): cid 0x004b len 4 [psm 3]
RFCOMM(s): SABM: cr 0 dlci 3 pf 1 ilen 0 fcs 0xfa
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 0 dlci 3 pf 1 ilen 0 fcs 0x31
< ACL data: handle 43 flags 0x02 dlen 12
L2CAP(d): cid 0x004b len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
> ACL data: handle 43 flags 0x02 dlen 12
L2CAP(d): cid 0x0041 len 8 [psm 3]
RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
< ACL data: handle 43 flags 0x02 dlen 12
L2CAP(d): cid 0x004b len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 0 len 0
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 12
L2CAP(d): cid 0x0041 len 8 [psm 3]
RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
dlci 3 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x004b len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 1 ilen 0 fcs 0x29 credits 33
> ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0041 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 1 ilen 0 fcs 0xf3 credits 15
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x004a
< ACL data: handle 43 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x004a
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 82
L2CAP(d): cid 0x0041 len 78 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 0 ilen 74 fcs 0xef
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x004b len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x004b len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x004b len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x004b len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x004b len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x004b len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x004b len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x004b len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x004b len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x004b len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
< ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x004b len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 3 pf 0 ilen 1 fcs 0x35
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 43 flags 0x02 dlen 9
L2CAP(d): cid 0x0041 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 3 pf 1 ilen 0 fcs 0xf3 credits 8
> HCI Event: Disconn Complete (0x05) plen 4
< HCI Command: Create Connection (0x01|0x0005) plen 13
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Connect Complete (0x03) plen 11
----------------------------- part of ps
1428 root 368 S hcid: processing events
1439 root 408 S /usr/sbin/sdpd
----------------------------- part of dmesg
Bluetooth: HCI USB driver ver 2.7
usbcore: registered new driver hci_usb
Bluetooth: VHCI driver ver 1.1
Bluetooth: HCI UART driver ver 2.1
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Bluetooth: Broadcom Blutonium firmware driver ver 1.0
usbcore: registered new driver bcm203x
Bluetooth: BlueFRITZ! USB driver ver 1.1
usbcore: registered new driver bfusb
Advanced Linux Sound Architecture Driver Version 1.0.6 (Sun Aug 15 07:17:53
2004 UTC).
s3c2410_pcm1748_map_registers: mapped dev s3c2410-iis registers to
0xc4e80000
s3c2410_pcm1748_init_hardware
pclk rate: 50700000
snd_card_pcm1748_setup_irq tcon=00590900, tcnt 041f, tcfg 00000200,00000030
TIMER_HZ: 8000
snd_card_pcm1748_probe: sound card registered!
ALSA device list:
#0: pcm1748 1
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET: Registered protocol family 1
NET: Registered protocol family 17
Bluetooth: L2CAP ver 2.6
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.3
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM ver 1.3
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: BNEP (Ethernet Emulation) ver 1.2
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.0
----------------------------- stdout/stderrs
Read from rfcomm0
/var/lib/bluetooth/00:A0:96:0D:3B:80.cmds: 20: cannot create /dev/rfcomm0:
Connection reset by peer
Reading from rfcomm0
Read from rfcomm0
/var/lib/bluetooth/00:A0:96:0D:3B:80.cmds: 20: cannot create /dev/rfcomm0:
Connection reset by peer
Reading from rfcomm0
Read from rfcomm0
/var/lib/bluetooth/00:A0:96:0D:3B:80.cmds: 20: cannot create /dev/rfcomm0:
Connection reset by peer
Reading from rfcomm0
Read from rfcomm0
/var/lib/bluetooth/00:A0:96:0D:3B:80.cmds: 20: cannot create /dev/rfcomm0:
Connection reset by peer
Reading from rfcomm0
Read from rfcomm0
/var/lib/bluetooth/00:A0:96:0D:3B:80.cmds: 20: cannot create /dev/rfcomm0:
Connection reset by peer
Reading from rfcomm0
Read from rfcomm0
/var/lib/bluetooth/00:A0:96:0D:3B:80.cmds: 20: cannot create /dev/rfcomm0:
Host is down
----------------------------- hciconfig
hciconfig
hci0: Type: USB
BD Address: 00:0A:4F:00:41:84 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:47592 acl:1364 sco:0 events:2726 errors:0
TX bytes:36502 acl:2022 sco:0 commands:304 errors:0
----------------------------- ls of ...
crw-rw-rw- 1 root root 216, 0 Oct 3 11:08 /dev/rfcomm0
crw-rw-r-- 1 root root 10, 250 Oct 3 10:23 /dev/vhci
[-- Attachment #2: Type: text/html, Size: 84259 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [Bluez-devel] Cannot send through serial device rfcomm
2005-10-03 20:42 Robert Wlaschin
@ 2005-10-04 11:16 ` Marcel Holtmann
0 siblings, 0 replies; 10+ messages in thread
From: Marcel Holtmann @ 2005-10-04 11:16 UTC (permalink / raw)
To: bluez-devel
Hi Robert,
please stop using HTML emails and especially don't use colors. The good
old plain ASCII is enough.
> I'm cross-compiling for an Arm processor using a Debian 2.6.10 kernel
> with bluez-utils/lib 2.21, and bluez-hcidump 2.25 w/ a brainbox usb
> adapter for rs-232 replacement (CSR chipset)
>
> I'm having a problem communicating through the /dev/rfcomm0 device. I
> thought that once the device was connected it would be have like a
> serial device and I could do this ...
>
> cat /dev/rfcomm0 > myfile.dat
> echo AT > /dev/rfcomm0
>
> Am I assuming correctly? If not what am I missing? Do I need to use
> the pppd or the dund to communicate? Am I in the wrong mode (master
> vs slave).
>
> If this should work please look at my log files, I'm executing
> these commands ...
>
> hcid
> sdpd
> sdptool add SP
> rfcomm bind 0 XX:XX ...
I think you made a big mistake in understanding how Bluetooth and Linux
are working. Describe what kind of communication you try to achieve and
then we might be able to help you.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [Bluez-devel] Cannot send through serial device rfcomm
@ 2005-10-04 16:32 Robert Wlaschin
2005-10-04 19:58 ` Marcel Holtmann
0 siblings, 1 reply; 10+ messages in thread
From: Robert Wlaschin @ 2005-10-04 16:32 UTC (permalink / raw)
To: 'bluez-devel@lists.sourceforge.net',
'Marcel Holtmann'
[-- Attachment #1: Type: text/plain, Size: 2293 bytes --]
I appreciate the heads up.
In regards to the type of communication, I'm trying to create a BT serial
connection. The device I'm attempting to connect to is actually a weight
scale (medical device). It doesn't support any other services. I probably
need to add that I changed rfcomm.conf to listen, bind, and connect for
rfcomm0. Note: The last time I used linux was in college and it was only to
compile my assignments, so I'm not savvy.
If you are at all familiar with Windows XP, I can use Hyperterminal to
communicate with the meter simply by typing commands in the terminal area
but for this to work I have to assign a port to the BT adapter.
Thanks,
Robert
-----Original Message-----
From: Marcel Holtmann
To: bluez-devel@lists.sourceforge.net
Sent: 10/4/05 04:16
Subject: RE: [Bluez-devel] Cannot send through serial device rfcomm
Hi Robert,
please stop using HTML emails and especially don't use colors. The good
old plain ASCII is enough.
> I'm cross-compiling for an Arm processor using a Debian 2.6.10 kernel
> with bluez-utils/lib 2.21, and bluez-hcidump 2.25 w/ a brainbox usb
> adapter for rs-232 replacement (CSR chipset)
>
> I'm having a problem communicating through the /dev/rfcomm0 device. I
> thought that once the device was connected it would be have like a
> serial device and I could do this ...
>
> cat /dev/rfcomm0 > myfile.dat
> echo AT > /dev/rfcomm0
>
> Am I assuming correctly? If not what am I missing? Do I need to use
> the pppd or the dund to communicate? Am I in the wrong mode (master
> vs slave).
>
> If this should work please look at my log files, I'm executing
> these commands ...
>
> hcid
> sdpd
> sdptool add SP
> rfcomm bind 0 XX:XX ...
I think you made a big mistake in understanding how Bluetooth and Linux
are working. Describe what kind of communication you try to achieve and
then we might be able to help you.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads,
discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
[-- Attachment #2: Type: text/html, Size: 4235 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [Bluez-devel] Cannot send through serial device rfcomm
2005-10-04 16:32 Robert Wlaschin
@ 2005-10-04 19:58 ` Marcel Holtmann
0 siblings, 0 replies; 10+ messages in thread
From: Marcel Holtmann @ 2005-10-04 19:58 UTC (permalink / raw)
To: Robert Wlaschin; +Cc: 'bluez-devel@lists.sourceforge.net'
Hi Robert,
> In regards to the type of communication, I'm trying to create a BT
> serial connection. The device I'm attempting to connect to is
> actually a weight scale (medical device). It doesn't support any
> other services. I probably need to add that I changed rfcomm.conf to
> listen, bind, and connect for rfcomm0. Note: The last time I used
> linux was in college and it was only to compile my assignments, so I'm
> not savvy.
you need to do a "rfcomm bind 0 <bdaddr> <channel>" and you will get a
new /dev/rfcomm0 TTY device. Now use a terminal program like minicom or
cu for the communication.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [Bluez-devel] Cannot send through serial device rfcomm
@ 2005-10-04 22:46 Robert Wlaschin
2005-10-05 4:10 ` Marcel Holtmann
0 siblings, 1 reply; 10+ messages in thread
From: Robert Wlaschin @ 2005-10-04 22:46 UTC (permalink / raw)
To: 'Marcel Holtmann', Robert Wlaschin
Cc: 'bluez-devel@lists.sourceforge.net'
[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]
Marcel,
That was a good suggestion. I've seen usage of those programs on various
help/websites.
Due to a hardware limitations, I only have microcom available which seems
flaky at best. I seem to be getting the 'Exitcode 2 - cannot open device
/dev/rfcomm0' error message. But I have tried opening a standard serial
connection with microcom and it does function.
The code in attest should work given the method I am using, is this correct?
If so I can just rewrite it to something ... a little more towards my
purpose.
Thanks,
Robert
-----Original Message-----
From: Marcel Holtmann [mailto:marcel@holtmann.org]
Sent: Tuesday, October 04, 2005 12:59 PM
To: Robert Wlaschin
Cc: 'bluez-devel@lists.sourceforge.net'
Subject: RE: [Bluez-devel] Cannot send through serial device rfcomm
Hi Robert,
> In regards to the type of communication, I'm trying to create a BT
> serial connection. The device I'm attempting to connect to is
> actually a weight scale (medical device). It doesn't support any
> other services. I probably need to add that I changed rfcomm.conf to
> listen, bind, and connect for rfcomm0. Note: The last time I used
> linux was in college and it was only to compile my assignments, so I'm
> not savvy.
you need to do a "rfcomm bind 0 <bdaddr> <channel>" and you will get a
new /dev/rfcomm0 TTY device. Now use a terminal program like minicom or
cu for the communication.
Regards
Marcel
[-- Attachment #2: Type: text/html, Size: 2561 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [Bluez-devel] Cannot send through serial device rfcomm
2005-10-04 22:46 Robert Wlaschin
@ 2005-10-05 4:10 ` Marcel Holtmann
0 siblings, 0 replies; 10+ messages in thread
From: Marcel Holtmann @ 2005-10-05 4:10 UTC (permalink / raw)
To: Robert Wlaschin; +Cc: 'bluez-devel@lists.sourceforge.net'
Hi Robert,
> That was a good suggestion. I've seen usage of those programs on
> various help/websites.
>
> Due to a hardware limitations, I only have microcom available which
> seems flaky at best. I seem to be getting the 'Exitcode 2 - cannot
> open device /dev/rfcomm0' error message. But I have tried opening a
> standard serial connection with microcom and it does function.
>
> The code in attest should work given the method I am using, is this
> correct? If so I can just rewrite it to something ... a little more
> towards my purpose.
check if the /dev/rfcomm0 device node has been created and if yes, then
run "hcidump -X -V" to see why the RFCOMM channel can't be opened.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [Bluez-devel] Cannot send through serial device rfcomm
@ 2005-10-05 17:32 Robert Wlaschin
2005-10-05 17:54 ` Marcel Holtmann
0 siblings, 1 reply; 10+ messages in thread
From: Robert Wlaschin @ 2005-10-05 17:32 UTC (permalink / raw)
To: 'Marcel Holtmann', Robert Wlaschin
Cc: 'bluez-devel@lists.sourceforge.net'
[-- Attachment #1: Type: text/plain, Size: 3781 bytes --]
Marcel,
Thanks so much for the help thus far. Yes the rfcomm0 device is created:
This is the output from rfcomm; rfcomm0: 00:A0:96:0D:3B:80 channel 1 closed,
I have also seen it report [tty-attached] when I am attempting to
read/write/connect, but it says 'config' not 'open'
So, I saw this error message:
> HCI Event: Connect Complete (0x03) plen 11
status 0x05 handle 41 bdaddr 00:A0:96:0D:3B:80 type ACL encrypt 0x00
Error: Authentication Failure
So I did this: hciconfig hci0 auth, but I still got the same error, so I
followed with this: hciconfig hci0 encrypt, but I still seem to be getting
the error message.
Thanks,
Robert
--- hcidump -V -X ---
HCI sniffer - Bluetooth packet analyzer ver 1.25
device: hci0 snap_len: 1028 filter: 0xffffffff
> HCI Event: Connect Request (0x04) plen 10
bdaddr 00:A0:96:0D:3B:80 class 0x000000 type ACL
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
bdaddr 00:A0:96:0D:3B:80 role 0x01
Role: Slave
> HCI Event: Command Status (0x0f) plen 4
Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Link Key Request (0x17) plen 6
bdaddr 00:A0:96:0D:3B:80
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:A0:96:0D:3B:80 key 5375351370402E9AE37B284D7DD72EDC
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:A0:96:0D:3B:80
> HCI Event: Connect Complete (0x03) plen 11
status 0x05 handle 41 bdaddr 00:A0:96:0D:3B:80 type ACL encrypt 0x00
Error: Authentication Failure
> HCI Event: Connect Request (0x04) plen 10
bdaddr 00:A0:96:0D:3B:80 class 0x000000 type ACL
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
bdaddr 00:A0:96:0D:3B:80 role 0x01
Role: Slave
> HCI Event: Command Status (0x0f) plen 4
Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Link Key Request (0x17) plen 6
bdaddr 00:A0:96:0D:3B:80
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
bdaddr 00:A0:96:0D:3B:80 key 5375351370402E9AE37B284D7DD72EDC
> HCI Event: Command Complete (0x0e) plen 10
Link Key Request Reply (0x01|0x000b) ncmd 1
status 0x00 bdaddr 00:A0:96:0D:3B:80
> HCI Event: Connect Complete (0x03) plen 11
status 0x05 handle 42 bdaddr 00:A0:96:0D:3B:80 type ACL encrypt 0x00
Error: Authentication Failure
Usage: microcom [options]
[options] include:
-Ddevfile use the specified serial port device;
if a port is not provided, microcom
will try to autodetect a modem
example: -D/dev/ttyS3
-S run script from script.scr (default)
-Sscrfile run script from scrfile
microcom provides session logging in microcom.log file
Exitcode 2 - cannot open device /dev/rfcomm0
-----Original Message-----
From: Marcel Holtmann [mailto:marcel@holtmann.org]
Sent: Tuesday, October 04, 2005 9:11 PM
To: Robert Wlaschin
Cc: 'bluez-devel@lists.sourceforge.net'
Subject: RE: [Bluez-devel] Cannot send through serial device rfcomm
Hi Robert,
> That was a good suggestion. I've seen usage of those programs on
> various help/websites.
>
> Due to a hardware limitations, I only have microcom available which
> seems flaky at best. I seem to be getting the 'Exitcode 2 - cannot
> open device /dev/rfcomm0' error message. But I have tried opening a
> standard serial connection with microcom and it does function.
>
> The code in attest should work given the method I am using, is this
> correct? If so I can just rewrite it to something ... a little more
> towards my purpose.
check if the /dev/rfcomm0 device node has been created and if yes, then
run "hcidump -X -V" to see why the RFCOMM channel can't be opened.
Regards
Marcel
[-- Attachment #2: Type: text/html, Size: 7091 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [Bluez-devel] Cannot send through serial device rfcomm
2005-10-05 17:32 Robert Wlaschin
@ 2005-10-05 17:54 ` Marcel Holtmann
0 siblings, 0 replies; 10+ messages in thread
From: Marcel Holtmann @ 2005-10-05 17:54 UTC (permalink / raw)
To: Robert Wlaschin; +Cc: 'bluez-devel@lists.sourceforge.net'
Hi Robert,
> much for the help thus far. Yes the rfcomm0 device is created:
> This is the output from rfcomm; rfcomm0: 00:A0:96:0D:3B:80 channel 1
> closed, I have also seen it report [tty-attached] when I am attempting
> to read/write/connect, but it says 'config' not 'open'
>
> So, I saw this error message:
>
> > HCI Event: Connect Complete (0x03) plen 11
> status 0x05 handle 41 bdaddr 00:A0:96:0D:3B:80 type ACL encrypt
> 0x00
> Error: Authentication Failure
this means that you provide the wrong link key. Delete all your link
keys or set the device into pairing mode.
> So I did this: hciconfig hci0 auth, but I still got the same error, so
> I followed with this: hciconfig hci0 encrypt, but I still seem to be
> getting the error message.
This is a misconception. What activated security mode 3 and this is not
helpful at all.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [Bluez-devel] Cannot send through serial device rfcomm
@ 2005-10-05 18:38 Robert Wlaschin
2005-10-05 18:55 ` Marcel Holtmann
0 siblings, 1 reply; 10+ messages in thread
From: Robert Wlaschin @ 2005-10-05 18:38 UTC (permalink / raw)
To: 'Marcel Holtmann'; +Cc: 'bluez-devel@lists.sourceforge.net'
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
Marcel,
Thanks, that seems to get rid of the Authentication error. I seem to be
able to issue commands through microcom now.
I appreciate the help. Is there a recommended way to verify the linkkey
isn't incorrect?
Thanks,
Robert
-----Original Message-----
From: Marcel Holtmann [mailto:marcel@holtmann.org]
Sent: Wednesday, October 05, 2005 10:54 AM
To: Robert Wlaschin
Cc: 'bluez-devel@lists.sourceforge.net'
Subject: RE: [Bluez-devel] Cannot send through serial device rfcomm
Hi Robert,
> much for the help thus far. Yes the rfcomm0 device is created:
> This is the output from rfcomm; rfcomm0: 00:A0:96:0D:3B:80 channel 1
> closed, I have also seen it report [tty-attached] when I am attempting
> to read/write/connect, but it says 'config' not 'open'
>
> So, I saw this error message:
>
> > HCI Event: Connect Complete (0x03) plen 11
> status 0x05 handle 41 bdaddr 00:A0:96:0D:3B:80 type ACL encrypt
> 0x00
> Error: Authentication Failure
this means that you provide the wrong link key. Delete all your link
keys or set the device into pairing mode.
> So I did this: hciconfig hci0 auth, but I still got the same error, so
> I followed with this: hciconfig hci0 encrypt, but I still seem to be
> getting the error message.
This is a misconception. What activated security mode 3 and this is not
helpful at all.
Regards
Marcel
[-- Attachment #2: Type: text/html, Size: 2702 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [Bluez-devel] Cannot send through serial device rfcomm
2005-10-05 18:38 [Bluez-devel] Cannot send through serial device rfcomm Robert Wlaschin
@ 2005-10-05 18:55 ` Marcel Holtmann
0 siblings, 0 replies; 10+ messages in thread
From: Marcel Holtmann @ 2005-10-05 18:55 UTC (permalink / raw)
To: Robert Wlaschin; +Cc: 'bluez-devel@lists.sourceforge.net'
Hi Robert,
> I appreciate the help. Is there a recommended way to verify the
> linkkey isn't incorrect?
in case of an authentication and an previous requested link key we
should remove it from the file storage, but we are not doing this at the
moment.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2005-10-05 18:55 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-05 18:38 [Bluez-devel] Cannot send through serial device rfcomm Robert Wlaschin
2005-10-05 18:55 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2005-10-05 17:32 Robert Wlaschin
2005-10-05 17:54 ` Marcel Holtmann
2005-10-04 22:46 Robert Wlaschin
2005-10-05 4:10 ` Marcel Holtmann
2005-10-04 16:32 Robert Wlaschin
2005-10-04 19:58 ` Marcel Holtmann
2005-10-03 20:42 Robert Wlaschin
2005-10-04 11:16 ` Marcel Holtmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).