This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: lpc2xxx timer interrupt
- From: Sergei Gavrikov <w3sg at SoftHome dot net>
- To: Shusharin Alexey <mrfinch at mail dot ru>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Mon, 28 May 2007 11:04:00 +0300
- Subject: Re: [ECOS] lpc2xxx timer interrupt
- References: <465A68C0.4040405@mail.ru>
Ð ÐÐÐ, 28/05/2007 Ð 12:29 +0700, Shusharin Alexey ÐÐÑÐÑ:
> Hello,
>
> I'm trying to port eCos to my platform (ARM7, LPC2292, my own board). My
> driver should scan a hardware with 100 Hz frequency, but the variant
> layer of HAL is using both timers.
> Is there some method to add call of my function to the system timer
> interrupt routine without modifying the variant and architecture code?
> Or does anybody know other solution of this problem?
100 Hz latency isn't a hard-timing polling. So, you can use one eCos
thread to fullfil that work with a cyg_thread_delay(1) waiting. If you
want really to release TIMER1 resources for your own needs (that timer
uses itself to implement the variant hal_delay_us() function) you would
can to declare the variant's hal_delay_us() with a WEAK attribute and
overwrite this function in your platform HAL, but, it seems, that is
more tricky.
-- Sergei
>
> Thanks
> Best regards
>
> Alexey Shusharin
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss