<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-gb">
	<link rel="self" type="application/atom+xml" href="https://forums.obdev.at/app.php/feed/topic/8769" />

	<title>Objective Development Forums</title>
	
	<link href="https://forums.obdev.at/index.php" />
	<updated>2013-12-13T13:26:56+02:00</updated>

	<author><name><![CDATA[Objective Development Forums]]></name></author>
	<id>https://forums.obdev.at/app.php/feed/topic/8769</id>

		<entry>
		<author><name><![CDATA[horo]]></name></author>
		<updated>2013-12-13T13:26:56+02:00</updated>

		<published>2013-12-13T13:26:56+02:00</published>
		<id>https://forums.obdev.at/viewtopic.php?t=8769&amp;p=26335#p26335</id>
		<link href="https://forums.obdev.at/viewtopic.php?t=8769&amp;p=26335#p26335"/>
		<title type="html"><![CDATA[Re: V-USB certification non-compliance details]]></title>

		
		<content type="html" xml:base="https://forums.obdev.at/viewtopic.php?t=8769&amp;p=26335#p26335"><![CDATA[
Hi,<br /><br />some more <a href="http://forums.obdev.at/viewtopic.php?f=8&amp;t=2376" class="postlink">facts</a> about non-compliance.<br /><br />Ciao, Martin<p>Statistics: Posted by <a href="https://forums.obdev.at/memberlist.php?mode=viewprofile&amp;u=891">horo</a> — Fri Dec 13, 2013 1:26 pm</p><hr />
]]></content>
	</entry>
		<entry>
		<author><name><![CDATA[blargg]]></name></author>
		<updated>2013-12-11T23:56:25+02:00</updated>

		<published>2013-12-11T23:56:25+02:00</published>
		<id>https://forums.obdev.at/viewtopic.php?t=8769&amp;p=26328#p26328</id>
		<link href="https://forums.obdev.at/viewtopic.php?t=8769&amp;p=26328#p26328"/>
		<title type="html"><![CDATA[Re: V-USB certification non-compliance details]]></title>

		
		<content type="html" xml:base="https://forums.obdev.at/viewtopic.php?t=8769&amp;p=26328#p26328"><![CDATA[
I think at the very least it doesn't do differential reception, where the voltages of the two data lines are compared (which increases noise immunity). I also don't think the CRC of packets is checked and errors reported to the host so it can re-send transparently.<p>Statistics: Posted by <a href="https://forums.obdev.at/memberlist.php?mode=viewprofile&amp;u=20076">blargg</a> — Wed Dec 11, 2013 11:56 pm</p><hr />
]]></content>
	</entry>
		<entry>
		<author><name><![CDATA[suncm]]></name></author>
		<updated>2013-12-11T20:34:45+02:00</updated>

		<published>2013-12-11T20:34:45+02:00</published>
		<id>https://forums.obdev.at/viewtopic.php?t=8769&amp;p=26326#p26326</id>
		<link href="https://forums.obdev.at/viewtopic.php?t=8769&amp;p=26326#p26326"/>
		<title type="html"><![CDATA[V-USB certification non-compliance details]]></title>

		
		<content type="html" xml:base="https://forums.obdev.at/viewtopic.php?t=8769&amp;p=26326#p26326"><![CDATA[
V-USB states that &quot;devices based on V-USB cannot comply to the electrical specifications of the USB standard because the AVR's I/O characteristics don't match the requirements of USB&quot;.<br /><br />Can someone elaborate on this? What specific characteristics of AVR's does the USB certification not agree with? I'm trying to understand why it seems like the only way to make a USB-compliant device is to use a much more powerful MCU with built-in USB communication (I'm currently using the ATTiny series) or one of those expensive FTDI interface chips.<p>Statistics: Posted by <a href="https://forums.obdev.at/memberlist.php?mode=viewprofile&amp;u=19855">suncm</a> — Wed Dec 11, 2013 8:34 pm</p><hr />
]]></content>
	</entry>
	</feed>
