Re: [avr-chat] avrdude - strange behaviour when binary don't start @0x0000

[Joerg Wunsch]

Massimiliano Cialdi <address@hidden> wrote:

> it is a strange behaviour: it read boot.hex file as it contains 28774
> byets (that is 28K + 102).

This is because AVRDUDE internally has no real notion about anything
like the actual segmentation of the input data, with respect to the
target memory.  It flattens all data into a single (internal) memory
image, so anything before your bootloader image will be padded with
0xff (empty EPROM pattern) first.

It would be really nice to fix this somehow, but alas, it requires a
major rewrite of some parts of AVRDUDE, which currently nobody intends
to do.  It's only marginally annoying in certain situations, but
apparently not enough to motivate someone to actually rewrite that
part of the code.

-- 
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)