bugAVR Downloader/UploaDEr - Bugs: bug #10907, flashing atmel mega 32 fails 4.4.0

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #10907: flashing atmel mega 32 fails 4.4.0

Submitter:  None
Submitted:  Thu 04 Nov 2004 01:59:53 PM UTC
   
 
Category:  None Severity:  3 - Normal
Priority:  5 - Normal Item Group:  None
Status:  Need Info Privacy:  Public
Assigned to:  joerg_wunsch Originator Name:  christian fleischer
Originator Email:  -email is unavailable- Open/Closed:  Closed
Release:  None Programmer hardware: 
Device type: 

Mon 21 Aug 2006 11:14:26 AM UTC, comment #5: 

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.

Joerg Wunsch <joerg_wunsch>
Group administrator
Tue 27 Sep 2005 03:45:00 AM UTC, comment #4: 

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

Anonymous
Sun 18 Sep 2005 12:51:22 AM UTC, comment #3: 

Also, what programmer are you using?

Brian Dean <bdean>
Group administrator
Wed 14 Sep 2005 10:12:46 PM UTC, comment #2: 

Could you please answer Eric's question?

Joerg Wunsch <joerg_wunsch>
Group administrator
Thu 04 Nov 2004 04:41:36 PM UTC, comment #1: 

What OS are you using?

Eric Weddington <arcanum>
Group Member
Thu 04 Nov 2004 01:59:53 PM UTC, original submission:  

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.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

 

Follow 6 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2006-08-21 joerg_wunsch Assigned toNone joerg_wunsch
    Open/ClosedOpen Closed
2005-09-17 joerg_wunsch StatusNone Need Info
2005-09-14 joerg_wunsch Originator Name christian fleischer
    Originator Email -email is unavailable-
2004-11-04 arcanum Carbon-Copy- Added fleischer --AT-- cs --DOT-- tuminusberlin --DOT-- de

Back to the top

Powered by Savane 3.13-4b48.
Corresponding source code