Fwd: RTEMS core: bad work with _Watchdog_* ?

[Brett Swimley]

Has any further progress been made with regard to this issue?  I was having
problems with a task hangning while using

rtems_task_wake_after( 1 );

Values > 1 seem to work fine.

As a test, I commented out the _ISR_Flash call as Joel suggested and it
_appears_ as if this has solved my problems (e.g. rtems_task_wake_after(1)
does not hang my task).


Regards,

Brett Swimley



> -----Original Message-----
> From: root at kampong.aedinc.net
> [mailto:root at kampong.aedinc.net]On Behalf
> Of Joel Sherrill
> Sent: Wednesday, February 06, 2002 7:41 AM
> To: ilya at continuum.ru
> Cc: rtems-users at oarcorp.com
> Subject: Re: Fwd: RTEMS core: bad work with _Watchdog_* ?
>
>
> Ilya Alexeev wrote:
>
> > > I have been working offline with Ilya and sent him the suggestion
> > > to comment out the _ISR_Flash in src/watchdoginsert.c.
> Then he should
> > > have a finer grain view of the problem.
> > >
> > > --joel
> >
> > Yes, after commenting out _ISR_Flash in src/watchdoginsert.c
> > my 'stress test' works fine.
> >
> > There were a some my incorrectness in the previous letter:
> > the application worked good with _ISR_Disable/Enable around the
> > _Watchdog_Insert_ticks only.
> >
>
> Just to double check... you now have removed the _ISR_Disable/Enable's
> you added and commented out the _ISR_Flash in src/watchdoginsert.c
> and it works.  Right?
>
> If so, then something is wrong with the critical section
> logic.  I wonder
> if we need to mark something as volatile.
>
>
> >
> > Ilya.
>