From: Satish Kumar <satish@bvt.sc.sanyo.co.jp>
To: Mahesh <mahesh@cranessoftware.com>
Cc: ecos <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Spurious interrupt
Date: Thu, 09 Oct 2003 00:42:00 -0000 [thread overview]
Message-ID: <20031009093914.16F2.SATISH@bvt.sc.sanyo.co.jp> (raw)
In-Reply-To: <1065602396.11174.15.camel@MAHESH>
well, it seems that u have not defined the RTC interrupt vector in ur
hal_platform_ints.h file..
firstly check if u r RTC interrupts are gettin invoked..? if yes the
corresponding ISR routined should be called..put a breakpoint in ur
ISR routine and debug ur code.
this will help u to diagnose ur code..
satish
On 08 Oct 2003 14:09:56 +0530
Mahesh <mahesh@cranessoftware.com> wrote:
> Hi,
>
>
> 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.
>
> The program is going into spurious INTR code.
> What is this spurious interrupt?
> Is this the reason for tick function not to be called and second alarm
> not to be triggerd ?
>
>
> Plz reply for this mail.
> 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
> --
> 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
--
Satish Kumar <satish@bvt.sc.sanyo.co.jp>
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
prev parent reply other threads:[~2003-10-09 0:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NMEDLDELHPEFHOMFIJBHMEPECOAA.rcc@jennic.com>
2003-10-01 8:31 ` [ECOS] second alarm not triggering Mahesh
2003-10-07 5:06 ` Mahesh
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 [this message]
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=20031009093914.16F2.SATISH@bvt.sc.sanyo.co.jp \
--to=satish@bvt.sc.sanyo.co.jp \
--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).