<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.hardware.avr.avrdude.devel">
    <title>gmane.comp.hardware.avr.avrdude.devel</title>
    <link>http://blog.gmane.org/gmane.comp.hardware.avr.avrdude.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3255"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3242"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3239"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3235"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3234"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3230"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3229"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3228"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3227"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3226"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3224"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3210"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3209"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3199"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3194"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3190"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3189"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3186"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3184"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3177"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3255">
    <title>Problems with avrdude 5.11+</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3255</link>
    <description>&lt;pre&gt;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 hel&lt;/pre&gt;</description>
    <dc:creator>Bill O'Neill</dc:creator>
    <dc:date>2012-05-19T19:48:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3242">
    <title>Include GPIO sysfs patch in next release?</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3242</link>
    <description>&lt;pre&gt;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 &amp;lt;bhenrion at ffii.org&amp;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."
&lt;/pre&gt;</description>
    <dc:creator>Benjamin Henrion</dc:creator>
    <dc:date>2012-05-11T12:42:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3239">
    <title>FT2232 issues - ident yes, program no</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3239</link>
    <description>&lt;pre&gt;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"
&lt;/pre&gt;</description>
    <dc:creator>Ing. Daniel Rozsnyó</dc:creator>
    <dc:date>2012-05-10T09:49:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3235">
    <title>atmega48pa support</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3235</link>
    <description>&lt;pre&gt;I had to add support in avrdude.conf for the ATmega48PA to reflash a
xwusbasp board with it. I copy-paste-changed the following to make it
work with the dragon. Warning: Unsure about stk500, etc., constants.
This is a mostly blind copy of the ATmega48P with the signature bytes
changed.

Cheers,

Simon-

diff --git a/avrdude.conf.orig b/avrdude.conf
index bb785ab..0527eae 100644
--- a/avrdude.conf.orig
+++ b/avrdude.conf
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -8293,6 +8293,188 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; part
       ;
   ;
 
+part
+    id               = "m48pa";
+    desc             = "ATMEGA48PA";
+     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 0x0a;
+    pagel            = 0xd7;
+    bs2              = 0xc2;
+    chip_erase_delay = 45000;
+    pgm_enable       = "1 0 1 0  1 1 0 0    0 1&lt;/pre&gt;</description>
    <dc:creator>Simon Kirby</dc:creator>
    <dc:date>2012-05-08T07:41:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3234">
    <title>Protocol recommendation</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3234</link>
    <description>&lt;pre&gt;Hello!

I am developing open BL-ESC software for common Atmega8 boards. I have
implemented wire-level support for the Turnigy USB linker, which gives
a 9600 baud half duplex serial link over the standard servo connector.
I intend to support flashing over this, to make it easier later to update
without having to reconnect ISP bits.

I'd rather not reinvent the wheel when it comes to the actual protocol,
and would rather make it work as something avrdude can already talk to.

It seems stk500/arduino, butterfly, avr910, etc., are all protocols that
don't need anything other than data to work, and should be OK with half
duplex operation. Can somebody familiar with them suggest one as a simple
and reasonable choice to implement the client side for?

Also feel free to point out if this is a horrible idea.

Thanks :)

