[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avrdude-dev] Autodetection of output-file-format ;-(
From: |
Mike Murphree |
Subject: |
Re: [avrdude-dev] Autodetection of output-file-format ;-( |
Date: |
Mon, 14 Feb 2005 08:44:49 -0600 (CST) |
E. Weddington said:
> Joerg Wunsch wrote:
>
>>
>>However, I think the feature might be extended somewhat in case the
>> output file does not exist. An attempt could be made to derive the
>> file type of the file about to be created based on its filename
>>suffix. Failing this, either default it to binary (*), or return an
>> error.
>>
>>
>
> This sounds good.
>
>>(*) While this might sound odd at first, it's basically the way the
>> input file type detection is handled. First, all specific file type
>> handlers are asked whether they could handle the file, and if all else
>> fails, it's considered to be binary.
>>
>>Known filename suffixes?
>>
>>.hex -> Intel Hex
>>.ihex -> Intel Hex
>>.srec -> Motorola Srecord
>>
>>What would be a historical 3-letter suffix Windows users are so fond of
>> for Srecord?
>>
> I've seen .s19 on the internet.
Yup, very common for Motorola S records.
There was Tek Hex a long time ago, but the suffix elludes me.
.bin for straight binary files.
Mike