[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[avrdude-dev] offset in flash when programming an .elf file
From: |
Thomas Pircher |
Subject: |
[avrdude-dev] offset in flash when programming an .elf file |
Date: |
Sun, 20 Jul 2008 16:42:32 +0100 |
User-agent: |
KMail/1.9.9 |
Hi,
this is a follow-up from the AVRFreaks thread
http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&p=468691
I run into trouble with avrdude when I try to flash an AT90USB647 with an .elf
file:
| avrdude -cdragon_jtag -pusb647 -Pusb -F -e -Uflash:w:i2c.elf
As a result, I get the code offset by 116 bytes. When I read back the content
of the Flash with AVRStudio, I get the following data:
| :100000007F454C4601010100000000000000000097
| :100010000200530001000000000000003400000056
| :10002000241C00008500000034002000020028008D
| :1000300011000E000100000074000000000000002C
| :1000400000000000A8020000A80200000500000057
| :1000500001000000010000001C03000000018000FE
| :100060000001800000000000060000000600000003
| :10007000010000004BC0000064C0000062C000002E
| ...
instead of the expected one:
| :100000004BC0000064C0000062C0000060C000007F
| :100010005EC000005CC000005AC0000058C0000074
| ...
Is this offset of 166 bytes expected?
When I program an .hex file, then everything is OK.
I have no idea which version of avrdude I'm using. There is no --version
option. Debian/sid reports the package version as 5.5-3.
Cheers,
Thomas
As a side note (nag):
I need to use the -F switch with the AT90USB647 because the avrdude config
file has the right signature (0x1e9682) commented out and a wrong signature
(0x1e9782) enabled.
--
pycrc -- a free CRC calculator and C source code generator
http://www.tty1.net/pycrc/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [avrdude-dev] offset in flash when programming an .elf file,
Thomas Pircher <=