Objective Development Forums

Hi, I just downloaded HIDkeys, got it working on a USBasp stick (with fewer keys), and came up with this modification to generate distinct key events when you release the button. So you get 1-17 when pressed, 18-34 when released (in the keyReport array). So when I pressed a certain button, it types ...

The main issue is that you make your code incompatible with older versions of GCC. Personally I've found the cost of using the older macro to be trivial in terms of clarity and finding bugs. It's not like this new approach magically makes functions work with pointers to flash, as a pointer to flash ...

The licensing page is probably the place to go. Look at the source code to see whatever you're using V-USB. If usbdrv/ is in there, you almost certainly need to follow the licensing terms above. Note that the GPL doesn't prevent you from selling a product commercially as long as you make the full so...

I've used the LC Technology USBASP V2.0 for almost everything and it's worked very well. I'm on Ubuntu 12.04 and use avrdude as the host software. I have a handful of these as they are great for putting projects on as well, since they have all the hardware needed for V-USB. Get two and use one to pr...

Have you got a pin floating in your device? That could make it very sensitive to touching things.

I used that version successfully on an atmega8 at 12MHz (reprogrammed a USBasp). I notice that I switched to the most current usbdrv, not sure if that was necessary. I'm on Ubuntu 12.04 and I used something like this to test, with the device's TX and RX connected together for a loopback test: # Conf...

At least with avr-gcc 4.5.3, I think I was able to silence the optimizer warnings by initializing a variable with itself, e.g.char c = c;. Too bad there are so many snags to inlining assembly, as otherwise it could be possible to get more optimal code by using just C rather than mixing it with assem...

I think for reliable detection of the presence of a USB host you'd have to do this: 0) For enumeration 1) Wait for reset (long SE0). If reset times out, quit bootloader 2) After that, wait for n keepalive pulses (short SE0). If reset times out, quit bootloader All of this will take at least 500ms i...

Looking at the tiny schematic on HIDKeys' page, it says PD1 is TX. usbdrv includes optional debugging output over TX. If you don't need it, then I see no reason why it can't be used for an extra key.

You could have the USB Vcc connected (via a resistor perhaps) to an input pin that you poll or whatever in your normal program. If you detect that USB is connected, reset and run the bootloader. You could set the bootloader entry condition as a watchdog reset and then trigger that in your program. /...

Can you just set them as out variables? That would force the compiler to give them registers and let it know that you're modifying them.

There shouldn't be any bouncing, as that's an artifact of mechanical switches. You may be thinking of ringing, but that's much more mild than switch bounce, and shouldn't get near logic thresholds so shouldn't affect the digital data. As I understand it, usbPoll() detects reset by one of the USB lin...

Lots of hardware vendors work around the 100mA limit by simply providing a Y-cable with two USB plugs, which allows the device to draw up to 200mA. Y-cables are prohibited by the USB spec : Use of a 'Y' cable (a cable with two A-plugs) is prohibited on any USB peripheral. If a USB peripheral requir...

Actually not so much call overhead, but richer information to the optimizer about exactly what registers are modified. It could probably also be written to let the compiler assign all the registers it uses.

I couldn't find that variable in several of the 2008 versions. From the comment, it looks more like it's just trying to emphasize that static objects in C are initialized to 0 if no initializer is present. In other versions there's a local static for calling a user-defined reset handler only once, a...