From: "A Shobhan" <shobana@in.ceeyes.com>
To: <ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] please help me
Date: Thu, 02 Aug 2001 22:09:00 -0000 [thread overview]
Message-ID: <007601c11bdb$bd41fa10$0f09010a@shobhan> (raw)
Hi,
I have a multi threaded program consists of just two threads on ARM =
7TDMI SOC target. The program is running fine if the eCos is built with =
"Bitmap Scheduler" option, I am able to create Mutex and =
cyg_thread_delay() is also working fine. If I use "Multi Level Scheduler =
with Time Slicing Enabled" option the program is hanging at =
cyg_mutex_init() and no thread is working. The cyg_thread_delay() is =
also hanging.=20
Why the cyg_mutex_init() is hanging in Multi level scheduler and not in =
Bitmap scheduler?
Why cyg_thread_delay() is hanging in Multi level scheduler and not in =
Bitmap scheduler?
Please help.
Thanks in advance...
Shobhan
next reply other threads:[~2001-08-02 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-02 22:09 A Shobhan [this message]
2001-08-03 5:31 ` Jonathan Larmour
2001-08-03 12:27 ` A Shobhan
2001-08-03 12:41 ` Jonathan Larmour
2001-08-03 13:36 ` [ECOS] mips_rm7000.ld and dwarf Chris Morrow
2001-08-03 13:45 ` Jonathan Larmour
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='007601c11bdb$bd41fa10$0f09010a@shobhan' \
--to=shobana@in.ceeyes.com \
--cc=ecos-discuss@sourceware.cygnus.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).