Bluetooth Support?

Discussion about my Wifi Radio project at http://mightyohm.com/wifiradio/ or my WL-520gU talk at NOTACON.
Post Reply
El1m1nate
Posts: 9
Joined: Thu Apr 16, 2009 5:12 am

Bluetooth Support?

Post by El1m1nate »

Ive been playing around with this router since i read part 7. The one nice addition would be bluetooth. I have a generic module which has been tested running on Linux [SLES11].
Im using external storage, so no worry about space.

It would be cool if i could control this router using a ps3 'blu-ray' remote or maybe even an IR remote via an MCU. Im building a 'jukebox' based on the radio idea. With mpd listening to music hosted on another server.

So far it doesn't look like the bluetooth module is even loading. Ive read about people having troubles with bluetooth, but no one seems to be using this good router. When i plug the module in, it seems fine.
hcid
dmesg: hub.c: new USB device 00:03.0-1.4, assigned address 4
then i try:
hcitool dev
and get
Devices:
...nothing

Has anyone successfully connected a bluetooth dongle to this router?
User avatar
mightyohm
Site Admin
Posts: 1064
Joined: Fri Apr 03, 2009 10:29 pm
Location: Seattle, WA
Contact:

Re: Bluetooth Support?

Post by mightyohm »

Are you using the firmware I posted in the tutorial or your own? I can't remember if I compiled USB-bluetooth support or not. If you do an lsmod do you see any bluetooth kernel modules being loaded?

I have a USB-bluetooth adapter, I'll have to play with it once of these days and see if i can get it working. If I do I'll definitely post here.
El1m1nate
Posts: 9
Joined: Thu Apr 16, 2009 5:12 am

Re: Bluetooth Support?

Post by El1m1nate »

Im using my own, but its extremely similar, there are some extra packages added, that's all.
I recently reflashed the router, and gave it bluetooth from scratch. ie using opkg to install kmod-bluetooth, bluezlibs and bluezutils. This was all install on the router, no external storage.

after running dbus [ /etc/init.d/dbus start] and hcid [hcid -n], i have a look at dmesg and see hcid has shot an error. some kind of kernel problem. this happens everytime i start hcid. My bluetooth module does register [even after that error] using hcitooll dev, but when scanning for devices [hcitool scan] the router crashes.

This is how far i am. If i have time ill try to find out what error hcid is throwing.
User avatar
mightyohm
Site Admin
Posts: 1064
Joined: Fri Apr 03, 2009 10:29 pm
Location: Seattle, WA
Contact:

Re: Bluetooth Support?

Post by mightyohm »

This might be another reason to try harder and get the 2.6 kernel running on the WL-520 with wireless... Last time I tried there were boot issues with b43 wireless driver problems but those might be fixed now.
El1m1nate
Posts: 9
Joined: Thu Apr 16, 2009 5:12 am

Re: Bluetooth Support?

Post by El1m1nate »

yeah. there is more support for webcams in 2.6

I did try bluetooth with usb2... router was fine, seemed to work. but the bluetooth didnt.

i havent tried 2.6 yet. i might give it a go. Sacrificing wifi wouldn't be good. does everything else work? [usb,ethernet,serial port]
User avatar
mightyohm
Site Admin
Posts: 1064
Joined: Fri Apr 03, 2009 10:29 pm
Location: Seattle, WA
Contact:

Re: Bluetooth Support?

Post by mightyohm »

Afaik - yes.
El1m1nate
Posts: 9
Joined: Thu Apr 16, 2009 5:12 am

Re: Bluetooth Support?

Post by El1m1nate »

Detailed info on my setup [for bluetooth].

