public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Jesper K. Pedersen" <linux@famped.dk>
To: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] AT91SAM7S256 problem with test/example twothreads
Date: Sun, 17 Jun 2012 14:43:00 -0000	[thread overview]
Message-ID: <20120617164302.74bdd347@io.solnet> (raw)

I am at my wits end getting the twothreads example working on my Olimex
P256 board (AT91SAM7S256 based).

Calling the cyg_mutex_init does not return. Also I notice that the call
to the printf line before the call to cyg_mutex_init prints extremely
slow on my terminal.

I have set the default console up to tty0 going to ser0. This part
works fine with my other software running on the board (normal expected
transmission speed).

Are there any "gotcha'" involving threading on the AT91 series
microcontrollers?

Best regards
JesperKP

Extra info (note I have added a couple of debugging lines):

void cyg_user_start(void)
{
  printf("Entering twothreads' cyg_user_start() function\n\r");

  cyg_mutex_init(&cliblock);

  printf("cyg_mutex_init() done\n\r"); // <--- Never gets sent 

  cyg_thread_create(4, simple_program, (cyg_addrword_t) 0,
		    "Thread A", (void *) stack[0], 4096,
		    &simple_threadA, &thread_s[0]);
  printf("Done setting up ThreadA\n\r");

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2012-06-17 14:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-17 14:43 Jesper K. Pedersen [this message]
2012-06-19 13:17 ` Jesper K. Pedersen
2012-06-19 20:18   ` Lambrecht Jürgen
2012-06-20  5:38     ` Jesper K. Pedersen
2012-06-20  9:54       ` Lambrecht Jürgen

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=20120617164302.74bdd347@io.solnet \
    --to=linux@famped.dk \
    --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).