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

[bluetooth-dev] other (same?) SDP problem



using a toshiba PC card (digianswer software, Win98, Laptop) to connect
to the 0.0.4 stack compiled for ericsson (i386, 2.2.16) everything
works.
when connecting to a _csr_ device connected to our target (ARM7, uclinux
2.0.X) connection fails and the error "Error ocured while attempting to
establish Serial Port link" appears on the laptop.

enabling all the debugging, i noticed the following difference on the
line that says "l2cap_send_data:  (18):".
could this be a problem with sdp_server?
has someone tested the sdp_server on a ARM platform?
david LIBAULT: do we have the same problem?


1. this works (ericsson, i386, 2.2.16)
--------------------------------------
...
...
sdp_receive_data (13):
0x02 0x77 0x77 0x00 0x08 0x35 0x03 0x19 0x11 0x09 0x01 0x00 0x00 
wake_up process 231 (syslogd) awakening
wake_up process 231 (syslogd) woke up
HCI: hci_clear_buffer, 
HCI: get_inbuffer, Found inbuffer for hci_hdl 39 c2849ff4
sdp_database_read Returning 21 bytes
sdp_database_write Someone wrote 8 bytes to sdp proc-file
sdp_database_write Someone wrote 14 bytes to sdp proc-file
          SDP sdp_database_write preparing to send 14 bytes data to
sdp_con[0]
 
Data to be sent to client: (14):
0x01 0x00 0x00 0x00 0x00 0x40 0x32 0xc0 0x0e 0x00 0x00 0x00 0x00 0x00 
    L2CAP l2cap_send_data: hdl : 39, rcid : 64, len:14 

l2cap_send_data:  (18):
0x0e 0x00 0x40 0x00 0x03 0x77 0x77 0x00 0x09 0x00 0x01 0x00 0x01 0x01
0x01 0xff 
0xff 0x00 
HCI: hci_send_data, 18 bytes 
sdp_database_read Someone is trying to read 256 bytes from sdp proc-file
sdp_database_read No bytes available, going to sleep
HCI: send_acl_data_task, 18 bytes 
HCI: send_acl_data_task, 18 bytes 
HCI: send_acl_packet, send 18 bytes (excl HCI header) out of 18
HCI: send_acl_packet, There are 5 bytes space for the headers

send_acl_packet,  (23):
...
...




2. this dosen't (csr, ARM7, uclinux 2.0.38)
-------------------------------------------
...
...
sdp_receive_data (13):
0x02 0x77 0x77 0x00 0x08 0x35 0x03 0x19 0x11 0x09 0x01 0x00 0x00
wake_up process 0 (swapper) awakening
wake_up process 0 (swapper) woke up
HCI: hci_clear_buffer,
HCI: get_inbuffer, Found inbuffer for hci_hdl 39 80014b94
HCI: send_cmd_queue, start: Num_HCI_Command_Packets=1
 
send_cmd_queue,  (8):
0x01 0x0d 0x08 0x04 0x27 0x00 0x01 0x00
BT DATA <--|X|      8
 
<--|X| (8):
0x01 0x0d 0x08 0x04 0x27 0x00 0x01 0x00
HCI: send_cmd_queue, end : 0 cmds left in queue
sdp_database_read Returning 21 bytes
BT DATA -->|X|      9
 
-->|X| (9):
0x04 0x0e 0x06 0x01 0x0d 0x08 0x00 0x27 0x00
 
hci_receive_data,  (9):
0x04 0x0e 0x06 0x01 0x0d 0x08 0x00 0x27 0x00
hci_receive_data, hci-9
HCI: hci_receive_data, WAIT_FOR_PACKET_TYPE
HCI: hci_receive_data, WAIT_FOR_EVENT_TYPE
HCI: hci_receive_data, WAIT_FOR_EVENT_LENGTH
 
process_event (6):
0x01 0x0d 0x08 0x00 0x27 0x00
HCI: process_event, COMMAND_COMPLETE
HCI: <CC>
process_return_param, WRITE_LINK_POLICY_SETTINGS
 HCI: update_nhcp, Num_HCI_Command_Packets=1
HCI: send_cmd_queue, start: Num_HCI_Command_Packets=1
HCI: send_cmd_queue, end : 0 cmds left in queue
sdp_database_write Someone wrote 8 bytes to sdp proc-file
sdp_database_write Someone wrote 14 bytes to sdp proc-file
          SDP sdp_database_write preparing to send 14 bytes data to
sdp_con[0]
 
Data to be sent to client: (14):
0x01 0x00 0x00 0x00 0x18 0x00 0x06 0x80 0x0e 0x00 0x00 0x00 0x00 0x00
    L2CAP l2cap_send_data: hdl : 39, rcid : 64, len:14
 
l2cap_send_data:  (18):
0x0e 0x00 0x40 0x00 0x03 0x77 0x77 0x00 0x09 0x00 0x01 0x00 0x01 0x00
0x00 0x00
0x00 0x00
HCI: hci_send_data, 18 bytes
sdp_database_read Someone is trying to read 256 bytes from sdp proc-file
sdp_database_read No bytes available, going to sleep
HCI: send_acl_data_task, 18 bytes
HCI: send_acl_data_task, 18 bytes
HCI: send_acl_packet, send 18 bytes (excl HCI header) out of 18
HCI: send_acl_packet, There are 5 bytes space for the headers
 
send_acl_packet,  (23):
...
...

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