Re: [avr-chat] RFC: Unified Microcontroller Programming File

[E. Weddington]

Richard Urwin wrote:

> Is there not the possibility of multiple .hex files? I know that's how I 
> program Flash and eeprom from gas-generated objects.
>
> Might it be a good idea to put a list of hex files and their targets 
> into the .txt, or their own file. 
You have a very good point. The toolchain generates a .hex file for the 
Flash and a seperate .hex file for the EEPROM. For that matter, there 
will have to be a way to distinguish between a low, high, and extended 
fuse setting or files.


> The fashionable way to do that would 
> be XML; the parser is a large overhead when a simple text format would 
> surfice, but it would make room for expansion.
>
>  
Hmmm. You're right on both counts.

> Something like (in XML for self-documentation):
> <file name="flash.hex" address="0x8000" label="flash">
> textual description
> </file>
>  
Technically, the address would not have to be encoded as the addresses 
are specified in the .hex file proper. But, yeah, the label would be 
needed to mark what the file was for.

> You could encode other information in there for the microcontroller part 
> number, the release number, the author and the copyright details.
>
>  
Good point.

Eric