This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: spurious interrupts on scanf
Christian Mueller wrote:
hi!
there is no source, that is the problem...
at the moment the interrupt occures (the bad one) there is zero read out
of the interrupt register....
Sounds like it could be sort of race condition with interrupt acknowledgement.
thats why I thought, there is an interrupt but disappears when it is
read out (because there is some latency on the bus -> DMA)
level triggered interrupts... that's it! mine are level triggered but
the uart, i don't now... i will have to check...
A possibility is that you may have the interrupt acknowledge in the wrong
place, e.g. before the code has finished dealing with the cause of the
interrupt. (If that happens it may just assert the interrupt again straight
away).
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss