public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Alan Bowman <alan.michael.bowman@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Fwd: [ECOS] Interrupt stacking issues
Date: Thu, 19 Jul 2012 10:11:00 -0000	[thread overview]
Message-ID: <CAGT=SvKTrDKr6ZihzJJZ2BjysKvr0eKzy=JkEveR1Mr3wL3yjg@mail.gmail.com> (raw)
In-Reply-To: <CAGT=Sv+C1C2Tqt05uLzphZfc=dCrhfOBBcDJwYg6uhKMFs1pKA@mail.gmail.com>

Sorry - forgot to send it to the mailing list...


---------- Forwarded message ----------
From: Alan Bowman <alan.michael.bowman@gmail.com>
Date: 19 July 2012 11:10
Subject: Re: [ECOS] Interrupt stacking issues
To: Martin Hans <mha@sophion.com>


> what are you using the serial port for?

I'm sending commands to my board, and some of them run to hundreds of
characters long.  I'm also receiving responses back, although I've
never had any issue with that side of the link.  I have three ports in
use, and I think I've seen the same issue with all three.  It's more
repeatable with one, though, as I have more control over the data
being sent.

> I've had the problem that I would miss interrupts because I was using diag_printf. This function apparently disables interrupts. Switching to printf and configuring printf such that it is interrupt driven fixed that situation for me.

I don't think this is quite the same thing.  I don't think I'm missing
interrupts (at least, I'm definitely not when I have a "working"
configuration).  When it breaks, though, I have what seems to be the
same interrupt piled on top of itself a load of times until the stack
overflows.  It's like there's a place where the old ISR is still on
the stack when it gets re-enabled and run again... and again.. etc.
It's more likely the DSR/scheduler, rather than the ISR itself,
though.

Alan

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

  parent reply	other threads:[~2012-07-19 10:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19  9:46 Alan Bowman
2012-07-19  9:58 ` Martin Hans
     [not found]   ` <CAGT=Sv+C1C2Tqt05uLzphZfc=dCrhfOBBcDJwYg6uhKMFs1pKA@mail.gmail.com>
2012-07-19 10:11     ` Alan Bowman [this message]
2012-07-19 10:10 ` Manuel Borchers
2012-07-19 10:22   ` Alan Bowman
2012-07-19 15:46 ` Bernard Fouché
2012-07-19 16:28   ` Alan Bowman
2012-07-19 16:58     ` Bernard Fouché
2012-07-23  8:42       ` Alan Bowman

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='CAGT=SvKTrDKr6ZihzJJZ2BjysKvr0eKzy=JkEveR1Mr3wL3yjg@mail.gmail.com' \
    --to=alan.michael.bowman@gmail.com \
    --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).