Socket Bluetooth Rev G working with BlueZ out of the box

[ajaustin]

I just got the following response from Ambicom:

All I know is BT2000C has CSI chipset and BT2000E has Ericsson chipset.
Best Regards,
William Lee
AmbiCom Support Team

Do you think he is confirming the CSR chipset?

Tony

[tumnus]

Try:

hciattach /dev/ttyS3 bcsp

But we could do with knowing the UART protocol (bcsp, h4, etc) and the UART initialisation parameters.

[ajaustin]

Tumnus,

Try:

hciattach /dev/ttyS3 bcsp

Sorry, I did not make it clear that I have already tried that with same results as others (ie BCSP initialization timed out).

I am emailing William Lee for answers to your addition questions.

Tony

[n8a]

I am emailing William Lee for answers to your addition questions. 

I know William, too

Any luck with getting the card working, ajaustin?  I haven\'t time to try getting this working... I\'m considering a return for the old bt CF card very strongly now, but let me know if you have a chance to try it out.

Nate

[tumnus]

I have just uploaded the latest BlueZ driver package to the ZUG Downloads (in the driver package section). When they appear I will update the BlueZ Bluetooth Howto.

I have done away with the extra CSR UART package and with any luck the Socket Rev G card should still work out of the box.

If I\'m on a roll even the Ambicom BT2000C card may work out of the box (I realised I was being stupid and forgot to try something obvious)

Let me know how it goes. I\'m off to bed, so I\'ll probably update the howto tomorrow.

[doublec]

What was the change to try and get the BT2000C to work?

[n8a]

As a real quick note, I tried the latest bluez drivers loaded to ZUG, and the results with my AmbiCom BT2000C were noticeable.  When I did the ipkg install, the card LED immediately started to blink as bluetooth was turned on.  I performed a BT restart, and for the first time, hciconfig returned something:

Code: [Select]

# hciconfig

hci0:  Type: PCCARD

         BD Adress: 00:00:00:00:00:00 ACL MTU: 0:0   SCO MTU: 0:0

         DOWN

         RX bytes:0 acl:0 sco:0 events:0 errors:0

         TX bytes:0 acl:0 sco:0 commands:1 errors:0



#

But, same ol\' with the hciattach and hciconfig hci0 up commands:

Code: [Select]

# depmod -a

# hciconfig hci0 up

Can\'t init device hci0.  Connection timed out(110)

# hciattach /dev/ttyS3 bcsp 230400

Can\'t get port settings: Input/output error

Can\'t initialize device: Input/output error

#

When I perform a lsmod, it shows that the bt950_cs driver is being used for bluez.  I have to perform all of the other settings/edits I believe, but it\'s too late for me to try it tonight...

[tumnus]

I don\'t think anyone actually tried the bt950 driver, unless I missed a post. The bt950.conf from Holtmann\'s site doesn\'t include the BT2000C entry so I added it to bluetooth.conf

If it is working with the bt950 driver then you do not need hciattach. Although the fact that it starts with the HCI device down is a bit worrying.

Try \'hciconfig hci0 up\' and then something like \'sdptool browse\' with another bluetooth device set to discoverable.

[doublec]

If you do a dmesg I think you\'ll see lots of errors listed. That\'s what I got with the Billionton card when using the bt950_cs driver. If you look at the results of the hciconfig you\'ll see the \'bd address\' is \'00:00:00:00\' which indicates that something hasn\'t worked right I think.

[n8a]

Well, thanks for the feedback.  FYI- I tried several things to get the AmbiCom BT2000C card to work.

If it is working with the bt950 driver then you do not need hciattach. Although the fact that it starts with the HCI device down is a bit worrying.  

Try \'hciconfig hci0 up\' and then something like \'sdptool browse\' with another bluetooth device set to discoverable.

I tried the \'hciconfig hci0 up\' command, and the result after about 10 secs was:

Can\'t init device hci0.  Connection timed out(110)

I tried \'sdptool browse\', and the result was an immediate:

Inquiring ...
Inquiry failed

The next thing that I tried was to get the newly created Bluez drivers to use hci_uart instead of bt950_cs.  I edited the file /etc/pcmcia/bluetooth.conf and changed the setting for the BT2000C card as follows:

card “AmbiCom BT2000C Bluetooth CF Card”
   version “AmbiCom BT2000C”, “Bluetooth PC/…”
   bind “bt950_cs”

to

card “AmbiCom BT2000C Bluetooth CF Card”
   version “AmbiCom BT2000C”, “Bluetooth PC/…”
   bind “hci_uart”

After doing that, I did the following:

# depmod –a
# /etc/rc.d/init.d/pcmcia restart
# /etc/rc.d/init.d/bluetooth restart
Shutting down Bluetooth… Done.
Starting Bluetooth… Can’t get port settings: Input/output error
Can’t initialize device: Input/output error
Done.
# cardctl ident
Socket 0:
   no product info available
Socket 1:
   no product info available
#

Thus, after using the latest Bluez drivers that were created, hciconfig was able to return information (albeit erroneous as doublec indicated), and the AmbiCom BT2000C was using the bt950_cs driver based on the bluetooth.conf file.  However, once that setting was changed to use the correct driver, it no longer seemed to work.  Any help/ideas appreciated as usual.

[tumnus]

You needed to run \'cardctl insert\' before \'/etc/rc.d/init.d/bluetooth restart\' but I\'m still not confident it will work.

[n8a]

Well, I took your advice and it the results changed – the bluetooth restart caused no errors, and the ‘cardctl ident’ once again was able to determine correctly the device in Socket 0.  

However, I then received the following results:

