<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Getting the Broadcom BCM2035B to play ball</title>
	<atom:link href="http://stuartl.longlandclan.yi.org/blog/2008/03/25/bcm2035b/feed/" rel="self" type="application/rss+xml" />
	<link>http://stuartl.longlandclan.yi.org/blog/2008/03/25/bcm2035b/</link>
	<description>The life and times of Stuart Longland (VK4MSL)</description>
	<pubDate>Sat, 22 Nov 2008 12:44:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Mariano Dupont</title>
		<link>http://stuartl.longlandclan.yi.org/blog/2008/03/25/bcm2035b/#comment-1634</link>
		<dc:creator>Mariano Dupont</dc:creator>
		<pubDate>Fri, 23 May 2008 02:22:03 +0000</pubDate>
		<guid isPermaLink="false">http://stuartl.longlandclan.yi.org/blog/2008/03/25/bcm2035b/#comment-1634</guid>
		<description>I also have this dongle, and I've managed to solve the problem. It seems that some chinese company decided not to pay for a bdaddress range, so our dongles have the address zeroed.

You have to download bluez source code from http://www.bluez.org/download.html. You have to compile the libs first, and then  compile a tool called 'bdaddr' inside bluez-utils. This will allow you to set a new address manually. (you have to reset the device after running bdaddr)

The problem with this is that the bdaddres isn't retained when you unplug the dongle. I've tried to flash a new firmware, expecting that way to fix a new address, but it seems this model cannot be flashed, or bluez doesn't know how.

If you guys dare to open the dongle, maybe with the chip codes we can know if it is possible to flash it.

Good luck.</description>
		<content:encoded><![CDATA[<p>I also have this dongle, and I&#8217;ve managed to solve the problem. It seems that some chinese company decided not to pay for a bdaddress range, so our dongles have the address zeroed.</p>
<p>You have to download bluez source code from <a href="http://www.bluez.org/download.html" rel="nofollow">http://www.bluez.org/download.html</a>. You have to compile the libs first, and then  compile a tool called &#8216;bdaddr&#8217; inside bluez-utils. This will allow you to set a new address manually. (you have to reset the device after running bdaddr)</p>
<p>The problem with this is that the bdaddres isn&#8217;t retained when you unplug the dongle. I&#8217;ve tried to flash a new firmware, expecting that way to fix a new address, but it seems this model cannot be flashed, or bluez doesn&#8217;t know how.</p>
<p>If you guys dare to open the dongle, maybe with the chip codes we can know if it is possible to flash it.</p>
<p>Good luck.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Redhatter (VK4FSJL)</title>
		<link>http://stuartl.longlandclan.yi.org/blog/2008/03/25/bcm2035b/#comment-1631</link>
		<dc:creator>Redhatter (VK4FSJL)</dc:creator>
		<pubDate>Mon, 05 May 2008 22:09:34 +0000</pubDate>
		<guid isPermaLink="false">http://stuartl.longlandclan.yi.org/blog/2008/03/25/bcm2035b/#comment-1631</guid>
		<description>I managed to get mine working under Windows 2000... although support for headsets is utter crap there.  Interestingly, the Bluetooth address under the Widcomm stack showed all zeros there too.

So this may not necessarily be the problem, either the device isn't revealing its address to the OS, or Broadcom made a whoopsie producing these devices.

I shall certainly have a look at those links... for now I've just palmed the device off to my father so he can sync his new phone to his Windows 2000-based desktop.  I can borrow it to try and fix problems under Linux though.</description>
		<content:encoded><![CDATA[<p>I managed to get mine working under Windows 2000&#8230; although support for headsets is utter crap there.  Interestingly, the Bluetooth address under the Widcomm stack showed all zeros there too.</p>
<p>So this may not necessarily be the problem, either the device isn&#8217;t revealing its address to the OS, or Broadcom made a whoopsie producing these devices.</p>
<p>I shall certainly have a look at those links&#8230; for now I&#8217;ve just palmed the device off to my father so he can sync his new phone to his Windows 2000-based desktop.  I can borrow it to try and fix problems under Linux though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eddie</title>
		<link>http://stuartl.longlandclan.yi.org/blog/2008/03/25/bcm2035b/#comment-1630</link>
		<dc:creator>eddie</dc:creator>
		<pubDate>Mon, 05 May 2008 18:06:30 +0000</pubDate>
		<guid isPermaLink="false">http://stuartl.longlandclan.yi.org/blog/2008/03/25/bcm2035b/#comment-1630</guid>
		<description>Something I came across when I was trying to get it to work. Not the same device, but the same issue… no address assigned to the device.

http://linuxgazette.net/109/oregan3.html</description>
		<content:encoded><![CDATA[<p>Something I came across when I was trying to get it to work. Not the same device, but the same issue… no address assigned to the device.</p>
<p><a href="http://linuxgazette.net/109/oregan3.html" rel="nofollow">http://linuxgazette.net/109/oregan3.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eddie</title>
		<link>http://stuartl.longlandclan.yi.org/blog/2008/03/25/bcm2035b/#comment-1629</link>
		<dc:creator>eddie</dc:creator>
		<pubDate>Mon, 05 May 2008 18:05:32 +0000</pubDate>
		<guid isPermaLink="false">http://stuartl.longlandclan.yi.org/blog/2008/03/25/bcm2035b/#comment-1629</guid>
		<description>Same problem with the BCM2035B Bluetooth dongle. Haven’t found a solution yet.

Here’s what I had done…

http://www.debiantutorials.org/talkitup/index.php?topic=1662.0

Couldn’t get it to work on Debian Etch, kernel 2.6.18-6-686.
Hasn’t worked on Windows XP either (with the WIDCOMM driver which came on CD).</description>
		<content:encoded><![CDATA[<p>Same problem with the BCM2035B Bluetooth dongle. Haven’t found a solution yet.</p>
<p>Here’s what I had done…</p>
<p><a href="http://www.debiantutorials.org/talkitup/index.php?topic=1662.0" rel="nofollow">http://www.debiantutorials.org/talkitup/index.php?topic=1662.0</a></p>
<p>Couldn’t get it to work on Debian Etch, kernel 2.6.18-6-686.<br />
Hasn’t worked on Windows XP either (with the WIDCOMM driver which came on CD).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
