Objective Development Forums

I see that you send some data with txChar_poll() and then wait for a reply with rxChar_poll(). I don't have the USB spec in front of me, but I remember that there is a time limit for processing messages. This time limit might be 50 ms. Please also note that the host polls the USB aggressively while ...

If the PID is your own, there is no limitation on what you may do with it.

If you have control over the manufacturer string's domain, you are responsible for it. If you allow others to use it, that's your (potential) problem, and that of those people who use it. It might still be a good idea to get your own Product ID in this case because you don't have to worry about stri...

It looks as if the host were not polling the interrupt endpoint. Can you try to debug this with a USB sniffer? Maybe toggle the LED when a new ADC value is captured?

The technical description is correct. You can send control-in messages of up to 254 bytes. If your out-data fits into a setup package (one or two integers), then you can do the same as PowerSwitch and parse the data from setup. Otherwise you need a control-out transfer and implment usbFunctionWrite(...

You need to install libusb-win32 and attach it to RemoteSensor's IDs. I'm not a Windows expert, so I don't have much experience with that, but the libusb-win32 package contains some instructions.

When I make software for Windows, I usually prefer HID because it saves me the extra driver.

Yes, RemoteSensor needs its own driver since it's not based on HID. HID is somewhat limited, you can't do generic control requests. All data must be transferred in fixed size structures which must be described to the operating system by means of Report Descriptors. In spite of the limits, HID is sui...

Another quick note: If you have the Mega88 with the "V" suffix, it's only specified up to 10 MHz and therefore not suitable for AVR-USB.

In this case I would recommend that you use an interrupt-in endpoint just to notify the host if new data is available and use control in and out transfers to read and write the actual data. The same technology is used in RemoteSensor. When new data arrives, a one byte interrupt is sent to the host t...

Der AVR-Doper macht sowas Ähnliches im CDC-Modus. Zum Betriebssystem meldet er sich als serielle Schnittstelle an und interpretiert das STK500 Protokoll selbst. Den Protokoll-Parser muesstest Du natuerlich neu schreiben.

Please check out AVR-CDC or AVR-Doper. Both use Bulk endpoints for I/O, but they are the same as interrupt endpoints except that they are polled much faster.

Please check the AVR-Doper project. It has an option to compile for the ATMega88.

Does this version of WinAVR use the Makefile or does it control the build process by itself? If it uses the Makefile, it depends on the rules in the Makefile whether a .hex file is created or not.

What you want is definitely not possible with AVR-USB and the AVR in general. I would recommend that you use a controller with USB Host and USB Device hardware. With both of these you can implement a USB bridge and do any protocol filtering you like. However, you can't use standard drivers and creat...

Regarding the original question whether the controller can send data to the host or only receive data from the host: On the physical layer, all data transfers are initiated by the host. If the controller should transfer data to the host, it must be polled in regular intervals. On a logical layer, US...