Objective Development Forums

The debug interface is not registered as a serial interface with the operating system, you need to compile avrdebug for it.

It should be possible to tune the AVR-Doper firmware for this hardware. Have not looked closely, but it seems to be very similar to USBasp. See the USBasp section in hardware.h.

That's easily possible. See AVR-Doper as an example. In main.c of the firmware, have a look at the report descriptor (usbDescriptorHidReport). It defines various feature reports of different sizes.

It depends on your report descriptors. You can choose any block size you like (as long as you don't exceed the limits of V-USB or the host side drivers), provided that you describe the block in the report descriptor.

It's in the "examples" directory of the current driver package found at http://www.obdev.at/products/vusb/download.html

You can use HID for bidirectional data transfer. However, since you must use feature reports (set and get), you are limited to fixed size data blocks. See the hid-data example, it uses HID feature reports to send and receive data.

PowerSwitch happens to be (or have been) the reference design simply because it was the first project every done with the driver. We needed such a device to switch the supply for a couple of servers. We now recommend to start with the examples which ship with the driver. They require much less hardw...

EEPROM writes may take quite a while (milliseconds!). Make sure that you don't wait for the write to complete while interrupts are disabled.

Yes. For every non-trivial configuration, you need to create your own descriptor. And in order to use more than just control transfers on endpoint 0, you must set a configuration and interface with libusb.

I have a low power USB design which uses the following tricks to reduce battery consumption: (1) The design uses a 32 kHz crystal and synchronizes the RC oscillator to it. (2) When USB is connected, the main clock frequency is synchronized to 12.8 MHz, without USB, we use 1 MHz. (3) Every 1 s interv...

Regarding Vista: I have not tried it, but I see no reason why it should fail.

LSPx are connections to the outside world. LSP1 and 2 are the mains connection, LSP3...10 are switched outputs.

Relays are K1...K8.

You need to add the USB related files (assembler and C) to your project. Instead of copy/pasteing the contents of main.c, simply add main.c to your project and remove firmware.c. Also, please make sure that defines like F_CPU and options like the -I options for gcc are set correctly. See the Makefil...

Sorry, but this would take more time to debug. Please make sure you understand the format of the report data and check the values in USB Snoopy. You should send reports for key down and key up.

I spotted at least one problem: You defined USB_CFG_HID_REPORT_DESCRIPTOR_LENGTH in main.c and not in usbconfig.h. The constant is therefore not known in usbdrv.c where it is needed.

If you really want to define it in main.c, please do it before including usbdrv.c.

I'm afraid no. Simon prefers this type of schematic.