Objective Development Forums

I'm not saying that the clock on your target device is too slow. It's the ISP clock which is probably too slow. You can configure the ISP clock either via the "-B" option to avrdude, through the STK500 programmer or simply with the "Slow SCK" jumper. My first guess would be that ...

The relevant lines here are: tk500v2_command(): unknown status 0x80 avrdud: stk500v2_paged_write: write command failed Status code 0x80 means "command timed out". Did you set the jumper for low speed programming ("Slow SCK" in circuit diagram)? This jumper currently reduces the I...

If you use AVR-Doper in serial emulation mode, you should not need any patches for avrdude. A binary is included with WinAVR. To get very verbose debug information with avrdude, use option "-v" multiple times. I don't know how debug info can be obtained from the STK500 command line program...

This may be due to the somewhat unreliable operation of bulk endpoints. Osamu Tamura maintains a list of hardware/operating system combinations which work or don't work with bulk endpoints. And he has some hints how to improve things. See his project at m. Other than that I can recommend avrdude. If...

If you want to connect a memory stick to your AVR: This can't be done because AVR-USB implements the device side only, not a host. If you want to implement a memory stick: This can't be done either, because AVR-USB is a low speed implementation only and low speed devices are not allowed to use bulk ...

Just because it works with usbtiny does not mean that the wiring is OK. The wiring must match your settings in usbconfig.h and these may differ from the usbtiny settings. In order to see debug info, you must connect the Tx pin through an inverting level converter (such as the MAX232) to the Rx pin o...

The most recent version is always in the PowerSwitch project. This is the most basic example.

The version of AVRUSB which was available when usbtiny was written had a timing bug in the USB ID assignment. This bug has been fixed several versions ago.

If you get the "device not accepting address" error, there is no USB communication at all. The "new low speed USB device" message means only that the 1.5 k pull-up resistor was detected. This may mean almost anything. Good candidates are ⋅ Fuse bits not set for external...

Regarding an assembler module for 16 MHz: Maybe there's a skilled assembler programmer in the arduino community who could do it? We may provide such a module in the long run, but don't expect it within the next couple of months. AVR-USB needs only little CPU resources, unless you implement a bulk en...

In principle, it should be possible to use AVR-USB on this board. A couple of issues must be solved, though: (1) Clock frequency: Our driver is built exclusively for 12 MHz. You must either swap the crystal for a 12 MHz type OR rewrite the assembler module and insert NOPs to ensure the same timing. ...

No, the schematics should be OK.

Another idea: Have you set the fuse bits of the AVR correctly? Make sure that it is clocked with the external crystal (which MUST be 12 MHz), not the internal RC oscillator.

This indicates a very fundamental problem. Only the pull-up resistor on D- is detected, no other communication succeeds.

I therefore suspect that you have a hardware problem. Have you checked wiring? And are you sure that you use zener diodes on D+ and D- or a 3.3V regulator for the supply?

Did you know that the USB Implementers Forum (http://www.usb.org) offers an application which creates HID descriptors? I can't find it right now, but it must be somewhere in the Downloads area of the Developer section.

Yes, it is possible. However, you'll need your own host-side driver. Implementing the printer device class requires at least one bulk endpoint which is not supported by low speed USB devices. If you write your own host-side driver, you can choose a protocol based on control- and interrupt-endpoints ...