[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [avr-gcc-list] strange behaviour of avr-ld, maybe a bug?
From: |
Massimiliano Cialdi |
Subject: |
RE: [avr-gcc-list] strange behaviour of avr-ld, maybe a bug? |
Date: |
Mon, 14 Feb 2011 12:10:51 +0100 |
Il giorno lun, 14/02/2011 alle 18.49 +0800, Boyapati, Anitha ha scritto:
> >In the linker script be sure the MEMORY command is:
> >MEMORY
> >{
> > text (rx) : ORIGIN = 0, LENGTH = 32K
> > data (rw!x) : ORIGIN = 0x800060, LENGTH = 2K
> > eeprom (rw!x) : ORIGIN = 0x810000, LENGTH = 1K
> >}
> >
> >text region is as long as 32KB, as atmega32's flash.
> >
> It is the program section which is 102.0% full not .text section. AFAIK
> linker script is not handling the size of PROGRAM segment.
Ok, in any case this binary may not work.
linker knows that .data section is to be loaded in ram from flash in
init step.
In the map file, LMA awareness is explicit at the start of .data:
.data 0x00800060 0x5dc load address 0x00007ca2
but at:
0x0080063c _edata = .
there's no sign that ld is looking much past VMAs.
linker should know that image of section .data exceeds limit of test
memory region
regards
- [avr-gcc-list] strange behaviour of avr-ld, maybe a bug?, Massimiliano Cialdi, 2011/02/14
- RE: [avr-gcc-list] strange behaviour of avr-ld, maybe a bug?, Boyapati, Anitha, 2011/02/14
- RE: [avr-gcc-list] strange behaviour of avr-ld, maybe a bug?,
Massimiliano Cialdi <=
- Re: [avr-gcc-list] strange behaviour of avr-ld, maybe a bug?, Erik Christiansen, 2011/02/14
- RE: [avr-gcc-list] strange behaviour of avr-ld, maybe a bug?, Boyapati, Anitha, 2011/02/17
- A work-around Re: [avr-gcc-list] strange behaviour of avr-ld, maybe a bug?, Erik Christiansen, 2011/02/17
- RE: A work-around Re: [avr-gcc-list] strange behaviour of avr-ld, maybe a bug?, Boyapati, Anitha, 2011/02/20
- Re: A work-around Re: [avr-gcc-list] strange behaviour of avr-ld,maybe a bug?, Erik Christiansen, 2011/02/21