Simon-
&lt;/pre&gt;</description>
    <dc:creator>Simon Kirby</dc:creator>
    <dc:date>2012-05-08T07:37:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3230">
    <title>[bug #36399] Fixed usersig erase</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3230</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.nongnu.org/bugs/?36399&amp;gt;

                 Summary: Fixed usersig erase
                 Project: AVR Downloader/UploaDEr
            Submitted by: rasm
            Submitted on: Fri 04 May 2012 08:17:34 PM GMT
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: Ricardo Martins
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

The following patch fixes usersig erase.



    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Fri 04 May 2012 08:17:34 PM GMT  Name: usersig_erase.patch  Size: 494B  
By: rasm

&amp;lt;http://savannah.nongnu.org/bugs/download.php?file_id=25789&amp;gt;

    ____________________&lt;/pre&gt;</description>
    <dc:creator>Ricardo Martins</dc:creator>
    <dc:date>2012-05-04T20:17:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3229">
    <title>[patch #7774] ATxmega32A4: fixed page sizes andusersig settings</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3229</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.nongnu.org/patch/?7774&amp;gt;

                 Summary: ATxmega32A4: fixed page sizes and usersig settings
                 Project: AVR Downloader/UploaDEr
            Submitted by: rasm
            Submitted on: Fri 04 May 2012 08:16:10 PM GMT
                Category: None
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

The following patch fixes the settings of the ATmega32A4 device.



    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Fri 04 May 2012 08:16:10 PM GMT  Name: atxmega32a4_mem_sizes.patch 
Size: 1021B   By: rasm

&amp;lt;http://savannah.nongnu.org/patch/download.php?file_id=25788&amp;gt;

    _______________________________________________________

Reply to&lt;/pre&gt;</description>
    <dc:creator>Ricardo Martins</dc:creator>
    <dc:date>2012-05-04T20:16:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3228">
    <title>BusPirate Patch for 5.11</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3228</link>
    <description>&lt;pre&gt;Hi all,

First post to this list, so my apologies if I've broken etiquette by
posting like this.  I'm the author of a patch to the BusPirate which gives
it a new mode to verify the flash on an AVR at a much higher speed.  This
patch has been incorporated into the 6.0 firmware for the BusPirate, but
the component that is required in AVRDUDE to make it work is not included
in the official AVRDUDE release.  As such, I'd like to make you aware of it.

The original article I wrote about the patch (and all related information)
can be found here:
http://coding.zencoffee.org/2011/08/bus-pirate-40x-verify-speed-increase.html

The original forum thread posted on Dangerous Prototypes regarding this
patch can be found here:
http://dangerousprototypes.com/forum/viewtopic.php?f=41&amp;amp;t=2629

The patch file for AVRDUDE, which is confirmed to work with 5.11 (and can
most likely be applied to other versions) can be found here:
http://zencoding-blog.googlecode.com/svn/trunk/buspirate/avrdude-5.11-buspirate.patch

Thanks for read&lt;/pre&gt;</description>
    <dc:creator>dw.avrdude-list&lt; at &gt;zencoffee.org</dc:creator>
    <dc:date>2012-05-03T23:52:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3227">
    <title>[bug #36384] ATxmega32A4 usersig size</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3227</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.nongnu.org/bugs/?36384&amp;gt;

                 Summary: ATxmega32A4 usersig size
                 Project: AVR Downloader/UploaDEr
            Submitted by: None
            Submitted on: Thu 03 May 2012 01:45:43 PM UTC
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: Ricardo Martins
        Originator Email: rasm&amp;lt; at &amp;gt;fe.up.pt
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

The datasheet of the XMEGA A4 devices mentions that the "User Signature Row"
is one flash page in size. In the trunk's version of avrdude.conf.in all XMEGA
devices share the same usersig configuration, yet they are not the same:

Page Sizes (words):
ATxmega16A4: 128
ATxmega32A4: 128
ATxmega64A4: 128
ATxmega128A4: 256






    _________&lt;/pre&gt;</description>
    <dc:creator>anonymous</dc:creator>
    <dc:date>2012-05-03T13:45:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3226">
    <title>Q: change "safemode" default?</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3226</link>
    <description>&lt;pre&gt;Hi *,

I intend to name the upcoming new release of AVRDUDE V6.0, as there
have been many changes recently, including larger ones (like direct
ELF file reading).

Now, bumping the major version number allows to also introduce some
things that aren't completely backwards-compatible.  I already
disabled the default readout of the last four EEPROM locations (for
the erase cycle counter), which used to be there to announce the user
that an erase cycle counter possibly already exists even if no -y/-Y
option was given.

Given all my past experience, I now also tend to disable the
"safemode" feature except for the ancient bitbang programming adapters
it once has been designed for.

Historical note: with those bitbang adapters, it could occasionally
happen on bad wiring, or due to missing line drivers, that signaly
flipped unintentionally, worst case leading to unsolicited fuse
modifications.  This eventually led to the invention of the "safemode"
feature.

With all the programmers that are in use these days (in par&lt;/pre&gt;</description>
    <dc:creator>Joerg Wunsch</dc:creator>
    <dc:date>2012-04-25T09:30:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3224">
    <title>[patch #7769] Write flash fails for AVR910 programmers</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3224</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.nongnu.org/patch/?7769&amp;gt;

                 Summary: Write flash fails for AVR910 programmers
                 Project: AVR Downloader/UploaDEr
            Submitted by: branez
            Submitted on: Tue 24 Apr 2012 12:42:13 PM GMT
                Category: None
                Priority: 7 - High
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

When downloading hex file with AVR910 compatible programmer it increments
address by number of bytes not words (programm memory is two bytes wide).



    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Tue 24 Apr 2012 12:42:13 PM GMT  Name: avr910.patch  Size: 416B   By:
branez

&amp;lt;http://savannah.nongnu.org/patch/download.php?file_id=25719&amp;gt;

    ______&lt;/pre&gt;</description>
    <dc:creator>Brane Ždralo</dc:creator>
    <dc:date>2012-04-24T12:42:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3210">
    <title>Does AVRdude support the AT90SC6464C?</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3210</link>
    <description>&lt;pre&gt;Two questions:

Does AVRdude support the AT90SC series chips (specifically the AT90SC6464C-USB)?

and

Does anyone on the AVRdude dev list have a full 200+ page datasheet
for the AT90SC6464C-USB chip?
&lt;/pre&gt;</description>
    <dc:creator>Martin Bogomolni</dc:creator>
    <dc:date>2012-04-07T19:12:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3209">
    <title>Issues with ATXMEGA256A3U and AVR Dragon</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3209</link>
    <description>&lt;pre&gt;Hello,

I'm having some issues with avrdude and AVR Dragon to program an
ATXMEGA256A3U via JTAG/USB.

The version of avrdude I'm using is 5.11.1 (Sep. 2011 apparently).

In short, I can connect to the board, read fuses and even read bytes
from the flash/eeprom (apparently). However I can't manage to get the
programming to work (neither with or without prior erase). In fact,
the erase itself doesn't work. The programming fails at verification.
Also I've seen that I cannot even switch to JTAG_XMEGA emulator if the
board is powered by more than 2V. It only works when the voltage is
between 1.5 and 2 V (I am using the default internal clock, which
should be 2MHz after reset).

If you have any suggestions or there are any known problems I would be
extremely happy to know.

Thanks (more details below).

In detail:

&lt;/pre&gt;</description>
    <dc:creator>Omar Choudary</dc:creator>
    <dc:date>2012-04-06T16:28:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3199">
    <title>Load Extended Address command and word/byteprogramming issues</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3199</link>
    <description>&lt;pre&gt;Hello,

I'm currently streamlining avrftdi's paged load and write functions. In the process, I adapt them to the new avrdude interface for paged load and write. However, I stumbled across some issues I'm not entirely clear about.

1) Does avrdude take care of issuing a load extended address command? Because page programming is now done page-by-page avrdude "knows" when the 128k boundary is crossed and could issue a load extended address command. is this the case?

2) If the programmer has to issue the load extended address command: Does the command need to be issued _exactly_ once, or can it be issued multiple times? For example, before loading a page with an address greater 128k, is it "safe" for the programmer to send the command before loading the page. This would slow down the programming time noticeably, but simplify the programmer code a lot.

3) It seems to me, today all AVRs are programmed word-by-word, and a word being 2 bytes wide. Is this correct? Code in avr.c:373 suggests that there are AVRs whi&lt;/pre&gt;</description>
    <dc:creator>Hannes Weisbach</dc:creator>
    <dc:date>2012-03-20T12:54:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3194">
    <title>[bug #35886] Error crossing segment boundaries onreads</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3194</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.nongnu.org/bugs/?35886&amp;gt;

                 Summary: Error crossing segment boundaries on reads
                 Project: AVR Downloader/UploaDEr
            Submitted by: None
            Submitted on: Sun 18 Mar 2012 04:45:10 PM UTC
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: Sam Lin
        Originator Email: lincomatic&amp;lt; at &amp;gt;hotmail.com
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

Using a USBtinyISP with AT90USB1286, the memory above 0x10000 is getting read
incorrectly with the -U flash:r/v commands.

It's easy to reproduce this.  Try writing flash above 0x10000 and the verify
will fail.  Try dumping memory, and the contents above 0x10000 is always 0xFF




    _________________________________&lt;/pre&gt;</description>
    <dc:creator>anonymous</dc:creator>
    <dc:date>2012-03-18T16:45:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3190">
    <title>XMega D support</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3190</link>
    <description>&lt;pre&gt;Hi &amp;lt; at &amp;gt; all,

we are going to use an ATXMegaD3 in a new designs. Unfortunately this 
device seems to be not supported by the current version of avrdude.
Therefore the following questions:
- is anybody already working on integrating the D-devices?
- is there a big difference to the A-devices (in terms of programming 
them via PDI), in other words is integrating them so easy i could do it 
myself in a reasonable amount of time?

Best regards,
Ralf
&lt;/pre&gt;</description>
    <dc:creator>Ralf Glaser, track IT</dc:creator>
    <dc:date>2012-03-15T15:35:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3189">
    <title>AVRDUDE and ATmega328p problems</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3189</link>
    <description>&lt;pre&gt;
There is more then a few people having troubles with this chip and AVRDUDE and it seems not to be exclusive to any specific programmer or OS (not sure if it's a 64bit problem perhaps), the standard is a "avrdude: initialization failed, rc=-1" response and if forced passed that with -F swtich then you get a faulty device ID response

avrdude: Device signature = 0x000000
avrdude: Expected signature for ATMEGA328P is 1E 95 0F

I've had a look around in the code and the problem seems to be with these things

1. Power-up sequence:
Apply power between VCC and GND while RESET and SCK are set to “0”. In some sys-
tems, the programmer can not guarantee that SCK is held low during power-up. In this
case, RESET must be given a positive pulse of at least two CPU clock cycles duration
after SCK has been set to “0”.

2. Wait for at least 20ms and enable serial programming by sending the Programming
Enable serial instruction to pin MOSI.

3. The serial programming instructions will not work if the communication is&lt;/pre&gt;</description>
    <dc:creator>Patrick .</dc:creator>
    <dc:date>2012-03-14T03:46:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3186">
    <title>[bug #35800] Compilation error on certain systems ifparport is disabled</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3186</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.nongnu.org/bugs/?35800&amp;gt;

                 Summary: Compilation error on certain systems if parport is
disabled
                 Project: AVR Downloader/UploaDEr
            Submitted by: None
            Submitted on: mån 12 mar 2012 11.39.26
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: Robert Niemi
        Originator Email: robert.den.klurige&amp;lt; at &amp;gt;gmail.com
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

For systems with no parallel port, the corresponding header files could be
non-existing, thus resulting in a build failure.

The following patch will fix the issue (patch-file is included):

--- avrdude-5.11/linux_ppdev.h2009-03-06 21:09:11.000000000 +0100
+++ avrdude-5.11_parport/linux_ppdev.h&lt;/pre&gt;</description>
    <dc:creator>anonymous</dc:creator>
    <dc:date>2012-03-12T11:39:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3184">
    <title>Support for custom purpose built programmer</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3184</link>
    <description>&lt;pre&gt;
Hello.  I hope this is a good place to post.

I'm designing a custom interface board for end-users of a particular device. 
That device contains an Atmega64 and needs frequent flashing by end user, so
my (current) interface board is basically a stock USBasp that is permanently
installed on the device.

My new interface board is going to have much more functionality for the
end-user so I can't follow simple stock USBasp.  I want to base it on an
Atmega32U4 so I can take advantage of the bootloader so that my custom
interface can, itself, be updated frequently without a standalone ISP
programmer (so the target device gets updated via my interface board, and my
interface board itself gets updated via USB).

The end-user is already using avrdude to flash the device via the usbasp and
I don't want to change that.  So I guess my question is... can I be
confident that avrdude can be configured to use my custom board?  I'm trying
to figure out HOW I can put usbasp onto an Atmega32U4 but I'm not really
sure how that&lt;/pre&gt;</description>
    <dc:creator>FrustratedAlways</dc:creator>
    <dc:date>2012-02-24T20:54:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3177">
    <title>[patch #7729] Updated support for FTDI-232H</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3177</link>
    <description>&lt;pre&gt;URL:
  &amp;lt;http://savannah.nongnu.org/patch/?7729&amp;gt;

                 Summary: Updated support for FTDI-232H
                 Project: AVR Downloader/UploaDEr
            Submitted by: roklobster
            Submitted on: Fri 24 Feb 2012 02:13:17 PM GMT
                Category: None
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

I was having some problems with certain .hex files not being verified
correctly in my old 5.11-patch7610 of AVRDUDE.

I have since checked out SVN1068 and applied patch #7610 making the necessary
changes so that it compiled.

The new binary now verifies the problematic hex files correctly. 

This patch adds support for the FTDI-232H part which will be properly
available in the upcoming libftdi-0.20.  In addition it enables the 30MHz
clock in the &lt;/pre&gt;</description>
    <dc:creator>Jason Hecker</dc:creator>
    <dc:date>2012-02-24T14:13:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3176">
    <title>SVN build issue</title>
    <link>http://comments.gmane.org/gmane.comp.hardware.avr.avrdude.devel/3176</link>
    <description>&lt;pre&gt;After a hiatus since 5.11 was released I have tried to build the
latest (1068) version from SVN of AVRDUDE.  In both Cygwin/MinGW and
Ubuntu after running ./bootstrap and ./configure the latter on both
machines terminates with:

checking if gcc accepts -Wno-pointer-sign ... yes
configure: creating ./config.status
.in'ig.status: error: cannot find input file: `

and no Makefile appears.  Any ideas?
&lt;/pre&gt;</description>
    <dc:creator>Jason Hecker</dc:creator>
    <dc:date>2012-02-24T07:24:55</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.hardware.avr.avrdude.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.hardware.avr.avrdude.devel</link>
  </textinput>
</rdf:RDF>

