<?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 on: Benito: My first at90USB162 project.</title>
	<atom:link href="http://www.osx-avr.org/dorkbot/blogfeurigbenito_my_first_at90usb162_project/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.osx-avr.org/dorkbot/blogfeurigbenito_my_first_at90usb162_project/</link>
	<description>I am pretty certain that Apple Hates Developers. I am almost positive they despise embedded developers.</description>
	<lastBuildDate>Wed, 14 Jul 2010 16:04:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: paul</title>
		<link>http://www.osx-avr.org/dorkbot/blogfeurigbenito_my_first_at90usb162_project/comment-page-1/#comment-184</link>
		<dc:creator>paul</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/osx-avr/sortme/blogfeurigbenito_my_first_at90usb162_project/#comment-184</guid>
		<description>You should really locate C3 right next to pins 3 and 4, with direct, short traces.    There&#039;s really no reason not to, since there&#039;s plenty of room under the crystal.  Or better yet, put another capacitor there.  The value doesn&#039;t matter, 0.01 uF with short traces is a LOT more effective that 1 uF on the other side of the board.

Virtually all the current consumed by the chip is via those two pins, and it&#039;s all high speed current pulses.  Locating the cap on the other side of the board makes all that high frequency current travel though a pretty horrific loop since the Vdd trace runs around the right edge of the board and the primary ground return is back up and slightly to the left (on the top side).

Atmel recommends a 10uF capacitance capacitor on the Vbus line (section 19.3.3, Design Guidelines, page 187).  That&#039;s mainly because of worry over poor power quality from the PC and the high voltage spike during dynamic disconnect (due to current still flowing in the inductive lines inside the USB cable).  The FTDI chip suggests a series inductor, which is great for protecting your device against the spike, but totally goes against the letter and spirit of the USB spec, where both host and device and supposed to put low ESL capacitance on the bus to share the burden of suppressing that spike.

