From: Rene.Affourtit@pemstar.nl
To: Gary Thomas <gthomas@redhat.com>
Cc: ecos-discuss@sourceware.cygnus.com, gary@ares.chez-thomas.org
Subject: RE: [ECOS] Threading on EDB7211
Date: Mon, 19 Jun 2000 05:24:00 -0000 [thread overview]
Message-ID: <OF6BA11BFF.DEB53E41-ONC1256903.0042EBA1@pemstar.nl> (raw)
I modified the code to let ecos cooperate with the angel debugger.
this dates back to the time gdb, cygwin and angel didn't cooperate (problem
is fixed in cygwin 1.1, I haven't tested it, but I haven't heard complaints
either).
What I do in the interrupt handler is I check for interupts from uart2 (and
some checks to see if angel is currently running) and let these be handled
by angel.
It turns out angel doesn't acknowledge a transmit interrupt for uart2. So,
once a Tx interupt was set all interupts got handled by angel including the
timer interrupts. Solution? don't let angel handle this interupt or make
sure it is acknowleged.
Gary Thomas
<gthomas@redhat To: Rene.Affourtit@pemstar.nl
.com> cc: ecos-discuss@sourceware.cygnus.com
Sent by: Subject: RE: [ECOS] Threading on EDB7211
gary@ares.chez-
thomas.org
06/19/00 02:06
PM
On 19-Jun-00 Rene.Affourtit@pemstar.nl wrote:
>
> Thanks for the hint,
>
> but as it turned out my problem was caused by a modification I made in
> vectors.s which caused that no interupts were handled by ecos at all.
> It's strange how two very different problems can have the same symptoms.
> Sorry to have bothered you all with something that was entirely my own
> fault.
>
No need to apologize (just don't do it again :-)
This mailing list is supposed to be a forum where ideas and questions can
be posted and hopefully resolved. Even if the problem was your fault,
asking it here let's everyone who uses eCos about it. When a solution
is found, we all hear about it as well and can benefit from the experience.
Just for grins - what did you change in vectors.S, why did you do it and
what did you do wrong? [Just for pedagogic enlightment :-) ]
next reply other threads:[~2000-06-19 5:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-19 5:24 Rene.Affourtit [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-19 4:42 Rene.Affourtit
2000-06-19 5:06 ` Gary Thomas
2000-06-19 11:55 ` Alfredo Knecht
2000-06-19 13:22 ` Gary Thomas
2000-06-19 0:04 Rene.Affourtit
2000-06-19 4:11 ` Gary Thomas
2000-06-16 8:29 Alfredo Knecht
[not found] ` <XFMail.000616095000.gthomas@redhat.com>
2000-06-16 12:29 ` Alfredo Knecht
2000-06-16 13:34 ` Gary Thomas
2000-06-16 6:39 Rene.Affourtit
2000-06-16 7:03 ` Gary Thomas
2000-06-12 12:51 Alfredo Knecht
2000-06-10 19:55 Alfredo Knecht
2000-06-11 4:38 ` Gary Thomas
2000-06-12 1:19 ` Alfredo Knecht
2000-06-12 6:10 ` Gary Thomas
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=OF6BA11BFF.DEB53E41-ONC1256903.0042EBA1@pemstar.nl \
--to=rene.affourtit@pemstar.nl \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=gary@ares.chez-thomas.org \
--cc=gthomas@redhat.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).