This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Initialization routines take too long?
- To: 'Grant Edwards' <grante at visi dot com>
- Subject: RE: [ECOS] Initialization routines take too long?
- From: Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>
- Date: Fri, 10 Nov 2000 12:09:55 -0800
- Cc: ecos-discuss at sources dot redhat dot com
> -----Original Message-----
> From: Grant Edwards [mailto:grante@visi.com]
> Subject: Re: [ECOS] Initialization routines take too long?
>
>
> On Fri, Nov 10, 2000 at 11:57:05AM -0800, Fabrice Gautier wrote:
>
> > > It seems that if my first 10ms timer tick occurs before system
> > > initialization is complete, something gets corrupted and the
> > > system crashes in various different ways.
> >
> > Why should your timer be initialized before everything it needs is
> > initialized?
>
> I'm not sure what you mean. The timer doesn't need anything
> else to be initialized before it is initialized.
I meant that maybe your timer IRQ handler used some classes (Counter, Alarm
maybe...) which constructor had not been called before your handler is
called.
> > Maybe it's a problem in the constructors priority order.
>
> I think it's more likely a problem with what happens when the
> ARM IRQ is finally enabled. It appears that the system crashes
> if there is a pending interrupt when that happens.
Strange, that would mean you can't disable and reenable the IRQ without
problem...
--
Fabrice Gautier
fabrice_gautier@sdesigns.com