[En-Nut-Discussion] [Understand compilation process] avr-objcopy -R .eeprom

[Rodrigue]

Sorry but I didn't find anywhere the memory layout in Ethernut's software
manual. Howerver, there is a document about this subject on Ethernut's
website.
I read this article 
http://winavr.scienceprog.com/avr-gcc-tutorial/save-constants-to-avr-eeprom-using-winavr.html
http://winavr.scienceprog.com/avr-gcc-tutorial/save-constants-to-avr-eeprom-using-winavr.html 
I think that the internal Eeprom of the ATmega is not used because, the
keyword EEMEM isn't used in Nut/OS...
Maybe, that explained why the .eeprom section is removed with avr-objcopy? 
Moreover, I read that during the "programmation" (makeburn), the internal
eeprom is not writted. It's was an article about Ponyprog and the AVR.


Ernst Stippl wrote:
> 
> Hi!
> 
> Yes,
> Nut/OS and Nut/Net use the eeprom section. 
> There is a memory layout in Ethernut's software manual ..
> 
> regards
> 
> Ernst
> 
> -----Ursprüngliche Nachricht-----
> Von: en-nut-discussion-bounces at egnite.de
> [mailto:en-nut-discussion-bounces at egnite.de] Im Auftrag von Rodrigue
> Gesendet: Dienstag, 20. Februar 2007 12:46
> An: en-nut-discussion at egnite.de
> Betreff: Re: [En-Nut-Discussion] [Understand compilation process]
> avr-objcopy -R .eeprom
> 
> 
> Anybody doesn't know why we suppress the .eeprom section ? 
> Is this section used Nut/OS? I think that the answer is yes but only
> within
> the software...
> 
> 
> Rodrigue wrote:
>> 
>> Hello,
>> 
>> When I compile "simple" project. The following commands are executed:
>> avr-objcopy -R .eeprom -O ihex simple.elf simple.hex avr-objcopy -O 
>> binary simple.elf simple.bin
>> 
>> The first command removes the .eeprom section form simple.elf and 
>> converts the rest of the file in ihex format (is it Intel Format?). 
>> Why remove this section? How to write the eeprom section? If I have a 
>> variable like this in my software:
>> static const char my_string[] __attribute__ ((section(".eeprom"))) = 
>> "This data will be loaded into EEPROM"; What's happening?
>> 
>> The second command converts simple.elf file in binary format which is 
>> not used after, so I don't understand why it's generated?
>> make -k burn
>> avrdude -p atmega128 -P com1 -c stk500v2 -V -U flash:w:simple.hex
>> 
>> Thanks in advance!
>> Rodrigue
>> 
>> 
> 
> --
> View this message in context:
> http://www.nabble.com/-Understand-compilation-process--avr-objcopy--R-.eepro
> m-tf3250513.html#a9060304
> Sent from the MicroControllers - Ethernut mailing list archive at
> Nabble.com.
> 
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
> 
> 
> 
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.441 / Virus Database: 268.18.3/693 - Release Date: 19.02.2007
> 17:01
> 
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
> 
> 

-- 
View this message in context: http://www.nabble.com/-Understand-compilation-process--avr-objcopy--R-.eeprom-tf3250513.html#a9087698
Sent from the MicroControllers - Ethernut mailing list archive at Nabble.com.