<?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/3114" />

	<title>Objective Development Forums</title>
	
	<link href="https://forums.obdev.at/index.php" />
	<updated>2009-08-12T10:36:07+02:00</updated>

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

		<entry>
		<author><name><![CDATA[christian]]></name></author>
		<updated>2009-08-12T10:36:07+02:00</updated>

		<published>2009-08-12T10:36:07+02:00</published>
		<id>https://forums.obdev.at/viewtopic.php?t=3114&amp;p=10506#p10506</id>
		<link href="https://forums.obdev.at/viewtopic.php?t=3114&amp;p=10506#p10506"/>
		<title type="html"><![CDATA[Re: usb to avr]]></title>

		
		<content type="html" xml:base="https://forums.obdev.at/viewtopic.php?t=3114&amp;p=10506#p10506"><![CDATA[
Although it should be possible to use USB between two AVRs, I really doubt that you can save complexity this way.<br /><br />BTW: V-USB is the device side driver only. There's also a low speed host implementation available for the AVR, see the links section on our site.<br /><br />I would recommend TWI, SPI or UART communication between the two. You could use some of the higher level framework of USB, e.g. the descriptor logic.<p>Statistics: Posted by <a href="https://forums.obdev.at/memberlist.php?mode=viewprofile&amp;u=8">christian</a> — Wed Aug 12, 2009 10:36 am</p><hr />
]]></content>
	</entry>
		<entry>
		<author><name><![CDATA[ulao]]></name></author>
		<updated>2009-08-11T19:15:12+02:00</updated>

		<published>2009-08-11T19:15:12+02:00</published>
		<id>https://forums.obdev.at/viewtopic.php?t=3114&amp;p=10494#p10494</id>
		<link href="https://forums.obdev.at/viewtopic.php?t=3114&amp;p=10494#p10494"/>
		<title type="html"><![CDATA[usb to avr]]></title>

		
		<content type="html" xml:base="https://forums.obdev.at/viewtopic.php?t=3114&amp;p=10494#p10494"><![CDATA[
Yeah I know it sounds a bit weird but here is what I'm pondering. I wan to create an adapter that accepts a usb connection. And processes  out the descriptor data. This is mainly for a HID joystick, but I imagine its the same data that I'm after in any case, keyboard, mice...etc. I want to get this in to an avr. Like so:<br /><br />Atmega168 device -&gt; usb cable -&gt; atmega168(2) -&gt; a deice not usb. <br /><br /><br />The idea here is that I have created a device that accepts 15 types of controllers ( various consoles ), they all talk the same language once they are a usb devices, so now I want to send that to an avr that I can talk to multiple devices. Like so:<br /><br />example snes to saturn<br /><br />snes -&gt; Atmega168 device -&gt; usb cable -&gt; atmega168(2) -&gt; saturn<br /><br />just not sure how a person would create this (2) avr code to read the descriptor data. I know I could create my own language in my first chip and use my own serial out, but I'm running out of room. Also I want to config buttons on the fly.<br /><br />Can anyone comment on the complexity, if or if not possible, thoughts?<p>Statistics: Posted by <a href="https://forums.obdev.at/memberlist.php?mode=viewprofile&amp;u=1281">ulao</a> — Tue Aug 11, 2009 7:15 pm</p><hr />
]]></content>
	</entry>
	</feed>
