Objective Development Forums

It's defined in asmcommon.inc: ;---------------------------------------------------------------------------- ; Processing of received packet (numbers in brackets are cycles after center of SE0) ;---------------------------------------------------------------------------- ;This is the only non-error ...

Welp, from usbdrv.h: USB_PUBLIC void usbSetInterrupt(uchar *data, uchar len); /* This function sets the message which will be sent during the next interrupt * IN transfer. The message is copied to an internal buffer and must not exceed * a length of 8 bytes. The message may be 0 bytes long just to i...

See USB 2.0 specs, chap. 9.6.7 String Descriptors. The Laguage Identifiers document is located here

You are welcome For development check out the Teensy boards. Be aware that his code examples don't implement a full USB state machine in the interrupt, they are good for learning tho. As an alternative take a look at the Atmel USBkey board. Atmel has example source code for the USB chips online, you...

Well, w/o knowing the details of what you need I really don't know (you may get away w/ a AT90USB82, as low as $1.80 @ 100 quantity). Just making sure you're aware of native USB AVRs The main problems w/ V-USB are 1. USB 1.1 (slow) and 2. it needs a guaranteed low ISR latency. Depending on your devi...

For pro-development I'd suggest to check out the Atmel chips that come w/ a USB module like the Atmega16U4.

Why ? WinAVR and AVR Studio are free, professional high performance tools.

On a 2nd thought -- the SOFs also go away if the device is suspended, that could be a problem. Am afraid that the only really safe way to detect a disconnect is monitoring the VBus signal.

Hm, that's probably because V-USB doesn't detect the disconnect. Forgot about that In order for this to work you could enable the SOF counter (see USB_COUT_SOF in usbconfig-prototype.h) and monitor the SOFs. If they stop comming you are disconnected and could manually reset the driver with this func...

Christian, could you flag this for inclusion w/ the next release please ?

I tested the variable usbConfiguration in the main loop. It doesnt change at all. If i disconnect or re-connect the device , it remains the same. Is there something i did wrong ? No, the driver has a bug (oversight actually), usbConfiguration doesn't get cleared if a reset happens on the bus: Chris...

You can reconnect automatically if you connect the D- pull up resistor to an I/O pin instead of Vcc. See the USB_CFG_PULLUP_* macros in usbconfig.h . To reconnect, issue usbDeviceDisconnect(), wait 1-2s, then issue a usbDeviceConnect().

Usually the last thing the host does during enumeration is setting the configuration. You can check if the variable usbConfiguration is not zero for an indication if the device is plugged in and enumerated. Christian, usbConfiguration should be cleared during a reset condition (usbPoll(), where usbD...

Try this (see usbPoll()):

Use


to disable the interrupt and


to re-enable it.