USB bluetooth adapter for rev C with Angstrom

Hello

Just curious if anyone has some recommendations of which Bluetooth adapter works well with Angstrom (demo image) and the Beagleboard using rev c

Thanks,

G

I've been using a micro adapter from Rocketfish that I picked up at
Best Buy.

http://www.bestbuy.com/site/olspage.jsp?skuId=8820886&type=product&id=1207351932175&ref=06&loc=01&ci_src=14110944&ci_sku=8820886

It's a bit pricey, but FWIW it works!

Thank you

Do you have any documentation on the steps to enable the adapter?

Thanks,
G

Using the demo image I still had to connect the adapter to a powered
USB hub connected to the USB OTG port. To connect the hub to the
board, I used a Mini-A to USB A Female cable. You can see the whole
setup at the Special Computing website:

https://specialcomp.com/beagleboard/RevC2.htm

On boot, the board recognizes the bluetooth adapter and you're good to
go. If for some reason the device doesn't come up automatically, you
can try the following command to bring it up:

# hciconfig hci0 up

Once the device is up, you'll have access to all the normal commands:
hcitool, sdptool, etc.

Best of luck!

Sounds easy..

Thank you..
G

Aren't all HCI adapters the same?

I grabbed the first one I could find (IOGEAR GBU211) :

root@beagleboard:~# dmesg | grep -i blue
[ 20.495117] Bluetooth: HCI UART driver ver 2.2
[ 20.499603] Bluetooth: HCI H4 protocol initialized
[ 20.504516] Bluetooth: HCI BCSP protocol initialized
[ 20.509552] Bluetooth: HCILL protocol initialized
[ 20.514312] Bluetooth: Broadcom Blutonium firmware driver ver 1.2
[ 20.526702] Bluetooth: Digianswer Bluetooth USB driver ver 0.10
[ 20.538696] Bluetooth: BlueFRITZ! USB driver ver 1.2
[ 20.549621] Bluetooth: Generic Bluetooth USB driver ver 0.4
[ 20.561126] Bluetooth: Generic Bluetooth SDIO driver ver 0.1
[ 20.799530] Bluetooth: L2CAP ver 2.11
[ 20.803222] Bluetooth: L2CAP socket layer initialized
[ 20.808380] Bluetooth: SCO (Voice Link) ver 0.6
[ 20.812957] Bluetooth: SCO socket layer initialized
[ 20.823272] Bluetooth: RFCOMM socket layer initialized
[ 20.828521] Bluetooth: RFCOMM TTY layer initialized
[ 20.833496] Bluetooth: RFCOMM ver 1.10
[ 20.837341] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 20.842681] Bluetooth: BNEP filters: protocol multicast
[ 20.847991] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
root@beagleboard:~#

root@beagleboard:~# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0002
Bus 002 Device 002: ID 0409:005a NEC Corp.
Bus 002 Device 003: ID 0a5c:200a Broadcom Corp. Bluetooth dongle
Bus 002 Device 004: ID 0b95:772a ASIX Electronics Corp.
root@beagleboard:~#

Probably not, but the interface seems very standardised. I used
different dongles in the past and never encountered problems.
Only thing to look out for is that you need a hub if it is a USB 1.1
dongle and you are using the EHCI port.

FM

> Aren't all HCI adapters the same?

Probably not, but the interface seems very standardised. I used
different dongles in the past and never encountered problems.
Only thing to look out for is that you need a hub if it is a USB 1.1
dongle and you are using the EHCI port.

FM

There has been some chipsets that did not play well in the past. About 2 years
ago, a sampling of the local electronics store resulted in 1 non functional
adapter, 2 that worked fine, and 1 that didn't work in certain profiles.
Right now, the one that did not work seems to be working. At the moment, it
seems most dongles will do okay for basic data but for the more exotic
profiles, things may need vendor specific commands. Exotic would include
things like sound.

What about bluetooth networking and bluetooth printing.. do those
require vendor specific commands

What about bluetooth networking and bluetooth printing.. do those
require vendor specific commands

Those seems to just work if the device is recogonized by the stack.

Maybe I am thinking of IEEE-1394 (FireWire). Are all those devices the same?

- dan

Hi,

I am having trouble getting the BB rev c to recognize my rocketfish Bluetooth adapter with angstrom demo image. I have a powered USB hub with other dongles working on the hub (USB Ethernet). When I do a hcitool scan, the following message.. Any suggestions?

root@beagleboard:~# hcitool scan
Device is not available: No such device

root@beagleboard:~# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 003: ID 0b95:7720 ASIX Electronics Corp.
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 005: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen
Bus 001 Device 006: ID 413c:2105 Dell Computer Corp.
Bus 001 Device 007: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 001 Device 011: ID 0a5c:4500 Broadcom Corp.
Bus 001 Device 012: ID 0a5c:4502 Broadcom Corp.
Bus 001 Device 013: ID 0a5c:4503 Broadcom Corp.
Bus 002 Device 001: ID 1d6b:0002

Here are the debug messages

root@beagleboard:~# dmesg | grep -y -n blue
47:Bluetooth: Core ver 2.13
49:Bluetooth: HCI device and connection manager initialized
50:Bluetooth: HCI socket layer initialized
136:Bluetooth: HCI USB driver ver 2.10
138:Bluetooth: Broadcom Blutonium firmware driver ver 1.2
140:Bluetooth: Digianswer Bluetooth USB driver ver 0.10
142:Bluetooth: Generic Bluetooth SDIO driver ver 0.1
162:Bluetooth: L2CAP ver 2.11
163:Bluetooth: L2CAP socket layer initialized
164:Bluetooth: SCO (Voice Link) ver 0.6
165:Bluetooth: SCO socket layer initialized
166:Bluetooth: RFCOMM socket layer initialized
167:Bluetooth: RFCOMM TTY layer initialized
168:Bluetooth: RFCOMM ver 1.10
169:Bluetooth: BNEP (Ethernet Emulation) ver 1.3
170:Bluetooth: BNEP filters: protocol multicast
171:Bluetooth: HIDP (Human Interface Emulation) ver 1.2
root@beagleboard:~#

Hi,

Have you checked for the basic things? They are listed in my ESC Boston and
ESC Silicon Valley slides for the BYOE Bluetooth session. It goes through the
basics of how to get bluetooth going. If you need a sanity check/sample
output, look at the last few slides for the lab. They are on my website,
specifically this page -
http://www.hy-research.com/downloads.html

One question is whether you got the micro adapter or the regular size
one. Even though they are both branded as "Rocketfish" from BestBuy,
if you look at the specs, they are actually two different chipsets
that BestBuy (or whoever) rebranded as Rocketfish. I only tried the
micro adapter on the BB, but I tried both on a laptop running CentOS
before I bought a BB and only the micro adapter would be recognized.

I got the regular sized one so that might be the problem. I will return tomorrow and report the results.

Thanks
G

Hello

Thanks for the feedback on the micro adapter. I returned the regular adapter and bought the micro rocketfish. It appears that the micro-adapter works now..

hciconfig
hci0: Type: USB
        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:0 errors:0
        TX bytes:0 acl:0 sco:0 commands:0 errors:0

G