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

Re: [bluetooth-dev] Re: PPP over RFComm



Hi Baldeep,


Baldeep anand wrote:

> Hi Chan,
>
> Thanks for replying. I tried doing as you suggested but encountered the
> following problems. I am also using RH 7.2 Kernel 2.4.7 and trying to connect
> two laptops using null modem.
>
> *****************
> Server
> ***********
>  when i run >btdm -m 0 on the server i get -
>         ERROR: init_phys() not implemented!
>         ERROR: init_hw() not implemented!
>
>         And it doesn't return to the command prompt.

I think the ERROR is normal because you don't have physical hardware so you don't
need initialize the hardware.
In my case, I was using the version in 01-07-2001 (I can't remember the version
number). The server side command I used was different from you. Here is my
command:

#insmod bt.o
#./btd --physdev /dev/ttyS0 --cmdmode --speed 57600

(The menu will be appeared few seconds later)

>
>
> The kernel gave the following messages:-
>
> Feb 19 13:37:53 localhost kernel: Bluetooth Driver v1.3, Copyright (c) 2000,
> 2001 Axis Communications AB
> Feb 19 13:37:53 localhost kernel: BT SYS: Bluetooth driver registered as ttyBT
> Feb 19 13:37:53 localhost kernel: BT SYS: Bluetooth line discipline
> registered.
> Feb 19 13:37:53 localhost kernel: BT (driver) Initialising bt ctrl struct
> Feb 19 13:37:53 localhost kernel: BT SYS: Registering BT proc files
> Feb 19 13:37:53 localhost kernel: BT SYS: Bluetooth Driver Using ttyBT[0-6]
> (data), ttyBTC (ctrl [7])
> Feb 19 13:38:26 localhost btdm: Bluetooth daemon starting
> Feb 19 13:38:26 localhost btdm: open_socket: Failed to connect /tmp/ipa_server
> Feb 19 13:38:26 localhost sdp_server: SDP Server starting
> Feb 19 13:38:27 localhost btdm: open_socket: Failed to connect /tmp/ipa_server
> Feb 19 13:38:41 localhost last message repeated 3 times
> Feb 19 13:38:41 localhost kernel: BT (driver) bt_open: Line 7
> Feb 19 13:38:41 localhost kernel: BT (driver) Registering tty on line 7 (btdm)
> Feb 19 13:38:41 localhost kernel: BT (driver) Now 1 open fd:s for ttyBTC
> [btdm]
> Feb 19 13:38:41 localhost kernel: BT (driver) bt_close: Line 7
> Feb 19 13:38:41 localhost kernel: BT (driver) Unregistering tty on line 7
> Feb 19 13:38:41 localhost kernel: BT (ldisc) bt_tty_open
> Feb 19 13:38:41 localhost kernel: BT SYS: Setting BT driver to use serial tty
> Feb 19 13:38:41 localhost btdm: Registered bluetooth line discipline on
> /dev/ttyS0
> Feb 19 13:38:41 localhost kernel: BT (driver) bt_open: Line 7
> Feb 19 13:38:41 localhost kernel: BT (driver) Registering tty on line 7 (btdm)
> Feb 19 13:38:41 localhost kernel: BT (driver) Now 1 open fd:s for ttyBTC
> [btdm]
> Feb 19 13:38:41 localhost kernel: BT (ldisc) bt_tty_ioctl: Forwarding ioctl
> 0x540b to n_tty line disc
> Feb 19 13:38:41 localhost btdm: Init stack
> Feb 19 13:38:41 localhost kernel: BT SYS: Initialising Bluetooth Stack
> Feb 19 13:38:41 localhost kernel: BT SYS: Current HW: Unknown
> Feb 19 13:38:41 localhost kernel: BT SYS: Initialising BTMEM [2500 bytes]
> Feb 19 13:38:41 localhost kernel: BT SYS: Initialising HCI
> Feb 19 13:38:41 localhost kernel: BT SYS: *** HCI emulator on ***
> Feb 19 13:38:41 localhost kernel: BT SYS: Initialising HCI inbuffers [800]
> Feb 19 13:38:41 localhost kernel: BT SYS: Reading buffer sizes in HW module
> Feb 19 13:38:43 localhost kernel: cmd_timeout: Timeout when waiting for
> command response
> Feb 19 13:38:43 localhost kernel: BT SYS: Reading firmware info in HW module
> Feb 19 13:38:43 localhost kernel: BT SYS: ERROR: hci_read_firmware_rev_info
> [Generic] not supported.
> Feb 19 13:38:43 localhost kernel: BT SYS: Host flow control not enabled
> Feb 19 13:38:43 localhost kernel: BT SYS: M/S switch disabled
> Feb 19 13:38:43 localhost kernel: BT SYS: Force M/S switch set to 0
> Feb 19 13:38:43 localhost kernel: BT SYS: Initialising L2CAP
> Feb 19 13:38:43 localhost kernel: command_handler: Unknown command
> ogf:0x4,ocf:0x9
> Feb 19 13:38:45 localhost kernel: cmd_timeout: Timeout when waiting for
> command response
> Feb 19 13:38:45 localhost kernel: BT SYS: ERROR: l2cap_init: Failed to get
> local BD addr
> Feb 19 13:38:45 localhost kernel: BT SYS: Initialising RFCOMM
> Feb 19 13:38:45 localhost kernel: BT SYS: Initialising SDP
> Feb 19 13:38:45 localhost kernel: BT SYS: Init SDP as server
> Feb 19 13:38:45 localhost kernel: BT SYS: Initialising TCS
> Feb 19 13:38:45 localhost kernel: BT SYS: Initialising TEST
> Feb 19 13:38:45 localhost kernel: BT (driver) BT_SET_DFU_MODE: -1
> Feb 19 13:38:45 localhost btdm: bt_set_classofdevice : srv class 0x10, maj
> class 0x3, min class 0x0, format 0x0
> Feb 19 13:38:45 localhost kernel: BT (driver) __bt_ioctl:
> HCIWRITECLASSOFDEVICE
> Feb 19 13:38:45 localhost kernel: command_handler: Unknown command
> ogf:0x3,ocf:0x24
> Feb 19 13:38:47 localhost kernel: cmd_timeout: Timeout when waiting for
> command response
> Feb 19 13:38:47 localhost btdm: bt_set_local_name: AXIS
> (localhost.localdomain)
> Feb 19 13:38:47 localhost kernel: BT (driver) __bt_ioctl: HCISETLOCALNAME
> Feb 19 13:38:47 localhost kernel: command_handler: Unknown command
> ogf:0x3,ocf:0x13
> Feb 19 13:38:49 localhost kernel: cmd_timeout: Timeout when waiting for
> command response
>
> ##########
>  Client
> ##########
>  On the client when i say  ./bti -u /dev/ttyS0 , i get
>
>         ERROR: init_phys() not implemented!
>                 ERROR: init_hw() not implemented!
>
>         (Doesn't return to the command prompt)

In the client side, my command is like this.

#insmod bt.o
#./btd --physdev /dev/ttyS0 --speed 57600 --client

Once menu appeared, use command

Menu
-------------------------
bah bah bah
quit
> rf_conn 11:22:33:44:55:66 1 0
Connected.

Bluetooth address is just dummy value which will never used.

>
>
> /var/log/messages gives,
>
> Feb 19 14:17:07 localhost bti: Init stack
> Feb 19 14:17:08 localhost kernel: BT SYS: Initialising Bluetooth Stack
> Feb 19 14:17:08 localhost kernel: BT SYS: Current HW: Unknown
> Feb 19 14:17:08 localhost kernel: BT SYS: Initialising BTMEM [2500 bytes]
> Feb 19 14:17:08 localhost kernel: BT SYS: Initialising HCI
> Feb 19 14:17:08 localhost kernel: BT SYS: *** HCI emulator on ***
> Feb 19 14:17:08 localhost kernel: BT SYS: Initialising HCI inbuffers [800]
> Feb 19 14:17:08 localhost kernel: BT SYS: Reading buffer sizes in HW module
> Feb 19 14:17:10 localhost kernel: cmd_timeout: Timeout when waiting for
> command response
> Feb 19 14:17:10 localhost kernel: BT SYS: Reading firmware info in HW module
> Feb 19 14:17:10 localhost kernel: BT SYS: ERROR: hci_read_firmware_rev_info
> [Generic] not supported.
> Feb 19 14:17:10 localhost kernel: BT SYS: Host flow control not enabled
> Feb 19 14:17:10 localhost kernel: BT SYS: M/S switch disabled
> Feb 19 14:17:10 localhost kernel: BT SYS: Force M/S switch set to 0
> Feb 19 14:17:10 localhost kernel: BT SYS: Initialising L2CAP
> Feb 19 14:17:10 localhost kernel: command_handler: Unknown command
> ogf:0x4,ocf:0x9
> Feb 19 14:17:12 localhost kernel: cmd_timeout: Timeout when waiting for
> command response
> Feb 19 14:17:12 localhost kernel: BT SYS: ERROR: l2cap_init: Failed to get
> local BD addr
> Feb 19 14:17:12 localhost kernel: BT SYS: Initialising RFCOMM
> Feb 19 14:17:12 localhost kernel: BT SYS: Initialising SDP
> Feb 19 14:17:12 localhost kernel: BT SYS: Init SDP as server
> Feb 19 14:17:12 localhost kernel: BT SYS: Initialising TCS
> Feb 19 14:17:12 localhost kernel: BT SYS: Initialising TEST
> Feb 19 14:17:12 localhost kernel: BT (driver) BT_SET_DFU_MODE: -1
> Feb 19 14:17:12 localhost bti: bt_set_classofdevice : srv class 0x10, maj
> class
> 0x3, min class 0x0, format 0x0
> Feb 19 14:17:12 localhost kernel: BT (driver) __bt_ioctl:
> HCIWRITECLASSOFDEVICE
> Feb 19 14:17:12 localhost kernel: command_handler: Unknown command
> ogf:0x3,ocf:0x24
> Feb 19 14:17:14 localhost kernel: cmd_timeout: Timeout when waiting for
> command
> response
> Feb 19 14:17:14 localhost bti: bt_set_local_name: AXIS (localhost.localdomain)
> Feb 19 14:17:14 localhost kernel: BT (driver) __bt_ioctl: HCISETLOCALNAME
> Feb 19 14:17:14 localhost kernel: command_handler: Unknown command
> ogf:0x3,ocf:0x13
> Feb 19 14:17:16 localhost kernel: cmd_timeout: Timeout when waiting for
> command
> response
>
> ******************************
>
> NOW, in a seperate terminal window if I give a > btcon -d /dev/ttyBT0 -a
> 11:22:33:44:55:66 (WHAT SHUD THIS ADDRESS BE...I think it is ignored.....Am i
> correct), I get
>
> Connecting to bd: 11:22:33:44:55:66
> Connecting to 11:22:33:44:55:66 on line 0
> (Doesn't return back to command prompt)
>
> Kernel gives the messages,
>
> Feb 19 14:28:57 localhost kernel: BT (driver) bt_open: Line 7
> Feb 19 14:28:57 localhost kernel: BT (driver) Registering tty on line 7
> (btcon)
> Feb 19 14:28:57 localhost kernel: BT (driver) Now 2 open fd:s for ttyBTC
> [btcon]Feb 19 14:28:57 localhost kernel: BT (driver) __bt_ioctl: BTCONNECT
> Feb 19 14:28:57 localhost kernel: BT (driver) bt_connect: Connecting srv ch 1
> on line 0
> Feb 19 14:28:57 localhost kernel:
> Feb 19 14:28:57 localhost kernel: bd (6):
> Feb 19 14:28:57 localhost kernel: 0x66 0x55 0x44 0x33 0x22 0x11
> Feb 19 14:28:57 localhost kernel: l2ca_connect_req: wait baseband, sleep on
> wq 0xc98a7304
>
> *****************************************************************************
>
> After running all these on the client, the kernel at the server doesn't give
> any new message.
>
> I sent you the kernel messages from the point i start the stack so that you
> can check whether or not the stack initialized properly.
>
> Thanks again and hoping to hear back from you soon.
>
> -Baldeep.
> -
> To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
> the body of a message to majordomo@xxxxxxx.com

Hope you can success.

Tim

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