Objective Development Forums

Two methods:

1. create an interface for each device (see viewtopic.php?f=8&t=2911)
2. define two reports in a single HID report descriptor (there should be examples of that in the reference/public projects)

I am trying to implement two different interface in a single device, Not using ReportID, i.e. there should be two different interface descriptor each containing HID and endpoint descriptor, each HID descriptor has its Report descriptor(say one for keyboard with boot capabilities and the other is mo...

Looks good, make sure you setup usbconfig.h accordingly. BTW, you will need a 1.5K pullup resistor on D- to V+ or, alternatively, a port pin. From the usbconfig.h file: /* ---------------------------- Hardware Config ---------------------------- */ #define USB_CFG_IOPORTNAME D /* This is the port wh...

V-USB is very well documented actually. You may want to take a closer look at the v-usb distribution package..

That were physically the same Z-diodes and the same USB port tho. Odd, I better recheck that.

Most self-powered devices seem to request 2mA (smallest value possible) via config descriptor for that reason it seems.

2k2 worked for me w/ mega8 & tinyX61 devices. I tested a bit, 6k8 still works w/ m8, 2k2 is pretty much max. for the tinys (trying to minimize power use.. )

i think maybe i dont need a far pointer address Correct. You only need the far access w/ devices that have more than 64k of FLASH memory. In other words: If a device doesn't have the RAMPZ (extended Z-pointer) register you don't need far access. #if defined(RAMPZ) [use far routines] #else [use norm...

Check out Replacing ATmega8 by ATmega88 , Migrating between ATmega48, ATmega88 and ATmega168 , and Migrating from ATmega48/88 and ATmega48P/88P to ATmega48PA/88PA . Also, IIRC the electrical specs for the I/O pins are different betw. the 8 and 88. If you use Z-diodes on D+/D-, they HAVE to be 3V6/<=...

i have read usbdrv have to be LINKED to the base-project, but i cant do that since im working on codevisionAVR.. i tried to "include" it and correct it to fit codevision, but i still got many errors when i compile it... any comments? You could use AVR Studio/WinAVR to build the boot loade...

Grendel wrote:Check out the community HID projects for references as well (esp. the HIDKeys).

Check out this project. More can be found here.

Well, first, the 500uA are really only 300uA -- a host has 15k pull-downs on D- & D+, you get a 16.5k base load to Vterm; 200uA. That is new to me. What I don't understand is why they specify 500uA for the device if the host consumes some of that. Side effect of USB 2.0 HS -- USB 2.0 spec, chap...

Well, first, the 500uA are really only 300uA -- a host has 15k pull-downs on D- & D+, you get a 16.5k base load to Vterm; 200uA. If you want timely wakeup you should only use Standby (note that INT0 can only be used as a level ISR) -- ~150uA if you also shut everything else down (BOD, AC, ADC .....

I use a 2k2 resistor to 5V, works fine, uses less power. Shouldn't be a problem since you need a self powered device to met the specs for suspend. Leakage over the Zeneres is probably neglegtable if you use 3V6 ones.

Most (non OTG) hosts will do nothing if you draw 5-10mA during suspend tho.