OESF Portables Forum

Everything Else => General Support and Discussion => Zaurus General Forums => Archived Forums => Security and Networking => Topic started by: woodbri on July 18, 2004, 02:09:59 pm

Title: Ambicon Bluetooth, Z55, 3.13 ROM problems
Post by: woodbri on July 18, 2004, 02:09:59 pm

Hi all,
I'm Zaurus newbie and having trouble getting bluetooth running. I would like to establish a network with my Win2k box and/or pair with my Royaltek BlueGPS.

Installation details:
Rom 3.13
bluez-zaurus_2.3_2.4.18e_arm.ipk
bluez-csr-serial_0.1_arm.ipk
qtopia-bluetoothnetworkapplet_1.0.1+arm.ipk
qtopia-pannetworkapplet_1.0.1_arm.ipk
sudo_0.1_arm.ipk
susp-resume-bluez_0.9.1_arm.ipk

I have the Ambicom BT2000-CF card that has the purple top and the light is blinking on it when it is installed.

$ sudo hciconfig
hci0:  Type: PCCARD
  BD Address: 00:00:00:00:00:00 ACL MTU: 0:0  SCO MTU 0:0
  DOWN
  RX bytes:0 acl:0 sco:0 events: errors:0
  TX bytes:4 acl:0 sco:0 commands:1 errors:0

It does not seem to be reading the MAC address of the card.

I have also tried installing

bluez-bt950-cs-high-speed_1.0.0_arm.ipk with the same results.

I have read through this forum and most of the other documents I have found regarding bluetooth and Z. I also tried installing all the BlueZ kernel, libs, utils, sdp, rfcommd, rfcomm instead of the above but that did not even get to the point of recognizing and reseting the CF card.

Any ideas what I should do now, that will get this working?

Title: Ambicon Bluetooth, Z55, 3.13 ROM problems
Post by: albertr on July 18, 2004, 07:10:31 pm

I'm afraid somebody needs to write a driver for this card, unless somebody already did that recently (I'm not following these boards closely lately, so I might miss that). But you do seem to have a newer design of BT2000 card WITH LIGHT, and these cards were not supported by existing drivers. If you still can return this card, I'd suggest you to do so and get a supported card instead, sorry. For a list of supported cards, check out BlueZ and Affix web sites.
-albertr

Title: Ambicon Bluetooth, Z55, 3.13 ROM problems
Post by: woodbri on July 18, 2004, 08:55:44 pm

Arrgh! I don't think I can return it  
It is a shame there is no support for this card or most of the cheaper cards that are available today.  What does it take to write a driver for this card?

Title: Ambicon Bluetooth, Z55, 3.13 ROM problems
Post by: maslovsky on July 19, 2004, 11:55:14 am

Quote

What does it take to write a driver for this card?

It takes a skillfull enough linux kernel driver developer, some of his time and a donation of the card...

PS: Don't ask me, I'm not a skillfull linux kernel driver developer

Title: Ambicon Bluetooth, Z55, 3.13 ROM problems
Post by: tumnus on July 19, 2004, 12:10:33 pm

Quote

PS: Don't ask me, I'm not a skillfull linux kernel driver developer

Me neither, as I found out. While the mind is willing I simply haven't got the time to learn

I had a look at this and from what I could see, the Oxford 950 UART initialisation code from the bt950 kernel module needs porting to hciattach so then the hci_usb driver could be used with the new Ambicom card. It uses a common CSR chip which hci_usb should be able to drive, whereas the older card uses an Ericsson chip, yet both still use the Oxford 950 UART chip AIUI.

Title: Ambicon Bluetooth, Z55, 3.13 ROM problems
Post by: woodbri on July 21, 2004, 10:45:55 pm

Just for completeness and the hope that this will help others, if you do:

$ sudo cardctl ident

on the two Ambicom Bluetooth cards you get the following reports:

For the one that works:

Socket: 0
  product info: "AmbiCom,Inc", "BT2000E", "Bluetooth PC/CF Card"
  nanfid: 0x022d, 0x2000
  function: 2 (serial)

For the one that does NOT work:

Socket: 0
  product info: "AmbiCom BT2000C", "Bluetooth PC/CF Card" "" ""
  nanfid: 0x022d, 0x2000
  function: 2 (serial)