Objective Development Forums

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:

Atmega168 device -> usb cable -> atmega168(2) -> a deice not usb.


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:

example snes to saturn

snes -> Atmega168 device -> usb cable -> atmega168(2) -> saturn

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.

Can anyone comment on the complexity, if or if not possible, thoughts?

Although it should be possible to use USB between two AVRs, I really doubt that you can save complexity this way.

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.

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.