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

[bluetooth-dev] Some buffers problems, TI chip and PPP



Hi all,

I've a problem that is really not easy to locate because it has a lot of
parameters. I'll explain the status, and if someone have an idea where the
problem comes from, I'll be very gratefull. Precise questions are at the
end of this e-mail.

Generic Situation :

- Hardware : TI 6030 chip (point-to-point) on TI developpment board
- OpenBT 0.0.8 with Hardware "Generic" setting.
- Simple security manager
- Remote device : Ericsson T39m phone

Test 1 : Don't Activate "Use In buffers" option in kernel config

Test 2 : Activate "Use In buffers" option in kernel config

--> Problem During test 1 :

After the connection has been made (it doesn't always work, but most of
the time, the connection can be established), I start ppp. it can compose
the phone number, but when ppp start negociation, nothing more happen
until I got errors. Note that it's strange that I get "invalid inbuffer"
error event if I didn't activate this option...

Here are the log (with some logs from other softwares) :

--- Test 1 logs ---

btcon -d /dev/ttyBT0 -a 00:80:37:16:b5:54 -S 2

bd (6):
0x54 0xb5 0x16 0x37 0x80 0x00 
l2ca_connect_req: wait baseband, sleep on wq 0x107902a8
Link key returned

hci_link_key_request_reply:  BD_addr (6):
0x54 0xb5 0x16 0x37 0x80 0x00 

hci_link_key_request_reply:  Link Key (16):
0x44 0xc8 0xed 0xed 0x87 0xd7 0x6a 0xe6 0x54 0xc0 0x5e 0xa0 0x5e 0x59 0xd3
0x4a lp_connect_cfm (pos), wake up wq 0x107902a8
lp_connect_cfm, wake up flag not set
BT SYS: process_event: ACL link is up
l2ca_connect_req: wait baseband, woke up !
l2ca_connect_req: wait rsp, sleep on wq 0x107902a8
BT SYS: ERROR: get_inbuffer: WARNING! No inbuffer with hci_hdl 2
BT SYS: ERROR: invalid inbuffer
BT SYS: ERROR: get_inbuffer: WARNING! No inbuffer with hci_hdl 2
BT SYS: ERROR: invalid inbuffer
REMOTE_NAME_REQUEST_COMPLETE : wake_up(get_name_wq)
BT SYS: ERROR: get_inbuffer: WARNING! No inbuffer with hci_hdl 2
BT SYS: ERROR: invalid inbuffer
BT SYS: ERROR: get_inbuffer: WARNING! No inbuffer with hci_hdl 2
BT SYS: ERROR: invalid inbuffer
l2cap con rsp, wake up wq 0x107902a8

