This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: E7T timer0 interrupt issue ?
- From: Jonathan Larmour <jlarmour at redhat dot com>
- To: peter_ku <peter_ku at issc dot com dot tw>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Tue, 28 May 2002 20:28:35 +0100
- Subject: Re: [ECOS] E7T timer0 interrupt issue ?
- Organization: Red Hat UK Ltd.
- References: <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