<?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 Frank&#039;s Random Wanderings</title>
	<atom:link href="http://blog.frankvh.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.frankvh.com</link>
	<description>A bunch of random musings, with a leaning towards electronics &#38; computers.</description>
	<lastBuildDate>Thu, 18 Mar 2010 06:37:48 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on AVR Xmega and AVRISP Mk2 by Willie Visagie</title>
		<link>http://blog.frankvh.com/2009/09/22/avr-xmega-and-avrisp-mk2/comment-page-1/#comment-127</link>
		<dc:creator>Willie Visagie</dc:creator>
		<pubDate>Thu, 18 Mar 2010 06:37:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.frankvh.com/?p=127#comment-127</guid>
		<description>It works in eclipse.  Just need to install new usb drivers.  Google it...</description>
		<content:encoded><![CDATA[<p>It works in eclipse.  Just need to install new usb drivers.  Google it&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Atmel Xplain Xmega board Gotchas by Kenneth Scharf</title>
		<link>http://blog.frankvh.com/2009/11/15/atmel-xplain-board/comment-page-1/#comment-123</link>
		<dc:creator>Kenneth Scharf</dc:creator>
		<pubDate>Fri, 26 Feb 2010 16:07:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.frankvh.com/?p=187#comment-123</guid>
		<description>Actually the avrispMKII DOES support the 10 pin cable without an adapter.  Atmel just didn&#039;t supply the cable.  Get or make up a short cable with a 10 pin connector on each end.  Snap open the avrisp (you have to insert a screwdriver into the plastic clamps holding the case together while prying it open with another screwdriver.  It looks hard to do, but it opens easily.  You&#039;ll see that the PC board has BOTH connectors on it.  In the event that they have depopulated the 10 pin connector from the board you&#039;ll have to solder one to the provided pads, however the units I&#039;ve opened up had both connectors installed.</description>
		<content:encoded><![CDATA[<p>Actually the avrispMKII DOES support the 10 pin cable without an adapter.  Atmel just didn&#8217;t supply the cable.  Get or make up a short cable with a 10 pin connector on each end.  Snap open the avrisp (you have to insert a screwdriver into the plastic clamps holding the case together while prying it open with another screwdriver.  It looks hard to do, but it opens easily.  You&#8217;ll see that the PC board has BOTH connectors on it.  In the event that they have depopulated the 10 pin connector from the board you&#8217;ll have to solder one to the provided pads, however the units I&#8217;ve opened up had both connectors installed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on GoDaddy sucks, and a new web host by David</title>
		<link>http://blog.frankvh.com/2009/06/06/hello-world/comment-page-1/#comment-121</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 25 Jan 2010 04:11:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.frankvh.com/?p=1#comment-121</guid>
		<description>Great article im in the domaining buisness and I find this information very useful</description>
		<content:encoded><![CDATA[<p>Great article im in the domaining buisness and I find this information very useful</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Blackfin Fast JPEG Encoding by Steve Howell</title>
		<link>http://blog.frankvh.com/2009/06/09/blackfin-fast-jpeg-encoding/comment-page-1/#comment-117</link>
		<dc:creator>Steve Howell</dc:creator>
		<pubDate>Mon, 04 Jan 2010 16:14:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.frankvh.com/?p=31#comment-117</guid>
		<description>Hi Frank,

Thanks for the very quick reply! I don&#039;t think it&#039;s a 64/32 bit problem. I have 32 bit int&#039;s, 16 bit short&#039;s and 8 bit char&#039;s, as expected by the code. Thanks anyway. I&#039;ll keep investigating.

Steve</description>
		<content:encoded><![CDATA[<p>Hi Frank,</p>
<p>Thanks for the very quick reply! I don&#8217;t think it&#8217;s a 64/32 bit problem. I have 32 bit int&#8217;s, 16 bit short&#8217;s and 8 bit char&#8217;s, as expected by the code. Thanks anyway. I&#8217;ll keep investigating.</p>
<p>Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Blackfin Fast JPEG Encoding by frank</title>
		<link>http://blog.frankvh.com/2009/06/09/blackfin-fast-jpeg-encoding/comment-page-1/#comment-116</link>
		<dc:creator>frank</dc:creator>
		<pubDate>Mon, 04 Jan 2010 16:04:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.frankvh.com/?p=31#comment-116</guid>
		<description>Hi Steve,

Hmm, I don&#039;t know. At one point I had a similar problem to what you&#039;re describing, where the JPG image started out correct but then got messed up. It was due to the assembly language DCT algorithm being used at the time. Switching to the C code DCT function fixed the problem, and I then wrote an assembly version of that C code to make it run faster. Is there any chance this might be a data type problem (eg you&#039;re running on a 64 bit machine when this code perhaps assumes 32 bits) or something like that?  

Good luck!

Frank.</description>
		<content:encoded><![CDATA[<p>Hi Steve,</p>
<p>Hmm, I don&#8217;t know. At one point I had a similar problem to what you&#8217;re describing, where the JPG image started out correct but then got messed up. It was due to the assembly language DCT algorithm being used at the time. Switching to the C code DCT function fixed the problem, and I then wrote an assembly version of that C code to make it run faster. Is there any chance this might be a data type problem (eg you&#8217;re running on a 64 bit machine when this code perhaps assumes 32 bits) or something like that?  </p>
<p>Good luck!</p>
<p>Frank.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Blackfin Fast JPEG Encoding by Steve Howell</title>
		<link>http://blog.frankvh.com/2009/06/09/blackfin-fast-jpeg-encoding/comment-page-1/#comment-115</link>
		<dc:creator>Steve Howell</dc:creator>
		<pubDate>Mon, 04 Jan 2010 15:42:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.frankvh.com/?p=31#comment-115</guid>
		<description>Hi,

I&#039;ve been trying to build and use this jpeg code in a Microsoft Visual C++ project to convert 24 bit RGB images to JPG. I removed the __attribute__ stuff and switched it back to using all the C routines instead of the assembler ones, but I can&#039;t get it to work properly. It seems to produce a JPEG file in which the first few 8x8 blocks of pixels look correct but the rest of the image is corrupted. On quality level 8 the length of the strip of blocks which look right is longer than it is on quality level 1. I don&#039;t suppose you&#039;d have any idea what I might have got wrong?

The only changes I made to the code were:
Remove the __attribute__s.
In &quot;encodeMCU&quot;, called &quot;quantization&quot; instead of &quot;quantization_asm&quot;.
In &quot;DCT&quot;, commented out the part were it just calls &quot;jpegdct&quot; and returns.
In &quot;huffman&quot;, made it call the PUTBITS macro instead of &quot;putbits_asm&quot;.
In &quot;read_rgb24_format&quot;, I changed the &quot;#if 0&quot;s to &quot;#if 1&quot;s and vice versa, this stopping it using &quot;read_rgb_yuv&quot;.

Any help gratefully accepted!

Thanks

Steve Howell</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I&#8217;ve been trying to build and use this jpeg code in a Microsoft Visual C++ project to convert 24 bit RGB images to JPG. I removed the __attribute__ stuff and switched it back to using all the C routines instead of the assembler ones, but I can&#8217;t get it to work properly. It seems to produce a JPEG file in which the first few 8&#215;8 blocks of pixels look correct but the rest of the image is corrupted. On quality level 8 the length of the strip of blocks which look right is longer than it is on quality level 1. I don&#8217;t suppose you&#8217;d have any idea what I might have got wrong?</p>
<p>The only changes I made to the code were:<br />
Remove the __attribute__s.<br />
In &#8220;encodeMCU&#8221;, called &#8220;quantization&#8221; instead of &#8220;quantization_asm&#8221;.<br />
In &#8220;DCT&#8221;, commented out the part were it just calls &#8220;jpegdct&#8221; and returns.<br />
In &#8220;huffman&#8221;, made it call the PUTBITS macro instead of &#8220;putbits_asm&#8221;.<br />
In &#8220;read_rgb24_format&#8221;, I changed the &#8220;#if 0&#8243;s to &#8220;#if 1&#8243;s and vice versa, this stopping it using &#8220;read_rgb_yuv&#8221;.</p>
<p>Any help gratefully accepted!</p>
<p>Thanks</p>
<p>Steve Howell</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Atmel Xplain Xmega board Gotchas by Dean Camera</title>
		<link>http://blog.frankvh.com/2009/11/15/atmel-xplain-board/comment-page-1/#comment-114</link>
		<dc:creator>Dean Camera</dc:creator>
		<pubDate>Tue, 15 Dec 2009 10:18:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.frankvh.com/?p=187#comment-114</guid>
		<description>And another update - I&#039;ve just finished a first revision of an XPLAIN programmer firmware for the onboard AT90USB1287, also located in the LUFA SVN as well as this AVRFreaks thread: http://www.avrfreaks.net/index.php?name=PNphpBB2&amp;file=viewtopic&amp;t=87393. When loaded, it will cause the XPLAIN board to enumerate as an Atmel AVRISP-MKII which (with the latest AVRStudio release) can PDI program the onboard XMEGA.

- Dean</description>
		<content:encoded><![CDATA[<p>And another update &#8211; I&#8217;ve just finished a first revision of an XPLAIN programmer firmware for the onboard AT90USB1287, also located in the LUFA SVN as well as this AVRFreaks thread: <a href="http://www.avrfreaks.net/index.php?name=PNphpBB2&amp;file=viewtopic&amp;t=87393" rel="nofollow">http://www.avrfreaks.net/index.php?name=PNphpBB2&amp;file=viewtopic&amp;t=87393</a>. When loaded, it will cause the XPLAIN board to enumerate as an Atmel AVRISP-MKII which (with the latest AVRStudio release) can PDI program the onboard XMEGA.</p>
<p>- Dean</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Atmel Xplain Xmega board Gotchas by ArnodB</title>
		<link>http://blog.frankvh.com/2009/11/15/atmel-xplain-board/comment-page-1/#comment-113</link>
		<dc:creator>ArnodB</dc:creator>
		<pubDate>Sat, 05 Dec 2009 13:02:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.frankvh.com/?p=187#comment-113</guid>
		<description>&gt; In theory you can reprogram the 1287 via the USB port, using Atmel’s “FLIP” utility
&gt; (available on their website). For me, that didn’t work either, and I really tried hard. No FLIP for me!

Old Rev 1 Xplains didn&#039;t have the necessary bootloader in the 1287. Rev 2 and later ones have it, but the procedure described in AVR1907 to enter the bootloader is incomplete. I have summarized my experience in http://www.avrfreaks.net/index.php?name=PNphpBB2&amp;file=viewtopic&amp;p=645225 I use Ubuntu, but checked that the pushbuttons I added works with FLIP under Windows, too.</description>
		<content:encoded><![CDATA[<p>&gt; In theory you can reprogram the 1287 via the USB port, using Atmel’s “FLIP” utility<br />
&gt; (available on their website). For me, that didn’t work either, and I really tried hard. No FLIP for me!</p>
<p>Old Rev 1 Xplains didn&#8217;t have the necessary bootloader in the 1287. Rev 2 and later ones have it, but the procedure described in AVR1907 to enter the bootloader is incomplete. I have summarized my experience in <a href="http://www.avrfreaks.net/index.php?name=PNphpBB2&amp;file=viewtopic&amp;p=645225" rel="nofollow">http://www.avrfreaks.net/index.php?name=PNphpBB2&amp;file=viewtopic&amp;p=645225</a> I use Ubuntu, but checked that the pushbuttons I added works with FLIP under Windows, too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on GoDaddy sucks, and a new web host by david</title>
		<link>http://blog.frankvh.com/2009/06/06/hello-world/comment-page-1/#comment-112</link>
		<dc:creator>david</dc:creator>
		<pubDate>Thu, 03 Dec 2009 01:12:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.frankvh.com/?p=1#comment-112</guid>
		<description>Wow this really suck I really havent run into any problems yet I guess I&#039;ve been lucky. Atleaset now I have the heads up so when things do start happening thanks..</description>
		<content:encoded><![CDATA[<p>Wow this really suck I really havent run into any problems yet I guess I&#8217;ve been lucky. Atleaset now I have the heads up so when things do start happening thanks..</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Atmel Xplain Xmega board Gotchas by frank</title>
		<link>http://blog.frankvh.com/2009/11/15/atmel-xplain-board/comment-page-1/#comment-111</link>
		<dc:creator>frank</dc:creator>
		<pubDate>Wed, 25 Nov 2009 18:03:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.frankvh.com/?p=187#comment-111</guid>
		<description>That is indeed a good note - thanks! I have updated the post.</description>
		<content:encoded><![CDATA[<p>That is indeed a good note &#8211; thanks! I have updated the post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
