public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@ecoscentric.com>
To: Carlos Perilla <transfers@phaber.com>
Cc: ecos <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] eb40a Interrupt, TC
Date: Thu, 23 Oct 2003 14:34:00 -0000	[thread overview]
Message-ID: <m37k2w2fqc.fsf@miso.calivar.com> (raw)
In-Reply-To: <3F9575D1.6030509@phaber.com>

Carlos Perilla <transfers@phaber.com> writes:

> Well , finally I got two  timers running, with the conf I want, Now I
> need to capture the interrupts that my configuration is generating, as
> long as the TC_SR says the events that I have programed had passed but
> not attended.
> 

> 
> Im using two other threads to capture and transmit the data I get from
> here, still the Interrupt Isn't captured, and the program keeps
> waiting for the semaphore signal.
> 

You should not be calling cyg_interrupt_enable(). This is done
implicitly when the scheduler is started. Calling it before then can
allow interrupts to be delivered to code that is not yet ready.

The code you have posted seems fine as far as it goes. Check that you
have used the right vector number.

Your code does not show where you are setting up the timer  device. I
suspect that this is where the problems are to be found. Have you, for
example, set the correct interrupt enable bit for the timer mode you
are using.



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


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

      reply	other threads:[~2003-10-23 14:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21 18:07 Carlos Perilla
2003-10-23 14:34 ` 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=m37k2w2fqc.fsf@miso.calivar.com \
    --to=nickg@ecoscentric.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=transfers@phaber.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).