public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: mekala natarajan <mekala_natarajan@yahoo.com>
To: Jonathan Larmour <jlarmour@redhat.com>,
	"Pamulapati, Indrasena \(CTS\)" <pindrase@chn.cognizant.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Watchdog Device
Date: Tue, 15 May 2001 01:44:00 -0000	[thread overview]
Message-ID: <20010515084420.67750.qmail@web9604.mail.yahoo.com> (raw)
In-Reply-To: <3B001BBB.E329435A@redhat.com>

Is watchdog driver available for MBX evaluation
board(MBX starter kit-MPC860).

Regards,mekala




--- Jonathan Larmour <jlarmour@redhat.com> wrote:
> "Pamulapati, Indrasena (CTS)" wrote:
> > 
> > Hi,
> > 
> > I have a doubt regarding the use of the watchdog
> device.
> > 
> > Can I program a watchdog device to interrupt my
> application after a
> > particular delay i.e., can I use the Watchdog
> device as a delay mechanism
> > instead of using the "delay" system clock provided
> by the OS.
> > 
> > The reason for this is, I need a particular
> application of mine to go to the
> > " wait " state for a time that is lower than the
> tick value I am using. And
> > I dont want to reduce the value of the system
> tick. For example, if I am
> > using a tick value of 10millisec I can make my
> application sleep for only an
> > integral multiple of 10millisec. But I want my
> application to sleep for a
> > time less than 10millisec, say for 10microsec.
> > In this case I can not use the " delay " system
> call provided by eCos
> > because it takes a parameter only in terms of
> ticks.
> 
> You can only interface with the watchdog support
> with C++. See
> io/watchdog/VERSION/include/watchdog.hxx. You need
> to instantiate a
> Cyg_Watchdog_Action object, and then install it.
> 
> But will your watchdog have any finer granularity
> than that? If this is a
> PC, have you written your own hardware watchdog
> driver for some watchdog
> hardware on your board? Because eCos doesn't have
> any for x86, and just
> emulates it with the system clock.
> 
> An alternative (admittedly undocumented) feature is:
> 
> #include <cyg/hal/hal_if.h>
> CYGACC_CALL_IF_DELAY_US(usec);
> 
> which delays for usec microseconds. Also enable
> CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_DELAY_US in your
> eCos configuration.
> 
> Jifl
> -- 
> Red Hat, Rustat House, Clifton Road, Cambridge, UK.
> Tel: +44 (1223) 271062
> Maybe this world is another planet's Hell -Aldous
> Huxley || Opinions==mine


__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/

  reply	other threads:[~2001-05-15  1:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-13 21:28 Pamulapati, Indrasena (CTS)
2001-05-14 10:54 ` Jonathan Larmour
2001-05-15  1:44   ` mekala natarajan [this message]
2001-05-17  0:10     ` Jonathan Larmour
2001-05-13 21:42 Pamulapati, Indrasena (CTS)
2001-05-17  4:08 Doug Fraser

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=20010515084420.67750.qmail@web9604.mail.yahoo.com \
    --to=mekala_natarajan@yahoo.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jlarmour@redhat.com \
    --cc=pindrase@chn.cognizant.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).