[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avrdude-dev] Initial STK600 support committed to CVS
From: |
Bob Paddock |
Subject: |
Re: [avrdude-dev] Initial STK600 support committed to CVS |
Date: |
Sun, 16 Mar 2008 17:24:30 -0400 |
User-agent: |
KMail/1.9.7 |
On Sunday 16 March 2008 04:49:50 pm Joerg Wunsch wrote:
> Alas, not very much. What we really need is some conversion from the
> Atmel XML to our own XML. We are not allowed to store the Atmel XML
> documents anywhere in a public CVS repository, so the only way is to
> convert them,
I know. The way I set things up is I copied the files from AVRStudio,
put them in a directory. When the program has had a successful run
they are deleted. Only the resultant file remains.
> As the best available hierarchical format these days
> is XML, what we need then is some XML -> XML transformation to get our
> own XML files out of the Atmel ones -- which we can store within our
> CVS.
> For the XML -> XML transformation, I lean towards using XSLT but only
> if it doesn't get too much into our way. Definately, the converter
> should become part of the AVRDUDE project.
I'll see if I can get XML out of what I already have.
> Why that? I'd see the natural choice to have them as subhierarchies
> within the same file.
Gives a clear separation of the Atmel derived data from
AVRDude supplied data, was my thinking.
Re: [avrdude-dev] Initial STK600 support committed to CVS, Dave N6NZ, 2008/03/15
Re: [avrdude-dev] Initial STK600 support committed to CVS, Dave N6NZ, 2008/03/15
Re: [avrdude-dev] Initial STK600 support committed to CVS, Bob Paddock, 2008/03/15