From: Mandeep Sandhu <mandeepsandhu.chd@gmail.com>
To: Sergei Gavrikov <sergei.gavrikov@gmail.com>
Cc: John Dallaway <john@dallaway.org.uk>, ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: ecos mem footprint with HTTPD support
Date: Thu, 16 Jul 2009 08:54:00 -0000 [thread overview]
Message-ID: <b18c5f790907160154j6bbcbe8lc8865b3340223312@mail.gmail.com> (raw)
In-Reply-To: <20090715142056.GA11032@sg-ubuntu.local>
>> Couldn't we have "added" RAM there?
>>
>
> That is defined in plf mlt files. I guess here for your target
> hal/arm/at91/at91sam7s/current/include/pkgconf/mlt*
>
Ok will check that. Thanks.
> [snip]
>
>> Do you think 256K RAM will be enough to run a similarly configured
>> system (with additional USB device and SPI driver support) on ARM7
>> based embedded SoC?
>
> IMO, it will be possible, if you will use lwIP TCP/IP stack.
I think I was wrongly calculating my RAM usage for the sample HTTPD
app (using lwIP).
When looking for the runtime RAM usage of my app+kernel...I should
add the bss+data+rwdata (if any) sections...right?
.text and .rodata will reside in the flash only. Am I correct in this
assumption?
Do all embedded systems work this way...i.e the code/text and rodata sections
reside in the flash and rest is loaded into the RAM? Who maps these addresses?
The linker script?
Because with this calc, my RAM requirement gets reduced drastically.
Also, any tips on how much space I should keep for expansion of the RW
area's?
Say my bss+data+rwdata comes to around 55KB...is it safe to go with a
system with 64KB on-chip RAM? Is 9KB margin safe enough?
thanks as always,
-mandeep
>
> Sergei
>
--
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:[~2009-07-16 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 10:37 [ECOS] " Mandeep Sandhu
2009-07-15 11:06 ` [ECOS] " John Dallaway
2009-07-15 13:14 ` Sergei Gavrikov
2009-07-15 13:18 ` Mandeep Sandhu
2009-07-15 13:53 ` Sergei Gavrikov
2009-07-15 14:05 ` Mandeep Sandhu
2009-07-15 14:17 ` Sergei Gavrikov
2009-07-16 8:54 ` Mandeep Sandhu [this message]
2009-07-16 9:10 ` Sergei Gavrikov
2009-07-16 18:30 ` John Dallaway
2009-07-17 8:24 ` Mandeep Sandhu
2009-07-15 13:16 ` Mandeep Sandhu
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=b18c5f790907160154j6bbcbe8lc8865b3340223312@mail.gmail.com \
--to=mandeepsandhu.chd@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
--cc=sergei.gavrikov@gmail.com \
/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).