Objective Development Forums

You force a RESET in the middle of a USB command. This may confuse the host. It would be cleaner to set a global variable so that the main loop does not call wdt_reset(), but still calls usbPoll() until the reset occurs. Other than that: Did you check whether delay(1400000) really generates a long e...

Your problem may have several causes: (1) Make sure that you force a disconnect for at least 250 ms during power-up of the controller. Newer versions of PowerSwitch already do that. (2) Some versions of libusb-win32 crash when Windows goes into sleep mode. The USB interface becomes unusable after th...

If you have some programming knowledge, see the HIDKeys example. You need to modify it so that it sends a sequence of keystrokes instead of one key. See the EasyLogger example for how to send a sequence of key strokes.

Here's the bootloaderconfig.h file I used: #define BOOTLOADER_INIT \ PORTB = 0; \ DDRB = 0; \ PORTC = 0; \ DDRC = 0; \ PORTD = 1 << 4; \ DDRD = (1<<USB_CFG_DMINUS_BIT) | (1<<USB_CFG_DPLUS_BIT);\ uchar i, j = 0; \ while(--j){ /* USB Reset by device only required on Watchd...

Regarding self calibration: It's not possible within the time constraints of the driver to store away a "too slow" or "too fast" bit. The best method would be to watch the 1ms pulses at D- shortly after connecting USB and calibrate with that. Note that the host will try to query ...

It is your responsibility to write a calibration value to the EEPROM. We don't have an algorithm for that yet, but I'm sure you can come up with something.

The PLL is in software only: It executes NOP instructions to get in sync with the sender. The OSCCAL value is not touched for that.

My first guess would be that the oscillator is not calibrated precisely enough or that it's not stable enough. Oscillator stability depends on the stability of the supply voltage.

It turned out that there was a copy/paste bug in the 15 and 16 MHz modules. This bug affected device enumeration depending on the USB timing.

Please get at least version 2008-02-05 of PowerSwitch for the latest release of AVR-USB which fixes this issue.

It turned out that there was a copy/paste bug in the 15 and 16 MHz modules. This bug affected device enumeration depending on the USB timing.

Please get at least version 2008-02-05 of PowerSwitch for the latest release of AVR-USB which fixes this issue.

It turned out that there was a copy/paste bug in the 15 and 16 MHz modules. This bug affected device enumeration depending on the USB timing.

Please get at least version 2008-02-05 of PowerSwitch for the latest release of AVR-USB which fixes this issue.

Can you please mail me the entire project to the avrusb8 at obdev dot at address? I'd like to have a look at the disassembled binary.

10 x 100 Ohm = 1000 Ohm = 1 kOhm
10 x 470 Ohm = 4700 Ohm = 4.7 kOhm

Then take 100pF and multiply the resistor values by 10. The frequency will be a bit lower due to stray capacities, but that's not so relevant.

For an NE555 oscillator, see the application example in the data sheet, e.g. http://www.ortodoxism.ro/datasheets/stm ... s/2182.pdf figure 13.

Choose R1 = 100 Ohm, R2 = 470 Ohm and C = 1 nF and you should be close to 1 MHz.

Yes. I would recommend that you run avrdude with the highest debugging level enabled and look at the communication. May be a wiring problem on the ISP end.