public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: unassigned@bugs.ecos.sourceware.org
Subject: [Bug 1001721] New: Watchdog driver for stm32 MCU
Date: Fri, 04 Jan 2013 09:52:00 -0000 [thread overview]
Message-ID: <bug-1001721-777@http.bugs.ecos.sourceware.org/> (raw)
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001721
Summary: Watchdog driver for stm32 MCU
Product: eCos
Version: CVS
Platform: stm32e_eval (ST STM3210E EVAL board)
OS/Version: Cortex-M
Status: UNCONFIRMED
Severity: enhancement
Priority: low
Component: Watchdog
AssignedTo: unassigned@bugs.ecos.sourceware.org
ReportedBy: ilijas@siva.com.mk
CC: ecos-bugs@ecos.sourceware.org
Class: Advice Request
Created an attachment (id=2020)
--> (http://bugs.ecos.sourceware.org/attachment.cgi?id=2020)
Watchdog device driver
A driver for stm32's Independent Watchdog (IWDG). It has been tested on
STM3210E-EVAL evaluation board, as well as on our proprietary board. Should
work with F4 (cortexm4) stm32 chips too, but not tested yet. This patch
contains the driver itself and amendments to ecos.db.
IWDG timeout (resolution) is based on LSI, an RC clock internal to stm32. This
time period can be configured by specifying both prescaler and reload value.
For convenience, the configtool displays the resulting timeout in microseconds,
calculated on nominal value of LSI clock.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2013-01-04 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 9:52 bugzilla-daemon [this message]
2013-01-04 9:55 ` [Bug 1001721] " bugzilla-daemon
2013-01-04 13:19 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2013-01-04 9:52 [Bug 1001721] New: " bugzilla-daemon
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=bug-1001721-777@http.bugs.ecos.sourceware.org/ \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=unassigned@bugs.ecos.sourceware.org \
/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).