We use some essential cookies to make our website work.

We use optional cookies, as detailed in our cookie policy, to remember your settings and understand how you use our website.

soend
Posts: 9
Joined: Sun Jun 17, 2012 7:23 pm

BCM2046B1 Bluetooth Dongle not working

Mon Aug 20, 2012 6:31 pm

So i have a USB Bluetooth dongle what i would like to use with my mini bluetooth keyboard. The problem is when run hcitool dev this is what i see:

Code: Select all

# hcitool dev
Devices:
No device..
Here's lsusb output:

Code: Select all

# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 005: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass)
Bus 001 Device 006: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface Subclass)
Bus 001 Device 007: ID 0a5c:2146 Broadcom Corp.
And lsmod | grep bluetooth:

Code: Select all

lsmod | grep bluetooth
bluetooth             168414  13 btusb,rfcomm,bnep
Can anybody help me where and what to look to get this running?

soend
Posts: 9
Joined: Sun Jun 17, 2012 7:23 pm

Re: BCM2046B1 Bluetooth Dongle not working

Thu Aug 23, 2012 2:56 pm

So anybody havent been using bluetooth dongle with this chipset?

kiki51
Posts: 2
Joined: Fri Aug 24, 2012 2:14 pm

Re: BCM2046B1 Bluetooth Dongle not working

Fri Aug 24, 2012 2:16 pm

Hello,

I am in the same situation. So, if you find the solutin it would be great to share it :)

kiki51
Posts: 2
Joined: Fri Aug 24, 2012 2:14 pm

Re: BCM2046B1 Bluetooth Dongle not working

Fri Aug 24, 2012 3:08 pm

I have the same problem. So if you find the solution, it would be great ! :)

gregd72002
Posts: 31
Joined: Tue May 08, 2012 9:17 pm

Re: BCM2046B1 Bluetooth Dongle not working

Tue Aug 28, 2012 11:31 am

can u post 'dmesg'?

ktkarhu
Posts: 1
Joined: Wed Aug 29, 2012 3:07 pm

Re: BCM2046B1 Bluetooth Dongle not working

Wed Aug 29, 2012 3:29 pm

Hi,

I have the same problem with A-LINK BLUEUSB21 dongle. Actually, at one point I was able to scan and see my Nokia phone using hcitool scan but then suddenly it stopped working.

Please find below some hopefully useful output (incl dmesg) from my setup.

Code: Select all

root@raspberrypi:/home/pi# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 012: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 013: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass)
Bus 001 Device 014: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface Subclass)
Bus 001 Device 015: ID 0a5c:2148 Broadcom Corp. BCM92046DG-CL1ROM Bluetooth 2.1 Adapter
root@raspberrypi:/home/pi# /etc/init.d/dbus status
[ ok ] dbus is running.
root@raspberrypi:/home/pi# /etc/init.d/bluetooth status
[ ok ] bluetooth is running.
root@raspberrypi:/home/pi# hcitool dev
Devices:
root@raspberrypi:/home/pi# hcitool scan
Device is not available: No such device

Code: Select all

root@raspberrypi:/home/pi# dmesg | tail -32
[ 1942.941736] usb 1-1.2: new full speed USB device number 12 using dwc_otg
[ 1943.044824] usb 1-1.2: New USB device found, idVendor=0a5c, idProduct=4500
[ 1943.044868] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1943.044890] usb 1-1.2: Product: BCM2046B1
[ 1943.044905] usb 1-1.2: Manufacturer: Broadcom
[ 1943.053836] hub 1-1.2:1.0: USB hub found
[ 1943.054293] hub 1-1.2:1.0: 3 ports detected
[ 1943.331917] usb 1-1.2.1: new full speed USB device number 13 using dwc_otg
[ 1943.624859] usb 1-1.2.1: New USB device found, idVendor=0a5c, idProduct=4502
[ 1943.624906] usb 1-1.2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1943.637505] input: HID 0a5c:4502 as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1:1.0/input/input4
[ 1943.641341] generic-usb 0003:0A5C:4502.0005: input: USB HID v1.11 Keyboard [HID 0a5c:4502] on usb-bcm2708_usb-1.2.1/input0
[ 1943.722106] usb 1-1.2.2: new full speed USB device number 14 using dwc_otg
[ 1943.824861] usb 1-1.2.2: New USB device found, idVendor=0a5c, idProduct=4503
[ 1943.824908] usb 1-1.2.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1943.848883] input: HID 0a5c:4503 as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.0/input/input5
[ 1943.849796] generic-usb 0003:0A5C:4503.0006: input: USB HID v1.11 Mouse [HID 0a5c:4503] on usb-bcm2708_usb-1.2.2/input0
[ 1943.922078] usb 1-1.2.3: new full speed USB device number 15 using dwc_otg
[ 1944.025951] usb 1-1.2.3: New USB device found, idVendor=0a5c, idProduct=2148
[ 1944.025997] usb 1-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1944.026019] usb 1-1.2.3: Product: BCM92046DG-CL1ROM
[ 1944.026036] usb 1-1.2.3: Manufacturer: Broadcom Corp
[ 1944.026052] usb 1-1.2.3: SerialNumber: 00027220322A
[ 1945.041646] Bluetooth: hci0 command tx timeout
[ 1946.041672] Bluetooth: hci0 command tx timeout
[ 1947.041676] Bluetooth: hci0 command tx timeout
[ 1948.041700] Bluetooth: hci0 command tx timeout
[ 1949.041725] Bluetooth: hci0 command tx timeout
[ 1950.041750] Bluetooth: hci0 command tx timeout
[ 1951.041773] Bluetooth: hci0 command tx timeout
[ 1952.041792] Bluetooth: hci0 command tx timeout
[ 1953.041805] Bluetooth: hci0 command tx timeout
Any help is highly appreciated.

Kimmo

zog
Posts: 216
Joined: Sun Nov 20, 2011 5:43 pm

Re: BCM2046B1 Bluetooth Dongle not working

Thu Aug 30, 2012 9:20 pm

Hi,
I have got blue tooth working, but it's tricky. You need to upgrade to the latest sid kernel and add the following setting to cmdline.txt found in /boot

dwc_otg.microframe_schedule=1

You will need a blue tooth dongle with a cambridge silicon chips set - typically nano dongles. Tesco's sell a Tecknika nano dongle that has such a chip set. I installed blueman and bluetooth packages. The blue tooth dongle works much better if you insert it directly into the usb ports. Finally to get blue tooth working well you have to over clock the rpi to at least 800 Mhz. Iv'e got my pi running at 880 Mhz at the moment, but it isn't terribly stable. Here my config file it is best to edit it using another computer. If the pi won't boot or you get errors on booting revise the arm_freq parameter downwards.

Code: Select all

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=1
hdmi_mode=4

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes

#hdmi_drive=2


# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display

#config_hdmi_boost=4


# uncomment for cocomposite PAL

#sdtv_mode=2


#uncomment to overclock the arm. 700 MHz is the default.

arm_freq=880
gpu_freq=350
core_freq=334
sdram_freq=465
# for more options see http://elinux.org/RPi_config.txt

Return to “Raspberry Pi OS”