Objective Development Forums

Oh also btw, the hidtool is hardcoded as well at 128 bytes. So you may want to look at that C code, because even if you were successful and only storing and sending back less than 128 bytes to the hidtool, it will "pad" it out anyway. Also keep in mind the smallest amount you can send and/...

I took a look at it myself and unfortunately can't see any other place to change it. Sorry I couldn't help but at least you know someone is also blind to what needs to be changed. I was told somewhere else that the data packets in this type of HID transfer are 64 bytes. So maybe you are looking for ...

Could my issue have anything to do with this setting in the usbconfig.h file? My current circuit doesn't have a crystal at all so I can't really test this and set it to 1. Based on the CRC checks is this the mechanism that is used at the host end to validate that the data was received? Is so is ther...

I have the hid-data example working fine when using the included command line testing tool called hidtool. However, I am using a Java library for communication with a HID http://code.google.com/p/javahidapi/ . I have used this successfully before on a project I created in Arduino using a Teensy 2.0 ...

Thanks for the reply but I am not using a crystal in the circuit. After burning up a few more chips I figured out that I needed to changed the fuse setting. The notes in the Makefile say this (see below), but for the ATTiny85 apparently you need to make the low fuse 0xe1 NOT 0xef as the excerpt show...

I am using the latest 2012-12 stock hid-data example. Since I am using a attiny85 chip I changed these settings in the usbconfig.h file: #define USB_CFG_IOPORTNAME B // was D #define USB_CFG_DMINUS_BIT 1 // was 4 #define USB_CFG_DPLUS_BIT 2 In the Makefile I changed these lines: DEVICE = attiny85 F_...