From: Michael Buksas <mwbuksas@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-help] S_memLib_NOT_ENOUGH_MEMORY error in porting VxWorks application.
Date: Wed, 10 Feb 2010 10:56:48 -0700 [thread overview]
Message-ID: <4B72F360.4050209@domain.hid> (raw)
I'm porting a VxWorks application to Xenomai/SOLO and getting
S_memLib_NOT_ENOUGH_MEMORY errors from taskSpawn.
I'm currently running on a desktop Linux system, so I doubt physical
memory is an issue. Rather, I think it's the allocation of memory for
tasks, and my crushing ignorance about how to do the same.
For example, does this occur when the memory needs of the task exceed
the stack size argument to taskSpawn? Increasing this value does not
appear to help.
Can anyone suggest how to further diagnose the memory problem?
And to address the broader question, where should a raw beginner at
embedded programming go for documentation on Xenomai/SOLO and guidance
for the porting process?
Thanks in advance,
Mike
next reply other threads:[~2010-02-10 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 17:56 Michael Buksas [this message]
2010-02-10 18:31 ` [Xenomai-help] S_memLib_NOT_ENOUGH_MEMORY error in porting VxWorks application Philippe Gerum
2010-02-10 22:22 ` Michael Buksas
2010-02-11 17:05 ` Philippe Gerum
2010-02-11 23:04 ` Michael Buksas
2010-02-11 23:20 ` Philippe Gerum
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=4B72F360.4050209@domain.hid \
--to=mwbuksas@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.