Hello everybody
I've a couple of questions regarding bluetooth v1.2:
- Does the bluetooth version only depend on the firmware or the hardware
too?
Following the page http://www.holtmann.org/linux/bluetooth/csr.html I need
a HCI 18.x firmware to have bluetooth 1.2 support. That would mean it's
hardware independent.
- How to upgrade a csr chip? I've d-link DBT-120 revision4. Following the
page http://www.holtmann.org/linux/bluetooth/features.html I need a
downgrade
to revision3 which supports bluetooth 1.2. why switched d-link back to
bluetooth 1.1 when they already had 1.2 on revision3?
I read the page http://www.holtmann.org/linux/bluetooth/dfu.html and my
conclusion is, that there's no way to upgrade/downgrade the firmware.
(Because apple explains that after upgrading a device, it will no longer
work with non apple computers and the windows firmware upgrader is no longer
available.)
Is there another way to upgrade the firmware? I could do it with linux,
windows and mac, but the dongle should still work with linux afterwards...
- actually i'm interested in the inquiry with rssi.
marcel told in a recent email in the mailinglist that silicon dongles
might return wrong values (or don't support it). So, which dongles
do support that and are they already buyable? Currently there are only
bluetooth 1.1 dongles in the stores I know...
Is it still to early for bluetooth v1.2?
- what are the other benefits of bluetooth v1.2?
regards
Marco
--
Sparen beginnt mit GMX DSL: http://www.gmx.net/de/go/dsl
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
On Sun, 2005-03-27 at 19:08 +0200, Marcel Holtmann wrote:
> The revision on a D-Link DBT-120 is a hardware revision. It is possible
> to update the Rev. 4 dongles, but not with the btdfu program. The flash
> timing are not correct.
>
This fixes btdfu for me with Rev. 4 dongles.
--- dfu.c~ 2004-06-16 20:02:01.000000000 -0400
+++ dfu.c 2005-03-03 14:07:53.000000000 -0500
@@ -33,7 +33,7 @@
#include "dfu.h"
#define DFU_PACKETSIZE 0x03ff /* CSR default value:
1023 */
-#define DFU_TIMEOUT 100
+#define DFU_TIMEOUT 1000
int dfu_detach(struct usb_dev_handle *udev, int intf)
{
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Marco,
> > check with "hciconfig hci0 revision" as root what BlueCore chip is on it
> > and no, these are not the problematic dongles.
>
> it's a BlueCore02
>
> >>so, an update to bt v1.2 wouldn't make sense to me...
> >
> > What does "lsusb" tells you?
>
> it think you mean this line:
> Bus 002 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
and if this chip now contains 8 Mbit flash you get a good chance to
upgrade it with HCI 18.x firmware and so get Bluetooth 1.2 support.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hello Marcel
Marcel Holtmann wrote:
> Hi Marco,
>
>
>>>The CSR BlueCore02/BlueCore3/BlueCore4 chips support inquiry with RSSI,
>>>but the Silicon Wave ROM chips I have seen so far have a problem with
>>>inquiry with RSSI event size. The Broadcom chips don't support inquiry
>>>with RSSI (this includes the Microsoft 2.0 dongle).
>>
>>hciconfig -a tells me that the manufacturer of my dongle is "Cambridge
>>Silicon Radio (10)". this is one of the problems-dongle, right?
>
>
> check with "hciconfig hci0 revision" as root what BlueCore chip is on it
> and no, these are not the problematic dongles.
it's a BlueCore02
>>so, an update to bt v1.2 wouldn't make sense to me...
>
> What does "lsusb" tells you?
it think you mean this line:
Bus 002 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
>>>>Is it still to early for bluetooth v1.2?
>>>
>>>
>>>It is actually too late, because we are moving to Bluetooth 2.0 with EDR
>>>support.
>>
>>but it's too early for 2.0 yet?
>
>
> Actually it is not. The only problem at the moment is that the Bluetooth
> module manufactures don't get the BlueCore4 modules done. After that you
> will see them in the USB dongles and the CSR BlueCore4 already supports
> EDR without any problems and so do BlueZ.
regards
Marco
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Marco,
> > The CSR BlueCore02/BlueCore3/BlueCore4 chips support inquiry with RSSI,
> > but the Silicon Wave ROM chips I have seen so far have a problem with
> > inquiry with RSSI event size. The Broadcom chips don't support inquiry
> > with RSSI (this includes the Microsoft 2.0 dongle).
>
> hciconfig -a tells me that the manufacturer of my dongle is "Cambridge
> Silicon Radio (10)". this is one of the problems-dongle, right?
check with "hciconfig hci0 revision" as root what BlueCore chip is on it
and no, these are not the problematic dongles.
> so, an update to bt v1.2 wouldn't make sense to me...
What does "lsusb" tells you?
> >>Is it still to early for bluetooth v1.2?
> >
> > It is actually too late, because we are moving to Bluetooth 2.0 with EDR
> > support.
>
> but it's too early for 2.0 yet?
Actually it is not. The only problem at the moment is that the Bluetooth
module manufactures don't get the BlueCore4 modules done. After that you
will see them in the USB dongles and the CSR BlueCore4 already supports
EDR without any problems and so do BlueZ.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
> The CSR BlueCore02/BlueCore3/BlueCore4 chips support inquiry with RSSI,
> but the Silicon Wave ROM chips I have seen so far have a problem with
> inquiry with RSSI event size. The Broadcom chips don't support inquiry
> with RSSI (this includes the Microsoft 2.0 dongle).
hciconfig -a tells me that the manufacturer of my dongle is "Cambridge
Silicon Radio (10)". this is one of the problems-dongle, right?
so, an update to bt v1.2 wouldn't make sense to me...
>>Is it still to early for bluetooth v1.2?
>
> It is actually too late, because we are moving to Bluetooth 2.0 with EDR
> support.
but it's too early for 2.0 yet?
regards
Marco
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Marco,
> I've a couple of questions regarding bluetooth v1.2:
>
> - Does the bluetooth version only depend on the firmware or the hardware
> too?
> Following the page http://www.holtmann.org/linux/bluetooth/csr.html I need
> a HCI 18.x firmware to have bluetooth 1.2 support. That would mean it's
> hardware independent.
this depends on the features of Bluetooth 1.2 that you need. For example
eSCO is only working with a BlueCore3 and BlueCore4 in the CSR case.
> - How to upgrade a csr chip? I've d-link DBT-120 revision4. Following the
> page http://www.holtmann.org/linux/bluetooth/features.html I need a
> downgrade
> to revision3 which supports bluetooth 1.2. why switched d-link back to
> bluetooth 1.1 when they already had 1.2 on revision3?
The revision on a D-Link DBT-120 is a hardware revision. It is possible
to update the Rev. 4 dongles, but not with the btdfu program. The flash
timing are not correct.
> I read the page http://www.holtmann.org/linux/bluetooth/dfu.html and my
> conclusion is, that there's no way to upgrade/downgrade the firmware.
> (Because apple explains that after upgrading a device, it will no longer
> work with non apple computers and the windows firmware upgrader is no longer
> available.)
This is non-sense. You simply need to run hid2hci if you upgrade with
the Apple Bluetooth 1.2 firmware.
> Is there another way to upgrade the firmware? I could do it with linux,
> windows and mac, but the dongle should still work with linux afterwards...
The best way is to use the CSR tools, but these tools are not public
available. You can update a D-Link DBT-120 with a MacOS X of course. And
if you are lucky the Linux btdfu also works.
> - actually i'm interested in the inquiry with rssi.
> marcel told in a recent email in the mailinglist that silicon dongles
> might return wrong values (or don't support it). So, which dongles
> do support that and are they already buyable? Currently there are only
> bluetooth 1.1 dongles in the stores I know...
The CSR BlueCore02/BlueCore3/BlueCore4 chips support inquiry with RSSI,
but the Silicon Wave ROM chips I have seen so far have a problem with
inquiry with RSSI event size. The Broadcom chips don't support inquiry
with RSSI (this includes the Microsoft 2.0 dongle).
> Is it still to early for bluetooth v1.2?
It is actually too late, because we are moving to Bluetooth 2.0 with EDR
support.
> - what are the other benefits of bluetooth v1.2?
Mostly AFH, Fast Connect and eSCO.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users