to install run:
[using the installation source from openwrt : http://downloads.openwrt.org/kamikaze/8 ... /packages/]
opkg install kmod-bluetooth
opkg install bluez-utils
this should install dbus and bluez-libs

Code: Select all

root@OpenWrt:~# cat /proc/bus/usb/devices
P:  Vendor=1131 ProdID=1001 Rev= 3.73
S:  Manufacturer=ISSC
S:  Product=ISSCEDRBTA
[This is my usb bluetooth adapter. i have to get special drivers for windows...]. It registers correctly on a SLES11 machine.

Code: Select all

root@OpenWrt:~# cat /proc/bus/usb/drivers
         usbdevfs
         hub
         audio
         usb-storage
      --   hci_usb -- The important one
/storage/etc/init.d/dbus start
I am using usb storage mounted to /storage. This does not change the results much [only the need to map some config files elsewhere]. The output is the same as if i had installed it to a fresh flash of the router, which i have in the past.

Plug in your usb device then run hcid -n

Code: Select all

root@OpenWrt:/# hcid -n &
hcid[8312]: Bluetooth HCI daemon
hcid[8312]: Starting SDP server
hcid[8312]: HCI dev 0 registered
At this point the led on the bluetooth module that was solid on, starts flashing at a constant rate.

Code: Select all


root@OpenWrt:~# hcitool dev
Devices:
        hci0    00:11:67:B0:98:C5
[1] + Segmentation fault         hcid -n
The device is registered. There is something new... a segmentation fault. This happened before when you sent ctrl + c to hcid...

Followed by something bad from dmesg:

Code: Select all

Unable to handle kernel paging request at virtual address 00000000, epc == 800c9                                              e6c, ra == 8011e28c
Oops in fault.c::do_page_fault, line 206:
$0 : 00000000 1000fc00 00000000 00000000 80b73828 00000000 1000fc01 80531e68
$8 : 801a0000 801a0000 8018a7a0 00000003 000001bc 06799c74 00000001 2ac5b320
$16: ffffffea 80b737e0 80538b28 7fff7c0c 80531e68 00000000 00000000 00000002
$24: 2ac565a0 2aca5b60                   80530000 80531e10 00409394 8011e28c
Hi : 00000000
Lo : 00000960
epc   : 800c9e6c    Tainted: P
Status: 1000fc02
Cause : 00000008
PrId  : 00029029
Process hcid (pid: 473, stackpage=80530000)
Stack:    80531ef0 00000000 0048ed28 8022ac00 8004f59c 80000000 80b80244
 80d37aa0 7fffffff 80dce9c0 ffffffea 80b737e0 80538b28 7fff7c0c 0048f030
 0048ed60 8011e28c 800305f0 800c408c 00491034 80396420 80531f30 ffffffea
 80530000 80538b28 80538588 7fff7b98 800c4e40 80b737e0 00000045 80c65008
 00000002 8011f854 00030002 80cefae0 00000000 80c65020 00000005 80c63ff0
 00000000 ...
Call Trace:   [<8004f59c>] [<8011e28c>] [<800305f0>] [<800c408c>] [<800c4e40>]
 [<8011f854>] [<80049f58>] [<8004ac74>] [<8004ab3c>] [<800090b0>] [<80008a60>]
 [<80008a60>] [<8005bb0c>]

Code: 00002821  8c820008  00602821 <8c630000> 2442ffff  ac820008  ac640004  ae23                                              0048  aca00004
Unable to handle kernel paging request at virtual address 00000000, epc == c026a                                              bc8, ra == c026aab8
Oops in fault.c::do_page_fault, line 206:
$0 : 00000000 1000fc00 00000000 00000000 00000000 1000fc01 801a0000 802bbe88
$8 : 0000000b fffff7ff 00000000 00000001 00000040 08060096 00000001 2abb0b48
$16: 80b734a8 80b73460 80538820 8045de40 00000002 00000000 00000000 00000002
$24: 2abafa48 80010000                   80aee000 80aefe98 00409394 c026aab8
Hi : 00000043
Lo : 0007cf55
epc   : c026abc8    Tainted: P
Status: 1000fc02
Cause : 00000008
PrId  : 00029029
Process hcid (pid: 474, stackpage=80aee000)
Stack:    98c50000 001167b0 80538be0 800500a8 80538948 8021d1e0 800c413c
 8045de40 00000002 00000000 00000000 00000002 80538820 800c4944 00000004
 00000000 80cef6e0 8021d1e0 80cef6e0 80038a10 7fff7bb8 00000000 400448d3
 80cef0e0 80cef6e0 802bbd40 00000000 00488280 80037644 8003763c 00000002
 2acf70c4 00000000 0000000c 7fff7c18 0000000b 00000000 80008a60 00000000
 7fff7658 ...
Call Trace:   [<800500a8>] [<800c413c>] [<800c4944>] [<80038a10>] [<80037644>]
 [<8003763c>] [<80008a60>] [<8005bb0c>]

Code: 00002021  8e020008  00602021 <8c630000> 2442ffff  ae020008  ae030000  ac70                                              0004  ac800000
Unable to handle kernel paging request at virtual address 00000000, epc == 8011c                                              fe8, ra == 8011cecc
Oops in fault.c::do_page_fault, line 206:
$0 : 00000000 1000fc00 00000000 00000000 80b70bc8 1000fc01 00000000 00000000
$8 : 00000000 1000fc01 00000cbc 00001000 8020707c 0000028c 801e4000 801a0000
$16: 00000000 80b70b80 00000000 00000003 00000000 00000007 00000000 00000002
$24: 8019f5d4 ba2e8ba3                   80aee000 80aefc18 00409394 8011cecc
Hi : 00000000
Lo : 00000020
epc   : 8011cfe8    Tainted: P
Status: 1000fc02
Cause : 00000008
PrId  : 00029029
Process hcid (pid: 474, stackpage=80aee000)
Stack:    80c3f004 ffffffbf 00000001 8000bb5c 80fd51a8 8021d1e0 80fd5080
 8045d5c0 0000000b 80aefde8 00000000 800c413c 0000000b 80aefde8 00000000
 00000002 80fd5080 800c4944 00000000 800131f4 80cefa60 8021d1e0 80cefa60
 80038a10 00000002 1000fc01 80b7fcc0 803966a0 80cefa60 802bbd40 00000000
 00000001 80037644 8003763c 7fff6000 800250d4 803966a0 801a0000 802bbd40
 000000ff ...
Call Trace:   [<8000bb5c>] [<800c413c>] [<800c4944>] [<800131f4>] [<80038a10>]
 [<80037644>] [<8003763c>] [<800250d4>] [<8001611c>] [<8001153c>] [<8001153c>]
 [<80142de0>] [<800166c4>] [<800166a8>] [<80006784>] [<8014878c>] [<80142de0>]
 [<80006784>] [<8000b544>] [<c026abc8>] [<c026aab8>] [<c028bd04>] [<8000f034>]
 [<c028c02c>] [<8012bb58>] [<80010000>] [<c026aab8>] [<c026abc8>] [<800500a8>]
 [<800c413c>] [<800c4944>] [<80038a10>] [<80037644>] [<8003763c>] [<80008a60>]
 [<8005bb0c>]

Code: 00008021  8c820008  00608021 <8c630000> 2442ffff  ac820008  ac640004  ae23                                              0048  ae000004

And when i run hcitool scan
It is scanning....
It doesnt do anything unless it finds something.
If i turn my phone on, or try to find the bluray remote. it crashes. ie a freeze. followed by 20 seconds of wait with the power light on, lights go off, wait a bit, come on again and it has rebooted.


Now that i think about it, i might make a couple of images just for bluetooth. one 2.4 and one 2.6.. this will have to wait for later in the week though.
Post Reply