This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Clock problem with eCos 1.3.1 using uITRON compatibility
- From: Jonathan Larmour <jlarmour at redhat dot com>
- To: jecer at Rational dot Com
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Fri, 25 Jan 2002 19:37:48 +0000
- Subject: Re: [ECOS] Clock problem with eCos 1.3.1 using uITRON compatibility
- Organization: Red Hat UK Ltd.
- References: <1E0ABA7B578BCC40AA5EED022EFE32E6019622C1@sca-can1it01.rational.com>
jecer@Rational.Com wrote:
>
> Hello,
>
> I am using eCos 1.3.1 with uITRON compatibility on the i386 pc target. The
> kernel is almost default. It was created by:
>
> > ecosconfig new pc uitron
> > ecosconfig resolve
> > ecosconfig check
> > ecosconfig tree
>
> The only thing that I changed is the memory layout. Anyhow, here is the
> problem.
May I first suggest using anonymous CVS? We're gearing up for an eCos 2.0
release because 1.3.1 is so old.
> It seems that the clock is not working at all. Any call to dly_tsk() and to
> tslp_tsk() will not return even when supplied with a positive argument. I
> also tried the supplied uITRON compatibility tests. test1 hangs after the
> first call to dly_tsk(), and testintr fails with the following:
You could increment some global variable in
kernel/VERSION/src/common/clock.cxx in both Cyg_RealTimeClock::isr() and
Cyg_RealTimeClock::dsr() to see if the int is being received at all.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine