<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for MakeStuff</title>
	<atom:link href="http://www.makestuff.eu/wordpress/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://www.makestuff.eu/wordpress</link>
	<description>Make stuff, not war!</description>
	<lastBuildDate>Tue, 10 Aug 2010 07:45:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on Fx2tools by Chris</title>
		<link>http://www.makestuff.eu/wordpress/?page_id=343&#038;cpage=1#comment-5159</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 10 Aug 2010 07:45:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.makestuff.eu/wordpress/?page_id=343#comment-5159</guid>
		<description>Ah, that won&#039;t work. The output from &quot;&lt;code&gt;ucm IN 0xA2 ...&lt;/code&gt;&quot; will be the I2C records (notice that the first byte is =0xC2=). An I8HEX file created from that will not load back into the EEPROM properly, because =fx2loader= will assume it&#039;s an I8HEX file of the actual program, not an I8HEX file of the I2C records. But I definitely see the value in being able to do what you&#039;re trying to do; I will implement the missing file source and destinations to allow you do to this, and I will make sure it works on my Nexys2. It will be fairly simple to do, but it will take a few days because I don&#039;t have much free time this week.</description>
		<content:encoded><![CDATA[<p>Ah, that won't work. The output from "<code>ucm IN 0xA2 ...</code>" will be the I2C records (notice that the first byte is <code>0xC2</code>). An I8HEX file created from that will not load back into the EEPROM properly, because <code>fx2loader</code> will assume it's an I8HEX file of the actual program, not an I8HEX file of the I2C records. But I definitely see the value in being able to do what you're trying to do; I will implement the missing file source and destinations to allow you do to this, and I will make sure it works on my Nexys2. It will be fairly simple to do, but it will take a few days because I don't have much free time this week.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fx2tools by Tyler</title>
		<link>http://www.makestuff.eu/wordpress/?page_id=343&#038;cpage=1#comment-5145</link>
		<dc:creator>Tyler</dc:creator>
		<pubDate>Mon, 09 Aug 2010 21:47:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.makestuff.eu/wordpress/?page_id=343#comment-5145</guid>
		<description>It is really a Nexys2 that I have also.  I also have the new Genesys board that I would like to poke around with too.  I think the issue is that if I wish to backup the onboard EEPROM, I was piping a ucm IN to hxd and sending that to a file which I parsed with a script into an Intel hex record.  From this point I tried loading that back to EEPROM with =fx2loader -src dump.ihx -dst eeprom= and I realized then that things weren&#039;t sitting in the right place in memory.  I am not extremely familiar with the i2c bootloader mechanism so I may have a misunderstanding.  It appears that maybe a straight hex .iic file may be what I wish to use for the backup image.  But then that is more complicated to load back onto the device.</description>
		<content:encoded><![CDATA[<p>It is really a Nexys2 that I have also.  I also have the new Genesys board that I would like to poke around with too.  I think the issue is that if I wish to backup the onboard EEPROM, I was piping a ucm IN to hxd and sending that to a file which I parsed with a script into an Intel hex record.  From this point I tried loading that back to EEPROM with <code>fx2loader&nbsp;-src&nbsp;dump.ihx&nbsp;-dst&nbsp;eeprom</code> and I realized then that things weren't sitting in the right place in memory.  I am not extremely familiar with the i2c bootloader mechanism so I may have a misunderstanding.  It appears that maybe a straight hex .iic file may be what I wish to use for the backup image.  But then that is more complicated to load back onto the device.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fx2tools by Chris</title>
		<link>http://www.makestuff.eu/wordpress/?page_id=343&#038;cpage=1#comment-5140</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Mon, 09 Aug 2010 19:26:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.makestuff.eu/wordpress/?page_id=343#comment-5140</guid>
		<description>Hi Tyler,

Sorry, I made a mistake in my last comment. It&#039;s the Nexys2 board that I&#039;ve been playing with, not the Nexys. I corrected my comment. There should be no changes to the fx2loader code to work with these boards (I was thinking more about changes to my custom firmware). I will try it now and let you know how I get on.

Chris</description>
		<content:encoded><![CDATA[<p>Hi Tyler,</p>
<p>Sorry, I made a mistake in my last comment. It's the Nexys2 board that I've been playing with, not the Nexys. I corrected my comment. There should be no changes to the fx2loader code to work with these boards (I was thinking more about changes to my custom firmware). I will try it now and let you know how I get on.</p>
<p>Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fx2tools by Tyler</title>
		<link>http://www.makestuff.eu/wordpress/?page_id=343&#038;cpage=1#comment-5137</link>
		<dc:creator>Tyler</dc:creator>
		<pubDate>Mon, 09 Aug 2010 17:48:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.makestuff.eu/wordpress/?page_id=343#comment-5137</guid>
		<description>Have you had any problems with writing images to the EEPROM on the Nexys board?  If I try to restore the stock donbusb image, it appears bits get scrambled.  I end up with bytes from the last few addresses of the hex file in the lower memory space of the chip.  If I truncate my hex file to only write, say, the first 4KB it appears to write correctly.  Could that be an unintentional limit in the fx2loader code?  Your note about suspected changes in the code to handle the Nexys is intriguing.</description>
		<content:encoded><![CDATA[<p>Have you had any problems with writing images to the EEPROM on the Nexys board?  If I try to restore the stock donbusb image, it appears bits get scrambled.  I end up with bytes from the last few addresses of the hex file in the lower memory space of the chip.  If I truncate my hex file to only write, say, the first 4KB it appears to write correctly.  Could that be an unintentional limit in the fx2loader code?  Your note about suspected changes in the code to handle the Nexys is intriguing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fx2tools by Chris</title>
		<link>http://www.makestuff.eu/wordpress/?page_id=343&#038;cpage=1#comment-4385</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 07 Jul 2010 01:17:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.makestuff.eu/wordpress/?page_id=343#comment-4385</guid>
		<description>Hi Brian,

I&#039;m glad you found it useful! Thanks for pointing out this bug. It looks like Dennis has made some incompatible changes to [[http://github.com/mulicheng/fx2lib/tree/master][fx2lib]] since I last built this stuff. I just fixed my [[http://github.com/makestuff/fx2tools/tree/master/firmware][git repo]]; I can now successfully build the firmware on a fresh Ubuntu 10.04 installation (actually running on VirtualBox under a Windows 7 host, but that should not matter) using these commands:

&lt;verbatim&gt;cd $HOME
sudo apt-get install sdcc
mkdir -p sandbox/apps
cd sandbox/apps/
wget http://github.com/makestuff/fx2tools/tarball/master
gunzip -c makestuff-fx2tools-*.tar.gz &#124; tar xf -
cd makestuff-fx2tools-*
make -f Makefile.linux firmware&lt;/verbatim&gt;

Let me know if you still can&#039;t build it.

Actually I need to update this stuff anyway to conform to my new [[http://www.makestuff.eu/wordpress/?p=811][build infrastructure]], and I suspect I will need to make firmware changes to cope with [[http://www.digilentinc.com/Products/Detail.cfm?Prod=NEXYS2][the Digilent Nexys2]], which I&#039;ve been playing with recently, so watch out for further updates.</description>
		<content:encoded><![CDATA[<p>Hi Brian,</p>
<p>I'm glad you found it useful! Thanks for pointing out this bug. It looks like Dennis has made some incompatible changes to <a href="http://github.com/mulicheng/fx2lib/tree/master">fx2lib</a> since I last built this stuff. I just fixed my <a href="http://github.com/makestuff/fx2tools/tree/master/firmware">git repo</a>; I can now successfully build the firmware on a fresh Ubuntu 10.04 installation (actually running on VirtualBox under a Windows 7 host, but that should not matter) using these commands:</p>
<pre><code>cd $HOME
sudo apt-get install sdcc
mkdir -p sandbox/apps
cd sandbox/apps/
wget <a href="http://github.com/makestuff/fx2tools/tarball/master" rel="nofollow">http://github.com/makestuff/fx2tools/tarball/master</a>
gunzip -c makestuff-fx2tools-*.tar.gz | tar xf -
cd makestuff-fx2tools-*
make -f Makefile.linux firmware</code></pre>
<p>Let me know if you still can't build it.</p>
<p>Actually I need to update this stuff anyway to conform to my new <a href="http://www.makestuff.eu/wordpress/?p=811">build infrastructure</a>, and I suspect I will need to make firmware changes to cope with <a href="http://www.digilentinc.com/Products/Detail.cfm?Prod=NEXYS2">the Digilent Nexys2</a>, which I've been playing with recently, so watch out for further updates.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fx2tools by Brian</title>
		<link>http://www.makestuff.eu/wordpress/?page_id=343&#038;cpage=1#comment-4382</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Tue, 06 Jul 2010 19:40:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.makestuff.eu/wordpress/?page_id=343#comment-4382</guid>
		<description>Thanks for this great set of tools and instructions! I have been successfully programming my chip with new firmwares, used your precompiled firmware, and also can compile many other examples I have come across. When I try to compile the firmware you provide from source, however, sdcc complains: error 20: Undefined identifier &#039;SETUP_TYPE&#039;. Any clue what might be going wrong? Thanks.</description>
		<content:encoded><![CDATA[<p>Thanks for this great set of tools and instructions! I have been successfully programming my chip with new firmwares, used your precompiled firmware, and also can compile many other examples I have come across. When I try to compile the firmware you provide from source, however, sdcc complains: error 20: Undefined identifier 'SETUP_TYPE'. Any clue what might be going wrong? Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Placing Vias Under Fine-Pitch SMDs on Home-Made PCBs by jrt</title>
		<link>http://www.makestuff.eu/wordpress/?p=877&#038;cpage=1#comment-4344</link>
		<dc:creator>jrt</dc:creator>
		<pubDate>Sun, 04 Jul 2010 20:51:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.makestuff.eu/wordpress/?p=877#comment-4344</guid>
		<description>Great guide. I&#039;m using these rivets too (punched by hand) but I hadn&#039;t been brave enough yet to try them under components.

http://blog.hodgepig.org/articles/000039-bn4/index.html</description>
		<content:encoded><![CDATA[<p>Great guide. I'm using these rivets too (punched by hand) but I hadn't been brave enough yet to try them under components.</p>
<p><a href="http://blog.hodgepig.org/articles/000039-bn4/index.html">http://blog.hodgepig.org/articles/000039-bn4/index.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cross-Platform Builds by Chris</title>
		<link>http://www.makestuff.eu/wordpress/?p=811&#038;cpage=1#comment-3753</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Mon, 14 Jun 2010 22:18:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.makestuff.eu/wordpress/?p=811#comment-3753</guid>
		<description>Hi Dean,

Yup, I will definitely upgrade. The project I used as an example for describing this build stuff was [[http://www.makestuff.eu/wordpress/?page_id=817][a JTAG dongle implemented on an AT90USB162]]. At the time, LUFA/091223 was quite recent, but time, tide and Dean Camera wait for no man...

Chris</description>
		<content:encoded><![CDATA[<p>Hi Dean,</p>
<p>Yup, I will definitely upgrade. The project I used as an example for describing this build stuff was <a href="http://www.makestuff.eu/wordpress/?page_id=817">a JTAG dongle implemented on an AT90USB162</a>. At the time, LUFA/091223 was quite recent, but time, tide and Dean Camera wait for no man...</p>
<p>Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cross-Platform Builds by Dean Camera</title>
		<link>http://www.makestuff.eu/wordpress/?p=811&#038;cpage=1#comment-3734</link>
		<dc:creator>Dean Camera</dc:creator>
		<pubDate>Mon, 14 Jun 2010 13:43:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.makestuff.eu/wordpress/?p=811#comment-3734</guid>
		<description>Great stuff, but I hope you switch over to a newer LUFA distribution than 091223. The latest releases carry many more fixes, which may benefit you with your applications.

- Dean</description>
		<content:encoded><![CDATA[<p>Great stuff, but I hope you switch over to a newer LUFA distribution than 091223. The latest releases carry many more fixes, which may benefit you with your applications.</p>
<p>- Dean</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on UMDKv1 by Chris</title>
		<link>http://www.makestuff.eu/wordpress/?page_id=398&#038;cpage=1#comment-1472</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Sun, 20 Dec 2009 01:27:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.makestuff.eu/wordpress/?page_id=398#comment-1472</guid>
		<description>Hi Joel, let me know if you decide to make it and if you make any improvements.

I am still working on v2. It&#039;s taking a long time, but I&#039;m learning a lot along the way which I guess is the point. I will definitely post the design here when it&#039;s ready.</description>
		<content:encoded><![CDATA[<p>Hi Joel, let me know if you decide to make it and if you make any improvements.</p>
<p>I am still working on v2. It's taking a long time, but I'm learning a lot along the way which I guess is the point. I will definitely post the design here when it's ready.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
