[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [avrdude-dev] optional hash mark progress indicator

From: Rune Christensen
Subject: RE: [avrdude-dev] optional hash mark progress indicator
Date: Fri, 25 Jul 2003 22:05:33 +0200


I have found the following lines of source code from main.c

     * write the buffer contents to the selected memory type
    fprintf(stderr, "%s: writing %s (%d bytes):\n", 
            progname, memtype, size);

    if (!nowrite) {
      rc = avr_write(pgm, p, memtype, size, 1);
    else {
       * test mode, don't actually write to the chip, output the buffer
       * to stdout in intel hex instead 
      rc = fileio(FIO_WRITE, "-", FMT_IHEX, p, memtype, size);

when avr_write is called it's called with ..., 1) where the last one is 
verbose (local variable).

from avr.h
int avr_write(PROGRAMMER * pgm, AVRPART * p, char * memtype, int size, 
              int verbose);

Best Regards
Rune Christensen 

-----Original Message-----
From: address@hidden
Behalf Of Brian Dean
Sent: Friday, July 25, 2003 3:07 PM
Cc: address@hidden
Subject: Re: [avrdude-dev] optional hash mark progress indicator

On Fri, Jul 25, 2003 at 06:52:23PM +1200, Alex Shepherd wrote:

> Are you saying that it is it is updated every 16 bytes now but used to be
> every byte? We could increase the numeric updating from every 16 bytes to
> say 128 or 256 bytes if that is a still considered a problem.

No.  I'm saying that progress used to be printed by default, i.e.,
there was no command line option to turn it off.  But due to slowness
with Windows console printing, we made it so that you had to specify
-v to enable it.  Note that on Unix, where I first wrote
AVRDUDE/AVRPROG, this was not a problem.

If you are really set on the hash marks, I'd at least like the number
of hash marks printed to be a fixed number, like a percentage.  So
that part way through, the display might look something like this:

  Writing: |###########                              |  29% ETA 22.3 sec

Should have one for reading also.  Does that seem reasonable?

If you you'd like to work on a patch for that, great.  If not, just
let me know and I'll work on it.  Also, I would like to pull this
could out from under the -v option and use a seperate -q option to
disable it instead of using the -v option to enable it.

Brian Dean

avrdude-dev mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]