[En-Nut-Discussion] What do do with big (demo) apps on small CPU

Henrik Maier hmnews at proconx.com
Wed Jan 30 02:00:51 CET 2013

On 29/01/2013 9:05 PM, Uwe Bonnes wrote:
> Hello,
> compiling the demo apps for xnut-105c with avr-gcc 4.3.3 fails for me like:
> avr-gcc lua.o -mmcu=at90can128 -Wl,--gc-sections -Wl,--defsym=main=0,-Map=lua.map,--cref -L../.././lib -Wl,--section-start=.data=0x801100 -Wl,--start-group ../.././lib/nutinit.o -lnutlua -lnutnet -lnutpro -lnutgorp -lnutos -lnutarch -lnutdev -lnutarch -lnutos -lnutcrt -lm   -Wl,--end-group -o lua.elf
> /opt/cross/avr/lib/gcc/avr/4.3.3/../../../../avr/bin/ld: lua.elf section `.text' will not fit in region `text'
> /opt/cross/avr/lib/gcc/avr/4.3.3/../../../../avr/bin/ld: region `text' overflowed by 58912 bytes
> Is this a problem with my setup? Or my avr-gcc? I think, we the agreed that
> make in the app directorty should succeed unconditional. How to fix?
> Thanks
Hello Uwe,

I wasn't even aware that lua can run the little AVR.

The XNUT-105 is one of my boards, so I checked using gcc 4.3.3 
(WinAVR-20100110) against Nut/OS 5.0 and 5.1 and the SVN Trunk with 
following results:

xnut-105c.conf: all examples compile
xnut-105d.conf: all examples compile
xnut-100.conf: all examples compile

Is it just this one conf file which fails for you or are there other AVR 
boards which fail as well?

As Harald said the overflow by 58912 bytes is unusually large.



More information about the En-Nut-Discussion mailing list