Asus BT400 failure on RPi Server

5 posts / 0 new
Last post
Asus BT400 failure on RPi Server

I'm trying to serve an Asus BT400 bluetooth adapter with Virtualhere running on an RPi and having problems. FTDI serial converter, Prolific serial converter, Logitech wireless keyboard receiver all worked immediately. I was using Raspbian Wheezy up until yesterday, and am on to Jessie now, kernel 4.1.17. I loaded a fresh image, ran update, and copied the .hcd file for the BT400 into the /lib/firmware/brcm/ directory so linux would find the driver. The BT adapter is connected to the RPI through a powered hub.

Ran the client on a WIN 7 box and it LOOKED like it was working, the WIN 7 client started to install a whole bunch of drivers, but as soon as I try to do something with it, it fails. The device manager reports error 43 "Windows has stopped this device because it has reported problems"

dmesg |grep usb on the RPi shows 'rest full-speed USB decive number 9 using dwc_otg every time the driver fails on the client.

I have verified the BT4-- works correctly when plugged directly into the WIN 7 machine, with all functions working.

Looking for suggestions here.....


Im wondering if the device needs to be attached to the raspbian kernel before virtualhere uses it. By default on raspberry pi, if virtualhere is running the device is not bound to the kernel and is held pending remote usage via virtualhere. Try stopping the virtualhere server, then adding the parameter below to the server config.ini file, then start the server again


That should then allow the bluetooth firmware to be uploaded to the dongle before virtualhere uses it.

Still reporting error 43 when

Still reporting error 43 when accessing it through VH and the RPi, but I notice now the Win7 machine reports error 10, device cannot start when I plug the BT400 directly into it.

Going to try a CSR based bluetooth instead of the Broadcom....

Must be a Broadcom thing

After much effort, it seems Linux doesn't play nice with the Broadcom Bluetooth chip the ASUS uses.

I bought a cheap Azio dongle with a CSR (Cambridge Silicon Radio) chip, plugged it in and it just works.

OK thats weird, i think

OK thats weird, i think broadcom try to patch their firmware when the dongle is plugged in an that may be the root cause, anyway glad its all working with the new dongle!

Log in or register to post comments