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

RE: [bluetooth-dev] newbie questions



Thanks for the input.

The module is configured for H4/115200, I confirmed this using BlueChat.
And yes, it is connected to the right serial port (I triple-checked it
:).

Additional (dumb) questions:
1. Does the kernel message "BT SYS: Current HW: Ericsson"
mean the stack is configured for Ericsson hardware? If so, how do I
configure
it for CSR?  I already tried `make CONFIG_BLUETOOTH_CSR=y` but the same
message is still there.

2. How is Config.in used?  Looks like it's used for
menu-driven/interactive
configuration of the stack, but I have no idea how it's done.

TIA!

Joey


> -----Original Message-----
> From: owner-bluetooth-dev@xxxxxxx.com
> [mailto:owner-bluetooth-dev@xxxxxxx.com]On Behalf Of Peter Kjellerstedt
> Sent: Friday, October 05, 2001 5:34 PM
> To: 'Joey Legaspi'; bluetooth-dev@xxxxxxx.com
> Subject: RE: [bluetooth-dev] newbie questions
> 
> 
> Ok, the stack cannot contact the Bluetooth module.
> There may be a number of reasons for this:
> * The inital speed may be wrong, try using -i 38400.
> * The module may be configured for BCSP, but you have configured 
>   the stack for H4. Make sure you have BCSP support enabled, and
>   use btdm which has support for switching between BCSP and H4.
> * You use the wrong serial port (far fetched, but worth checking)
> 
> //Peter
> 
> > -----Original Message-----
> > From: Joey Legaspi [mailto:joey_legaspi@xxxxxxx.com]
> > Sent: 05 October 2001 11:29
> > To: bluetooth-dev@xxxxxxx.com
> > Subject: RE: [bluetooth-dev] newbie questions
> > 
> > 
> > Here are the message logs:
> > 
> > Oct  5 16:24:50 linuxbox btduser: Shutting down bluetooth stack
> > Oct  5 16:24:50 linuxbox btduser: close_device
> > Oct  5 16:24:50 linuxbox btduser: close_device
> > Oct  5 16:24:50 linuxbox btduser: Why are we getting more 
> > than one signal
> > here ?
> > Oct  5 16:27:44 linuxbox kernel: Bluetooth Driver v1.3, 
> > Copyright (c) 2000,
> > 2001 Axis Communications AB
> > Oct  5 16:27:44 linuxbox kernel: BT SYS: Bluetooth driver 
> > registered as
> > ttyBT
> > Oct  5 16:27:44 linuxbox kernel: BT SYS: Bluetooth line discipline
> > registered.
> > Oct  5 16:27:44 linuxbox kernel: BT (driver) Initialising bt 
> > ctrl struct
> > Oct  5 16:27:44 linuxbox kernel: BT SYS: Registering BT proc files
> > Oct  5 16:27:44 linuxbox kernel: BT SYS: Bluetooth Driver 
> > Using ttyBT[0-6]
> > (data), ttyBTC (ctrl [7])
> > Oct  5 16:30:03 linuxbox btd: Initiating signal handler
> > Oct  5 16:30:03 linuxbox btd: Starting SDP server [sdp_server]
> > Oct  5 16:30:03 linuxbox sdp_server: SDP Server starting
> > Oct  5 16:30:03 linuxbox btd: Opening dev /dev/ttyS0
> > Oct  5 16:30:03 linuxbox kernel: BT (driver) bt_open: Line 7
> > Oct  5 16:30:03 linuxbox kernel: BT (driver) Registering tty 
> > on line 7 (btd)
> > Oct  5 16:30:03 linuxbox kernel: BT (driver) Now 1 open fd:s 
> > for ttyBTC
> > [btd]
> > Oct  5 16:30:03 linuxbox kernel: BT (driver) bt_close: Line 7
> > Oct  5 16:30:03 linuxbox kernel: BT (driver) Unregistering 
> > tty on line 7
> > Oct  5 16:30:03 linuxbox kernel: BT (ldisc) bt_tty_open
> > Oct  5 16:30:03 linuxbox kernel: BT SYS: Setting BT driver to 
> > use serial tty
> > Oct  5 16:30:03 linuxbox btd: Opening dev /dev/ttyBTC
> > Oct  5 16:30:03 linuxbox kernel: BT (driver) bt_open: Line 7
> > Oct  5 16:30:03 linuxbox kernel: BT (driver) Registering tty 
> > on line 7 (btd)
> > Oct  5 16:30:03 linuxbox kernel: BT (driver) Now 1 open fd:s 
> > for ttyBTC
> > [btd]
> > Oct  5 16:30:03 linuxbox kernel: BT (driver) 
> bt_flush_buffer: Ignored
> > Oct  5 16:30:03 linuxbox kernel: BT SYS: Initialising 
> Bluetooth Stack
> > Oct  5 16:30:03 linuxbox kernel: BT SYS: Current HW: Ericsson
> > Oct  5 16:30:03 linuxbox kernel: BT SYS: Initialising BTMEM 
> > [2500 bytes]
> > Oct  5 16:30:03 linuxbox kernel: BT SYS: Initialising HCI
> > Oct  5 16:30:03 linuxbox kernel: BT SYS: HCI emulator off
> > Oct  5 16:30:03 linuxbox kernel: BT SYS: Initialising HCI 
> > inbuffers [800]
> > Oct  5 16:30:03 linuxbox kernel: BT SYS: Reading buffer sizes 
> > in HW module
> > Oct  5 16:30:05 linuxbox kernel: cmd_timeout: Timeout when 
> waiting for
> > command response
> > Oct  5 16:30:05 linuxbox kernel: BT SYS: Reading firmware 
> > info in HW module
> > Oct  5 16:30:07 linuxbox kernel: cmd_timeout: Timeout when 
> waiting for
> > command response
> > Oct  5 16:30:07 linuxbox kernel: BT SYS: Host flow control 
> not enabled
> > Oct  5 16:30:07 linuxbox kernel: BT SYS: M/S switch disabled
> > Oct  5 16:30:07 linuxbox kernel: BT SYS: Force M/S switch set to 0
> > Oct  5 16:30:07 linuxbox kernel: BT SYS: ERROR: HCI failed to 
> > initialise
> > Oct  5 16:30:07 linuxbox kernel: BT SYS: Shutting down BTMEM
> > Oct  5 16:30:07 linuxbox btd: Killing SDP server
> > Oct  5 16:30:07 linuxbox btd: Shutting down bluetooth stack
> > Oct  5 16:30:07 linuxbox kernel: BT SYS: Shutting down 
> bluetooth stack
> > Oct  5 16:30:07 linuxbox kernel: BT SYS: Shutting down BTMEM
> > Oct  5 16:30:07 linuxbox btd: close_device
> > Oct  5 16:30:07 linuxbox kernel: BT (driver) bt_close: Line 7
> > Oct  5 16:30:07 linuxbox kernel: BT (driver) Unregistering 
> > tty on line 7
> > Oct  5 16:30:07 linuxbox btd: close_device
> > Oct  5 16:30:07 linuxbox kernel: BT (ldisc) bt_tty_ioctl: 
> > Forwarding ioctl
> > 0x540b to n_tty line disc
> > 
> > [root@linuxbox axisbt_root]# tail -f /var/log/messages
> > Oct  5 16:30:07 linuxbox kernel: BT SYS: Shutting down BTMEM
> > Oct  5 16:30:07 linuxbox btd: Killing SDP server
> > Oct  5 16:30:07 linuxbox btd: Shutting down bluetooth stack
> > Oct  5 16:30:07 linuxbox kernel: BT SYS: Shutting down 
> bluetooth stack
> > Oct  5 16:30:07 linuxbox kernel: BT SYS: Shutting down BTMEM
> > Oct  5 16:30:07 linuxbox btd: close_device
> > Oct  5 16:30:07 linuxbox kernel: BT (driver) bt_close: Line 7
> > Oct  5 16:30:07 linuxbox kernel: BT (driver) Unregistering 
> > tty on line 7
> > Oct  5 16:30:07 linuxbox btd: close_device
> > Oct  5 16:30:07 linuxbox kernel: BT (ldisc) bt_tty_ioctl: 
> > Forwarding ioctl
> > 0x540b to n_tty line disc
> > Oct  5 16:34:42 linuxbox btduser: Initiating signal handler
> > Oct  5 16:34:42 linuxbox btduser: Starting SDP server [sdp_user]
> > Oct  5 16:34:42 linuxbox btduser: Opening dev /dev/ttyS0
> > Oct  5 16:35:15 linuxbox btduser: Killing SDP server
> > Oct  5 16:35:15 linuxbox btduser: Shutting down bluetooth stack
> > Oct  5 16:35:15 linuxbox btduser: close_device
> > Oct  5 16:35:15 linuxbox btduser: close_device
> > Oct  5 16:35:21 linuxbox su(pam_unix)[1121]: authentication failure;
> > logname=joeyl uid=500 euid=0 tty= ruser= rhost=  user=root
> > Oct  5 16:35:29 linuxbox su(pam_unix)[1122]: session opened 
> > for user root by
> > joeyl(uid=500)
> > Oct  5 16:35:51 linuxbox btduser: Initiating signal handler
> > Oct  5 16:35:51 linuxbox btduser: Starting SDP server [sdp_user]
> > Oct  5 16:35:51 linuxbox btduser: Opening dev /dev/ttyS0
> > Oct  5 16:35:56 linuxbox btduser: Killing SDP server
> > Oct  5 16:35:56 linuxbox btduser: Shutting down bluetooth stack
> > Oct  5 16:35:56 linuxbox btduser: close_device
> > Oct  5 16:35:56 linuxbox btduser: close_device
> > Oct  5 16:49:51 linuxbox btduser: Initiating signal handler
> > Oct  5 16:49:51 linuxbox btduser: Starting SDP server [sdp_user]
> > Oct  5 16:49:51 linuxbox btduser: Opening dev /dev/ttyS0
> > Oct  5 16:50:05 linuxbox btduser: Killing SDP server
> > Oct  5 16:50:05 linuxbox btduser: Shutting down bluetooth stack
> > Oct  5 16:50:05 linuxbox btduser: close_device
> > Oct  5 16:50:05 linuxbox btduser: close_device
> > Oct  5 16:50:13 linuxbox btduser: Initiating signal handler
> > Oct  5 16:50:13 linuxbox btduser: Starting SDP server [sdp_user]
> > Oct  5 16:50:13 linuxbox btduser: Opening dev /dev/ttyS0
> > Oct  5 16:50:18 linuxbox btduser: Killing SDP server
> > Oct  5 16:50:18 linuxbox btduser: Why are we getting more 
> > than one signal
> > here ?
> > Oct  5 16:50:18 linuxbox btduser: Shutting down bluetooth stack
> > Oct  5 16:50:18 linuxbox btduser: close_device
> > 
> > > -----Original Message-----
> > > From: owner-bluetooth-dev@xxxxxxx.com
> > > [mailto:owner-bluetooth-dev@xxxxxxx.com]On Behalf Of Peter 
> Kjellerstedt
> > > Sent: Friday, October 05, 2001 5:00 PM
> > > To: 'Joey Legaspi'; bluetooth-dev@xxxxxxx.com
> > > Subject: RE: [bluetooth-dev] newbie questions
> > >
> > >
> > > Please provide the kernel messages, which will indicate the
> > > problem more accurately.
> > >
> > > Also, you should use btdm from the experimental directory
> > > instead of btd from the btd directory (ok, we really need
> > > to update the README to reflect this...)
> > >
> > > file://Peter
> > >
> > > > -----Original Message-----
> > > > From: Joey Legaspi [mailto:joey_legaspi@xxxxxxx.com]
> > > > Sent: 05 October 2001 10:51
> > > > To: bluetooth-dev@xxxxxxx.com
> > > > Subject: [bluetooth-dev] newbie questions
> > > >
> > > > Hi!
> > > >
> > > > This is my first time with this protocol stack, so
> > > > I apologize in advance for the "dumb" questions and
> > > > please bear with me. :)
> > > >
> > > > I'm using CSR hardware on a Redhat 7.1 box.
> > > > I followed the steps described in the README file but
> > > > I still get the following:
> > > >
> > > > ----
> > > >
> > > > [root@xxxxxxx./btd -u /dev/ttyS0 -b
> > > > /dev/ttyBT0 -m -e 0
> > > > Bluetooth Control Application
> > > > -----------------------------
> > > > Running as server
> > > > Physdev /dev/ttyS0, btdev /dev/ttyBT0, speed 115200
> > > > baud
> > > > Registered bluetooth line discipline on /dev/ttyS0
> > > > Init stack
> > > > Init stack: Operation not permitted
> > > >
> > > > ----
> > > >
> > > > What am I doing wrong?
> > > >
> > > > Also, with btduser:
> > > >
> > > > ----
> > > >
> > > > root] btduser -u /dev/ttyS0 -b /dev/ttyBT0 -m -e 0
> > > > Bluetooth Control Application
> > > > -----------------------------
> > > > Running as server
> > > > Running stack in user mode
> > > > Physdev /dev/ttyS0, btdev (not used), speed 115200
> > > > baud
> > > > sdp_parser.c::SDP Server starting
> > > > sdp_parser.c::Opening server socket /tmp/sdp_sock
> > > > sdp_parser.c::SDP Server listens...
> > > > Init stack
> > > > Initiating read thread
> > > > BT SYS: Initialising Bluetooth Stack
> > > > BT SYS: Initialising HCI
> > > > BT SYS: HCI emulator off
> > > > BT SYS: Initialising HCI inbuffers [800]
> > > > BT SYS: Reading buffer sizes in HW module
> > > >
> > > > ----
> > > >
> > > > From what I've read in the README, it should already
> > > > be able to accept commands (inq, setbd, readbd, etc).
> > > > But nothing happens when I type any of the commands
> > > > And when Ctrl-C is pressed, I get this:
> > > >
> > > > waitpid sdp server: No child processes
> > > >
> > > > What is going on here?
> > > >
> > > >
> > > > Any inputs will be greatly appreciated.
> > > >
> > > > TIA!
> > > >
> > > > -joey
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe
> > > bluetooth-dev" in
> > > the body of a message to majordomo@xxxxxxx.com
> > 
> > 
> > 
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @xxxxxxx.com">http://mail.yahoo.com
> > 
> > -
> > To unsubscribe from this list: send the line "unsubscribe 
> > bluetooth-dev" in
> > the body of a message to majordomo@xxxxxxx.com
> > 
> -
> To unsubscribe from this list: send the line "unsubscribe 
> bluetooth-dev" in
> the body of a message to majordomo@xxxxxxx.com
> 
-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com