OESF Portal | OESF Forum | OESF Wiki | LinuxPDA | #planetgemini chat on matrix.org | #zaurus and #alarmz chat on freenode.net | ELSI (coming soon) | Ibiblio


Welcome Guest ( Log In | Register )

> Bluetooth Problem On Henntges Oz 3.5.3, Getting Bluetooth started on OZ
post Aug 28 2005, 12:52 PM
Post #1

Group: Members
Posts: 44
Joined: 11-May 04
Member No.: 3,200

I have Hentges OZ 3.5.3 and Cardfs up and running on my Z.
Now how do I get bluetooth started on OZ 3.5.3 ?

I have an LSE038 Bluecard which is recognised as soon as I put it into the Z.
However the light never goes on.
The network bnep0 cant be started.
I've tried sdp tool browse but nothing happens.

Card Details

cardctl ident

socket 0:
product info : "WSS" , "LSE039"
manfid: 0x0264, 0x0008
funtion: 6 (network)
Socket 1:
no product info available

I've checked bluetooth.conf - here's the driver for my card.

device "bluecard_cs"
class "bluetooth" module "bluecard_cs"

card "LSE039 Bluetooth PC Card"
version "wss","LSE039"
bind "bluecard_cs"

I assume bluecard_cs is part of the bluetooth module - I dont see it as an opie or oz module -can someone confirm this?

Help please!
Go to the top of the page
+Quote Post
Start new topic
post Sep 18 2005, 03:51 PM
Post #2

Group: Members
Posts: 37
Joined: 29-June 05
Member No.: 7,484

Following your suggestions I'm going somewhere. smile.gif
It is not much pratical right now, but still it works, more or less.

I've wrote a little script:

modprobe hci_uart
sleep 1
setserial /dev/ttyS3 baud_base 921600
hciattach /dev/ttyS3 billionton
hciconfig hci0 up
/etc/init.d/bluetooth start

It basically does what /etc/init.d/bluetooth alone didn't do: setup my card and then startup the bluetooth services. Of course I too have commented out the references to HIDD in /etc/init.d/bluetooth.

However, even if when i run it everything seems to work well ("hciconfig -a" shows the device, and "hcitool -scan" gives the proper results), I get the following message just after running it:

BCSP initialization time out

Making some test, I found that is due to the "hciconfig hci0 up" being in the script.
If I remove it from there and run it manually, I don't get the message.
I've tried also to put some sleep time between "hciattach" and "hciconfig" in the script, but still I get the message. Any hint on this?

I can remove the card running /etc/init.d/bluetooth stop. When I re-insert it I should re-run my script. When I suspend, I have to resume the card manually, by "cardctl resume 0".

At least this way, I've to run just one command upon starting/stopping the bluetooth.
Thanks for any help so far.

***little update***

The card is somewhat unreliable. Sometimes, upon insertion, the led doesn't blink.
Even if "cardctl status" shows the card as being active, it is not.
Doing "cardctl suspend 0", waiting a couple of seconds, and then "cardctl resume 0",
makes it up. Then the script works well, and doesn't give that "BCSP initialization time out" error message.
Go to the top of the page
+Quote Post

Posts in this topic

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:


RSS Lo-Fi Version Time is now: 19th January 2018 - 07:38 PM