From: Andrew Lunn <andrew@lunn.ch>
To: Emmanuel Viollet <Emmanuel.Viollet@webdyn.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Memory footprint
Date: Wed, 10 May 2006 14:17:00 -0000 [thread overview]
Message-ID: <20060510141728.GE11815@lunn.ch> (raw)
In-Reply-To: <4461E29F.1030705@webdyn.com>
On Wed, May 10, 2006 at 02:54:55PM +0200, Emmanuel Viollet wrote:
> Andrew Lunn a ?crit :
> >On Wed, May 10, 2006 at 11:08:49AM +0200, Emmanuel Viollet wrote:
> >>Hi.
> >>
> >>I can't find any information on this on the internet, so perhaps you can
> >>help me out...
> >>
> >>I need to compile a kernel with PPP. Do you have any idea of the
> >>footprint of eCOS with lwIP and PPP?
> >>I compiled a minimal program with PPP for my Olimex LPC2106 evaluation
> >>board, and it takes 560Kb.
> >>Does this size seem normal?
> >
> >Is that the size of the elf or the size of the binary which is
> >actually loaded onto the target?
> >
> >what does arm-elf-size say?
>
> $ arm-elf-size.exe a.out
> text data bss dec hex filename
> 41920 1512 8028 51460 c904 a.out
>
> I suppose that this means the binary will be 51460Kb in size?
No. These are in units of bytes, not kilo bits. 51460Kb is about
6MBytes which makes no sense.
The binary will be 41920 + 1512 bytes. You also need 8028bytes of
statically allocated RAM. The size of the heap is not show here.
> I am using a Phlips 2106 processor with 128Kb EEPROM and 64Kb RAM.
> Do you think I can fit in LwIP + PPP + Zlib in this?
zlib will be a problem. In its default configuration it will allocate
64Kbytes from the heap..... You can make is use less memory, but it
will then no longer decompress data compressed with the default zlib
configuration. So i don't recommend zlib. lwip + PPP does seems
reasonable with 128Kb + 64Kb.
> The linker is giving me errors :
> $ arm-elf-gcc -I../../ecos_install/include hello.c
> -L../../ecos_install/lib -Ttarget.ld -nostdlib
> /usr/lib/gcc-lib/arm-elf/3.4.0/../../../../arm-elf/bin/ld: l'adresse
> 0x2624c de a.out de la section .text n'est pas dans la r?gion rom
> /usr/lib/gcc-lib/arm-elf/3.4.0/../../../../arm-elf/bin/ld: l'adresse
> 0x2624c de a.out de la section .fini n'est pas dans la r?gion rom
> /usr/lib/gcc-lib/arm-elf/3.4.0/../../../../arm-elf/bin/ld: l'adresse
> 0x2aff1 de a.out de la section .rodata n'est pas dans la r?gion
> rom
> /usr/lib/gcc-lib/arm-elf/3.4.0/../../../../arm-elf/bin/ld: l'adresse
> 0x2aff4 de a.out de la section .rodata1 n'est pas dans la r?gion rom
> /usr/lib/gcc-lib/arm-elf/3.4.0/../../../../arm-elf/bin/ld: l'adresse
> 0x2aff4 de a.out de la section .fixup n'est pas dans la r?gion rom
> /usr/lib/gcc-lib/arm-elf/3.4.0/../../../../arm-elf/bin/ld: l'adresse
> 0x2aff4 de a.out de la section .gcc_except_table n'est pas dans la
> r?gion rom
> /usr/lib/gcc-lib/arm-elf/3.4.0/../../../../arm-elf/bin/ld: l'adresse
> 0x4001ca20 de a.out de la section .bss n'est pas dans la r?gion ram
>
> I'm sorry, but the error messages are in french.
> From what I gather, the code is too big for RAM and ROM?
This should fit, so it suggests a problem with your linker script.
Is it trying to put everything in RAM?
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-05-10 14:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 9:09 Emmanuel Viollet
2006-05-10 9:12 ` Andrew Lunn
2006-05-10 12:55 ` Emmanuel Viollet
2006-05-10 13:15 ` [ECOS] Choice of Web Servers Laurie Gellatly
2006-05-10 14:17 ` Andrew Lunn [this message]
2006-05-11 7:12 ` [ECOS] Memory footprint Emmanuel Viollet
2006-05-11 16:24 ` Andrew Lunn
2006-05-10 14:53 ` [ECOS] " Grant Edwards
2006-05-10 15:19 ` Andrew Lunn
2006-05-10 15:24 ` Gary Thomas
2006-05-10 16:56 ` Grant Edwards
2006-05-10 16:55 ` Grant Edwards
-- strict thread matches above, loose matches on Subject: below --
2001-07-23 23:10 [ECOS] Memory Footprint Reto.Bucher@elektrobit.ch
2001-07-23 22:54 Reto.Bucher@elektrobit.ch
2001-07-26 0:12 ` Jonathan Larmour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060510141728.GE11815@lunn.ch \
--to=andrew@lunn.ch \
--cc=Emmanuel.Viollet@webdyn.com \
--cc=ecos-discuss@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).