This is the mail archive of the ecos-discuss@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]

RE: Initialization routines take too long?



On 10-Nov-2000 Fabrice Gautier wrote:
>> -----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...

As far as I know, this is not a problem with any of our internal ports.
This is not to say that a problem does not exist, but we've never seen such.

However, note that the normal case is for interrupts to remain disabled,
sometimes for long periods, until the scheduler is started from the main
thread.  Is this how your application works [Grant]?

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