Objective Development Forums

I think (would have to check the source to be sure), the 20 cycles were for an older version. The current release may allow longer latencies even at 12 MHz.

Yes, AVR-Doper ships with the latest library (as the version indicates).

If you want just AVR-USB, please download PowerSwitch. We prefer to ship a working example because that saves a lot of questions about how the library should be used.

The statement in usbdrv.h is for the worst case of the 12 MHz module. Timing is more relaxed if you switch to 16.5 MHz. Therefore the discrepancy.

Please also note that you need the most recent version (2007-08-07) of AVR-USB. Older versions had the interrupt vector hardcoded in the assembler modules.

The logic signals look perfectly OK on the first glance. When you look at the clock signal (SCI), you can see the end of a byte at the two short pulses. You can also see delays (when SCI does not change level) which indicate that the AVR processes an interrupt, most likely a USB interrupt. The data ...

I don't think that you need a logic analyzer. You can easily slow down the clocks in hvsp.c/hvspExecute() by inserting delays. I had no problem flashing a Tiny45 with avrdude so far. Either you have a newer chip revision which introduces an incompatibility or you experience some kind of hardware pro...

For real keyboard features (such as multiple keys pressed), please look at the C64 keyboard in the projects section. The code published there is capable to do that (among other things).

AVR-USB can't do full speed, only low speed. However, if you implement the same functionality (bulk endpoints) in low speed, most operating systems accept them as if it were full speed. I don't see how you can implement a mass storage device as HID, though, without custom drivers. As far as I know, ...

I guess you compiled the wrong file for the assembler module. Please enter usbdrvasm.S in your project makefile, not one of the specific files. This file contains the usbCrc16Append() function. If you just want to evaluate the size, download PowerSwitch. If you define the TEST_DRIVER_SIZE macro, it ...

Yes, the relative branch range is exceeded by one instruction if all endpoints are enabled (as it is required for AVR-Doper). You can fix this by moving the code block around handleIn3: #if USB_CFG_HAVE_INTRIN_ENDPOINT && USB_CFG_HAVE_INTRIN_ENDPOINT3 handleIn3: lds cnt, usbTxLen3 ;[43] sbrc...

Thanks for your updates!

You can't run EasyLogger on any other device than the ATTiny45 (and similar) because it uses special features of this chip, in particular the high speed I/O clock PLL. This allows the Tiny45 to run at 16.5 MHz from the internal RC oscillator. The AT90S2313 does not even have an internal RC oscillato...

I've completely overlooked that... PD1 is not a good choice if you compile with debugging enabled or if you otherwise enable the UART transmitter.

If you can ensure that the UART transmitter is off, the driver should work with PD1.

Sorry, I've somehow overlooked your posting... Regarding the first question: If the device stops working after some hours, it probably had a RESET due to EMI, brownout or whatever. If the host does not detect this RESET, it won't re-enumerate the device and the device-ID won't match. There are two w...

Sorry, but then I'm out of ideas...

Since the firmware has been tested very well, I would suspect that there is something wrong in the circuit...