You are right. If you want to install an image via say ISP, building a completely new image is not a problem. But if we have a network of devices (built from avr processors) that communicate wirelessly, the incremental way of installing the new application in the entire network (by wirelessly transmitting the image) can help significantly to reduce energy due to radio transmissions. This is especially important in some deployment scenarios where it is impossible/very difficult to change the batteries of the devices.
----- Original Message ----
From: "Weddington, Eric"
<address@hidden>
To: Raj Sharma <address@hidden>; Preston Wilson <address@hidden>; avr-gcc-list <address@hidden>
Sent: Tuesday, May 20, 2008 3:22:34 PM
Subject: RE: [avr-gcc-list] Order of variables placed in .data and .bsssections
> -----Original Message-----
> From: Raj Sharma [mailto:
address@hidden]
> Sent: Tuesday, May 20, 2008 2:17 PM
> To: Weddington, Eric; Preston Wilson; avr-gcc-list
> Subject: Re: [avr-gcc-list] Order of variables placed in
> .data and .bsssections
>
> Dear Eric,
>
> Thanks for the reply. I am working on incremental
> compilation/linking. One of the requirements is to maintain
> maximum similarity between the old and new versions of the
> binary image.
> Thanks
>
Raj
May I ask what would be the advantage of incremental compilation/linking
on the AVR target? When even the most extensive AVR application I've
seen only takes 1 minute to do a full rebuild.