Objective Development Forums

If Windows complains about a malfunctioning device, there's most likely a very fundamental problem. Your postings suggest that you have checked the supply voltage and that the device is actually running at the external crystal clock, not internal RC oscillator. Since the circuit is very simple, ther...

Please contact me through the AVR support form. I have a boot loader which is based on HID and should therefore be easier to compile on Windows. It's just not released to the public yet...

Sorry for the delay, I don't check the forum too often.

Any resistive humidity sensor should work. I have used conrad.com (Austrian site, but others should have them, too) order number 156545 and 182630. Both should work.

The spec demands a relatively tight tolerance, but in practice the value does not matter too much. The messages you see indicate that the host sees ONLY the pull-up resistor. There seems to be no (useful) communication with the device at all. Are you sure your AVR is running on external clock and no...

CDC or HID, Windows attaches a class driver to the device in both cases. In order to run avrdebug, you would have to attach a second (device specific) driver, in this case the libusb driver. I don't know Windows driver development well enough to tell how this can be done. I have not tried it, though...

The LE33 is even better from the USB perspective. We decided for the LE35 because the higher supply voltage allows higher clock rates. This is not so much of a problem with modern AVRs. You should compile the driver for bus-power because the device CAN draw power from the bus. In my opinion, you can...

Don't know, it depends on the clock speed and instruction set of the processor.

Look at the developer article (linked from AVR-USB's main page) for optimization ideas...

If you want to control inputs and outputs from a host application, you should make a HID which is neither a keyboard nor a mouse. Look at the "Automator" example. HIDs which are neither keyboard nor mouse are more or less ignored by the operating system and the application can use read/wri...

Don't know whether avrdebug will run on Windows, since it uses libusb for connecting to a HID compliant device. This could result in a driver conflict. Any Windows experts out there? We need to attach two applications to the same device, one using the HID interface, the other plain control transfers...

If you know the device, you don't need to decode the HID descriptor because you know it. Only if you want to build a general driver (e.g. for joysticks, not only your particular joystick) you need to parse the descriptor. In this case I'd recommend using the operating system's functions, if there ar...

Please see the function usbGetStringAscii() in the file sensord.c of the RemoveSensor project. This function reads a string descriptor in Unicode and converts it to ASCII. If you want to read the HID report descriptor, you don't need the ASCII conversion, but you (probably) need to interpret the str...

Thanks for that hint and thanks for testing the patch with large devices!

We'll include it in the next release of AVR-Doper.

AVR-Doper is not compatible with devices larger than 128 kB. The ISP protocol we have implemented only supports 16 bit word addresses. If you know how to extend this protocol, please provide a patch. See the file isp.c in AVR-Doper's firmware source code and search for "stkAddress". This y...

For an example which uses an interrupt-in endpoint, see RemoteSensor. For an example with the full set of endpoints, see Osamu Tamura's AVR-CDC or our AVR-Doper. I usually base my code on libusb because it offers the same API on all platforms. If your application is Mac only, you can use the Mac spe...

As far as I know, the debugWire protocol has not been published. It's therefore hard to implement an Open Source debugWire adapter.

Please correct me if I'm wrong!