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

Re: [bluetooth-dev] rfcomm connection



Mandana Amiri wrote:

> Hi again,
> I'm not sure if my email made it through yesterday. any suggestions for my
> problem described below?
>
> THanks,
> mandana
> ---------------------- Forwarded by Mandana Amiri/Inc/Celestica on 02/13/2001
> 10:33 AM ---------------------------
>
> "Mandana Amiri" <mamiri@xxxxxxx.com> on 02/12/2001 06:20:06 PM
>
>
>
>  To:      bluetooth-dev@xxxxxxx.com
>
>  cc:      (bcc: Mandana Amiri/Inc/Celestica)
>
>
>
>  Subject: [bluetooth-dev] rfcomm connection
>
>
> Hi,
> I can't get rfcomm connection to work. I've modified the stack because of a
> special setup that I have and I'm running it in usermode. (I know that user mode
> is not proven and sends data on dlci 2 only).
> I can get other things to work, like inquiry and read_bd. I type rf_conn
> 00:d0:b7:03:4b:e7 1 0
> and then rf_send 15 100 2
>
> Here is the dump for the client side, I wonder if someone can give me a clue of
> when things go wrong:
> Thanks,
>
> rf_conn 00:d0:b7:03:4a:0d 1 0
> Command Entered: rf_conn 00:d0:b7:03:4a:0d 1 0
> Connecting srv ch 1 on line 0
> we don't have l2cap ch yet for this rfcomm ch
>     L2CAP l2cap_connect_req
> l2ca_connect_req : sent to bd  (6)
>    0x00 0xd0 0xb7 0x03 0x4a 0x0d
>     L2CAP get_con : look for connections in state ANY_STATE (7)
> get_con : bd  (6)
>    0x0d 0x4a 0x03 0xb7 0xd0 0x00
>     L2CAP get_con : connection not found
>     L2CAP get_lcon : lcid 64 con_list.count = 0
>     L2CAP get_lcon : connection lcid : 64 not found
>     L2CAP Create_con rcid 0
>     L2CAP init_flow
> bd (6)
>    0x0d 0x4a 0x03 0xb7 0xd0 0x00
> show_con : insert_con() (64:0) [CLOSED] [RFCOMM] r_mtu[672] C[yes] link_up[no]
>     L2CAP insert_con : now 1 connections
>     L2CAP l2ca_connect_req : create new baseband link
> , bd addres is: (6)
>    0x0d 0x4a 0x03 0xb7 0xd0 0x00
> HCI: , start: Num_HCI_Command_Packets=1
> BT DATA <--|X|     17
> bt_write_lower_driver  (17)
>    0x01 0x05 0x04 0x0d 0x0d 0x4a 0x03 0xb7 0xd0 0x00 0x18 0xcc 0x00 0x00 0x00 0x
>    0x00
> BT DATA -->|X|      7  data rec :  (7)
>    0x04 0x0f 0x04 0x00 0x01 0x05 0x04
> , hci-7
>  (4)
>    0x00 0x01 0x05 0x04
> HCI: , Num_HCI_Command_Packets=1
> HCI: , start: Num_HCI_Command_Packets=1
> BT DATA -->|X|      8  data rec :  (8)
>    0x04 0x03 0x0b 0x00 0x01 0x00 0x0d 0x4a
> , hci-8
> BT DATA -->|X|      6  data rec :  (6)
>    0x03 0xb7 0xd0 0x00 0x01 0x00
> , hci-6
>  (11)
>    0x00 0x01 0x00 0x0d 0x4a 0x03 0xb7 0xd0 0x00 0x01 0x00
>     L2CAP lp_connectg: Success! (hci_handle : 1)
>     L2CAP get_con : look for connections in state CLOSED (0)
> get_con : bd  (6)
>    0x0d 0x4a 0x03 0xb7 0xd0 0x00
> get_con : con_list bd  (6)
>    0x0d 0x4a 0x03 0xb7 0xd0 0x00
>     L2CAP we are client
> lp_connect_cfm : HCI connected to  (6)
>    0x0d 0x4a 0x03 0xb7 0xd0 0x00
>     L2CAP Current state of (64:0) is W4_L2CAP_CONNECT_RSP
>     L2CAP l2cap_connect_req: Connecting RFCOMM (rcid:0)
> use NO timer...
> HCI: , 24 bytes
> HCI: , 24 bytes
> HCI: , send 24 bytes (excl HCI header) out of 24
> HCI: , There are 5 bytes space for the headers
> ,  (29)
>    0x02 0x01 0x20 0x18 0x00 0x10 0x00 0x01 0x00 0x00 0x00 0x00 0x00 0x02 0x01 0x
>    0x00 0x08 0x00 0x00 0x00 0x03 0x00 0x00 0x00 0x40 0x00 0x00 0x00
> BT DATA <--|X|     29
> bt_write_lower_driver  (29)
>    0x02 0x01 0x20 0x18 0x00 0x10 0x00 0x01 0x00 0x00 0x00 0x00 0x00 0x02 0x01 0x
>    0x00 0x08 0x00 0x00 0x00 0x03 0x00 0x00 0x00 0x40 0x00 0x00 0x00
> HCI: , now c = 24
> HCI: , unsubscribing tx_buf.
> BT SYS: , ACL link is up
> HCI: , WRAP
> HCI: , start: Num_HCI_Command_Packets=1
> HCI: , next_to_send WRAP
> BT DATA <--|X|      8
> bt_write_lower_driver  (8)
>    0x01 0x0f 0x04 0x04 0x01 0x00 0x00 0xcc
> HCI: , start: Num_HCI_Command_Packets=0
> BT DATA -->|X|      7  data rec :  (7)
>    0x04 0x0f 0x04 0x00 0x00 0x0f 0x04
> , hci-7
>  (4)
>    0x00 0x00 0x0f 0x04
> HCI: , Num_HCI_Command_Packets=0
> HCI: , start: Num_HCI_Command_Packets=0
> BT DATA -->|X|     15  data rec :  (15)
>    0x04 0x1d 0x05 0x00 0x01 0x00 0x00 0xcc 0x04 0x0e 0x04 0x01 0x00 0x00 0x00
> , hci-15
>  (5)
>    0x00 0x01 0x00 0x00 0xcc
> ? (4)
>    0x01 0x00 0x00 0x00
> HCI: , Num_HCI_Command_Packets=1
> HCI: , start: Num_HCI_Command_Packets=1
> BT DATA <--|X|     14
> bt_write_lower_driver  (14)
>    0x01 0x19 0x04 0x0a 0x0d 0x4a 0x03 0xb7 0xd0 0x00 0x00 0x00 0x00 0x00
> BT DATA -->|X|      7  data rec :  (7)
>    0x04 0x0f 0x04 0x00 0x01 0x19 0x04
> , hci-7
>  (4)
>    0x00 0x01 0x19 0x04
> HCI: , Num_HCI_Command_Packets=1
> HCI: , start: Num_HCI_Command_Packets=1
> BT DATA -->|X|      8  data rec :  (8)
>    0x04 0x07 0xff 0x00 0x0d 0x4a 0x03 0xb7
> , hci-8
> BT DATA -->|X|     14  data rec :  (14)
>    0xd0 0x00 0x62 0x6c 0x75 0x65 0x5f 0x6b 0x69 0x6e 0x67 0x00 0x00 0x00
> , hci-14
> BT DATA -->|X|     47  data rec :  (47)
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> , hci-47
> BT DATA -->|X|     95  data rec :  (95)
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> , hci-95
> BT DATA -->|X|     94  data rec :  (94)
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> , hci-94
>  (255)
>    0x00 0x0d 0x4a 0x03 0xb7 0xd0 0x00 0x62 0x6c 0x75 0x65 0x5f 0x6b 0x69 0x6e 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x
>    0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
>
> -
> To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
> the body of a message to majordomo@xxxxxxx.com
>
>   ------------------------------------------------------------------------
>                Name: att1.eml
>    att1.eml    Type: unspecified type (application/octet-stream)
>            Encoding: base64

Hm... I'd say things go wrong about the time you start getting all those zeros.
I've never seen that. Any idea why you are? Is the server side really sending all
that crap?

--gmcnutt

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