Objective Development Forums

no, sorry your USB device descriptor config. Normaaly at the top of the main.c file, shows your Interface Descriptors and endpoints...

in your usbFunctionWrite, it seems data[0] is the field bmRequestType of the USB device request sent by the host and not the actual data to be transfered after the data stage transaction. Correct, I'm leaving that up to you to figure out. Your problem may be how you set up the pipes. Can you post y...

When you download the v-usb code it comes with an example that demonstrates this in a command prompt. I wrote some code using PID. This is the set up. unsigned usbFunctionSetup(uchar data[8]) { usbRequest_t *rq = (void *)data; usbMsgPtr = reportBuffer; if((rq->bmRequestType & USBRQ_TYPE_MASK) ==...

The pins are identical, the only code changes out of make are the timers. If you dont use timers your good to go. also the usb diodes have to be 1/2 watt 1/4 will not work. Not sure if that is the same for the AVR-Doper but it is for the v-usb usb interface.

I knew nothing of usb and had very little firmware programming experience when I started on v-usb. I only needed two things, 1) example code 2) this form.

Ok, got it! Thx for that summary. Good luck on the 8mhz!

Trying to follow along here? I'm wondering if this would be an effective way to cheat the fact that windows uses 8 -10 ms to take its polls on an interrupt transfer. Or am I way off here.

I'm not aware of a limitation or fixed current in v-usb but make sure to use the USB_CFG_MAX_BUS_POWE define in the usb device descriptor as well or also make the needed change.

atmega 8 and 128 are indeed a bit different. the bootloader start address for the 128 is 0x3800 (this is counted in "words") or in "bytes" (2x) its 0x7000.

so when you set the bootloader start address it's 0x7000.

Look at http://www.raphnet.net/electronique/sne ... dex_en.php ( source at bottom of page )
He made an adapter that changes the reportDescriptor based on a variable. Depending on what the condition is, it leads a new descriptor. This maybe what you are after.

You can not transfer that much data in one go but of course you can do it by chunks in interrupt transfers. while (!usbInterruptIsReady()){usbPoll(); } usbSetInterrupt( reportBuffer, 8 ); while (!usbInterruptIsReady()){usbPoll(); } usbSetInterrupt((void *)&reportBuffer + 8, 8 ); while (!usbInter...

I'm not sure what you want to know? There are a few composite examples around that is how I figure it out.

No that is in prog mem I think. You would be better off with a dual device layout and figure out how to switch via vendor ( using software) or a hardware switch.

what's funny about that is I had that same misunderstanding.
http://www.avrfreaks.net/index.php?name ... bootloader
Guess who helped me?

Though I completely over looked that.

You know I meant to bring that up, do you really need that much flash? The 168 is a very rock solid chip and easy to find without pico power. I have had great success with my 328's thus far. I never used a second bypass capacitor like that. Assuming its also near the mcu that good enough. I do put 2...