# hciconfig
# hciconfig hci0 up
Can’t get device info: No such device
# hciattach /dev/ttyS3 bcsp 230400
Can’t get port settings: Input/output error
Can’t initialize device: Input/output error
# sdptool browse
Inquiring ...
Inquiry failed
#

One thing to note – lsmod returns the following results:

<exerpt>
# lsmod
Module   Size   Used   by
Rfcomm   blah   1
…
hci_uart   blah   0   [unused]
…
bluez   blah   1   [rfcomm l2cap hci_uart]
…
l2cap   blah   1   [rfcomm]
#

Any thoughts?  tumnus – have you received the AmbiCom card yet?  Just curious… Thanks again.

Nate

[tumnus]

Any thoughts?  tumnus, have you received the AmbiCom card yet?  Just curious Thanks again

No thoughts, but I have just got the card, so I will have a look at it myself tonight.

[n8a]

tumnus, I bought a Socket BT card (Rev. G) on Amazon for $82.  After about 10-15 minutes, I had the card working with my t610 thanks to your latest drivers.  What a joy!  Hopefully, you\'ll get the BT2000C working, but I personally had to either return the card right away or I\'d be stuck with it.  I decided to play it safe, thankfully!

I still had some errors in the process (hciattach /dev/ttyS3 bcsp 230400 always times out), and it took some work before errors did not appear when bluetooth was starting up.  FYI - I first tried getting the card to work with Bluez v18e, but eventually I tried Bluez 18d and got the card working soon after.

Thanks for the help with this-

[n8a]

As a quick follow up, I wanted to show how I was able to get the socket bluetooth rev. G card working with the 5500 running tkcROM alpha3 (as it only worked easily with the bluez-zaurus_2[1].3-2.4.18d_arm.ipk package originally referenced in this thread):

# cd /mnt/card/Documents/ipkg/new_bluez
# ls
bluez-csr-serial_0[1].1_arm.ipk
bluez-zaurus_2[1].3-2.4.18d_arm.ipk
bluez-zaurus_2[1].3-2.4.18e_arm.ipk
sudo_0.1_arm.ipk
susp-resume-bluez_0[1].9.1_arm.ipk
susp-resume_0.9-3.1.ipk
# ipkg install susp-resume_0.9-3.1.ipk
Unpacking susp-resume...Done.
Configuring susp-resume...Done.
# ipkg install bluez-zaurus_2[1].3-2.4.18d_arm.ipk
Unpacking bluez-zaurus...Done.
Configuring bluez-zaurus...Starting Bluetooth... Can\'t get port settings: Input/output error
Can\'t initialize device: Input/output error
Done.
Done.
# ipkg install bluez-csr-serial_0[1].1_arm.ipk
Unpacking bluez-csr-serial...Done.
Configuring bluez-csr-serial...Done.
# hciconfig
# cardctl ident
Socket 0:
  product info: \"Socket\", \"CF+ Personal Network Card Rev 2.5\"
  manfid: 0x0104, 0x0096
  function: 2 (serial)
Socket 1:
  no product info available
# /etc/rc.d/init.d/pcmcia restart
# cardctl ident
Socket 0:
  no product info available
Socket 1:
  no product info available
# cardctl insert
# cardctl ident
Socket 0:
  product info: \"Socket\", \"CF+ Personal Network Card Rev 2.5\"
  manfid: 0x0104, 0x0096
  function: 2 (serial)
Socket 1:
  no product info available
# /etc/rc.d/init.d/bluetooth restart
Shutting down Bluetooth... Done.
Starting Bluetooth... Done.
# hciconfig
hci0:   Type: UART
        BD Address: 00:02:C7:1C:D0:2A ACL MTU: 340:4  SCO MTU: 64:10
        UP RUNNING PSCAN ISCAN
        RX bytes:264 acl:0 sco:0 events:13 errors:0
        TX bytes:448 acl:0 sco:0 commands:12 errors:0

# hciconfig hci0 up
# depmod -a
# hciattach /dev/ttyS3 bcsp 230400
BCSP initialization timed out
# sdptool browse
Inquiring ...
Browsing xx:xx:xx:xx:xx:xx ... <<replaced mac address>>
Service Name: Dial-up Networking
Service RecHandle: 0x10000
Service Class ID List:
  \"Dialup Networking\" (0x1103)
  \"Generic Networking\" (0x1201)
Protocol Descriptor List:
  \"L2CAP\" (0x0100)
  \"RFCOMM\" (0x0003)
    Channel: 1
Profile Descriptor List:
  \"Dialup Networking\" (0x1103)
    Version: 0x0100

<< the rest of output cut>>
#
# cd /etc/bluetooth
# ls
givepin      hcid.conf    pin          rfcomm.conf  uart
# vi rfcomm.conf

#
# RFCOMM configuration file.
#
# $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $
#

rfcomm0 {
        # Automatically bind the device at startup
        bind yes;

        # Bluetooth address of the device
        device xx:xx:xx:xx:xx:xx;   <<replaced mac address>>

        # RFCOMM channel for the connection
        channel 1;

        # Description of the connection
        comment \"t610 dial-up bluetooth connection\";
}


~
~
Wrote \"rfcomm.conf\"  21 lines, 354 characters
#
# /etc/rc.d/init.d/bluetooth restart
Shutting down Bluetooth... Done.
Starting Bluetooth... Done.
# hciattach /dev/ttyS3 bcsp 230400
BCSP initialization timed out
#

By doing that, my bt card is identified as a \"serial or modem\" and it works just fine for connecting to my t610 and providing a pretty quick connection to the web.  I was not able to get the socket bt card working with the bluez-zaurus_2[1].3-2.4.18e_arm.ipk, which identified my card correctly as the Socket Bluetooth Rev. G card, although I didn\'t try much after this worked.