From: Andrew Lunn <andrew@lunn.ch>
To: Nodir Qodirov <nodir.qodirov@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] eCos heartbeat function handler
Date: Sun, 19 Jul 2009 08:18:00 -0000 [thread overview]
Message-ID: <20090719081846.GE20164@lunn.ch> (raw)
In-Reply-To: <186ad4050907190108s119964a5x26d74ee8701ec52c@mail.gmail.com>
> 2) Where should I specify (some assembler file...) which function to
> call on each heartbeat?
Take a look at:
http://ecos.sourceware.org/docs-latest/user-guide/clocks-and-alarm-handlers.html
Call
cyg_alarm_initialize(test_alarmH, cyg_current_time()+1, 1);
and you alarm function will be called every tick.
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
next prev parent reply other threads:[~2009-07-19 8:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-19 8:08 Nodir Qodirov
2009-07-19 8:18 ` Andrew Lunn [this message]
2009-07-19 14:07 ` Nodir Qodirov
2009-07-19 14:47 ` Christophe Coutand
2009-07-21 6:52 ` Nodir Qodirov
2009-07-21 7:27 ` Christophe Coutand
2009-08-05 11:22 ` Ormund Williams
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=20090719081846.GE20164@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=nodir.qodirov@gmail.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).