|

»

»

Hid mouse example (vusb)

View: New views

5 Messages — Rating Filter: Alert me

	Hid mouse example (vusb) by ali hosseini-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Hi All problems to drive hid-mouse in windows I don’t know why this example (HID mouse from www.obdev.at ) doesn’t work at all for me .I’ve tried it one hundred times but actually I think I don’t know which files must be added to compile hid mouse driver successfully . So could you send your own hid mouse project for me to fix this problem with the complete files such as project and usbdriv files because I’m not familiar very much with winavr and vusb with some more descriptions. Thank you for your attention _______________________________________________ AVR-chat mailing list AVR-chat@... http://lists.nongnu.org/mailman/listinfo/avr-chat
	ATtiny48 avrdude config entry by Scott Shaw-3 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. Since there was no avrdude.conf entry I made my own. I based it on the ATtiny88 file and made changes as necessary. I'm not positive that everything is correct, but I have been using it for a few days now without any problems. Here are the differences between the 48 and 88. Also, I will add in the full t48 config entry after. Thanks. -Scott ****************************DIFFERENCES*************** 2c2 < # ATtiny48 --- > # ATtiny88 6,7c6,7 < id = "t48"; < desc = "attiny48"; --- > id = "t88"; > desc = "attiny88"; 13c13 < stk500_devcode = 0x59; --- > stk500_devcode = 0x73; 15c15 < signature = 0x1e 0x92 0x09; --- > signature = 0x1e 0x93 0x11; 92c92 < size = 4096; --- > size = 8192; 94c94 < num_pages = 64; --- > num_pages = 128; 157c157 < "x x x x x x x x x x x x x x x o"; --- > "x x x x x x x x x x x x x o o o"; 168c168 < "0 0 0 0 0 0 0 0 x x x x x x o o"; --- > "x x x x x x x x x x o o o o o o"; 170,171c170,171 < write = "1 0 1 0 1 1 0 0 1 1 1 0 0 0 0 0", < "0 0 0 0 0 0 0 0 x x x x x x i i"; --- > write = "1 0 1 0 1 1 0 0 1 1 1 x x x x x", > "x x x x x x x x 1 1 i i i i i i"; 176c176 < read = "0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0", --- > read = "0 0 1 1 1 0 0 0 0 0 0 x x x x x", 182,183c182,183 < read = "0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0", < "0 0 0 0 0 0 a1 a0 o o o o o o o o"; --- > read = "0 0 1 1 0 0 0 0 0 0 0 x x x x x", > "x x x x x x a1 a0 o o o o o o o o"; **************avrdude config entry************ #------------------------------------------------------------ # ATtiny48 #------------------------------------------------------------ part id = "t48"; desc = "attiny48"; has_debugwire = yes; flash_instr = 0xB6, 0x01, 0x11; eeprom_instr = 0xBD, 0xF2, 0xBD, 0xE1, 0xBB, 0xCF, 0xB4, 0x00, 0xBE, 0x01, 0xB6, 0x01, 0xBC, 0x00, 0xBB, 0xBF, 0x99, 0xF9, 0xBB, 0xAF; stk500_devcode = 0x59; # avr910_devcode = 0x; signature = 0x1e 0x92 0x09; pagel = 0xd7; bs2 = 0xc2; chip_erase_delay = 9000; pgm_enable = "1 0 1 0 1 1 0 0 0 1 0 1 0 0 1 1", "x x x x x x x x x x x x x x x x"; chip_erase = "1 0 1 0 1 1 0 0 1 0 0 x x x x x", "x x x x x x x x x x x x x x x x"; timeout = 200; stabdelay = 100; cmdexedelay = 25; synchloops = 32; bytedelay = 0; pollindex = 3; pollvalue = 0x53; predelay = 1; postdelay = 1; pollmethod = 1; pp_controlstack = 0x0E, 0x1E, 0x0F, 0x1F, 0x2E, 0x3E, 0x2F, 0x3F, 0x4E, 0x5E, 0x4F, 0x5F, 0x6E, 0x7E, 0x6F, 0x7F, 0x66, 0x76, 0x67, 0x77, 0x6A, 0x7A, 0x6B, 0x7B, 0xBE, 0xFD, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00; hventerstabdelay = 100; progmodedelay = 0; latchcycles = 5; togglevtg = 1; poweroffdelay = 15; resetdelayms = 1; resetdelayus = 0; hvleavestabdelay = 15; resetdelay = 15; chiperasepulsewidth = 0; chiperasepolltimeout = 10; programfusepulsewidth = 0; programfusepolltimeout = 5; programlockpulsewidth = 0; programlockpolltimeout = 5; memory "eeprom" paged = no; page_size = 4; size = 64; min_write_delay = 3600; max_write_delay = 3600; readback_p1 = 0xff; readback_p2 = 0xff; read = " 1 0 1 0 0 0 0 0", " 0 0 0 x x x x x", " x a6 a5 a4 a3 a2 a1 a0", " o o o o o o o o"; write = " 1 1 0 0 0 0 0 0", " 0 0 0 x x x x x", " x a6 a5 a4 a3 a2 a1 a0", " i i i i i i i i"; loadpage_lo = " 1 1 0 0 0 0 0 1", " 0 0 0 0 0 0 0 0", " 0 0 0 0 0 0 a1 a0", " i i i i i i i i"; writepage = " 1 1 0 0 0 0 1 0", " 0 0 x x x x x x", " x a6 a5 a4 a3 a2 0 0", " x x x x x x x x"; mode = 0x41; delay = 5; blocksize = 4; readsize = 64; ; memory "flash" paged = yes; size = 4096; page_size = 64; num_pages = 64; min_write_delay = 4500; max_write_delay = 4500; readback_p1 = 0xff; readback_p2 = 0xff; read_lo = " 0 0 1 0 0 0 0 0", " 0 0 0 0 a11 a10 a9 a8", " a7 a6 a5 a4 a3 a2 a1 a0", " o o o o o o o o"; read_hi = " 0 0 1 0 1 0 0 0", " 0 0 0 0 a11 a10 a9 a8", " a7 a6 a5 a4 a3 a2 a1 a0", " o o o o o o o o"; loadpage_lo = " 0 1 0 0 0 0 0 0", " 0 0 0 x x x x x", " x x x a4 a3 a2 a1 a0", " i i i i i i i i"; loadpage_hi = " 0 1 0 0 1 0 0 0", " 0 0 0 x x x x x", " x x x a4 a3 a2 a1 a0", " i i i i i i i i"; writepage = " 0 1 0 0 1 1 0 0", " 0 0 0 0 a11 a10 a9 a8", " a7 a6 a5 x x x x x", " x x x x x x x x"; mode = 0x41; delay = 6; blocksize = 64; readsize = 256; ; memory "lfuse" size = 1; min_write_delay = 4500; max_write_delay = 4500; read = "0 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0", "x x x x x x x x o o o o o o o o"; write = "1 0 1 0 1 1 0 0 1 0 1 0 0 0 0 0", "x x x x x x x x i i i i i i i i"; ; memory "hfuse" size = 1; min_write_delay = 4500; max_write_delay = 4500; read = "0 1 0 1 1 0 0 0 0 0 0 0 1 0 0 0", "x x x x x x x x o o o o o o o o"; write = "1 0 1 0 1 1 0 0 1 0 1 0 1 0 0 0", "x x x x x x x x i i i i i i i i"; ; memory "efuse" size = 1; min_write_delay = 4500; max_write_delay = 4500; read = "0 1 0 1 0 0 0 0 0 0 0 0 1 0 0 0", "x x x x x x x x x x x x x x x o"; write = "1 0 1 0 1 1 0 0 1 0 1 0 0 1 0 0", "x x x x x x x x x x x x x x x i"; ; memory "lock" size = 1; min_write_delay = 4500; max_write_delay = 4500; read = "0 1 0 1 1 0 0 0 0 0 0 0 0 0 0 0", "0 0 0 0 0 0 0 0 x x x x x x o o"; write = "1 0 1 0 1 1 0 0 1 1 1 0 0 0 0 0", "0 0 0 0 0 0 0 0 x x x x x x i i"; ; memory "calibration" size = 1; read = "0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0", "0 0 0 0 0 0 0 0 o o o o o o o o"; ; memory "signature" size = 3; read = "0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0", "0 0 0 0 0 0 a1 a0 o o o o o o o o"; ; ; Get free photo software from Windows Live Click here. _______________________________________________ AVR-chat mailing list AVR-chat@... http://lists.nongnu.org/mailman/listinfo/avr-chat
	RE: ATtiny48 avrdude config entry by Weddington, Eric :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message > -----Original Message----- > From: avr-chat-bounces+eric.weddington=atmel.com@... > [mailto:avr-chat-bounces+eric.weddington=atmel.com@...] > On Behalf Of Scott Shaw > Sent: Tuesday, August 04, 2009 6:39 PM > To: avr-chat@... > Subject: [avr-chat] ATtiny48 avrdude config entry > > Since there was no avrdude.conf entry I made my own. I based > it on the ATtiny88 file and made changes as necessary. I'm > not positive that everything is correct, but I have been > using it for a few days now without any problems. Here are > the differences between the 48 and 88. Also, I will add in > the full t48 config entry after. Thanks. Hi Scott, Your help is definitely appreciated, however, here are a few suggestions: - Don't send your avrdude patch to the avr-chat mailing list. The avrdude project resides on Savannah and has it's own mailing list. - Better still, don't send your patch to a mailing list, as emails get lost very quickly. Avrdude has a Patch Tracker, where you can attach your patch and I can guarantee you that the avrdude developers will then eventually get to that patch. See here: <https://savannah.nongnu.org/patch/?group=avrdude> You have to have a Savannah user ID and password to create a new Patch Tracker item. - It's better to use the -u switch when you create a patch. This creates a "unified" form patch, which is much easier to read when evaluating new patches. In general, most open source projects usually prefer to deal with patches created with diff -u (and sometimes other switches as well such as -p for C source code). HTH, Eric Weddington _______________________________________________ AVR-chat mailing list AVR-chat@... http://lists.nongnu.org/mailman/listinfo/avr-chat
	RE: ATtiny48 avrdude config entry by Scott Shaw-3 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. I'll be sure to submit it to the avrdude project on Savannah, I didn't realize that avrdude had a separate mailing list. So what topics are covered on this list? Once I know I'll be sure to contact the appropriate list. Thanks. -Scott > > Hi Scott, > > Your help is definitely appreciated, however, here are a few suggestions: > - Don't send your avrdude patch to the avr-chat mailing list. The avrdude project resides on Savannah and has it's own mailing list. > - Better still, don't send your patch to a mailing list, as emails get lost very quickly. Avrdude has a Patch Tracker, where you can attach your patch and I can guarantee you that the avrdude developers will then eventually get to that patch. See here: > <https://savannah.nongnu.org/patch/?group=avrdude> > You have to have a Savannah user ID and password to create a new Patch Tracker item. > - It's better to use the -u switch when you create a patch. This creates a "unified" form patch, which is much easier to read when evaluating new patches. In general, most open source projects usually prefer to deal with patches created with diff -u (and sometimes other switches as well such as -p for C source code). > > HTH, > Eric Weddington Get free photo software from Windows Live Click here. _______________________________________________ AVR-chat mailing list AVR-chat@... http://lists.nongnu.org/mailman/listinfo/avr-chat
	RE: ATtiny48 avrdude config entry by Weddington, Eric :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message > -----Original Message----- > From: Scott Shaw [mailto:scooterses@...] > Sent: Tuesday, August 04, 2009 8:02 PM > To: Weddington, Eric; avr-chat@... > Subject: RE: [avr-chat] ATtiny48 avrdude config entry > > I'll be sure to submit it to the avrdude project on Savannah, > I didn't realize that avrdude had a separate mailing list. So > what topics are covered on this list? Once I know I'll be > sure to contact the appropriate list. Thanks. > Descriptions of the avr-chat and avr-gcc-list mailing lists are here: <https://savannah.nongnu.org/mail/?group=avr> That should give you an idea of the typical subject matter. Avr-chat is fairly easy-going. The big thing is if you have patches to specific projects, or problems with a specific project, then you'll usually get better responses going to those project's mailing lists. If you have a bug report, than submit an item to the respective Bug Trackers. If you have a patch, then submit them to the respective Patch Trackers, etc. As a developer, it just makes it so much easier to keep track of and to work with volunteers. :-) Thanks, Eric _______________________________________________ AVR-chat mailing list AVR-chat@... http://lists.nongnu.org/mailman/listinfo/avr-chat