[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[avrdude-dev] [bug #34518] loading intel hex files > 64k using record-ty
From: |
anonymous |
Subject: |
[avrdude-dev] [bug #34518] loading intel hex files > 64k using record-type 4 (Extended Linear Address Record) |
Date: |
Mon, 10 Oct 2011 11:19:41 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Ubuntu/10.04 (lucid) Firefox/3.6.23 |
URL:
<http://savannah.nongnu.org/bugs/?34518>
Summary: loading intel hex files > 64k using record-type 4
(Extended Linear Address Record)
Project: AVR Downloader/UploaDEr
Submitted by: None
Submitted on: Mo 10 Okt 2011 11:19:40 UTC
Category: None
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Originator Name: tomcrus
Originator Email: address@hidden
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
I just upgraded to avrdude 5.11.1, because of another bug recently fixed.
But opposed to avrdude 5.8 - that I was using before - I'm unable to properly
flash my bootloader to an atmega128's boot-section now, if the hex-files uses
the hex-record-type 4 (extended linear address record).
The problem can be easily reproduced flashing the attached file
avr-bootloader.hex.qrUq5r to a device and subsequently reading it back again.
I already did these steps and attached also the read-back version; see
avr-bootloader.hex.read and cmd-prompt.txt for the command-output...
Comparing both files it can be seend, that the extended linear offset of 64k
(first line in original file) seems to get skipped completely.
After looking into fileio.c I came accross the function ihex2b(), that already
had several changes according to the >64k problem as can be seen in revs 851,
880, 928.
Now I think my problem is caused by the local variable offsetaddr (that's
purpose I cannot understand). Removing all this offsetaddr-stuff (meaning to
return this function to the state of rev 816, like in avrdude 5.8) solved my
issue.
Can anybody responsible please explain me the purpose of this
offsetaddr-variable. It seems it was introduced in rev 851, but the given
comment "AVR32" doesn't say anything meaningful and I don't know what
differences there are when reading intel-hex-files for avr32-architecture...
Greetings tomcrus
_______________________________________________________
File Attachments:
-------------------------------------------------------
Date: Mo 10 Okt 2011 11:19:40 UTC Name: avr-bootloader.hex.qrUq5r Size: 160B
By: None
<http://savannah.nongnu.org/bugs/download.php?file_id=24127>
-------------------------------------------------------
Date: Mo 10 Okt 2011 11:19:40 UTC Name: avr-bootloader.hex.read Size: 133kB
By: None
<http://savannah.nongnu.org/bugs/download.php?file_id=24128>
-------------------------------------------------------
Date: Mo 10 Okt 2011 11:19:40 UTC Name: cmd-prompt.txt Size: 2kB By: None
<http://savannah.nongnu.org/bugs/download.php?file_id=24129>
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?34518>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/
- [avrdude-dev] [bug #34518] loading intel hex files > 64k using record-type 4 (Extended Linear Address Record),
anonymous <=
- [avrdude-dev] [bug #34518] loading intel hex files > 64k using record-type 4 (Extended Linear Address Record), Joerg Wunsch, 2011/10/10
- [avrdude-dev] [bug #34518] loading intel hex files > 64k using record-type 4 (Extended Linear Address Record), Joerg Wunsch, 2011/10/10
- [avrdude-dev] [bug #34518] loading intel hex files > 64k using record-type 4 (Extended Linear Address Record), Joerg Wunsch, 2011/10/10
- [avrdude-dev] [bug #34518] loading intel hex files > 64k using record-type 4 (Extended Linear Address Record), Joerg Wunsch, 2011/10/10
- [avrdude-dev] [bug #34518] loading intel hex files > 64k using record-type 4 (Extended Linear Address Record), Joerg Wunsch, 2011/10/10
- [avrdude-dev] [bug #34518] loading intel hex files > 64k using record-type 4 (Extended Linear Address Record), David Hoerl, 2011/10/10
- [avrdude-dev] [bug #34518] loading intel hex files > 64k using record-type 4 (Extended Linear Address Record), Joerg Wunsch, 2011/10/10
- Re: [avrdude-dev] [bug #34518] loading intel hex files > 64k using record-type 4 (Extended Linear Address Record), Joerg Wunsch, 2011/10/10
- [avrdude-dev] [bug #34518] loading intel hex files > 64k using record-type 4 (Extended Linear Address Record), Joerg Wunsch, 2011/10/10
- [avrdude-dev] [bug #34518] loading intel hex files > 64k using record-type 4 (Extended Linear Address Record), Elif, 2011/10/21