Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug #10907] flashing atmel mega 32 fails 4.4.0 #23

Closed
avrs-admin opened this issue Dec 10, 2021 · 5 comments
Closed

[bug #10907] flashing atmel mega 32 fails 4.4.0 #23

avrs-admin opened this issue Dec 10, 2021 · 5 comments
Labels
question Further information is requested

Comments

@avrs-admin
Copy link

christian fleischer fleischer@cs.tu-berlin.de
Thu 04 Nov 2004 01:59:53 PM UTC

Hello!

flashing an atmega32 fails in the following way:
writing succeeds, reading too, but comparing the written data fails from the beginning.
this is the fact for version 4.4.0
it works fine with 4.2.0
the write-operation is 0.4s with version 4.4.0 and 1.3s for 4.2.0.
maybe the new version is too fast?
it runs on a 2.4GHz Pentium... I don't know how the timing for the write-operation is done.
hope this helps.

christian
fleischeratcsdottuminusberlindotde.

This issue was migrated from https://savannah.nongnu.org/bugs/?10907

@avrs-admin avrs-admin added the question Further information is requested label Dec 10, 2021
@avrs-admin
Copy link
Author

Eric Weddington
Thu 04 Nov 2004 04:41:36 PM UTC

What OS are you using?

@avrs-admin
Copy link
Author

Joerg Wunsch <joerg_wunsch>
Wed 14 Sep 2005 10:12:46 PM UTC

Could you please answer Eric's question?

@avrs-admin
Copy link
Author

Brian Dean
Sun 18 Sep 2005 12:51:22 AM UTC

Also, what programmer are you using?

@avrs-admin
Copy link
Author

Tue 27 Sep 2005 03:45:00 AM UTC

I have experienced the exact same problem (and solution) with an ATMEGA16, on Fedora Core 3 running on brand new AMD, using parallel port to perform ISP.

Using 4.4.0, the unsuccessful flash write and read are 1.77s and 1.69s respectively.

Using 4.2.0, the successful flash write and read are 3.05s and 2.89s respectively.

Thanks,
Simon

@avrs-admin
Copy link
Author

Joerg Wunsch <joerg_wunsch>
Mon 21 Aug 2006 11:14:26 AM UTC

There's now a new -i option now to insert additional delay cycles into
bit-bang ISP operations driven by AVRDUDE directly.

This should be able to fix your problem.  As this bug report is pretty
old already (we've got AVRDUDE 5.1 out for months, and are targetting
for 5.2), and there's no further feedback, I'm going to close the
report now.

If the problem still persists with the current CVS version (or 5.2,
once it is out), please open a new bug report, and provide the
information the developers might request from you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant