From: "mohanlal jangir" <mohanlaljangir@hotmail.com>
To: "Mahesh" <mahesh@cranessoftware.com>
Cc: "eCos Discussion" <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] stops at start function
Date: Tue, 14 Oct 2003 04:51:00 -0000 [thread overview]
Message-ID: <Law11-OE54D7G3Lbc1A00002ca0@hotmail.com> (raw)
In-Reply-To: <1066105298.1050.6.camel@MAHESH>
> I want first alarm to trigger only once.
> Second alarm i want to trigger is different from first one.
> But after my first alarm gets triggered,RTC ISR is not called at all
> and hence tick function is not called.So there is no increment in real
> time counter and hence no trigger.
> What may be the reason for ISR not to be called?
>
Do you mean, when your first alarm is triggered, the ISR registered is not
called!! If I understand your query properly, I would suggest you to check
following -
1. You are registering ISR, with cyg_alarm_create
2. Make 4th and 5th argument of cyg_alarm_create "global static". (Basically
I want to make sure, that valid memory is allocated for those arguments).
3. Make sure your alarm is really triggered. Can you send the code snippet,
which is creating and initialising the alarm?
Regards
Mohanlal
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-10-14 4:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 4:19 [ECOS] [Fwd: [Fwd: Re: [ECOS] stops at start function]] Mahesh
2003-10-14 4:28 ` [ECOS] stops at start function mohanlal jangir
[not found] ` <1066105298.1050.6.camel@MAHESH>
2003-10-14 4:51 ` mohanlal jangir [this message]
2003-10-14 9:36 ` [ECOS] thanks for the support " Mahesh
-- strict thread matches above, loose matches on Subject: below --
2003-10-10 8:48 Mahesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Law11-OE54D7G3Lbc1A00002ca0@hotmail.com \
--to=mohanlaljangir@hotmail.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=mahesh@cranessoftware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).