l2cap options:  (0):
l2ca_connect_req: wait rsp, woke up !
BT SYS: Setting remote mtu (64:77) to 251 bytes
BT SYS: l2cap channel (64,77) [RFCOMM] connected
BT SYS: rfcomm_config_cfm: l2cap is now open
BT SYS: bt_register_rfcomm: dlci 4 on line 0
rm_server: task 'pppd' 'name' 'remora1' 'connect' 'chat -v -s ABORT BUSY
ABORT 'NO CARRIER' '' ATZ OK 'ATD+41840840111' CONNECT ''' 'modem'
'defaultroute' '/dev/ttyBT0' '57600' on slot 2 [pid 56] pppd 2.2.0 started
by root, uid 0chat: abort on (BUSY) chat: abort on (NO CARRIER)
chat: send (ATZ^M)
chat: expect (OK)
chat: ATZ^M^M
chat: OK
chat:  -- got it

chat: send (ATD+41840840111^M)
chat: expect (CONNECT)
chat: ^M
chat: ATD+41840840111^M^M
chat: CONNECT
chat:  -- got it

chat: send (^M)
Serial connection established.
Using interface ppp0
Connect: ppp0 <--> /dev/ttyBT0
BT SYS: ERROR: hci_receive_data: 32000 is too big for our HCI inputbuffers -- discarding buffer
BT SYS: ERROR: hci_receive_data: discarding 2 bytes
BT SYS: ERROR: hci_receive_data: 32000 is too big for our HCI input buffers -- discarding buffer 
BT SYS: ERROR: hci_receive_data: discarding 2 bytes 
BT SYS: ERROR: hci_receive_data: discarding 2 bytes
BT SYS: ERROR: hci_receive_data: discarding 2 bytes
BT SYS: ERROR: hci_receive_data: discarding 2 bytes
BT SYS: ERROR: hci_receive_data: discarding 2 bytes
BT SYS: ERROR: hci_receive_data: discarding 2 bytes
Serial line is looped back.Connection terminated.Exit

---- End of test 1 logs ---

Note that after the line "Connect: ppp0 <--> /dev/ttyBT0", I have to wait
about 10 seconds before next lines come.



--> Problem during test 2 :

As soon as the connection is established, a deconnection happen... I've
not the time to start ppp.

Here are the logs (with some logs from other softwares) :

--- Logs of test 2 ---

bd (6):
0x54 0xb5 0x16 0x37 0x80 0x00 
l2ca_connect_req: wait baseband, sleep on wq 0x1075c2a8
Link key returned

hci_link_key_request_reply:  BD_addr (6):
0x54 0xb5 0x16 0x37 0x80 0x00 

hci_link_key_request_reply:  Link Key (16):
0x44 0xc8 0xed 0xed 0x87 0xd7 0x6a 0xe6 0x54 0xc0 0x5e 0xa0 0x5e 0x59 0xd3
0x4a lp_connect_cfm (pos), wake up wq 0x1075c2a8
lp_connect_cfm, wake up flag not set
BT SYS: process_event: ACL link is up
WRITE LINK_POLICY_SETTINGS
l2ca_connect_req: wait baseband, woke up !
l2ca_connect_req: wait rsp, sleep on wq 0x1075c2a8
BT SYS: ERROR: get_inbuffer: WARNING! No inbuffer with hci_hdl 2
BT SYS: ERROR: invalid inbuffer
BT SYS: ERROR: get_inbuffer: WARNING! No inbuffer with hci_hdl 2
BT SYS: ERROR: invalid inbuffer
BT SYS: ERROR: get_inbuffer: WARNING! No inbuffer with hci_hdl 2
BT SYS: ERROR: invalid inbuffer
BT SYS: ERROR: get_inbuffer: WARNING! No inbuffer with hci_hdl 2
BT SYS: ERROR: invalid inbuffer
BT SYS: ERROR: get_inbuffer: WARNING! No inbuffer with hci_hdl 2
BT SYS: ERROR: invalid inbuffer
BT SYS: ERROR: get_inbuffer: WARNING! No inbuffer with hci_hdl 2
BT SYS: ERROR: invalid inbuffer
l2cap con rsp, wake up wq 0x1075c2a8

l2cap options:  (0):
l2ca_connect_req: wait rsp, woke up !
REMOTE_NAME_REQUEST_COMPLETE : wake_up(get_name_wq)
BT SYS: Setting remote mtu (64:80) to 251 bytes
BT SYS: l2cap channel (64,80) [RFCOMM] connected
BT SYS: rfcomm_config_cfm: l2cap is now open
BT SYS: rfcomm_disconnect_ind: remote cid 80
BT SYS: l2cap channel (64,80) [RFCOMM] disconnected
BT SYS: process_event: DISCONNECTION_COMPLETE Other End Terminated
Connection: User Ended Connection
BT SYS: lp_disconnect_ind: Connection handle 2 disconnected

--- End of logs of test 2 ---


Does someone use TI bluetooth chip ?
Does someone use openBT in "Generic hardware" mode ?
Can someone precise me the why when having in buffers the result is a
deconnection ?

Thank you for any advice. 


-- 
Alain Paschoud                      SMARTDATA SA
alain.paschoud@xxxxxxx.ch         PSE-A
http://www.smartdata.ch             1015 Lausanne
Phone +41-21-693'84'98              
Fax   +41-27-693'84'91              
-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com