Skip to main content
george239955_st
Associate II
April 16, 2013
Question

What documents describe how to confiure SPI, I2C and USART stm32l151rd

  • April 16, 2013
  • 11 replies
  • 2007 views
Posted on April 16, 2013 at 15:16

I can't find the relevant documents they don't seem to be listed with the  product

#lmgtfy:-stm32-resources
    This topic has been closed for replies.

    11 replies

    Tesla DeLorean
    Guru
    April 16, 2013
    Posted on April 16, 2013 at 15:31

    Google ''STM32L151RD'', top hit is for ST's product page.

    Select ''Design Resource'' tab

    Scroll to ''Reference Manual''

    http://www.st.com/st-web-ui/static/active/en/resource/technical/document/reference_manual/CD00240193.pdf

    If this is inadequate for your purposes, refer also the firmware library with examples, and documentation for the protocol/interfaces in general.
    Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
    george239955_st
    Associate II
    April 16, 2013
    Posted on April 16, 2013 at 15:43

    thanks Clive,

    I'm trying to work out what the max baud rate for the SPI, I2C and USART when running from the 4.2 MHz MSI

    this doesn't seem to be covered in the reference manual, any idea what documents I could get this from.  I can't see what document would cover this in the STM32L151RD design resources.

    http://www.st.com/web/catalog/mmc/FM141/SC1169/SS1295/LN962/PF251634#

    Tesla DeLorean
    Guru
    April 16, 2013
    Posted on April 16, 2013 at 16:01

    The clock tree is described in the aforementioned manual, as are registers for the peripherals, and the clock dividers/prescalers which they configure.

    The USART speed will be limited by the rate of the APB to which it is attached, and the 8 times over sampling rate. If clocked at 4.2 MHz the highest baud rate would be 525 Kbaud. Observe also the ''USART block diagram'' for internal relationships.

    Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
    george239955_st
    Associate II
    April 16, 2013
    Posted on April 16, 2013 at 17:02

    thanks Clive,

    do you know why the reference manual shows 2 values of clock divider for each setting of the baud rate control register on page 715 of the reference manual RM0038?

    Tesla DeLorean
    Guru
    April 16, 2013
    Posted on April 16, 2013 at 17:15

    do you know why the reference manual shows 2 values of clock divider for each setting of the baud rate control register on page 715 of the reference manual RM0038?

    I'm look at RM0038 Rev 7, which figure/table is that?
    Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
    george239955_st
    Associate II
    April 16, 2013
    Posted on April 16, 2013 at 17:31

    27.5.1 page 744 on rev 7

    Tesla DeLorean
    Guru
    April 16, 2013
    Posted on April 16, 2013 at 17:58

    PDF sucks

    000: fPCLK/2

    100: fPCLK/32

    001: fPCLK/4

    101: fPCLK/64

    010: fPCLK/8

    110: fPCLK/128

    011: fPCLK/16

    111: fPCLK/256

    Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
    george239955_st
    Associate II
    April 16, 2013
    Posted on April 16, 2013 at 18:08

    thanks dude!

    Tesla DeLorean
    Guru
    April 16, 2013
    Posted on April 16, 2013 at 18:18

    Note ST Moderators and Technical Writers, there are several tables in this RM0038 document that run together in an unhelpful manner. Please resolve/address.

    0690X0000060502QAA.png
    Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
    waclawek.jan
    Super User
    April 16, 2013
    Posted on April 16, 2013 at 21:07

    This sort of typographical problems tends to appear across all manuals of the STM32 family, obviously as a result of copy/paste method of ''writing'' these documents. For example, this one is in RM0090 on page 838.

    I did not find it important to stress that when I submitted my list of findings (specifically addressing the STM32F4xx, but apparently many of them pertinent to other manuals too) some time ago, but now I am uncertain whether it shouldn't be said out more aloud... :|

    JW