USB Bluetooth device firmware update

[Schnurpf]

Hello all,

this very interesting thread
http://forum.gsmhosting.com/vbb/showthread.php?t=166014
finally changed into a firmware (f/w) discussion. It was agreed to open a new thread to specifically focus on USB BT dongle f/w related topics.

Summarizing some conclusions will provide a good starting point for the discussion in this thread:

1.) Thanks to billyx we have a f/w, which seems to be quite up-to-date:
http://forum.gsmhosting.com/vbb/show...5&postcount=33.
The file contains a HID+HCI f/w version, which obviously applies for 8 MB Flash ROM devices like the D-Link DBT-120, and a HCI only version, which applies for 4 MB Flash ROM devices, like the Acer DBT-500, Epox BT-DG02x etc.
2.) Both versions are CSR GENERIC, not vendor specific. They might or might NOT work properly with a particular dongle. Some members reported success with it, some members experienced problems with their dongles after the update, some dongles turned out to be unusable after the update, some members couldn't even flash their devices.
3.) (Some of?) the Bluetooth dongles, who were flashed with the HID+HCI version, turned up as HID devices after the update and weren't accessible by the Bluetooth stack. I found a tool, which solves that problem:
http://forum.gsmhosting.com/vbb/show...&postcount=130
4.) It turned out, that nobody should update without saving/uploading the existing firmware first. WidComm's update tool does not provide this function. lexab65 found an alternative:
http://forum.gsmhosting.com/vbb/show...&postcount=111
It turned out, a very special driver is needed to enable the upload function of this "BlueCore firmware upgrade wizard". Again lexab65 found the right thing:
http://forum.gsmhosting.com/vbb/show...&postcount=135

So, that's the status at the moment. Sorry, post became a bit lengthy. Comments of any kind are highly appreciated. If something is wrong, please feel free to correct me!

Let's start to discuss different f/w versions, which versions fit best to what kind of a BT devices etc. etc. etc.

I hope this will be an interesting and helpful thread...

[Schnurpf]

to Yolly Zubrick & all other "crippled" Epox dongle users

Thanks to lexab65 I was able to "suck" the f/w out of my Epox dongle. I am sorry, it's a rather old version, which obviously does only support 56-Bit encryption, but it will at least re-animate your devices:

"LOADER=bc02x_4hci_bt1.1_16.4_encr56 2002-10-09, STACK=bc02x_4hci_bt1.1_16.4_encr56 2002-10-09"

Pls report back, wether or not it works with your dongle. With some help from others here in the forum we might be able to find a newer version, which will boost our Epox'es into the future ...

[Yolly Zubrick]

@Schnurpf: Too bad the firmware (Epox v525) doesn't seem to work still I have flashed using btdfuapp and CSR DFU Wizard, but after a successful flash, it still can't find my phone which is just 1.5m away.

Also, I can't seem to make the BrainBoxes inf to work. My procedure below:

1. Changed the driver of CSR Generic BT to Brainboxes USB using the posted driver.
2. Now, the BT dongle is detected as a plain USB device (BrainBox USB) and not as a CSR BT device.
3. Tried flashing with CSR DFU Wizard, but still won't UPLOAD (BACKUP) the firmware.

So then I found you made it work with your BT-DG02A, noticed any flaw in my procedure?

[Schnurpf]

Originally Posted by Yolly Zubrick

@ ..the firmware (Epox v525) doesn't seem to work ...

Hi Yolly,
you said, you flashed the f/w successfully. Let's double-check.
I assume, you are working with Widcomm 3.0.x, right? Switch back to Widcomm drivers, right click the BT tray icon, click "Advanced Configuration". The "Bluetooth Configuration" windows appears, click the "Hardware" tab.
If the f/w flash has been successful, it would look EXACTLY like this:

[Schnurpf]

For your reference:

Chipsets: http://www.holtmann.org/linux/bluetooth/devices.html

CSR F/W revisions: http://www.holtmann.org/linux/bluetooth/csr.html

Could someone add a list of devices's PIDs and VIDs ?

[Reflex[NL]]

Maybe a good idea to have a separate firmware discussion,

My orignal Thread was intended to make other WIDCOMM drivers work with the same BT dongle with the help of a patch.

Thanks to pcristi, Phantasm and billyx

However, driver and firmware issues are still closely linked

[billyx]

Thanks Snurpf for the summary of information and tools.

Thanks to all for the collection of usefull information, tools and files within a few days.

[mortify]

i have a configuration like this..it's an old firmware or a newone?
i haven't see something like that again..

[billyx]

Originally Posted by mortify

i have a configuration like this..it's an old firmware or a newone?
i haven't see something like that again..

It's a quite new firmware. Would you please provide us a copy?

[billyx]

- Start DFUWizard (Link to the program http://61.71.104.13/drivers/1.4.2.11-N/dfu.zip)
- Select the attached firmware
- Respond to the message "Either the BlueCore module or device driver doesn't support upload of the existing firmware. Would you like to continue with the download anyway?" with No.
-Close the Wizard
-Look at the Properties of the Bluetooth-Stick in the system-manager to find out VID and PID
-Add a line with your VID and PID into BL554-2.inf (http://forum.gsmhosting.com/vbb/showpost.php?p=955220)
-Install the new driver for your device
-Now the DFUWizard can upload the firmware
- Select the attached firmware
-The firmware is stored in the user-profile at "Application Data\Cambridge Silicon Radio\BlueCore Device Firmware Upgrade Wizard"

You can use the attached firmware, it is accepted for all dongles but doesn't work for the most devices so the process is cancled after some seconds. But to be sure don't do the firmware download if the upload failed for some reason

[crux]

hi

is this updated?

thanks

[billyx]

Originally Posted by crux

hi

is this updated?

thanks

Version 1586 is the latest version we have, but it is not sure it will work with your dongle. Be sure to backup your firmware first (and provide us a copy of your firmware).

[Schnurpf]

@billyx
"We have" version 1586? I must have overseen the appropriate post!? Could you provide the link?

[Schnurpf]

Originally Posted by mortify

i have a configuration like this..it's an old firmware or a newone? I haven't see something like that again..

@mortify, @crux:
To judge the "age" of your particular f/w, please see here:
CSR F/W revisions: http://www.holtmann.org/linux/bluetooth/csr.html
Please provide us a copy!

[billyx]

Originally Posted by Schnurpf

@billyx
"We have" version 1586? I must have overseen the appropriate post!? Could you provide the link?

GenericCSR contains 1586.