public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@ecoscentric.com>
To: David Luca <davidluca3000@yahoo.com>
Cc: ecos-devel <ecos-devel@sourceware.org>,
		  ecos-discuss <ecos-discuss@sourceware.org>
Subject: Re: Unexpected exit from threads
Date: Thu, 23 Nov 2006 10:32:00 -0000	[thread overview]
Message-ID: <m3hcwqo3ms.fsf@xl5.calivar.com> (raw)
In-Reply-To: <20061123100721.3447.qmail@web38711.mail.mud.yahoo.com>

David Luca <davidluca3000@yahoo.com> writes:

> Yes, the for loops are long enough for the leds to be
> visible.

It might be better to change the function so that each call toggles
the LED rather than turn it off and on.


> I traced the cyg_thread_delay and after the
> Cyg_Thread::unlock() call, nothing happens, the
> execution goes to the main function.

What do you mean by going to the main function? Which function is
that? In some configurations you might end up with a dummy main()
thread which will just exit, it won't have any effect on your program.

Can you still get this program running as it was originally intended,
with just the printf()s? If so, what then happens if you then add the
led functions? Try to work out what differs between the working
version and the non-working version.


-- 
Nick Garnett                                     eCos Kernel Architect
http://www.ecoscentric.com                The eCos and RedBoot experts

      reply	other threads:[~2006-11-23 10:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-23  8:43 David Luca
2006-11-23  9:55 ` Nick Garnett
2006-11-23 10:07   ` David Luca
2006-11-23 10:32     ` Nick Garnett [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=m3hcwqo3ms.fsf@xl5.calivar.com \
    --to=nickg@ecoscentric.com \
    --cc=davidluca3000@yahoo.com \
    --cc=ecos-devel@sourceware.org \
    --cc=ecos-discuss@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).