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

RE: [bluetooth-dev] how generic the Axis stack is?



The main problem below is not what is highlighted.
It is rather the fact that we try to read the buffer sizes,
and the command times out. This is an indication of that
the Bluetooth module does not respond to commands.
There may be a number of reasons for this. One is that the
module may need to be reset (the --reset option will only
work correctly on Axis' hardware). Another may be that the
speed parameter is incorrect.
 
Reading the firmware information is done differently for
different brands, and cannot be done generically, which is
why you see the error message below (and it would not
work in this case anyway as the module does not respond
to commands sent by the stack, as stated above).
 
The stack itself is pretty generic. However, there is always
some initialisation which depends on the brand of the hardware
that has to be done to get everything to work optimally, and
this can of course not be generalised.
 
//Peter
-----Original Message-----
From: Yang Xiaoyong [mailto:linuxbluetooth@xxxxxxx.com]
Sent: 23 October 2001 05:10
To: bluetooth-dev@xxxxxxx.com
Subject: [bluetooth-dev] how generic the Axis stack is?

Hi dear Axis users and developers

I am using a generic device with Axis. After I compiled the tack with the generic option switched on in the config file, I  run the btd using "btd --reset --to read the hardware address. However i found that the following messages(the main part is highlighted in red) :

 

Oct 22 17:12:04 localhost btd: Initiating signal handler

Oct 22 17:12:09 localhost btd: Starting SDP server [sdp_server]

Oct 22 17:12:09 localhost btd: Opening dev /dev/ttyS0

Oct 22 17:12:09 localhost kernel: BT (driver) bt_open: Line 7

Oct 22 17:12:09 localhost kernel: BT (driver) Registering tty on line 7 (btd)

Oct 22 17:12:09 localhost kernel: BT (driver) Now 1 open fd:s for ttyBTC [btd]

Oct 22 17:12:09 localhost kernel: BT (driver) bt_close: Line 7

Oct 22 17:12:09 localhost kernel: BT (driver) Unregistering tty on line 7

Oct 22 17:12:09 localhost kernel: BT (ldisc) bt_tty_open

Oct 22 17:12:09 localhost kernel: BT SYS: Setting BT driver to use serial tty

Oct 22 17:12:09 localhost btd: Opening dev /dev/ttyBTC

Oct 22 17:12:09 localhost kernel: BT (driver) bt_open: Line 7

Oct 22 17:12:09 localhost kernel: BT (driver) Registering tty on line 7 (btd)

Oct 22 17:12:09 localhost kernel: BT (driver) Now 1 open fd:s for ttyBTC [btd]

Oct 22 17:12:09 localhost kernel: BT (driver) bt_flush_buffer: Ignored

Oct 22 17:12:09 localhost kernel: BT SYS: Initialising Bluetooth Stack

Oct 22 17:12:09 localhost kernel: BT SYS: Current HW: Generic

Oct 22 17:12:09 localhost kernel: BT SYS: Initialising BTMEM [2500 bytes]

Oct 22 17:12:09 localhost kernel: BT SYS: Initialising HCI

Oct 22 17:12:09 localhost kernel: BT SYS: HCI emulator off

Oct 22 17:12:09 localhost kernel: BT SYS: Initialising HCI inbuffers [800]

Oct 22 17:12:09 localhost kernel: BT SYS: Reading buffer sizes in HW module

Oct 22 17:12:09 localhost sdp_server: SDP Server starting

Oct 22 17:12:11 localhost kernel: cmd_timeout: Timeout when waiting for command response

Oct 22 17:12:11 localhost kernel: BT SYS: Reading firmware info in HW module

Oct 22 17:12:11 localhost kernel: BT SYS: ERROR: hci_read_firmware_rev_info [Generic] not supported.

Oct 22 17:12:11 localhost kernel: BT SYS: Host flow control not enabled

Oct 22 17:12:11 localhost kernel: BT SYS: M/S switch disabled

Oct 22 17:12:11 localhost kernel: BT SYS: Force M/S switch set to 0

Oct 22 17:12:11 localhost kernel: BT SYS: ERROR: HCI failed to initialise

Oct 22 17:12:11 localhost kernel: BT SYS: Shutting down BTMEM

Oct 22 17:12:11 localhost btd: Killing SDP server

Oct 22 17:12:11 localhost btd: Shutting down bluetooth stack

Oct 22 17:12:11 localhost kernel: BT SYS: Shutting down bluetooth stack

Oct 22 17:12:11 localhost kernel: BT SYS: Shutting down BTMEM

Oct 22 17:12:11 localhost btd: close_device

Oct 22 17:12:11 localhost kernel: BT (driver) bt_close: Line 7

Oct 22 17:12:11 localhost btd: close_device

Oct 22 17:12:11 localhost kernel: BT (driver) Unregistering tty on line 7

Oct 22 17:12:11 localhost kernel: BT (ldisc) bt_tty_ioctl: Forwarding ioctl 0x540b to n_tty line disc

Oct 22 17:14:28 localhost btduser: Initiating signal handler

Oct 22 17:14:33 localhost btduser: Starting SDP server [sdp_user]

Oct 22 17:14:33 localhost btduser: Opening dev /dev/ttyS0

Oct 22 17:14:35 localhost btduser: Starting modem_emulator

Oct 22 17:15:17 localhost automount[787]: attempting to mount entry /misc/.directory

Oct 22 17:15:17 localhost automount[1242]: lookup(file): lookup for .directory failed

 

 

 

What's more,  the btd configuration in the Axis new version 0.0.8  fails again:

 

[root@localhost bluetooth]# btd --reset --speed 9600

Bluetooth Control Application

-----------------------------

Please reset HW board within 5 seconds

Running as server

Physdev /dev/ttyS0, btdev /dev/ttyBT0, speed 9600 baud

Registered bluetooth line discipline on /dev/ttyS0

Init stack

Init stack: Operation not permitted

 

 

[root@xxxxxxx./btduser --reset --speed 9600

Bluetooth Control Application

-----------------------------

Please reset HW board within 5 seconds

Running as server

Running stack in user mode

Physdev /dev/ttyS0, btdev (not used), speed 9600 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

 

Oct 22 17:39:37 localhost kernel: BT (ldisc) bt_tty_ioctl: Forwarding ioctl 0x540b to n_tty line disc

Oct 22 17:40:18 localhost btduser: Initiating signal handler

Oct 22 17:40:23 localhost btduser: Starting SDP server [sdp_user]

Oct 22 17:40:23 localhost btduser: Opening dev /dev/ttyS0

Oct 22 17:40:23 localhost kernel: BT (ldisc) bt_tty_ioctl: Forwarding ioctl 0x540b to n_tty line disc

Oct 22 17:40:23 localhost kernel: BT (ldisc) bt_tty_ioctl: Forwarding ioctl 0x5401 to n_tty line disc

Oct 22 17:40:23 localhost kernel: BT (ldisc) bt_tty_ioctl: Forwarding ioctl 0x5402 to n_tty line disc

Oct 22 17:40:23 localhost kernel: BT (ldisc) bt_tty_ioctl: Forwarding ioctl 0x5401 to n_tty line disc

Oct 22 17:40:23 localhost kernel: BT (ldisc) bt_tty_poll: Nothing done!

Oct 22 17:40:23 localhost kernel: BT (ldisc) bt_tty_write: (4) done!

Oct 22 18:07:27 localhost kernel: BT SYS: ERROR: hci_receive_data: discarding 1 bytes

Oct 22 18:07:27 localhost kernel: BT SYS: ERROR: hci_receive_data: discarding 13 bytes

Oct 22 18:07:27 localhost kernel: BT SYS: ERROR: hci_receive_data: discarding 33 bytes

Oct 22 18:07:27 localhost kernel: BT SYS: ERROR: hci_receive_data: discarding 30 bytes

Oct 22 18:07:27 localhost kernel: BT SYS: ERROR: hci_receive_data: discarding 33 bytes

Oct 22 18:07:27 localhost kernel: BT SYS: ERROR: hci_receive_data: discarding 28 bytes

Oct 22 18:07:27 localhost kernel: BT SYS: ERROR: hci_receive_data: discarding 29 bytes

Oct 22 18:07:27 localhost kernel: BT SYS: ERROR: hci_receive_data: discarding 31 bytes

Oct 22 18:07:27 localhost kernel: BT SYS: ERROR: hci_receive_data: discarding 33 bytes

Oct 22 18:07:27 localhost kernel: BT SYS: ERROR: hci_receive_data: discarding 29 bytes

Oct 22 18:07:27 localhost kernel: BT SYS: ERROR: hci_receive_data: discarding 34 bytes

Oct 22 18:07:27 localhost kernel: BT SYS: ERROR: hci_receive_data: discarding 11 bytes

 

Linux could not read my firmware data here.

 

My question is that how generic the Axis stack is?

Regards,

Xiaoyong