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]
Other format: [Raw text]

Re: Mail Box Timeout


Hello Nick,

Yes. I can't catch any clock interrupt.
I have tried some similar test program, and those program can't run nomally.
Then, my platform is Richfield with processor IXP425.

Through further trace, some functions don't run just like hal_hadware_init,
hal_IRQ_handler, cyg_instrument.

Best regards,


Chuck


----- Original Message -----
From: "Nick Garnett" <nickg@ecoscentric.com>
To: "Chuck Chen" <ycchen@zcom.com.tw>
Cc: "Eric de Jong" <list_ericdejong_10@gmx.net>;
<ecos-discuss@sources.redhat.com>
Sent: Tuesday, July 22, 2003 4:41 PM
Subject: Re: [ECOS] Mail Box Timeout


> "Chuck Chen" <ycchen@zcom.com.tw> writes:
>
> > Hello,
> >
> > Thanks.
> >
> > I add the cyg_scheduler_start(), and the system seems to be hanged.
> > I can't see any redboot messages from console.
> >
> > Besides, the real-time clock can't tick automatically.
> > If modfied the alarm initial to be cyg_alarm_initialize(alarm_hdl,
> > cyg_current_time()+10, 50), the alarm is never executed.
> >
>
> It looks like you are not getting clock interrupts. Check that the
> kernel test programs like kalarm0 or tm_basic run. If they run then
> it is likely that your application is doing something silly. If it
> does not run then there is something wrong with the HAL -- you don't
> mention what target you are using, so it is hard to be more specific.
>
> --
> Nick Garnett                    eCos Kernel Architect
> http://www.ecoscentric.com      The eCos and RedBoot experts
>


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


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