Coldfire (MCF5235) Interrupt Problem

[Ivica Eftimovski]

Eric,

Thanks for the quick reply. The printf was just a dummy there, but I replaced it with the global that increments from zero if the ISR is entered and it has never updated. I must be doing something wrong, but cannot figure out what.



From: Eric Norum [mailto:wenorum at lbl.gov]
Sent: Friday, May 11, 2012 12:05 PM
To: Ivica Eftimovski
Cc: rtems-users at rtems.org
Subject: Re: Coldfire (MCF5235) Interrupt Problem

On May 11, 2012, at 8:55 AM, Ivica Eftimovski wrote:


Hi all,

I am just starting with RTEMS and I am trying to interface the MCF5235 BCC board to our existing hardware. I am trying to set it to use *IRQ4, which should have fixed level/priority.

When I execute the code noted below, the interrupts are disabled properly, the vector seems set and interrupts are re-enabled. But anytime I ground*IRQ4 (default high) line while my example program is running, I do not vector to the ISR.

I fashioned my code using the clock/network/console code as guide, and those work great.

Can anyone please give me a hint of what am I doing wrong?

Not sure about any of the MCF5235 code, but one thing for sure that is wrong is that you must not call printf from an interrupt handler...

Try declaring a volatile global variable -- increment it in the interrupt handler and print it in the main thread.

--
Eric Norum
wenorum at lbl.gov<mailto:wenorum at lbl.gov>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20120511/77ac7349/attachment-0001.html>