This is the mail archive of the ecos-devel@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: timer -> interrupt


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
> 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]