This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: cyg_alarm_initilize
- From: Andrew Lunn <andrew at lunn dot ch>
- To: "vasantha.rajan" <vasantha dot rajan at cranessoftware dot com>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Tue, 4 Apr 2006 12:10:46 +0200
- Subject: Re: [ECOS] cyg_alarm_initilize
- References: <200604031940.49073.vasantha.rajan@cranessoftware.com>
On Mon, Apr 03, 2006 at 07:40:48PM +0530, vasantha.rajan wrote:
> I have some problem in cyg_alarn_initialize() API.
>
> Our code contains nearly 20 threads sheduled to run. In one particular
> thread we have cyg_alarm_initilize() api as give below,
> cyg_alarm_initialize(handle_alarmTbcn,cyg_current_time() + 10 , 0 );(ie my
> alarm triggers fo every 100ms)
>
> In my CDL i have my CYGNUM_HAL_RTC_NUMERATOR value as 1000000000 and
> CYGNUM_HAL_RTC_DENOMINATOR value as 100.
>
> My problem is the code strucks at some point, I think there is some problem
> with alarm api and kernel timer.
The timer code is very mature. The problem is more likely to be in
your code. Try enabling CYGPKG_INFRA_DEBUG.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss