Re: [avr-gcc-list] big string into the ROM

[Keith Gudger]

Have you tried "info ld"?  Look at the part on linker scripts and "Input
Sections".

"If you use a file name without a list of sections, then all sections
in the input file will be included in the output section."

(Untested), this might work:

SECTIONS
{
  /* Read-only sections, merged into text segment: */
...
  .text :
  {
    *(.vectors)
     __ctors_start = . ;
...
    *(.fini0)  /* Infinite loop after program termination.  */
     mytext.o  /* <- Here is your file! */
     _etext = . ;
  }  > text

Keith

On Mon, 10 Apr 2006, drvdrv wrote:

> Hi,
> > > (and one more question: is there any way to modify avr-
> gcc so that
> > > allows compile bigger string and gives only warning and  
> not error?
> > > Then I could decide this warning is important or not.)
> > 
> > How did you declare it?
> > 
> > If you don't declare it correctly then it will be copied 
> >into RAM at startup 
> > because the compiler doesn't know it is read only.
> 
> I didn't declare it because at the first step I create a _pure_ binary file 
> from mytext.c and there is only text nothing else (in the .bin file)
> The question is:  how colud I tell the avr-objcopy or the linker that this 
> binary file put into the ROM?
> 
> 
> 
> 
> 
> 
> _______________________________________________________________________
> 3 könyv = 15+5% kedvezmény!
> http://www.bookline.hu/control/news?newsid=351&affiliate=fre3kokar2230
> 
> 
> 
> 
> _______________________________________________
> AVR-GCC-list mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
>