Help - Search - Members - Calendar
Full Version: Howto: Ambicom Bt2000c Working On Z
OESF Forums > General Forums > General Support and Discussion > Security and Networking
tetron
It looks like a number of people have run into trouble with this card, but I think I've got it figured out.

Actually I should preface this with a disclaimer that I haven't tested it with another bluetooth device yet (my bluetooth phone arrives tomorrow!) but it does show up in hciconfig as "UP" and "RUNNING" and has a hardware address, so it at least *thinks* it's working... :-)

Here's the steps I took to make it work. I have a C760 with the original 1.20-JP ROM.

1. Download and install these packages on your Zaurus:2. Download this kernel module:
http://interreality.org/~tetron/technology/zaurus/hci_uart.o
(It turns out that the hci_uart kernel module included in the bluez-kernel package wasn't compiled with support for the H4 protocol, which is necessary to make this card work!)

3. Copy the kernel module from step 2 into the modules directory:
QUOTE
bash$ su
# cp hci_uart.o /lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/bluetooth
# depmod -a
#


4. Insert the kernel module
QUOTE
# modprobe hci_uart
#


5. (re-)start the bluetooth services:
QUOTE
# /etc/rc.d/init.d/bluetooth stop
# /etc/rc.d/init.d/bluetooth start
#


5. Use hciattach:
QUOTE
# hciattach ttyS3 bt2000c flow
CSR build ID 0x02-0x0D
Speed 0 unrecognised. Remaining at 57600 baud
#


6. Now bring up the device:
QUOTE
# hciconfig hci0 up
# hciconfig hci0
hci0:  Type: UART
        BD Address: 00:10:7A:5C:10:D8 ACL MTU: 192:8  SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN
        RX bytes:105 acl:0 sco:0 events:12 errors:0
        TX bytes:308 acl:0 sco:0 commands:12 errors:0
#


That's it!
tumnus
blink.gif ok, that patch must have been missed by Marcel Holtmann then, because every time I've asked him about this, he didn't know. It certainly wasn't in the 2.3 utilities.

I'm hopefully going to be putting an ipk together this weekend with the latest software (v2.13) and utilities to update the one pointed to in the ZUG Bluetooth Howto. This will also match the ipk I did for the SL-3000, which incidentally should work fine with an entry in /etc/bluetooth/uart .
mgaughan
QUOTE(tetron @ Jan 6 2005, 08:39 PM)
It looks like a number of people have run into trouble with this card, but I think I've got it figured out.

Actually I should preface this with a disclaimer that I haven't tested it with another bluetooth device yet (my bluetooth phone arrives tomorrow!) but it does show up in hciconfig as "UP" and "RUNNING" and has a hardware address, so it at least *thinks* it's working... :-)

Here's the steps I took to make it work.  I have a C760 with the original 1.20-JP ROM.

1. Download and install these packages on your Zaurus:2. Download this kernel module:
http://interreality.org/~tetron/technology/zaurus/hci_uart.o
(It turns out that the hci_uart kernel module included in the bluez-kernel package wasn't compiled with support for the H4 protocol, which is necessary to make this card work!)

3.  Copy the kernel module from step 2 into the modules directory:
QUOTE

bash$ su
# cp hci_uart.o /lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/bluetooth
# depmod -a
#


4. Insert the kernel module
QUOTE
# modprobe hci_uart
#


5. (re-)start the bluetooth services:
QUOTE
# /etc/rc.d/init.d/bluetooth stop
# /etc/rc.d/init.d/bluetooth start
#


5. Use hciattach:
QUOTE
# hciattach ttyS3 bt2000c flow
CSR build ID 0x02-0x0D
Speed 0 unrecognised. Remaining at 57600 baud
#


6. Now bring up the device:
QUOTE
# hciconfig hci0 up
# hciconfig hci0
hci0:   Type: UART
        BD Address: 00:10:7A:5C:10:D8 ACL MTU: 192:8  SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN
        RX bytes:105 acl:0 sco:0 events:12 errors:0
        TX bytes:308 acl:0 sco:0 commands:12 errors:0
#


That's it!
*




Good Morning,

I followed the instructions as detailed above.

At step 5, /etc/rc.d/init.d/bluetooth start I get the following error -

Starting Bluetooth subsystem: hcid sdpCan't open RFCOMM control socket: no such file or directory rfcomm.

Any thoughts?

thanks in advance,

mikeg
tumnus
That error usually means something is trying to open an rfcomm device but 'rfcomm bind all' has not been run or there is nothing defined in /etc/bluetooth/rfcomm.conf. I don't know why the bluetooth script would be trying to open a rfcomm device.

In any case I don't think this is working after all. From what I can gather, although hciconfig reports the card as UP, no further communication with the card can be made. It still needs a specific driver to be written for it. sad.gif
egg8178
hi all, i'm new here, would like to know the progress of support on bt2000c from bluez, while http://www.oesf.org/index.php?title=Bluetooth_Card_Support clearly stated that it's working with bluez, yet I cannot make it to work with instruction from http://www.oesf.org/index.php?title=Bluetooth can some one explain the difference between those ipk? pre-emptive? from what i understand reading all those post in the forum, bt2000c indeed using the csr chipset, so I should install this too? -> bluez-csr-serial_0.1_arm.ipk -<
thanks for your time reading this, and yes, I'm new to linux, yet with all the "specific terms" used everywhere in the forum.. *sigh* sad.gif
tumnus
While the BT2000C uses the CSR chip for the Bluetooth comms, the communication between the Zaurus and the CF card itself is done using a serial protocol and the driver for the serial chip on the CF card does not exist at the moment as far as I know.
egg8178
Thanks for the info, but I already bought and opened the bt2000c.. too late to do a return.. well, but according to http://www.oesf.org/forums/index.php?showt...0575&hl=bt2000c cacko does support this card, guess I'll just have to wait for the cacko to be available for the SL-6000L then, and btw, shouldn't http://www.oesf.org/index.php?title=Bluetooth_Card_Support be updated to reflect that bluez currently has no support for bt2000c? because I bought it after checking there, just don't wish any newbie would make the same mistake as I did..

Thanks tumnus, appreciate what you did for a newbie like me
tumnus
I hadn't noticed tetron had updated that page. Did you try the instructions that tetron gave above? I haven't got that card to test this with.

I didn't think it was working as people have used the later version of the BlueZ libraries that I compiled, which have the stuff tetron said was missing. So I was wondering if tetron has done something else...
egg8178
hi, tried the instruction given above, while using the bluez-zaurus_2.3-2.4.18d_arm.ipk from http://www.oesf.org/index.php?title=Bluetooth, everything seems fine until step 5, I got the same error msg as mgaughan "At step 5, /etc/rc.d/init.d/bluetooth start I get the following error -
Starting Bluetooth subsystem: hcid sdpCan't open RFCOMM control socket: no such file or directory rfcomm."

if I use the ipk listed above, at first step, "depmod -a" returned
"depmod:*** Unresolved symbol in /lib/modules//2.4.18-rmk7-pxa3-embedix/kernel/net/bluetooth/bnep/bnep.o"

and ofcourse, the step 5 error as well..

did I miss something obvious?

Thanks for your time
tumnus
Nope, I think it simply isn't working. I'll remove the working comment on the wiki...
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.