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

[bluetooth-dev] no data on serial port



Hello everybody,

I am trying to get my board working now, for quite some time.

I just connected a serial monitor to my serial port and actually, there is no
data going out.

The messages I get are the following:

Bluetooth Driver v1.2, Copyright (c) 2000 Axis Communications AB 
Mar 27 12:53:15 ds18 kernel: BT SYS: Bluetooth driver registered in ttyBT 
Mar 27 12:53:15 ds18 kernel: BT SYS: Bluetooth line discipline registered. 
Mar 27 12:53:15 ds18 kernel: BT (driver) Initiating bt ctrl struct 
Mar 27 12:53:15 ds18 kernel: BT SYS: Registering BT proc files 
Mar 27 12:53:15 ds18 kernel: BT SYS: Bluetooth Driver Using ttyBT[0-6] (data),
ttyBTC (ctrl [7]) 
Mar 27 12:53:15 ds18 kernel: BT SYS: Using BT Inbuffers [4000] 
Mar 27 12:53:19 ds18 btd: Initiating signal handler 
Mar 27 12:53:19 ds18 btd: Starting SDP server 
Mar 27 12:53:19 ds18 btd: Opening dev /dev/ttyS0 
Mar 27 12:53:19 ds18 kernel: BT (ldisc) bt_tty_open 
Mar 27 12:53:19 ds18 kernel: BT SYS: Setting BT driver to use serial tty 
Mar 27 12:53:19 ds18 btd: Opening dev /dev/ttyBTC 
Mar 27 12:53:19 ds18 kernel: BT (driver) bt_open on line 7 
Mar 27 12:53:19 ds18 kernel: BT SYS: Registering tty on line 7 
Mar 27 12:53:19 ds18 kernel: BT SYS: Now 1 open fd:s for ttyBTC 
Mar 27 12:53:19 ds18 kernel: BT (driver) bt_ioctl: forwarding ioctl 0x540b to
serial driver 
Mar 27 12:53:19 ds18 kernel: BT (driver) bt_flush_buffer 
Mar 27 12:53:19 ds18 kernel:     BTMEM get_bt_buf : no data in buffer 
Mar 27 12:53:19 ds18 kernel: BT SYS: Initialising Bluetooth Stack 
Mar 27 12:53:19 ds18 kernel: BT SYS: hci_init, Initialising HCI 
Mar 27 12:53:19 ds18 kernel: BT SYS: HCI emulator off 
Mar 27 12:53:19 ds18 kernel: BT SYS: hci_init, Initialising HCI inbuffers [800] 
Mar 27 12:53:19 ds18 kernel: HCI: init_cmd_buf, Initializing 
Mar 27 12:53:19 ds18 kernel: BT SYS: hci_init, Reading buffer sizes in the
module... 
Mar 27 12:53:19 ds18 kernel: HCI: hci_read_buffer_size 
Mar 27 12:53:19 ds18 kernel: HCI: start_cmd_timer 
Mar 27 12:53:19 ds18 kernel: HCI: insert_cmd 
Mar 27 12:53:19 ds18 kernel: HCI: send_cmd_queue, start:
Num_HCI_Command_Packets=1 
Mar 27 12:53:19 ds18 kernel: BT DATA <--|X|      4 
Mar 27 12:53:19 ds18 kernel:  
Mar 27 12:53:19 ds18 kernel: bt_write_lower_driver : (4) 
Mar 27 12:53:19 ds18 kernel:    0x01 0x05 0x10 0x00  
Mar 27 12:53:19 ds18 kernel: HCI: send_cmd_queue, sent data..., freeing memory 
Mar 27 12:53:19 ds18 kernel: HCI: send_cmd_queue, end : 0 cmds left in queue 
Mar 27 12:53:22 ds18 kernel: cmd_timeout, Timeout when waiting for command
response 
Mar 27 12:53:22 ds18 kernel: HCI: hci_read_firmware_rev_info:  
Mar 27 12:53:22 ds18 kernel: HCI: start_cmd_timer 
Mar 27 12:53:22 ds18 kernel: HCI: insert_cmd 
Mar 27 12:53:22 ds18 kernel: HCI: send_cmd_queue, start:
Num_HCI_Command_Packets=1 
Mar 27 12:53:22 ds18 kernel: BT DATA <--|X|      4 
Mar 27 12:53:22 ds18 kernel:  
Mar 27 12:53:22 ds18 kernel: bt_write_lower_driver : (4) 
Mar 27 12:53:22 ds18 kernel:    0x01 0x0f 0xfc 0x00  

-------------------------------
so, it seems that everything works fine. at least there is no error when
doing the bt_write_lower_driver.

by the way, where does the first 0x01 byte come from? didn't find it in the
specs.

Thanks and Bye

Patrick



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