From: Mahesh <mahesh@cranessoftware.com>
To: ecos <ecos-discuss@sources.redhat.com>
Subject: [ECOS] second alarm not triggering
Date: Tue, 07 Oct 2003 05:06:00 -0000 [thread overview]
Message-ID: <1065501590.1049.11.camel@MAHESH> (raw)
In-Reply-To: <1064995692.11195.37.camel@MAHESH>
Hi,
Sorry for not giving the details.
I am using eCos for Arm pid target.I am using sid for printf's
.I am working on PC only not on board.In my code i have 5 threads being
created in cyg_user_start function.Alarm's are being used by the threads
for some tasks.I am using real time clock for alarms.tick function is
called after the scheduler is started,but once the first alarm is
triggered,tick function is not called at all.So my second
alarm(different from first one) is not triggering and the program is
getting stuck.
Plz reply for this mail.
Thanks and Regards
Mahesh
On Wed, 2003-10-01 at 13:17, Robert Cragie wrote:
> Nothing like enough information. You can't expect any help from what you've
> written. Give detailed examples of failing source code, target system,
> configuration etc. etc.
>
> Robert Cragie, Design Engineer
>
> Direct: +44 (0) 114 281 4512
> _______________________________________________________________
> Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK
> http://www.jennic.com Tel: +44 (0) 114 281 2655 Confidential
> _______________________________________________________________
>
> > -----Original Message-----
> > From: ecos-discuss-owner@sources.redhat.com
> > [mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Mahesh
> > Sent: 01 October 2003 06:12
> > To: ecos
> > Subject: [ECOS] second alarm not triggering
> >
> >
> > Hi,
> > My first alarm is triggered but the second alarm is not triggering at
> > all.After the first alarm is triggered the tick function is not called
> > at all.What may be problem?
> > Thanks and Regards
> > Mahesh
> >
--
Mahesh M Patil
Software Engineer
Cranes Software International Limited
VasanthNagar
Bangalore
Mobile:9845579634
Office:2381740/1/2 Extn:234
www.cranessoftware.com
_______________________________________________
This email with any attachments is for the exclusive use of the intended
recipient/s & may contain confidential & legally privileged information.
If you are not the intended recipient pls notify the sender immediately
& delete the email from your system. Any unauthorised use, disclosure,
printing, dissemination, forwarding or copying of this mail is strictly
prohibited and unlawful.
Visit us at : http://www.cranessoftware.com
--
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-07 5:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NMEDLDELHPEFHOMFIJBHMEPECOAA.rcc@jennic.com>
2003-10-01 8:31 ` Mahesh
2003-10-07 5:06 ` Mahesh [this message]
2003-10-07 5:12 ` Satish Kumar
2003-10-07 5:47 ` Mahesh
2003-10-07 5:54 ` Satish Kumar
[not found] ` <1065602343.1050.11.camel@MAHESH>
2003-10-08 9:24 ` [ECOS] Spurious interrupt Mahesh
2003-10-08 10:18 ` Andrew Lunn
2003-10-09 0:42 ` Satish Kumar
2003-10-07 8:54 [ECOS] FW: [ECOS] second alarm not triggering Robert Cragie
[not found] ` <1065526549.1061.32.camel@MAHESH>
2003-10-07 12:08 ` Mahesh
2003-10-08 12:01 ` [ECOS] " Nick Garnett
-- strict thread matches above, loose matches on Subject: below --
2003-10-01 5:33 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=1065501590.1049.11.camel@MAHESH \
--to=mahesh@cranessoftware.com \
--cc=ecos-discuss@sources.redhat.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).