Objective Development Forums

This question is not specific to AVR-USB, it's a general gcc question. I've found the following with a web search (can't remember where, though): What registers are used by the C compiler? Data types: char is 8 bits, int is 16 bits, long is 32 bits, long long is 64 bits, float and double are 32 bits...

With this code, you'll not only run into troubles with AVR-USB, you will also get hit by the watchdog. I don't know what your rxChar_poll() routine looks like, but I suspect that it busy-waits for a character to arrive on the UART. Since it may take a long time until 12 bytes are received, your main...

Thanks, iphi, for answering these questions. I should mention that we already have a Makefile target for programming the fuses. Type

make fuse_tiny2313

to set the fuse bits to the correct values.

OK. I've removed the URL from the Readme file.

Yes, I should have mentioned that. In order to save space, I've removed the initial USB disconnect.

A non-existing link has the same value as a broken link, so I think I'll leave the file as it is just out of laziness.

BTW: It's not us who support Delphi, we just re-distribute a contributed package. Thanks to everyone who supports the project by contributing code!

Please see the example projects such as e.g. Automator. The circuit diagram is in PDF format, you should have a viewer for that.

I think this minimal main() should suffice, but we have not tested this recently. It is primarily to check the size of the compiled binary.

I don't have a PowerSwitch hardware available for testing now, so I can't really confirm whether or not it should work with TEST_DRIVER_SIZE defined.

Thanks a lot! I have downloaded the package. It should be on our main server tomorrow morning.

I'd like to update the Delphi project on our site, but since I have no idea about Delphi, I'm not sure what to do with the new LibUSB.

Can you please download our package, make and test a new package with the new LibUSB and mail me the resulting zip file?

Thanks in advance!

The action timers are for timed on/off pulses on the outputs. The USB driver does not need any timer interrupts.

If the device is not recognized after your change, you must have broken something in the main module. Maybe it crashes and the driver is therefore unable to respond to requests...

We at Objective Development don't have any plans to support chips with USB hardware. But you are free to re-use any parts of our code under GPL and we would be happy to set a link to any related library.

The app note is correct: All transfers are initiated by the host. However, from an application logic point of view, you don't care how initiates the transfer. For interrupt endpoints, all polling is done by the host controller hardware or the driver. The application on the host does not have to worr...

In order to send notifications to the host, you need an Interrupt In endpoint. See our RemoteSensor example. I don't know how to handle these on Windows, though, if you need a callback called. Maybe you need a separate thread for that if you use libusb. You could also implement a HID device and send...

I think OSC would be the most versatile solution, if Traktor supports it. You could still make your device HID and write a daemon which connects to it and sends OSC events. That's a bit more installation and configuration work since you need a separate daemon, but you could easily control other soft...