public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: "Chris C." <hksbtx@2bzd.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Serial Driver + Multithreading
Date: Thu, 06 Sep 2001 13:53:00 -0000	[thread overview]
Message-ID: <3B97E257.5BA54793@redhat.com> (raw)
In-Reply-To: <2650020018329151513859@2bsure.com>

"Chris C." wrote:
> 
> 1. only transmit  to pc (in loop)
> 2. only receive from pc
> 3. transmit to (in loop) and receive from pc (hold on the enter key to send
> a block of data)
> 
> In case 1 and 2, the serial driver can work fine but it can't work in case
> 3. The problem occured in case 3 was that it can work correctly within a
> short time and then it can't do the transmit and receive. I use the Ctrl+C
> to break the program, I always see it break in the idle_thread_main.
> 
> What is the possible problem that cause the program run into this function?

You could look at the eCos at91 serial driver anyway for comparison
purposes. Without seeing your ISR/DSR it would be difficult to guess
anyway.

> What is the best way to do the debugging?

Use "info threads" to list other threads than the idle thread, and then the
"thread" command to switch GDB's view of threads. Type "help" to get more
information on GDB commands, or read the GDB manual.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

      reply	other threads:[~2001-09-06 13:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-29  8:23 Chris C.
2001-09-06 13:53 ` Jonathan Larmour [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=3B97E257.5BA54793@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=hksbtx@2bzd.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).