From: emanuel stiebler <emu@e-bbes.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] ek-lm3s811
Date: Sun, 24 Feb 2013 10:30:00 -0000 [thread overview]
Message-ID: <5129EBD9.5070705@e-bbes.com> (raw)
Hi.
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.
Increasing the internal memory (I know it isn't there) let's the test
compile ...
cheers
--
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 reply other threads:[~2013-02-24 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 10:30 emanuel stiebler [this message]
2013-02-25 18:15 ` [ECOS] ek-lm3s811 John Dallaway
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=5129EBD9.5070705@e-bbes.com \
--to=emu@e-bbes.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).