From: "Lange, Bert" <b.lange@hzdr.de>
To: "gcembed" <gcembed@gmail.com>,
"ecos-discuss@ecos.sourceware.org"
<ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Freeze with big const struct/array
Date: Wed, 18 Jan 2012 12:05:00 -0000 [thread overview]
Message-ID: <9386d21dc3cc7f47bd065a5cd29ef92c@cg.fzd.de> (raw)
In-Reply-To: <4F0EE3FF.3030400@gmail.com>
Hi,
> I am using ecos (20050912 with patches from Freescales).
Which controller, which platform?
> If I increase image size, the structure grows up to 64.909 bytes. In
> this case, board does not boot (no ++, nothing).
Maybe unsigned int is only 16 bit width?
Try to split you image in two halfes. So you can see if the problem in
image size or in the flash size.
regrads,
Bert
--
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:[~2012-01-18 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 13:48 gcembed
2012-01-18 12:05 ` Lange, Bert [this message]
2012-05-30 9:30 ` [ECOS] " gcembed
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=9386d21dc3cc7f47bd065a5cd29ef92c@cg.fzd.de \
--to=b.lange@hzdr.de \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=gcembed@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).