Objective Development Forums

The first error message mentioned, when you compile the command line tool, is a misconfiguration of your gcc. The message says that it fails to execute gcc. Regarding the firmware: You include usbdrv.c in your main code and define USB_PUBLIC to static, right? I'm not sure about the first message sin...

Regarding CPU load: The load is always above 90%, not only if data is transferred. That's because USB is a host-driven bus and the host polls the device for data when there is nothing else to transfer. But I think that it SHOULD work. It's the task of the low level driver to enforce "no bulk en...

You can post in English or German, but you can expect more answers to English posts since more users speak English. It's also more polite to others who don't speak German. I have no experience how reliable a mass storage low speed device would be. The latest version of the driver can implement enoug...

Your link referred to AVR-USB's index page, not a particular project. As far as I know, there is no project on our site (or linked form our site) which uses the ATMega32. If you use the Mega32, you need to update some configurations and probably fuse values. For a beginner, I would recommend that yo...

You can probably even use Igor's programmer. If the programmer accepts a Intel-Hex file, just send your own project's hex file instead of Igor's. If you use avrdude: You probably don't need to edit anything. It comes with a configuration for all known parallel port programmers, you just need to know...

Here are my screenshots from the scope for D+ (channel 1) and D- (channel 2). You can see that the reply from the device is with 5V levels since I omitted the zener diodes. Even with the zeners you should see which is the host's request and which the device reply by the voltage levels. http://at.obd...

I'm beginning to mix up threads. My reply should have gone to another thread where USB works when connected to INT0 but not with any other interrupt. If I remember correctly, it does not work regardless of the interrupt in your case. If the interrupt pin is "open", then it's normal that it...

It's a relatively new feature that you can choose a different interrupt than INT0, older versions of AVR-USB have the interrupt service routine hardcoded to INT0. Which version of the driver do you use? In particular, is the ISR label defined as "USB_INTR_VECTOR:" in usbdrvasm*.S?

It looks as if the modified code does not change anything. If you have a storage scope or a logic analyzer to caputure the failing communication, I'd be very curious to analyze it.

ff stands for Reset. It is output as long as the reset condition is detected on the USB. This indicates that at least the I/O pins can be read correctly.

Did you check the disassembler output to see whether the interrupt table has been compiled correctly? And did you try a different interrupt?

OK, so let's assume that the fuse values are correct. The debug output is at 19200 bps by default. Since only the TxD pin is used, there is no flow control. I don't know what settings you need for Hyperterminal, though, if you just want to receive data. If you interface to a PC, you need an inverter...

You need to implement usbFunctionWrite() and return -1 in usbFunctionSetup() for a particular request. When you send this request from the host, the driver will call usbFunctionWrite() in chunks of 8 bytes until all data is received. See usbdrv.h for a description of usbFunctionWrite() and usbFuncti...

If the device fails enumeration, USB does not work (probably not at all). You get a "not recognized" even if you only connect the 1.5k pull-up resistor. The ATMega32 should work without any changes, at least at the first glance. I have never used this chip myself, though. It definitely nee...

At least you have a solution. If somebody suggests a way how the #if can be made compatible with both, GCC/avr-libc and IAR-CC, I'd be happy to add it.

That's good. If INT0 works, it should be something simple. Your USB configuration looks OK. Only one slight thing: You use ISC30 and ISC31 instead of ISC70 and ISC71, but that does not matter since both constant sets are defined to the same values. If you are unsure about USB_INTR_VECTOR, run the re...