Single layer boards are difficult, and it&#039;s pretty impressive you got it all on there.  Sometimes it&#039;s just not possible to do good decoupling on a single layer board, but in this case (assuming you&#039;re only going to use 1 cap), you can easily put it right next to pins 3 &amp; 4 where it will do the most good.</description>
		<content:encoded><![CDATA[<p>You should really locate C3 right next to pins 3 and 4, with direct, short traces.    There&#8217;s really no reason not to, since there&#8217;s plenty of room under the crystal.  Or better yet, put another capacitor there.  The value doesn&#8217;t matter, 0.01 uF with short traces is a LOT more effective that 1 uF on the other side of the board.</p>
<p>Virtually all the current consumed by the chip is via those two pins, and it&#8217;s all high speed current pulses.  Locating the cap on the other side of the board makes all that high frequency current travel though a pretty horrific loop since the Vdd trace runs around the right edge of the board and the primary ground return is back up and slightly to the left (on the top side).</p>
<p>Atmel recommends a 10uF capacitance capacitor on the Vbus line (section 19.3.3, Design Guidelines, page 187).  That&#8217;s mainly because of worry over poor power quality from the PC and the high voltage spike during dynamic disconnect (due to current still flowing in the inductive lines inside the USB cable).  The FTDI chip suggests a series inductor, which is great for protecting your device against the spike, but totally goes against the letter and spirit of the USB spec, where both host and device and supposed to put low ESL capacitance on the bus to share the burden of suppressing that spike.</p>
<p>Single layer boards are difficult, and it&#8217;s pretty impressive you got it all on there.  Sometimes it&#8217;s just not possible to do good decoupling on a single layer board, but in this case (assuming you&#8217;re only going to use 1 cap), you can easily put it right next to pins 3 &#038; 4 where it will do the most good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ax</title>
		<link>http://www.osx-avr.org/dorkbot/blogfeurigbenito_my_first_at90usb162_project/comment-page-1/#comment-185</link>
		<dc:creator>ax</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/osx-avr/sortme/blogfeurigbenito_my_first_at90usb162_project/#comment-185</guid>
		<description>I am running Ubuntu, I installed the Ubuntu packages for binutils-avr and gcc-avr but had to install avr-libc from source because (at least at this time) Ubuntu doesn&#039;t have a package for avr-libc-1.6.2.  I installed avr-libc-1.6.2 with prefix /usr/ because I couldn&#039;t figure out how to use it from /usr/local/.

I did run into the problem where the linker doesn&#039;t find crtusb162.o, but on my platform it is looking in avr5/

so what I did was:
cd /usr/avr/lib/avr5/
sudo ln -s ../avr3/crtusb162.o

Then the Benito software will build (though my version of avr-size does not take the option --mcu=at90usb162, so I had to change it from:
ELFSIZE = $(SIZE) --mcu=$(MCU) --format=avr $(TARGET).elf
to:
ELFSIZE = $(SIZE) --target=elf32-avr $(TARGET).elf

Is this even correct?


Alternatively (with out having to use sudo) you could do:
avr-gcc -dumpspecs &gt; /tmp/specs
then substitute:
mmcu=at90usb162 mmcu=avr5
with:
mmcu=at90usb162 mmcu=avr3
(I use vim :%s/mmcu=at90usb162 mmcu=avr5/mmcu=at90usb162 mmcu=avr3)

Then edit the CC target in your Makefile to be
CC = avr-gcc -specs=/tmp/specs

Then you should be able to build.

(maybe you could put it in a better place and use it again later)

Anyways, with these two methods I was able to install the benito firmware onto my device (sudo make program).  Then I did:
cat /dev/urandom &gt; /dev/ttyACM0
and the light lights up!</description>
		<content:encoded><![CDATA[<p>I am running Ubuntu, I installed the Ubuntu packages for binutils-avr and gcc-avr but had to install avr-libc from source because (at least at this time) Ubuntu doesn&#8217;t have a package for avr-libc-1.6.2.  I installed avr-libc-1.6.2 with prefix /usr/ because I couldn&#8217;t figure out how to use it from /usr/local/.</p>
<p>I did run into the problem where the linker doesn&#8217;t find crtusb162.o, but on my platform it is looking in avr5/</p>
<p>so what I did was:<br />
cd /usr/avr/lib/avr5/<br />
sudo ln -s ../avr3/crtusb162.o</p>
<p>Then the Benito software will build (though my version of avr-size does not take the option &#8211;mcu=at90usb162, so I had to change it from:<br />
ELFSIZE = $(SIZE) &#8211;mcu=$(MCU) &#8211;format=avr $(TARGET).elf<br />
to:<br />
ELFSIZE = $(SIZE) &#8211;target=elf32-avr $(TARGET).elf</p>
<p>Is this even correct?</p>
<p>Alternatively (with out having to use sudo) you could do:<br />
avr-gcc -dumpspecs > /tmp/specs<br />
then substitute:<br />
mmcu=at90usb162 mmcu=avr5<br />
with:<br />
mmcu=at90usb162 mmcu=avr3<br />
(I use vim :%s/mmcu=at90usb162 mmcu=avr5/mmcu=at90usb162 mmcu=avr3)</p>
<p>Then edit the CC target in your Makefile to be<br />
CC = avr-gcc -specs=/tmp/specs</p>
<p>Then you should be able to build.</p>
<p>(maybe you could put it in a better place and use it again later)</p>
<p>Anyways, with these two methods I was able to install the benito firmware onto my device (sudo make program).  Then I did:<br />
cat /dev/urandom > /dev/ttyACM0<br />
and the light lights up!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: apollo21</title>
		<link>http://www.osx-avr.org/dorkbot/blogfeurigbenito_my_first_at90usb162_project/comment-page-1/#comment-186</link>
		<dc:creator>apollo21</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/osx-avr/sortme/blogfeurigbenito_my_first_at90usb162_project/#comment-186</guid>
		<description>I have &quot;AT90USB162&quot; and &quot;AT90USB647&quot;.
I want to use &quot;AT90USB162&quot; for &quot;ISP&quot; and &quot;JTAG&quot;.
I want to use &quot;AT90USB647&quot; for &quot;Dragon&quot;, but do you have the document?
How do you write in those firm ware?

[[Image:A test board&#124;left&#124;100x75px&#124;]]</description>
		<content:encoded><![CDATA[<p>I have &#8220;AT90USB162&#8243; and &#8220;AT90USB647&#8243;.<br />
I want to use &#8220;AT90USB162&#8243; for &#8220;ISP&#8221; and &#8220;JTAG&#8221;.<br />
I want to use &#8220;AT90USB647&#8243; for &#8220;Dragon&#8221;, but do you have the document?<br />
How do you write in those firm ware?</p>
<p>[[Image:A test board|left|100x75px|]]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: apollo21</title>
		<link>http://www.osx-avr.org/dorkbot/blogfeurigbenito_my_first_at90usb162_project/comment-page-1/#comment-187</link>
		<dc:creator>apollo21</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/osx-avr/sortme/blogfeurigbenito_my_first_at90usb162_project/#comment-187</guid>
		<description>As for Schematic which I watched, &quot;Benito board rev 5&quot; frequency is not clear.
I supposed it to be &quot;8MHz&quot;.
I have holdings of &quot;only &quot;12MHZ&quot; and 16MHz&quot; unfortunately.
I intended I exchanged frequency in &quot;Avrstudio4&quot;, and to compile it, but was not able to find the method.
I want &quot;five Benito board rev Firmware_12MHz&quot;.
Is it difficult?</description>
		<content:encoded><![CDATA[<p>As for Schematic which I watched, &#8220;Benito board rev 5&#8243; frequency is not clear.<br />
I supposed it to be &#8220;8MHz&#8221;.<br />
I have holdings of &#8220;only &#8220;12MHZ&#8221; and 16MHz&#8221; unfortunately.<br />
I intended I exchanged frequency in &#8220;Avrstudio4&#8243;, and to compile it, but was not able to find the method.<br />
I want &#8220;five Benito board rev Firmware_12MHz&#8221;.<br />
Is it difficult?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: apollo21</title>
		<link>http://www.osx-avr.org/dorkbot/blogfeurigbenito_my_first_at90usb162_project/comment-page-1/#comment-188</link>
		<dc:creator>apollo21</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/osx-avr/sortme/blogfeurigbenito_my_first_at90usb162_project/#comment-188</guid>
		<description>I confirmed that AT90USB162 worked in &quot;8MHZ&quot; and &quot;16MHZ&quot; and &quot;12MHZ&quot; did not work.
I supposed that the voltage was right in reading it not having JTAG and HVPP, the voltage of HVSP that I made the trial of the pin arrangement and applied a pin arrangement as follows.
I can use 2-pin elsewhere when I use an oscillator in substitution for a crystal.[[Image:New pin arrangement&#124;left&#124;87x100px&#124;]]</description>
		<content:encoded><![CDATA[<p>I confirmed that AT90USB162 worked in &#8220;8MHZ&#8221; and &#8220;16MHZ&#8221; and &#8220;12MHZ&#8221; did not work.<br />
I supposed that the voltage was right in reading it not having JTAG and HVPP, the voltage of HVSP that I made the trial of the pin arrangement and applied a pin arrangement as follows.<br />
I can use 2-pin elsewhere when I use an oscillator in substitution for a crystal.[[Image:New pin arrangement|left|87x100px|]]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: apollo21</title>
		<link>http://www.osx-avr.org/dorkbot/blogfeurigbenito_my_first_at90usb162_project/comment-page-1/#comment-189</link>
		<dc:creator>apollo21</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/osx-avr/sortme/blogfeurigbenito_my_first_at90usb162_project/#comment-189</guid>
		<description>Furthermore, a signal turned over and shared &quot;RST_CTL&quot; with &quot;SS_RST&quot;, and &quot;RST_HZ_CTL reversed a signal, too&quot; and saved Schematic and put up speed more.
[[Image:A voltage control circuit.&#124;left&#124;100x63px&#124;]]</description>
		<content:encoded><![CDATA[<p>Furthermore, a signal turned over and shared &#8220;RST_CTL&#8221; with &#8220;SS_RST&#8221;, and &#8220;RST_HZ_CTL reversed a signal, too&#8221; and saved Schematic and put up speed more.<br />
[[Image:A voltage control circuit.|left|100x63px|]]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: feurig</title>
		<link>http://www.osx-avr.org/dorkbot/blogfeurigbenito_my_first_at90usb162_project/comment-page-1/#comment-190</link>
		<dc:creator>feurig</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/osx-avr/sortme/blogfeurigbenito_my_first_at90usb162_project/#comment-190</guid>
		<description>Because the chips built in dfu will work with 8 and 16, and I thought I read somewhere that 12 would work but I haven&#039;t tested that.</description>
		<content:encoded><![CDATA[<p>Because the chips built in dfu will work with 8 and 16, and I thought I read somewhere that 12 would work but I haven&#8217;t tested that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mrbatu</title>
		<link>http://www.osx-avr.org/dorkbot/blogfeurigbenito_my_first_at90usb162_project/comment-page-1/#comment-191</link>
		<dc:creator>mrbatu</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/osx-avr/sortme/blogfeurigbenito_my_first_at90usb162_project/#comment-191</guid>
		<description>I&#039;m unable to download the project files including the at90usb.lbr eagle library. Is there someone who can help and send me this file?

Thanks in advance.</description>
		<content:encoded><![CDATA[<p>I&#8217;m unable to download the project files including the at90usb.lbr eagle library. Is there someone who can help and send me this file?</p>
<p>Thanks in advance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: feurig</title>
		<link>http://www.osx-avr.org/dorkbot/blogfeurigbenito_my_first_at90usb162_project/comment-page-1/#comment-192</link>
		<dc:creator>feurig</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/osx-avr/sortme/blogfeurigbenito_my_first_at90usb162_project/#comment-192</guid>
		<description>After some experimentation and realizing that my 3 v circuit didnt work I found that I had better results with a 16mhz crystal. All benitos built out by me since november have 16mhz crystals.</description>
		<content:encoded><![CDATA[<p>After some experimentation and realizing that my 3 v circuit didnt work I found that I had better results with a 16mhz crystal. All benitos built out by me since november have 16mhz crystals.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: feurig</title>
		<link>http://www.osx-avr.org/dorkbot/blogfeurigbenito_my_first_at90usb162_project/comment-page-1/#comment-193</link>
		<dc:creator>feurig</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/osx-avr/sortme/blogfeurigbenito_my_first_at90usb162_project/#comment-193</guid>
		<description>I recently added a teensy++ entry and also a part for the 32u4 so I will reupload them shortly.</description>
		<content:encoded><![CDATA[<p>I recently added a teensy++ entry and also a part for the 32u4 so I will reupload them shortly.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

