From: "Boni Jean" <zamdawg@hotmail.com>
To: ecos-discuss@sourceware.org
Subject: [ECOS] Triggering interrupt on the mpc5200 running eCos
Date: Thu, 15 Dec 2005 12:42:00 -0000 [thread overview]
Message-ID: <BAY16-F497ADB332DF41F4901453AC3B0@phx.gbl> (raw)
hi everybody!
i am working with the boa5200 evaluation board, which has an mpc5200 chip on
it.
i want an interrupt to be triggered, once i pull external pin /IRQ2 down
low.
I created an interrupt with the cyg_interrupt_create function, using the
vector
number 27 (from #define CYGNUM_HAL_INTERRUPT_IRQ2 which i found in
cyg/hal/var_intr.h).
I set the right bits in the Mpc5200's register MPC5XXX_ICTL_EENAB (in
cyg/hal/mpc5xxx).
The main problem is that i am not able to attach the interrupt to the global
interrupt
vector, using the cyg_interrupt_attach command. From debugging, i see that
the attach()
command calls the HAL_INTERRUPT_SET_LEVEL macro from intr.cxx
(in ecos/packages/kernel/current/src/intr.cxx). From there, it jumps to the
EMPTY function
cyg_hal_interrupt_set_level in var_intr.c (in
ecos/packages/hal/powerpc/mpc5xxx/current/src/var_intr.c).
It then jumps back to the macro HAL_INTERRUPT_IN_USE in the intr.cxx
function, then to the
macro HAL_INTERRUPT_ATTACH in intr.cxx, but nothing more is done.
I also checked out the mpc5200 register Main Interrupt Status All Register,
but
it does not indicate any pending interrupt, which means that the interrupt
has not been
attached.
please, HELP!!!!
-John-
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2005-12-15 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 12:42 Boni Jean [this message]
2005-12-15 13:55 ` Alluitz
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=BAY16-F497ADB332DF41F4901453AC3B0@phx.gbl \
--to=zamdawg@hotmail.com \
--cc=ecos-discuss@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).