From: Mahesh <mahesh@cranessoftware.com>
To: mohanlal jangir <mohanlaljangir@hotmail.com>
Cc: radhakrishnan R <radhaamanji@yahoo.co.uk>,
ecos <ecos-discuss@sources.redhat.com>
Subject: [ECOS] thanks for the support Re: [ECOS] stops at start function
Date: Tue, 14 Oct 2003 09:36:00 -0000 [thread overview]
Message-ID: <1066122702.2531.6.camel@MAHESH> (raw)
In-Reply-To: <Law11-OE54D7G3Lbc1A00002ca0@hotmail.com>
Hi,
I got the error in my problem.
I had allocated a pointer to a structure,but in this particular
flow,it missed the assignment of address of structure to the pointer and
hence the pointer was pointing to 0x0.
It was changing this address contents and hence getting stuck.
Thanks for the support the group gave to me.It was really a good
experience.
Once again thanks all
Thanks and Regards
Mahesh
On Tue, 2003-10-14 at 10:13, mohanlal jangir wrote:
>
> > 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
>
>
--
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
prev parent reply other threads:[~2003-10-14 9:36 UTC|newest]
Thread overview: 4+ 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
2003-10-14 9:36 ` Mahesh [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=1066122702.2531.6.camel@MAHESH \
--to=mahesh@cranessoftware.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=mohanlaljangir@hotmail.com \
--cc=radhaamanji@yahoo.co.uk \
/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).