avr-chat
[Top][All Lists]
Advanced

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

Re: [avr-chat] ATmega2561: bootloader can not write in application secti


From: Thomas Richter
Subject: Re: [avr-chat] ATmega2561: bootloader can not write in application section
Date: Fri, 09 Mar 2007 16:03:49 +0100
User-agent: Thunderbird 1.5.0.10 (Windows/20070221)

Hi Eric,

that means my bootloader application was inside the application flash section (RWW Section)?

When I use
   LDFLAGS += -Wl,--section-start=.text=0x3E000
then I get a verification error:

   avrdude -p atmega2561 -P com2     -c stk500v2    -U flash:w:BootLoader.hex

   avrdude: AVR device initialized and ready to accept instructions

   Reading | ################################################## | 100% 0.01s

   avrdude: Device signature = 0x1e9802
   avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed
            To disable this feature, specify the -D option.
   avrdude: erasing chip
   avrdude: reading input file "BootLoader.hex"
   avrdude: input file BootLoader.hex auto detected as Intel Hex
   avrdude: writing flash (256878 bytes):

   Writing | ################################################## | 100% 0.49s

   avrdude: 256878 bytes of flash written
   avrdude: verifying flash memory against BootLoader.hex:
   avrdude: load data flash data from input file BootLoader.hex:
   avrdude: input file BootLoader.hex auto detected as Intel Hex
   avrdude: input file BootLoader.hex contains 256878 bytes
   avrdude: reading on-chip flash data:

   Reading | ################################################## | 100% 42.72s

   avrdude: verifying ...
   avrdude: verification error, first mismatch at byte 0x1e000
            0xff != 0x0d
   avrdude: verification error; content mismatch

   avrdude done.  Thank you.

When I compare the flash data with avrdude by calling
   avrdude -p m2561 -c stk500v2 -P COM2 -b 115200 -v -t
in terminal mode with command
   dump flash 0x3E000 1024
then the data are "correct" (I have checked the first bytes).
  The file BootLoader.hex (Intel Hex Format) begins with following content:
   :020000023000CC
   :10E000000D9466F00D9483F00D9483F00D9483F0DD
   :10E010000D9483F00D9483F00D9483F00D9483F0B0
   :10E020000D9483F00D9483F00D9483F00D9483F0A0
   :10E030000D9483F00D9483F00D9483F00D9483F090

The bootloader does not work.

Thomas



reply via email to

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