Objective Development Forums

Somehow building a commandline tool for the mac with an AVR compiler doesn't strike me as a good idea. I don't own a mac, but you'll need to install & use gcc for the mac for the commandline tools.

Then learn a bit about C before you touch micro-controllers.

Implement V-USB in your project instead of using the UART from the AVR chip.

USB_PUBLIC void usbPoll(void); /* This function must be called at regular intervals from the main loop. * Maximum delay between calls is somewhat less than 50ms (USB timeout for * accepting a Setup message). Otherwise the device will not be recognized. * Please note that debug outputs through the U...

You're going to hit yourself in the head:

Maybe you need to send 3 bytes instead of 1?

Take a look at how the arduino serial driver does it, it also keeps a buffer for data, you could do the same thing. And this is more a general C/Arduino question so the avr-freaks forums might serve you better.

Small note, you're better off not using the Arduino libraries if you want to be in control of your AVR. The avr-libc library provides quite a few functions to help you on your way. And using hardware registers is a lot faster then using the Arduino libraries. (avr-libc is included and used by the ar...

My USB cable is somewhat homebrew; abused an old standard cable (fullspeed max), soldered wires to pins for breadboarding. Could this be the problem? If there is too much interference (because of unshielded pins), the "illegal byte sequence" reported by wireshark makes sense. I had an old...

The AU/PU are different packaging types (see section 29 of the ATMega8A datasheet "ordering information") I also have a few ATMega8 chips that are not working with V-USB. But I'm overclocking the AVR to 20Mhz. So I think my problems are related to the 20Mhz (as 16Mhz is max according to th...

USB has data 8 bytes per packet. The usbdrvasm20.inc say "106.666667 cycles per byte" so it's at least 800 cycles busy with the interrupt, and this doesn't even include the start/end/stuffing. This also matches the 1.5Mbit/s low speed USB spec. Which means 8 bytes will take 0.043ms while 5...

Well, you could do the same as tinyUSB, and just ignore the license issue (the IR example contains the Atmel vendor ID). Or you could leave the vendor/device ID out so people have to give it on the command line during compile. At which point you don't violate the license, but the user will on compil...

If it's for personal hobby use, I say go wild. Nobody is going to sue you for using the a vendor/product ID in your own house. They won't even know. If you are going to sell devices, then you'll have a problem. Looks like the LIRC vendor/product ID you are using is the one from: m (after some search...

Each request you do to the USB device has a "value" parameter, which can be filled with anything you want. You could use it as an address so you can do multiple requests. (the usbRequest_t recieves this value in wValue)

I think "USB_RX_USER_HOOK" is what you are looking for. Once the device has been found by the PC the PC will keep communicating with it, so if you put a timeout after the USB_RX_USER_HOOK you can detect if the PC is running and knows the device is there.

First, you should work on your English. Your posts hardly make any sense at all.

Commenting out code because it doesn't compile and then complain it doesn't work. And you are not surprised that it won't work?