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

[bluetooth-dev] Pairing with Ericsson T68 phone



I've been trying to establish connection between Ericsson Bluetooth
module ROK 008 and Ericsson T68 mobile phone.  I've had couple of
problems...

1) When I start the pairing process from the phone and when the
"Searching" progress bar has reached the end, sometimes I get a lot of
weird looking HCI packets.  They seem to be Ericsson vendor specific,
can anybody recognize the following?

process_event (8):
0x04 0x00 0x02 0x00 0x00 0x0a 0x42 0x04
BT SYS: ERROR: process_vendor_event [Ericsson] Vendor specific event not
recognized.

Usually I get hundreds of those which after the Host Controller seem to
reset itself.


2) After it has searched and found my Bluetooth device (ROK 008), the
phone asks "Add to paired devices?". After I say "Yes", it asks for
passkey and starts the "Pairing" process.  Everything seems to go well,
connection gets requested and accepted, the phone asks for pin code to
which my simple security manager replies, pin code seems to get accepted
and the phone sends link key notification event.

But, what's supposed to happen next?  Should I reply to the
LINK_KEY_NOTIFICATION event?  Currently I don't, and what happens is
that the phone waits for a while, timeouts and says "Pairing failed".
Obviously, the phone was still waiting to get something back, but what
should I send?

Any help is appreciated.

PS. I'll include a complete HCI log from the pairing process.

Regards,
Kim

----

hci_receive_data:  (13):
0x04 0x04 0x0a 0xcd 0x6a 0xee 0x37 0x80 0x00 0x04 0x02 0x52 0x01

process_event (10):
0xcd 0x6a 0xee 0x37 0x80 0x00 0x04 0x02 0x52 0x01
HCI: process_event: CONNECTION_REQUEST

lp_connect_ind: from:  (6):
0xcd 0x6a 0xee 0x37 0x80 0x00
    L2CAP lp_connect_ind: Accepting connection
    L2CAP l2cap_create_con

l2cap_create_con: bd  (6):
0xcd 0x6a 0xee 0x37 0x80 0x00
    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
show_con: insert_con (64:0) [CLOSED] [unknown] r_mtu[672] C[no]
link_up[yes]
    L2CAP insert_con: now 1 connections
HCI: lp_connect_rsp: Status: 1
HCI: accept_connection_request: bd_addr cd 6a ee 37 80 0
HCI: insert_cmd
HCI: insert_cmd: WRAP
HCI: get_next_cmd: next_to_send WRAP

send_cmd_queue:  (11):
0x01 0x09 0x04 0x07 0xcd 0x6a 0xee 0x37 0x80 0x00 0x01

hci_receive_data:  (7):
0x04 0x0f 0x04 0x00 0x01 0x09 0x04

process_event (4):
0x00 0x01 0x09 0x04
HCI: release_cmd_timer
HCI: process_event: COMMAND_STATUS

hci_receive_data:  (9):
0x04 0x16 0x06 0xcd 0x6a 0xee 0x37 0x80 0x00

process_event (6):
0xcd 0x6a 0xee 0x37 0x80 0x00
HCI: process_event: PIN_CODE_REQUEST forwarding event to security
manager

hci_pin_code_request_reply: New pin is
 (4): 0x30 0x30 0x30 0x30

hci_pin_code_request_reply:  BD_addr (6):
0xcd 0x6a 0xee 0x37 0x80 0x00

hci_pin_code_request_reply:  pin (4):
0x30 0x30 0x30 0x30
HCI: insert_cmd

send_cmd_queue:  (27):
0x01 0x0d 0x04 0x17 0xcd 0x6a 0xee 0x37 0x80 0x00 0x04 0x30 0x30 0x30
0x30 0x00
0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00

hci_receive_data:  (13):
0x04 0x0e 0x0a 0x01 0x0d 0x04 0x00 0xcd 0x6a 0xee 0x37 0x80 0x00

process_event (10):
0x01 0x0d 0x04 0x00 0xcd 0x6a 0xee 0x37 0x80 0x00
HCI: process_event: COMMAND_COMPLETE
HCI: release_cmd_timer
HCI: process_return_param: PIN_CODE_REQUEST_REPLY
HCI: process_return_param: PIN_CODE_REQUEST_REPLY  Success

hci_receive_data:  (26):
0x04 0x18 0x17 0xcd 0x6a 0xee 0x37 0x80 0x00 0xd8 0xd6 0x7c 0xb2 0xf0
0x23 0x9d
0xeb 0x14 0x12 0x02 0x1a 0xe3 0x77 0xe8 0x63 0x00

process_event (23):
0xcd 0x6a 0xee 0x37 0x80 0x00 0xd8 0xd6 0x7c 0xb2 0xf0 0x23 0x9d 0xeb
0x14 0x12
0x02 0x1a 0xe3 0x77 0xe8 0x63 0x00
HCI: process_event: LINK_KEY_NOTIFICATION forwarding event to security
manager
Called sec_man_event user:0 event:18



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