From: John Dallaway <john@dallaway.org.uk>
To: emanuel stiebler <emu@e-bbes.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: ek-lm3s811
Date: Mon, 25 Feb 2013 18:15:00 -0000 [thread overview]
Message-ID: <512BAA16.8020900@dallaway.org.uk> (raw)
In-Reply-To: <5129EBD9.5070705@e-bbes.com>
Emanuel
On 24/02/13 10:30, emanuel stiebler wrote:
> is there a chance, ECOS got to large for the 8k this cpu has?
> just tried it, and getting messages, that some of the memory is outside
> of the .bs segment.
You will find that many eCos tests require more than 8KiB RAM. I suggest
you stick with the "kernel" package template (not the "default" package
template) and build as many tests as you can by instructing GNU make to
ignore linker errors:
make && make -i tests
I hope this helps...
John Dallaway
eCos maintainer
http://www.dallaway.org.uk/john
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2013-02-25 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 10:30 [ECOS] ek-lm3s811 emanuel stiebler
2013-02-25 18:15 ` John Dallaway [this message]
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=512BAA16.8020900@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=emu@e-bbes.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).