Skip to main content
Visitor II
August 11, 2020
Question

STM32F429, I2C_CR2 register setting, maximum APB frequency...

  • August 11, 2020
  • 4 replies
  • 1711 views

Is the maximum APB frequency setting 36MHz or 50MHz? See the dm00031020, page 863. FREQ[5:0]: Peripheral clock frequency..."Higher than 0b100100: Not allowed"

0b100100 corresponds to 36MHz, not 50MHz. Hopefully this is just a document error. We are using APB1 at 45MHz. Here is a link to the manual:

https://www.st.com/resource/en/reference_manual/dm00031020-stm32f405415-stm32f407417-stm32f427437-and-stm32f429439-advanced-armbased-32bit-mcus-stmicroelectronics.pdf

Is this a typo in the manual or is APB1 really limited to 36MHz for I2C?

    This topic has been closed for replies.

    4 replies

    Super User
    August 11, 2020

    Obviously a typo, relic probably from 'F1.

    https://community.st.com/s/question/0D50X00009XkYWJSA3/i2c-config-on-stm32f446xx

    @Imen DAHMEN​ , can you please have a look at it.

    Thanks,

    JW

    Technical Moderator
    August 28, 2020

    Hello,

    Thank you for bringing this to my attention. I will raise it internally to correct the RM0090.

    The maximum frequency should be 45MHz with the overdrive for STM32F42x

    In the RM0090: Higher than 0b100100: Not allowed

    should be 0b101010:

    Bits 5:0 FREQ[5:0]: Peripheral clock frequency

    Higher than 0b101010: Not allowed

    "

    Best Regards,

    Imen

    Visitor II
    February 26, 2024

    Hello Imen,

     

    sure that 0b101010 for FREQ[5:0] is correct?

    It would mean 42 MHz, where 45 MHz would be 0b101101.

    But according to RM0090 Rev 9 not allowed?

     

    Best regards,

    Steffen

    Super User
    February 26, 2024

    Hi @sk-st ,

    RM0090 is currently at rev.20.

    Nonetheless, the said line should be fixed there:

    waclawekjan_0-1708951978933.png

    @Imen.D, can you please have a look at this? Thanks.

    JW

    Technical Moderator
    February 26, 2024

    Hi @waclawek.jan,

    Thank you for raising this up.

    An internal ticket ID 91710 is submitted in order to fix this issue.

    Super User
    February 26, 2024

    Thanks, Imen.

    JW