Objective Development Forums

It might more be a hardware problem in combination with your laptop. V-USB isn't 100% up to USB spec, but it works in most cases. I had some troubles with my laptop, I made the cables a bit shorter which resolved the problem in my case.

I don't have the schematic at hand. But I only used a few components:
100nF to stabelize VCC
2.2k Ohm pull up from VCC to D-
470 Ohm from D- to INT1
470 Ohm from D+ to INT0
20Mhz XTal with 2x 20pF to ground

Your are right, the HEX file is larger then 2k, because the HEX file is in plain text HEX with extra data ( Intel HEX format ) So this uses about 2bytes in the hex file for each final byte in the AVR flash. The correct way to get the size of the final flash is by using the "avr-size" tool ...

I used the ATMega32A just fine for V-USB (with 5V hardware, no zeners). Just make sure you use the right crystal, and set the fuses right (some "A" parts have different fuse settings then the not "A" variants)

@jamesotron: And his question had nothing to do with avr-gcc. Roman, Most likely MacOS libusb does not ship with "libusb-config" tool. You'll need to edit the Makefile so gcc can find the usb.h file and libusb.so file. Instead of "`libusb-config --cflags`" you'll need to add some...

First, you are using an Arduino, with the Arduino library. Which is like putting a 2 stroke engine in a Ferrari.

Secondly, you are mixing C and C++. You'll need to add around the C header files.

My lastest code can be found at:
http://daid2.mine.nu/~daid/tiny2313_vusb.tgz

It stands at 1206 bytes. You could save a few more bytes by moving more variables to GPIOR (GPIOR0 is used as usbMsgFlags, which saves a 8 bytes, the ATTiny2313 has 3 GPIO registors)

Note, I haven't actually tested this version, so it might not work!

Just reporting back that I got down to 1200 bytes. Which seems to be the 1.2k you where asking for. You can get down to 1400~1300 bytes by removing the mouse code, and not using usbFunctionRead/usbFunctionWrite.
The last 100~200 bytes where gained by a lot of tiny optimizations.

USB enumeration happens as soon as you connect the resistor from D- to VCC. So if you remove the chip you'll still get a enumeration failed error. So if the VID/PID pair isn't found then the chip isn't communicating with the host yet. Which could be one of the following: ⋅ Wrong fuse setti...

Ok (forgetting the fuse settings is my most common error ) I have no experience using the 12Mhz version (I overclock my ATMega8 to 20Mhz) but it should work. First, make sure the device is really running. Your computer will try to enumerate the USB device with just the resistor from VCC to D- (remov...