public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: qber_@poczta.onet.pl
To: ecos-devel@ecos.sourceware.org,
	Gian Maria <g_giacomello@yahoo.it>,
	jerzy dyrda <jerzdy@gmail.com>
Subject: RE: Re: STM32F107 on STM3210C-EVAL
Date: Mon, 28 Mar 2011 11:23:00 -0000	[thread overview]
Message-ID: <23137663-1e0ca441f77eb82df61226bca1165220@pkn7.m5r2.onet> (raw)

Hello again

W dniu 2011-03-28 12:47:07 użytkownik jerzy dyrda <jerzdy@gmail.com> napisał:
> Hello all,
> 
> On Monday 28 March 2011 11:51:45 qber_@poczta.onet.pl wrote:
> (...)
> > There is only one thing left - the RCC differences. In RM there is a
> > seperate section about RCC config for CL. But at the first look it seems
> > that registers are compatible.
> RCC registers are extended to support 2 extra PPL's with appropriate divider and multiplier.
> Main differences is that source of PLL clock it isn't anymore taken directly from HSE or HSE/2 clock 
> but it's introduced new divider PREDIV1 thus PLLSRC bit in RCC_CFGR register has partially 
> different meaning. And another issue is external crystal. It value is 25MHz not 8 MHz like in 
> STM3210E what causes need of using second PLL to produce CPU 72MHz.
> 
> HSE == 25MHz   /  PREDIV2 == 5 -> 5MHz   *  PLLMUL2 == 8 ->  
> 40MHz / PREDIV1 == 5 -> 8MHz * PLLMUL == 9 -> 72MHz = SYSCLK
> 
> It's looks ugly but above method it's used in ST source code for STM3210C evaluation board.
> 

It's not quite true. According to scheme and RM the clock can be takien from PLL2 or HSE directly. This is configured in RCC_CFGR2 bit 16
PREDIV1_SRC. Only the crystal have to be replaced on PCB.
> Best regards
> jerzy
> 
> 
Best regards
Qber


             reply	other threads:[~2011-03-28 11:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28 11:23 qber_ [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-22 19:15 Gian Maria
2011-03-28  9:55 ` qber_
2011-04-14 10:59   ` mlazcoz

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=23137663-1e0ca441f77eb82df61226bca1165220@pkn7.m5r2.onet \
    --to=qber_@poczta.onet.pl \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=g_giacomello@yahoo.it \
    --cc=jerzdy@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).