gmane.comp.hardware.avr.avrdude.devel http://blog.gmane.org/gmane.comp.hardware.avr.avrdude.devel hourly 1 1901-01-01T00:00+00:00 Gmane http://gmane.org/img/gmane-25t.png http://gmane.org [patch #7538] Add support for AT89S52/51 MCS-51 MPUs http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3256 <pre>Follow-up Comment #2, patch #7538 (project avrdude): Where can I find the preamble in the patch tracker? Should I submit a patch containing further program internal documentation? Will the patch afterwards be applied to the avrdude source with the result that the next release will support AT89S52/51 MCU programming? (I did write "MPUs" in the subject field by mistake) Thanks for your help! _______________________________________________________ Reply to this item at: &lt;http://savannah.nongnu.org/patch/?7538&gt; _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/ </pre> Tobias Kaiser 2012-05-22T21:35:37 Problems with avrdude 5.11+ http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3255 <pre>So, over to the list... Hi All, Here is a quick satatement of the problem. When using avrdude 5.11 or 5.11.1 under Windows XP to program the flash memory on a ATmega328P using either a ponsyser programmer or USBtinyISP programmer it fails verification. Incorrect data is being written to the device. The input and output files are here: http://users.vianet.ca/omegamic/avrdude_test/ test_input.hex is the file being written to the device. dump_ponyser.hex is what got written by the ponyser bit-bang programmer. dump_usbtiny.hex is what got written by the USBtinyISP programmer. Here are some interesting facts: 1) The problem does not occur with avrdude 5.4 (I only have 5.4, 5.11 and 5.11.1 at my disposal, so I do not know which version the problem got introduced) 2) The problem does not occur with a programmer emulating an STK500 (so this maybe protocol related) 3) The problem does not occur on a faster system (I have not yet tested a slower system, but will try to if anyone thinks this might help) 4) The ponyser programmer creates far more errors 5) The errors in each case appear at the begining of a record 6) In the vast majority of the cases, the incorrect data written is the 2nd last byte or last 2 bytes of the previous record Anyone have any ideas? ____________________________ Bill O'Neill Aztec MCU Prototyping www.aztecmcu.com ----- Original Message ----- From: "Joerg Wunsch" &lt;j&lt; at &gt;uriah.heep.sax.de&gt; To: "Bill O'Neill" &lt;bill&lt; at &gt;aztecmcu.com&gt; Sent: Friday, May 18, 2012 3:20 AM Subject: Re: Problems with avrdude 5.11+ </pre> Bill O'Neill 2012-05-19T19:48:38 Re: Include GPIO sysfs patch in next release? http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3254 <pre> Just discovered the job has already been done here: http://svn.dragino.com/openwrt/package/avrdude/ </pre> Benjamin Henrion 2012-05-12T19:41:12 Re: Include GPIO sysfs patch in next release? http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3253 <pre> &gt;&gt; I don't know how it can be auto-probed for, because it targets &gt;&gt; embedded Linux systems. Eric&gt; Well, then are there a finite number of embedded linux systems Eric&gt; that support this feature? Can that information still be captured Eric&gt; in the configuration? No, gpios are a very basic feature - So it is basically infinite. </pre> Peter Korsgaard 2012-05-12T06:55:19 Re: Include GPIO sysfs patch in next release? http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3252 <pre> Well, then are there a finite number of embedded linux systems that support this feature? Can that information still be captured in the configuration? Eric </pre> Weddington, Eric 2012-05-11T22:09:45 Re: Include GPIO sysfs patch in next release? http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3251 <pre> Hi, Joerg&gt; Still, having the code in on a system that could otherwise support the Joerg&gt; feature at all (*) would not hurt those who don't want to use it. Am Joerg&gt; I missing something? It's common practice for AVRDUDE to include all Joerg&gt; programmer handling code that would *potentially* be applicable for a Joerg&gt; particular target system, without requiring the user to include or Joerg&gt; exclude each of them by configure options (as, e.g. OpenOCD is doing). Joerg&gt; (*) I'm not knowledgable enough about *which* Linux systems are Joerg&gt; candidates for it. Every Linux with a recent enough kernel? (Which Joerg&gt; one?) Every Linux that has /sys/class/gpio around? Something else? In concept every Linux system with a gpio driver + sysfs interface. Realisticly seen, this is fairly uncommon on a normal PC system (but very common on embedded-style hw). It's a Linux specific interface, but otherwise doesn't have any special system dependencies as it's just normal file I/O, and doesn't add a lot of bloat. I would say, enable by default for all (Linux) systems. </pre> Peter Korsgaard 2012-05-11T16:08:17 Re: Include GPIO sysfs patch in next release? http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3250 <pre> Sysfs+gpio is in linux since 2.6.28: http://lxr.free-electrons.com/source/Documentation/gpio.txt To my mind, potentially all the openwrt routers with a kernel upper than .28 should be able to work with gpio+sysfs exposure. I have a bunch of them at home, but I need to make update of the avrdure openwrt with the gpio patch to see how it behaves, but avrdude is available as a binary for openwrt since backfire: http://downloads.openwrt.org/backfire/10.03.1/adm5120_router_be/packages/ For now, I would say disable it by default, people who want tge feature will just have to add a ./configure --enable-gpio option. I will try to give a shot to the avrdude+gpio patch against openwrt if I find the time this week-end. -- Benjamin Henrion &lt;bhenrion at ffii.org&gt; FFII Brussels - +32-484-566109 - +32-2-3500762 "In July 2005, after several failed attempts to legalise software patents in Europe, the patent establishment changed its strategy. Instead of explicitly seeking to sanction the patentability of software, they are now seeking to create a central European patent court, which would establish and enforce patentability rules in their favor, without any possibility of correction by competing courts or democratically elected legislators." </pre> Benjamin Henrion 2012-05-11T13:56:36 Re: XMega D support http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3249 <pre> Yes, probably. Well, there might be minor issues, like the AVR Dragon not being able to talk PDI to certain (older) Xmega A devices. </pre> Joerg Wunsch 2012-05-11T13:38:59 Re: Include GPIO sysfs patch in next release? http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3248 <pre> Let's say, it's the major item blocking it. Please re-check the patch against the SVN version. Some things in avrdude.conf have been changed lately (like the programmer type being a string rather than an ID now), I guess the patch needs to be modified in order to adopt these changes. Assuming the documentation is there, and the patch is a smooth drop-in, I can promise to include it into the next release. You might also want to mention it in the NEWS file (which serves as a kind of release notes document). OK, point taken. In that case, users are forced to compiler their own version anyway. This detail wasn't clear to me before. It's probably really a good idea to add a reference to a website in the documentation then which explains the entire setup used in some more detail than AVRDUDE's documentation could. Btw., ac_cfg.h.in is not SVN-maintained. It is automatically generated by the autoconf stuff. </pre> Joerg Wunsch 2012-05-11T13:37:17 Re: Include GPIO sysfs patch in next release? http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3247 <pre> Well, I don't think we can do something about this. The sysfs/GPIO subsystem is Linux specific. I volunteer to write the documentation if this is the only issue preventing the patch from inclusion. I don't know how it can be auto-probed for, because it targets embedded Linux systems. And there the usual situation is you cross compile, and the check needs to be if the target system has the sysfs/GPIO support, not the build system (which most probably doesn't). Regards, Rado </pre> Radoslav Kolev 2012-05-11T13:30:15 Re: Include GPIO sysfs patch in next release? http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3246 <pre> I did not say so, but it's reducing its priority, compared to things that are important for every AVRDUDE user. If you look in the patch trackers, there are many things around waiting for integration, but our (i.e., the maintainers') time is finite, so we have to prioritize, at least mentally. A blog post is *not* documentation to me. (It might be useful in addition to regular documentation, no question.) I need at least one of the two documentation files (avrdude.1, and docs/avrdude.texi) patched, preferrably both. Both could use the same wording, of course, and if someone cannot test one of them due to the lack of tools (like the texinfo suite), the patch could be made "blindly", just indicate this in the patch description. I never indicated any doubts about its functionality. I cannot see the relation between your statement, and the text you quoted from me. I wrote that my time until AVRDUDE 6.0 is tied up with fixing various Xmega stuff (I've been shoving in front of me for too long already), so I don't have free cycles to write the documentation patch myself. You are replying something about shell commands ... Still, having the code in on a system that could otherwise support the feature at all (*) would not hurt those who don't want to use it. Am I missing something? It's common practice for AVRDUDE to include all programmer handling code that would *potentially* be applicable for a particular target system, without requiring the user to include or exclude each of them by configure options (as, e.g. OpenOCD is doing). (*) I'm not knowledgable enough about *which* Linux systems are candidates for it. Every Linux with a recent enough kernel? (Which one?) Every Linux that has /sys/class/gpio around? Something else? IMHO, the autoconf.ac stuff could just determine, based on something like those symptoms I mentioned, whether the respective system supports the feature or not, and then enable it. If it's not enabled by default on systems that *could* potentially use it, each user who actually wants it were forced to compile their own, customized binary, because maintstream distribution maintainers will regularly miss to add this option to their configuration scripts. </pre> Joerg Wunsch 2012-05-11T13:29:44 Re: Include GPIO sysfs patch in next release? http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3245 <pre> Sure, but that does not mean because it is a minority that it should not go in. I will write a blog post on how it works for me. Right now I have a gentoo ebuild + patch-for-gpio file, it works. Will push my ebuild to github. And even a complete binary image of the linux distro so that people can try it just by flashing a binary on their SD card (for the beaglebone at least). Yes, the gpio enabling requires some commands to enable them, but that's 4 shell commands to expose the GPIOs in /sys/class/gpio. Sure, if you do not want to activate that feature in your build, that should not go in. </pre> Benjamin Henrion 2012-05-11T13:10:14 Re: XMega D support http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3244 <pre> Except for Xmega D devices not having the JTAG feature. But you're right, from AVRDUDE's point of view, they should be the same. </pre> Joerg Wunsch 2012-05-11T12:53:51 Re: Include GPIO sysfs patch in next release? http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3243 <pre> There's at least a reason that it's not very generic: it covers only a small fraction of the OSes supported by AVRDUDE. But the second (and more important) reason for why its priority regarding inclusion is rather low: documentation update is left as an exercise to the reader. Of course, in practice, it means it's left as an exercise for the maintainer(s). :-( Would someone be willing to add documentation for it? My main goal for AVRDUDE 6.0 is to fix all of the outstanding Xmega issues, and all my available resources are tied up with this. Besides, I wonder whether the --enable-gpio feature would better be auto-probed in configure.ac? </pre> Joerg Wunsch 2012-05-11T12:52:52 Include GPIO sysfs patch in next release? http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3242 <pre>Hi, I have tried a patched version of avrdude to support GPIOs as bitbang pins through sysfs. Is there any reason why you don't want to include it in your main repo? I have tested it on the beaglebone under gentoo, I am porting it to openwrt package to use it on some routers, such as the fonera, ubiquity routerstation, and soon the raspberry pi. Could you include it in your next release? Best, -- Benjamin Henrion &lt;bhenrion at ffii.org&gt; FFII Brussels - +32-484-566109 - +32-2-3500762 "In July 2005, after several failed attempts to legalise software patents in Europe, the patent establishment changed its strategy. Instead of explicitly seeking to sanction the patentability of software, they are now seeking to create a central European patent court, which would establish and enforce patentability rules in their favor, without any possibility of correction by competing courts or democratically elected legislators." </pre> Benjamin Henrion 2012-05-11T12:42:09 Re: XMega D support http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3241 <pre>Actually i don't yet have hardware available to test on but i expect to be able to test within the next two weeks and will report the results back to you. Besides this AFAIK you can swap from each XMega D to a pin and code compatible XMega A. Best regards, Ralf Am 10.05.2012 00:11, schrieb Dan Merillat: </pre> Ralf Glaser, track IT 2012-05-11T07:32:43 Re: FT2232 issues - ident yes, program no http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3240 <pre> Am 10.05.2012 um 11:49 schrieb Ing. Daniel Rozsnyó: I believe the issue is related to the polling following a page write - the software reads the last byte of the page, until it is read back correctly, thus the page is programmed and we can continue to program the next page (or finish up). There are multiple problems with this code: a) a page may not be programmed up until the last byte b) a value 0xff is indistinguishable from un-programmed flash I have worked on the page write code for a while now and my changes include a fix for both problems and I tested the code for a while now. I actually wanted to rework the flash read routine too and submit all changes together. However, I could submit a patch just fixing the write routine, if necessary. To check, if this really is your problem you can compile avrdude with debug symbols and check in gdb. If I'm correct, a loop located in avrftdi.c:917 will never be left. Best regards, Hannes Weisbach </pre> Hannes Weisbach 2012-05-10T11:48:30 FT2232 issues - ident yes, program no http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3239 <pre>Hello, I am trying my new board, which got integrated a FT2232 chip to support a serial port (Port B) and act as a programmer (Port A). The wiring is according to avrdude.conf with a LS244 tri-state buffer. When I run a quick test, with chip identification, the result was ok - it reads the chip ID correctly. But when it gets to actual programming, the avrdude is stuck at start of programming and no other commands work (not even ident), I must disconnect the USB cable. The command which run is: /usr/bin/avrdude -p atmega2560 -c 2232HIO -P usb -vvvv The command which wont run and gets stuck is: /usr/bin/avrdude -p atmega2560 -c 2232HIO -P usb -vvvv -U flash:w:devel.hex The resulting logs are in attachment. Any idea where the issue is? Daniel avrdude: Version 5.11.1, compiled on Oct 3 2011 at 18:38:04 Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/ Copyright (c) 2007-2009 Joerg Wunsch System wide configuration file is "/etc/avrdude.conf" User configuration file is "/home/daniel/.avrduderc" User configuration file does not exist or is not a regular file, skipping Using Port : usb Using Programmer : 2232HIO avrdude: device: 004, serial number: ? type 0x0700 found avrdude: Using device VID:PID 0403:6010 type 0x0700(H) and SN '?'. avrdude: Using USB Interface A avrdude info: reset pin value: 3 avrdude info: direction: 0x0000, value: 0x0000, inversion: 0x0000 FTDI LOG: 80 00 00 82 00 00 add_pins: 1: 0x0000, inv=0x0000 add_pins: 2: 0x0010, inv=0x0000 add_pin: 7: bit 0x008c inv=0x0800 add_pin: 8: bit 0x008f inv=0x4000 add_pin: 9: bit 0x008e inv=0x2000 add_pin: 10: bit 0x008d inv=0x1000 pin direction mask: 781b pin value mask: 0000 avrdude info: clock divisor: 0x0027 avrdude info: pin 008f bit 4000 value 0x4000 avrdude info: direction: 0x781b, value: 0x4000, inversion: 0x7800 FTDI LOG: 80 00 1b 82 40 78 avrdude info: pin 008f bit 4000 value 0x0000 avrdude info: direction: 0x781b, value: 0x0000, inversion: 0x7800 FTDI LOG: 80 00 1b 82 00 78 AVR Part : ATMEGA2560 Chip Erase delay : 9000 us PAGEL : PD7 BS2 : PA0 RESET disposition : dedicated RETRY pulse : SCK serial program mode : yes parallel program mode : yes Timeout : 200 StabDelay : 100 CmdexeDelay : 25 SyncLoops : 32 ByteDelay : 0 PollIndex : 3 PollValue : 0x53 Memory Detail : Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- eeprom 65 10 8 0 no 4096 8 0 9000 9000 0x00 0x00 Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- flash 65 10 256 0 yes 262144 256 1024 4500 4500 0x00 0x00 Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- lfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00 Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- hfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00 Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- efuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00 Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- lock 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00 Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- calibration 0 0 0 0 no 1 0 0 0 0 0x00 0x00 Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- signature 0 0 0 0 no 3 0 0 0 0 0x00 0x00 Programmer Type : avrftdi Description : FT2232H based generic programmer avrdude info: pin 008f bit 4000 value 0x4000 avrdude info: direction: 0x781b, value: 0x4000, inversion: 0x7800 FTDI LOG: 80 00 1b 82 40 78 avrdude info: pin 008c bit 0800 value 0x0800 avrdude info: direction: 0x781b, value: 0x4800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 48 78 avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x6800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 68 78 avrdude info: pin 008d bit 1000 value 0x1000 avrdude info: direction: 0x781b, value: 0x7800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 78 78 avrdude info: pin 0004 bit 0008 value 0x0000 SameVal avrdude info: pin 0010 value 0 avrdude info: direction: 0x781b, value: 0x7800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 78 78 avrdude info: pin 0001 bit 0001 value 0x0000 SameVal avrdude info: pin 0004 bit 0008 value 0x0008 avrdude info: direction: 0x781b, value: 0x7808, inversion: 0x7800 FTDI LOG: 80 08 1b 82 78 78 avrdude info: pin 0004 bit 0008 value 0x0000 avrdude info: direction: 0x781b, value: 0x7800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 78 78 avrdude info: pin 008f bit 4000 value 0x0000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: AVR device initialized and ready to accept instructions Reading | | 0% 0.00savrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 Reading | ################# | 33% 0.02savrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 Reading | ################################################## | 100% 0.02s avrdude: Device signature = 0x1e9801 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 1, lfuse value: e6 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 2, lfuse value: e6 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 3, lfuse value: e6 avrdude: safemode: lfuse reads as E6 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 1, hfuse value: d1 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 2, hfuse value: d1 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 3, hfuse value: d1 avrdude: safemode: hfuse reads as D1 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 1, efuse value: fc avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 2, efuse value: fc avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 3, efuse value: fc avrdude: safemode: efuse reads as FC avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 1, lfuse value: e6 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 2, lfuse value: e6 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 3, lfuse value: e6 avrdude: safemode: lfuse reads as E6 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 1, hfuse value: d1 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 2, hfuse value: d1 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 3, hfuse value: d1 avrdude: safemode: hfuse reads as D1 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 1, efuse value: fc avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 2, efuse value: fc avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 3, efuse value: fc avrdude: safemode: efuse reads as FC avrdude: safemode: Fuses OK avrdude info: pin 008f bit 4000 value 0x4000 avrdude info: direction: 0x781b, value: 0x7800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 78 78 avrdude info: pin 0010 value 16 avrdude info: direction: 0x781b, value: 0x7810, inversion: 0x7800 FTDI LOG: 80 10 1b 82 78 78 avrdude info: pin 0004 bit 0008 value 0x0008 avrdude info: direction: 0x781b, value: 0x7818, inversion: 0x7800 FTDI LOG: 80 18 1b 82 78 78 LED Mask=0x7800 value =0x7818 &amp;=0x7800 avrdude info: direction: 0x7800, value: 0x7800, inversion: 0x7800 FTDI LOG: 80 00 00 82 78 78 avrdude done. Thank you. avrdude: Version 5.11.1, compiled on Oct 3 2011 at 18:38:04 Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/ Copyright (c) 2007-2009 Joerg Wunsch System wide configuration file is "/etc/avrdude.conf" User configuration file is "/home/daniel/.avrduderc" User configuration file does not exist or is not a regular file, skipping Using Port : usb Using Programmer : 2232HIO avrdude: device: 004, serial number: ? type 0x0700 found avrdude: Using device VID:PID 0403:6010 type 0x0700(H) and SN '?'. avrdude: Using USB Interface A avrdude info: reset pin value: 3 avrdude info: direction: 0x0000, value: 0x0000, inversion: 0x0000 FTDI LOG: 80 00 00 82 00 00 add_pins: 1: 0x0000, inv=0x0000 add_pins: 2: 0x0010, inv=0x0000 add_pin: 7: bit 0x008c inv=0x0800 add_pin: 8: bit 0x008f inv=0x4000 add_pin: 9: bit 0x008e inv=0x2000 add_pin: 10: bit 0x008d inv=0x1000 pin direction mask: 781b pin value mask: 0000 avrdude info: clock divisor: 0x0027 avrdude info: pin 008f bit 4000 value 0x4000 avrdude info: direction: 0x781b, value: 0x4000, inversion: 0x7800 FTDI LOG: 80 00 1b 82 40 78 avrdude info: pin 008f bit 4000 value 0x0000 avrdude info: direction: 0x781b, value: 0x0000, inversion: 0x7800 FTDI LOG: 80 00 1b 82 00 78 AVR Part : ATMEGA2560 Chip Erase delay : 9000 us PAGEL : PD7 BS2 : PA0 RESET disposition : dedicated RETRY pulse : SCK serial program mode : yes parallel program mode : yes Timeout : 200 StabDelay : 100 CmdexeDelay : 25 SyncLoops : 32 ByteDelay : 0 PollIndex : 3 PollValue : 0x53 Memory Detail : Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- eeprom 65 10 8 0 no 4096 8 0 9000 9000 0x00 0x00 Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- flash 65 10 256 0 yes 262144 256 1024 4500 4500 0x00 0x00 Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- lfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00 Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- hfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00 Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- efuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00 Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- lock 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00 Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- calibration 0 0 0 0 no 1 0 0 0 0 0x00 0x00 Block Poll Page Polled Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- --------- signature 0 0 0 0 no 3 0 0 0 0 0x00 0x00 Programmer Type : avrftdi Description : FT2232H based generic programmer avrdude info: pin 008f bit 4000 value 0x4000 avrdude info: direction: 0x781b, value: 0x4000, inversion: 0x7800 FTDI LOG: 80 00 1b 82 40 78 avrdude info: pin 008c bit 0800 value 0x0800 avrdude info: direction: 0x781b, value: 0x4800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 48 78 avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x6800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 68 78 avrdude info: pin 008d bit 1000 value 0x1000 avrdude info: direction: 0x781b, value: 0x7800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 78 78 avrdude info: pin 0004 bit 0008 value 0x0000 SameVal avrdude info: pin 0010 value 0 avrdude info: direction: 0x781b, value: 0x7800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 78 78 avrdude info: pin 0001 bit 0001 value 0x0000 SameVal avrdude info: pin 0004 bit 0008 value 0x0008 avrdude info: direction: 0x781b, value: 0x7808, inversion: 0x7800 FTDI LOG: 80 08 1b 82 78 78 avrdude info: pin 0004 bit 0008 value 0x0000 avrdude info: direction: 0x781b, value: 0x7800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 78 78 avrdude info: pin 008f bit 4000 value 0x0000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: AVR device initialized and ready to accept instructions Reading | | 0% 0.00savrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 Reading | ################# | 33% 0.02savrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 Reading | ################################################## | 100% 0.02s avrdude: Device signature = 0x1e9801 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 1, lfuse value: e6 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 2, lfuse value: e6 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 3, lfuse value: e6 avrdude: safemode: lfuse reads as E6 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 1, hfuse value: d1 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 2, hfuse value: d1 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 3, hfuse value: d1 avrdude: safemode: hfuse reads as D1 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 1, efuse value: fc avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 2, efuse value: fc avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: safemode read 3, efuse value: fc avrdude: safemode: efuse reads as FC avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed To disable this feature, specify the -D option. avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal avrdude info: pin 008e bit 2000 value 0x2000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: erasing chip avrdude info: pin 0004 bit 0008 value 0x0000 SameVal avrdude info: pin 0010 value 0 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude info: pin 0001 bit 0001 value 0x0000 SameVal avrdude info: pin 0004 bit 0008 value 0x0008 avrdude info: direction: 0x781b, value: 0x3808, inversion: 0x7800 FTDI LOG: 80 08 1b 82 38 78 avrdude info: pin 0004 bit 0008 value 0x0000 avrdude info: direction: 0x781b, value: 0x3800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 38 78 avrdude: reading input file "devel.hex" avrdude: input file devel.hex auto detected as Intel Hex avrdude: writing flash (13368 bytes): Writing | | 0% 0.00savrdude info: pin 008c bit 0800 value 0x0800 SameVal -&lt; bytes = 256 of 13368, blocksize = 128 of 128 address = 128, page_size = 256 command buffer begin: 40 00 00 0c 48 00 00 94 40 00 01 ca 48 00 01 02 40 00 02 0c 48 00 02 94 40 00 03 ec 48 00 03 02 40 00 04 0c 48 00 04 94 40 00 05 ec 48 00 05 02 40 00 06 0c 48 00 06 94 40 00 07 ec 48 00 07 02 40 00 08 0c 48 00 08 94 40 00 09 ec 48 00 09 02 40 00 0a 0c 48 00 0a 94 40 00 0b ec 48 00 0b 02 40 00 0c 0c 48 00 0c 94 40 00 0d ec 48 00 0d 02 40 00 0e 0c 48 00 0e 94 40 00 0f ec 48 00 0f 02 40 00 10 0c 48 00 10 94 40 00 11 ec 48 00 11 02 40 00 12 0c 48 00 12 94 40 00 13 ec 48 00 13 02 40 00 14 0c 48 00 14 94 40 00 15 ec 48 00 15 02 40 00 16 0c 48 00 16 94 40 00 17 ec 48 00 17 02 40 00 18 0c 48 00 18 94 40 00 19 ec 48 00 19 02 40 00 1a 0c 48 00 1a 94 40 00 1b ec 48 00 1b 02 40 00 1c 0c 48 00 1c 94 40 00 1d ec 48 00 1d 02 40 00 1e 0c 48 00 1e 94 40 00 1f ec 48 00 1f 02 40 00 20 0c 48 00 20 94 40 00 21 ec 48 00 21 02 40 00 22 0c 48 00 22 94 40 00 23 ec 48 00 23 02 40 00 24 0c 48 00 24 94 40 00 25 ec 48 00 25 02 40 00 26 0c 48 00 26 94 40 00 27 ec 48 00 27 02 40 00 28 0c 48 00 28 94 40 00 29 ec 48 00 29 02 40 00 2a 0c 48 00 2a 94 40 00 2b ec 48 00 2b 02 40 00 2c 0c 48 00 2c 94 40 00 2d ec 48 00 2d 02 40 00 2e 0c 48 00 2e 94 40 00 2f ec 48 00 2f 02 40 00 30 0c 48 00 30 94 40 00 31 ec 48 00 31 02 40 00 32 0c 48 00 32 94 40 00 33 ec 48 00 33 02 40 00 34 0c 48 00 34 94 40 00 35 ec 48 00 35 02 40 00 36 0c 48 00 36 94 40 00 37 ec 48 00 37 02 40 00 38 0c 48 00 38 94 40 00 39 ec 48 00 39 02 40 00 3a 0c 48 00 3a 94 40 00 3b ec 48 00 3b 02 40 00 3c 0c 48 00 3c 94 40 00 3d ec 48 00 3d 02 40 00 3e 0c 48 00 3e 94 40 00 3f ec 48 00 3f 02 40 00 40 0c 48 00 40 94 40 00 41 b4 48 00 41 03 40 00 42 0c 48 00 42 94 40 00 43 ec 48 00 43 02 40 00 44 0c 48 00 44 94 40 00 45 ec 48 00 45 02 40 00 46 0c 48 00 46 94 40 00 47 ec 48 00 47 02 40 00 48 0c 48 00 48 94 40 00 49 ec 48 00 49 02 40 00 4a 0c 48 00 4a 94 40 00 4b ec 48 00 4b 02 40 00 4c 0c 48 00 4c 94 40 00 4d ec 48 00 4d 02 40 00 4e 0c 48 00 4e 94 40 00 4f ec 48 00 4f 02 40 00 50 0c 48 00 50 94 40 00 51 ec 48 00 51 02 40 00 52 0c 48 00 52 94 40 00 53 ec 48 00 53 02 40 00 54 0c 48 00 54 94 40 00 55 ec 48 00 55 02 40 00 56 0c 48 00 56 94 40 00 57 ec 48 00 57 02 40 00 58 0c 48 00 58 94 40 00 59 ec 48 00 59 02 40 00 5a 0c 48 00 5a 94 40 00 5b ec 48 00 5b 02 40 00 5c 0c 48 00 5c 94 40 00 5d ec 48 00 5d 02 40 00 5e 0c 48 00 5e 94 40 00 5f ec 48 00 5f 02 40 00 60 0c 48 00 60 94 40 00 61 ec 48 00 61 02 40 00 62 0c 48 00 62 94 40 00 63 ec 48 00 63 02 40 00 64 0c 48 00 64 94 40 00 65 ec 48 00 65 02 40 00 66 0c 48 00 66 94 40 00 67 ec 48 00 67 02 40 00 68 0c 48 00 68 94 40 00 69 ec 48 00 69 02 40 00 6a 0c 48 00 6a 94 40 00 6b ec 48 00 6b 02 40 00 6c 0c 48 00 6c 94 40 00 6d f2 48 00 6d 02 40 00 6e 0c 48 00 6e 94 40 00 6f ec 48 00 6f 02 40 00 70 0c 48 00 70 94 40 00 71 ec 48 00 71 02 40 00 72 45 48 00 72 6e 40 00 73 61 48 00 73 62 40 00 74 6c 48 00 74 69 40 00 75 6e 48 00 75 67 40 00 76 20 48 00 76 69 40 00 77 6e 48 00 77 74 40 00 78 65 48 00 78 72 40 00 79 72 48 00 79 75 40 00 7a 70 48 00 7a 74 40 00 7b 73 48 00 7b 00 40 00 7c 53 48 00 7c 2f 40 00 7d 4e 48 00 7d 3a 40 00 7e 20 48 00 7e 00 40 00 7f 20 48 00 7f 73 4c 00 00 00 command buffer end avrdude info: buffer size: 1028 avrdude info: pin 008e bit 2000 value 0x0000 avrdude info: direction: 0x781b, value: 0x1800, inversion: 0x7800 FTDI LOG: 80 00 1b 82 18 78 avrdude info: pin 008c bit 0800 value 0x0800 SameVal ^Cmake: *** [program_mcu] Interrupt _______________________________________________ avrdude-dev mailing list avrdude-dev&lt; at &gt;nongnu.org https://lists.nongnu.org/mailman/listinfo/avrdude-dev </pre> Ing. Daniel Rozsnyó 2012-05-10T09:49:38 [bug #36384] ATxmega32A4 usersig size http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3238 <pre>Follow-up Comment #4, bug #36384 (project avrdude): I attach a file with the right settings for all XMEGA MCUs. This file is automatically converted by a Python script from this table: https://docs.google.com/spreadsheet/ccc?key=0Aj00gvm9SJiUdEpncFpGZUM3d1dCbFZhU09tZjBGbGc (file #25825) _______________________________________________________ Additional Item Attachment: File name: xmega.conf Size:20 KB _______________________________________________________ Reply to this item at: &lt;http://savannah.nongnu.org/bugs/?36384&gt; _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/ </pre> Ricardo Martins 2012-05-09T22:02:02 Re: Protocol recommendation http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3237 <pre> Yes, that's the case. If you've got enough code space to implement the protocol, I'd suggest picking STK500v2. It's the most flexible one, as it doesn't rely on any kind of "magic numbers" (as the AVR910 protocol does) but gets all the relevant information downloaded during the setup phase. </pre> Joerg Wunsch 2012-05-08T21:53:36 Re: atmega48pa support http://permalink.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3236 <pre> With the SVN version of AVRDUDE, there's no need for copy&amp;paste anymore. Hmm. The ATmega48P entry (now) has: part parent "m48" id = "m48p"; desc = "ATmega48P"; signature = 0x1e 0x92 0x0a; ; Your ATmega48PA entry has: Where's the difference in signatures? I guess a new entry would rather look like: part parent "m48p" id = "m48pa"; desc = "ATmega48PA"; ; But then, someone should probably make a sweep through all those die-shrink "A" versions, and submit a patch for all of them. </pre> Joerg Wunsch 2012-05-08T21:51:52 Search Engine Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.hardware.avr.avrdude.devel