public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
* RE: timer -> interrupt
@ 2004-10-22 15:11 Daly, Jeffrey
  2004-10-22 15:18 ` Sicheri Marco
  0 siblings, 1 reply; 3+ messages in thread
From: Daly, Jeffrey @ 2004-10-22 15:11 UTC (permalink / raw)
  To: eCos Dev.List

Uh.... CPU? Platform?

>-----Original Message-----
>From: ecos-devel-owner@sources.redhat.com [mailto:ecos-devel-
>owner@sources.redhat.com] On Behalf Of Sicheri Marco
>Sent: Friday, October 22, 2004 11:07 AM
>To: eCos Dev.List
>Subject: timer -> interrupt
>
>I All,
>I need to create a timer that cause an interrupt.
>Oh yes, the cyg_alarm_xxx work fine! But the resolution (tick) isn't
>sufficient... :o(
>My timer must count and each 100us (time between 100us and 800us) cause
a
>interrupt, so that my interrupt routine can work.
>How can i do it?
>Normaly I programming the CPU registers with time and interupt vector.
But
>in eCos: How do i do?
>Thanks,
>
>Ossequi,  (Best Regards/Obrigado)
>Marco SICHERI
>CTS electronics  - R&D Department
>phone: +39 0125 235637, +39 0125 235630
>e-mail: m.sicheri@ctsgroup.it
>http://www.ctsgroup.it

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: timer -> interrupt
  2004-10-22 15:11 timer -> interrupt Daly, Jeffrey
@ 2004-10-22 15:18 ` Sicheri Marco
  0 siblings, 0 replies; 3+ messages in thread
From: Sicheri Marco @ 2004-10-22 15:18 UTC (permalink / raw)
  To: Daly, Jeffrey, eCos Dev.List

Oh Yes sorry, I have:
Samsung S3C44B0X arm7

Ossequi,  (Best Regards/Obrigado)
Marco SICHERI
CTS electronics  - R&D Department
phone: +39 0125 235637, +39 0125 235630
e-mail: m.sicheri@ctsgroup.it
http://www.ctsgroup.it


----- Original Message ----- 
From: "Daly, Jeffrey" <jeffrey.daly@intel.com>
To: "eCos Dev.List" <ecos-devel@sources.redhat.com>
Sent: Friday, October 22, 2004 5:10 PM
Subject: RE: timer -> interrupt


> Uh.... CPU? Platform?
> 
> >-----Original Message-----
> >From: ecos-devel-owner@sources.redhat.com [mailto:ecos-devel-
> >owner@sources.redhat.com] On Behalf Of Sicheri Marco
> >Sent: Friday, October 22, 2004 11:07 AM
> >To: eCos Dev.List
> >Subject: timer -> interrupt
> >
> >I All,
> >I need to create a timer that cause an interrupt.
> >Oh yes, the cyg_alarm_xxx work fine! But the resolution (tick) isn't
> >sufficient... :o(
> >My timer must count and each 100us (time between 100us and 800us) cause
> a
> >interrupt, so that my interrupt routine can work.
> >How can i do it?
> >Normaly I programming the CPU registers with time and interupt vector.
> But
> >in eCos: How do i do?
> >Thanks,
> >
> >Ossequi,  (Best Regards/Obrigado)
> >Marco SICHERI
> >CTS electronics  - R&D Department
> >phone: +39 0125 235637, +39 0125 235630
> >e-mail: m.sicheri@ctsgroup.it
> >http://www.ctsgroup.it
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* timer -> interrupt
@ 2004-10-22 15:04 Sicheri Marco
  0 siblings, 0 replies; 3+ messages in thread
From: Sicheri Marco @ 2004-10-22 15:04 UTC (permalink / raw)
  To: eCos Dev.List

I All,
I need to create a timer that cause an interrupt.
Oh yes, the cyg_alarm_xxx work fine! But the resolution (tick) isn't
sufficient... :o(
My timer must count and each 100us (time between 100us and 800us) cause a
interrupt, so that my interrupt routine can work.
How can i do it?
Normaly I programming the CPU registers with time and interupt vector. But
in eCos: How do i do?
Thanks,

Ossequi,  (Best Regards/Obrigado)
Marco SICHERI
CTS electronics  - R&D Department
phone: +39 0125 235637, +39 0125 235630
e-mail: m.sicheri@ctsgroup.it
http://www.ctsgroup.it

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-10-22 15:18 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-10-22 15:11 timer -> interrupt Daly, Jeffrey
2004-10-22 15:18 ` Sicheri Marco
  -- strict thread matches above, loose matches on Subject: below --
2004-10-22 15:04 Sicheri Marco

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).