Objective Development Forums

Understanding all of usbconfig-prototype.h may be a bit hard for a newbie. In any case you should know the general architecture, that V-USB drives the USB lines directly and that there is no FT232 involved. Then you should know that USB requires descriptors, what they are good for and what is inside...

Should be possible, of course. But you must be careful with the big device because it may need more than 16 bits for pointers. All of the driver must be in the low 64 kB.

See http://blog.flipwork.nl/?x=entry:entry081009-142605 for an example of a single key keyboard.

Yes, that's the core I meant. Except that you forgot to connect the Vcc line (power supply) from the USB connector to the rest of the circuit. I don't know the company who sells Metaboard. Did not even know that it's available commercially. Regarding Arduino: What makes it an interesting candidate a...

Regarding Metaboard: The advantage are the I/O pins and the breadboard area. It is intended to be used with a boot loader. A boot loader is a kind of built-in programmer, so you flash it via USB instead of connecting an external programmer to some pins. On the other hand, it contains an unnecessary ...

If you want something simple and educational to start with, I'd recommend m instead. The circuit is very easy to build AND you can use it to learn more about electronics. PowerSwitch is not really intended for the electronics newbie because it works with mains voltage. That can be rather dangerous. ...

Note that PowerSwitch ships with a really old version of the driver. It has not been updated since the driver comes in a separate package now (see m). The wiki documentation refers to more recent versions. Regarding USB_ENDPOINT_IN vs. USB_ENDPOINT_OUT in the host side software of PowerSwitch: This ...

Yes, INT0_vect is already there in the repository, it will be published with the next release.

Have you verified the interrupt vector? If SIG_PIN_CHANGE is not defined, the interrupt handler will never be called and there's no compiler/linker warning or error. Please check main.elf with avr-objdump -d main.elf Then check the verctor address for pin change and see whether it contains the jump ...

Yes, this means that the handler is never called. It seems that either the vector address is not correct (you can check this with a disassembler listing of the linked code) or the interrupt is not enabled. Don't know which steps are required to enable a PCINT, I would have to read the data sheet...

No, the driver works with all three, rising edge, falling edge and change triggered interrupt. You should verify whether the interrupt handler is actually called...

See viewtopic.php?f=8&t=1067

Have you checked that bytesRemaining is 16 bit, not 8 bit as in the example? In any case, you don't need to change the logical maximum. that's just the value range of a byte explained to the host side driver. Also, please check whether you use usbRequest->wLength anywhere. Most examples use the low ...

There are two hardware versions. The big one supports HVPP, as far as I know.

You keep the interrupts disabled while you do the busy wait. This way you lock out the driver during the write operation. See bootloadHID for an example where to disable interrupts and where to keep them enabled.

The error message says that the make utility can't find the gcc executable. This is some kind of misconfiguration of your MinGW installation.