Re: [avrdude-dev] [bug #44717] avrdude creates empty flash dump

[D]

Thank you Joerg,

This feature is a very bad style of programming and should not be the
default option for sure.
It resembles the game without an "exit-hotkey". :)
Now I see that the guy who invented this feature was trying to save some
space on his HDD but it is not polite to program in such a way.

I waste about 2 days to discover this undocumented feature because I got
assured that my AVR was pre-programmed and finally it was empty.
As you may see I was novice but I am a 20-year programmer and because of it
I entered and exited the same door not less 100 times.

And anyway this is the BUG!!!
BECAUSE:
if you do read and then just make verify then avrdude will crash with
divided by zero "feature"... :) Verify is not working with empty file... :)

Anyway thank you very much for the reply.

Kind regards,

Dmitry

PS: Nobody(Google, Yandex) knows about this feature by the way.... heck...
time wasted...




--------------
This e-mail message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message. If you are the intended recipient,
please be advised that the content of this message is subject to access,
review and disclosure by the sender's e-mail System Administrator.
--------------


On Thu, Apr 9, 2015 at 7:29 PM, Joerg Wunsch <address@hidden>
wrote:

> Update of bug #44717 (project avrdude):
>
>                   Status:                    None => Invalid
>              Assigned to:                    None => joerg_wunsch
>
>     _______________________________________________________
>
> Follow-up Comment #1:
>
> It's not a bug, it's a feature: your flash is empty (erased),
> thus the resulting file is empty, too.  You have chosen raw
> file output, so you get a file with length 0.  If you had
> chosen e.g. Intel hex output, you'd at least get the terminal
> record in the file - as an indication that everything worked
> well, but there simple are no data to display.
>
> Without that feature, readout of a partially filled flash
> would always get a bunch of 0xFFFF values at the end of the
> file.  The feature is only applied to flash, not to EEPROM,
> that's why your EEPROM readout indeed yields a file full of
> 0xFF.  Yes, that's not really quite consistent, but has been
> that way since the early days of AVRDUDE.
>
>     _______________________________________________________
>
> Reply to this item at:
>
>   <http://savannah.nongnu.org/bugs/?44717>
>
> _______________________________________________
>   Message sent via/by Savannah
>   http://savannah.nongnu.org/
>
>