Objective Development Forums

I don't know what "view channels" are, but there are other joystick examples, see m There are the SNES/NES Gamepad adapter, 3DP-Vert, USBJoy and the N64 adapter. The definitive reference is the USB "HID Usage Tables" document available from usb.org. It contains examples for a Joy...

I suppose you mean Raphael's Gamepad controller at

http://www.raphnet.net/electronique/sne ... dex_en.php

I have never built this thing myself because I don't have any old gamepads or joysticks, so I can't comment. Sorry...

Don't know, but the previous release (20060125) should be a good candidate. Maybe you can find more info in the change log of the project.

I prefer gcc 3 because I'm used to its behavior. I also suspect that it's more efficient in general on the AVR platform.

AVR-USB "weights" between 1.3 and 2 k, depending on the options you choose. It should easily fit into the remaining space of even an ATMega8 after subtracting the boot loader. Regarding performance: Whether you can do anything besides USB depends on your USB configuration. If you use bulk ...

We have released a new version of AVR-USB today which solves at least the cyrstal frequency issue: This version can be configured to run off a 12 MHz or 16 MHz crystal clock or a 16.5 MHz RC oscillator clock. The internal RC oscillator option is particularly interesting for 8 pin devices such as the...

This is because the latest WinAVR packages contain gcc version 4 while we use version 3 to prepare the package.

AVR-USB has been optimized for gcc version 3. It's therefore not too surprising that gcc version 4 generates slightly bigger code.

Receive and transmit data are sent through different endpoints. Receive data is transferred through a bulk-in endpoint. Your example suggests that this bulk-in endpoint stalls when you set the baud rate. Windows hosts stop polling bulk-in endpoints when an error occurs, e.g. when the device does not...

If you are sure that you have no bug in your baud rate setting code, then one possible problem might be data toggling on the USB side. When the data stream is reset, it must be initialized to either DATA0 or DATA1 (don't know which, please look at the code for a definitive answer). It is possible th...

If you want to start a re-enumeration "the correct way", you must be able to deactivate the 1.5k pull-up resistor. If it's connected to a port pin instead of the positive supply, just disconnect it for several 100 milliseconds. If your pull-up is wired directly to the positive supply, you ...

The HIDKeys project has a Makefile target "fuse". This target sets the fuse values to: # Fuse high byte: # 0xc9 = 1 1 0 0 1 0 0 1 <-- BOOTRST (boot reset vector at 0x0000) # ^ ^ ^ ^ ^ ^ ^------ BOOTSZ0 # | | | | | +-------- BOOTSZ1 # | | | | + --------- EESAVE (don't preserve E...

Yes, the poll interval time should be long enough. Regarding code readability: Yes, usbtiny is more readable since it has much less #ifdefs and other optional stuff. But all those features make AVR-USB more powerful. You can implement applications with up to 4 endpoints, such as AVR-CDC. AVR-CDC is ...

This is a problem with interrupt latency. If the USB interrupt is blocked for too long, USB packets are lost causing the host to stall the device. The problem occurs much more likely with higher baud rates. Have you tried the latest version of the driver as it ships with PowerSwitch? We could slight...

I'm glad to read that it works now! Although it's interesting that the old driver did not work with usbFunctionWrite(). I know about no bug which caused usbFunctionWrite() to fail in any previous versions. Maybe your extensions moved the RAM layout around and the alignment requirements for the USB r...

This is very likely a hardware voltage levels problem. Did you insert low power zener diodes at D+ and D- or add a voltage regulator?

Some computers tolerate 5 V levels, others don't.