Objective Development Forums

Did you set a configuration and claim the interface? Otherwise you can't use any endpoints other than 0 with libusb.

You need to declare all Arduino interrupts with __attribute__((interrupt)) so that they can be interrupted by USB traffic. The timer0 ISR is not well optimized, BTW, which makes the problem worse. And much of the Arduino code contains cli() sections, some of them long enough to cause problems with U...

The semantics are different for interrupt/bulk endpoints. There is no usbFunctionReadIn(). You need to call usbSetInterrupt*() and check for buffer space with usbInterruptIsReady*().

Just remove the "-lusb" from Makefile.windows. It is not required.

I just came across this... Want to mention one thing: The first time Elektor missed the citation, it was not the author's fault. It's probably the same here.

Legally, they are not required to cite AVR-USB, as long as the code is published under GPL.

It's not a question of USB 1 or 2, it's a question of the chipset. Some USB chipsets accept voltages outside the specified range, others don't. Older chipsets accept 5 V levels on D+ and D-, most newer chipsets get outside their common mode range.

usbtool is an example included with the driver download.

If you want a real-world GUI application, have a look at the Automator example.

You may also have a look at USBaspLoader.

A boot loader is a short program which sits at the end of the controller's flash memory and takes control after Reset. The boot loader waits for commands via USB and programs the rest of the flash memory.

Please post more info, e.g. the error messages you get.

This is most likely a voltage level problem. Please check the voltage level on D- in idle mode.

Make sure that C code in any of the headers (and includes of headers with C code) are in an #ifndef __ASSEMBLER__. The assembler module includes some of the header files, but the assembler can't understand C syntax, of course.

Is this on Windows? If you use Windows, you need libusb-win32 installed (the filter driver!).

Please check your boot loader init and boot loader condition code. This code determines how long the boot loader is active and whether it becomes active at reset.

Do you get an error for setting the configuration and claiming the interface? You can't use the interrupt endpoint without claiming the interface.

See the RemoteSensor example for how the interrupt endpoint can be used.

If it works with some computers and not with others, it's most likely a problem with the zener diodes. Either they are not built-in, or they are not low power types or have the wrong threshold voltage. AVR-Doper does not support AT89 chips. Don't know whether your source has modified the code, though.