avrdude-dev
[Top][All Lists]
Advanced

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

[avrdude-dev] [bug #53008] avrdude fails to read more than 440 bytes of


From: Joerg Wunsch
Subject: [avrdude-dev] [bug #53008] avrdude fails to read more than 440 bytes of EEPROM
Date: Tue, 30 Jan 2018 14:38:00 -0500 (EST)
User-agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:57.0) Gecko/20100101 Firefox/57.0

Update of bug #53008 (project avrdude):

                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #3:

Well, I got occasional retries on reading the EEPROM (heavily
depending on the clock value), sometimes the firmware appears
to fail, but if it passes, I get full 512 bytes of EEPROM from
an ATmega16 (don't have an ATmega8 handy):


./avrdude -C avrdude.conf -p m16  -c usbtiny -U ee:r:foo.hex:i

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x1e9403 (probably m16)
avrdude: reading eeprom memory:

Reading | #                                                  | 2%
0.40savrdude: 1 retries during read
Reading | #####                                              | 9% 1.81s
avrdude: error: usbtiny_receive: Unknown error (expected 128, got -1)
Reading | #####                                              | 10%
2.58savrdude: 10 retries during SPI command
Reading | ##########################                         | 52%
4.19savrdude: 3 retries during SPI command
Reading | ################################################## | 100% 5.85s

avrdude: writing output file "foo.hex"

avrdude: safemode: Fuses OK (E:FF, H:99, L:E4)

avrdude done.  Thank you.


The target is sitting in an STK500.  If I use the STK500
itself to read the EEPROM, everything is fine (and fast).

I also tried with the junk fill option of malloc enabled
(this is FreeBSD), to imcrease the probability of hitting
a segfault, but it passes just the same as above.

Can you analyze the segfault with a debugger, to see where
it crashes for you?

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?53008>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/




reply via email to

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