public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1002027] New: STM32 HSI clock initialized incorrectly
Date: Sat, 06 Dec 2014 22:30:00 -0000	[thread overview]
Message-ID: <bug-1002027-13@http.bugs.ecos.sourceware.org/> (raw)

Please do not reply to this email, use the link below.

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1002027

            Bug ID: 1002027
           Summary: STM32 HSI clock initialized incorrectly
           Product: eCos
           Version: CVS
            Target: stm32f4dis (ST STM32F4DISCOVERY)
  Architecture/Host Cortex-M
                OS:
            Status: UNCONFIRMED
          Severity: major
          Priority: low
         Component: HAL
          Assignee: unassigned@bugs.ecos.sourceware.org
          Reporter: mmajchrzycki@antmicro.com
                CC: ecos-bugs@ecos.sourceware.org

Created attachment 2557
  --> http://bugs.ecos.sourceware.org/attachment.cgi?id=2557&action=edit
Patch to fix HSI bug in STM32 architecture

In any STM32 platform, selecting internal RC oscillator (HSI) as clock source
causes a generate unstable frequency. This is because the HSITRIM field in
RCC_CR is cleared during clock initialization process.
Restoration of the default value of HSITRIM restores generation of stable
frequency by internal RC oscillator.

In attachment is a patch which fixes bug that is mentioned above.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


                 reply	other threads:[~2014-12-06 22:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-1002027-13@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-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).