The format of /etc/bluetooth/uart is:
Code:
<Product_Info>:<hciattach parameters>
Where <Product_Info> is the product info text given by the command \'cardctl ident\' with the CF card plugged in.
It is done like this as different CSR based cards seem to require different hciattach parameters, although all of them should start with \"/dev/ttyS3\" and some may only require that. You might have to search around a bit and play to find the correct hciattach parameters.
tumnus - I hate to admit it, but I may need the \"for dummies\" version of this. I do realize that you have better things to do, but humor me please
My results of $ cardctl ident:
# cardctl ident
Socket 0:
product info: \"AmbiCom BT2000C\", \"Bluetooth PC/CF Card
manfid: 0x022d, 0x2000
function: 2 (serial)
Socket 1:
no product info available
#
So, I would have to presume that the code that I would put in /etc/bluetooth/uart would be:
\"AmbiCom BT2000C\", \"Bluetooth PC/CF Card\":/dev/ttyS3 bcsp 230400
Then, for the first time ever, the following statement returned something:
# hciattach /dev/ttyS3 bcsp 230400
BCSP initialization timed out
#
Wow. Too bad it wasn\'t something better
I then started trying some additional points in the following thread:
http://www.zaurus.com/dev/board/index.php?...=5175&hl=socket (which you suggested checking out earlier)
I did the following:
# cd bluetooth
# ls
bluecard_cs.o bt950_cs.o dtl1_cs.o hci_vhci.o
bt3c_cs.o btuart_cs.o hci_uart.o
# cp /mnt/card/Documents/hci_bcsp.o .
# ls
bluecard_cs.o bt950_cs.o dtl1_cs.o hci_uart.o
bt3c_cs.o btuart_cs.o hci_bcsp.o hci_vhci.o
# depmod -a
# hciattach /dev/ttS3 bcsp 230400
Can\'t open serial port: No such file or directory
Can\'t initialize device: No such file or directory
#
You note the following in one of the posts in that thread:
\"Oh, and remember to ensure that it uses the hci_uart driver too. That will probably require adding an entry to /etc/pcmcia/bluetooth.conf and a restart of pcmcia.\"
In /etc/pcmcia/bluetooth.conf, I found the following entry:
device \"hci_uart\"
class \"bluetooth\" module \"hci_uart\"
Is that sufficient for what you were getting at in that post?
I also tried the following:
# hciattach /dev/ttyS3 csr
Initialization timed out.
#
Also, when I restarted my Z, I got the following lines in my dmesg:
# dmesg
<cut most of output>
BlueZ Core ver 2.3 Copyright © 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
BlueZ L2CAP ver 2.3 Copyright © 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
BlueZ RFCOMM ver 1.0
Copyright © 2002 Maxim Krasnyansky <maxk@qualcomm.com>
Copyright © 2002 Marcel Holtmann <marcel@holtmann.org>
This function is not support 411c
#
Don\'t know what that last comment was about!?!
Again, I was surprised that I received a response at all from hciattach, but now I am again stumped... Anything additional? Could the problem be my hciattach parameters? Thanks much again for any help.