From: Jonathan Larmour <jlarmour@redhat.com>
To: peter_ku <peter_ku@issc.com.tw>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] E7T timer0 interrupt issue ?
Date: Tue, 28 May 2002 12:28:00 -0000 [thread overview]
Message-ID: <3CF3DA63.93E2297@redhat.com> (raw)
In-Reply-To: <000001c201a4$73ca5760$790114ac@issc.com.tw>
peter_ku wrote:
>
> I found the casue that I can't enter my ISR.
> Because I use timer0, if I change to timer1, everything is fine.
> I guess eCos use timer0 to do something, right ???
Yes the kernel uses it for all timing related operations.
> If I have to use timer0 ISR to do something , what should I do?
Obviously either you have to use some either timer, or change the eCos E7T
port to use some other timer.
Or if you aren't interested in using the eCos kernel, for your example
program you could maybe get away with just calling show_led_proc directly
after cyg_interrupt_enable(). You should remove the eCos kernel
(CYGPKG_KERNEL) completely to do this though as otherwise it will include
some startup code to attach its own interrupt handler to timer 0.
And also in that case you should use the driver API (e.g.
cyg_drv_interrupt_enable() etc.)
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2002-05-28 19:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 7:24 [ECOS] GNU tools combination for eCos peter_ku
2002-05-20 18:53 ` Jonathan Larmour
2002-05-20 20:31 ` [ECOS] E7T timer0 interrupt issue ? peter_ku
2002-05-20 20:56 ` Simoncc
2002-05-21 7:34 ` Gary Thomas
2002-05-22 8:22 ` peter_ku
2002-05-28 12:28 ` Jonathan Larmour [this message]
2002-05-20 20:41 ` [ECOS] GNU tools combination for eCos peter_ku
2002-05-21 7:44 ` Jonathan Larmour
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=3CF3DA63.93E2297@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=peter_ku@issc.com.tw \
/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).