Skip to main content
Miha Mohor?i?
Miha Mohor?i?
Associate
October 11, 2017
Question

STM32CubeMX PLLSAI config for STM32L4

  • October 11, 2017
  • 1 reply
  • 1189 views
Posted on October 11, 2017 at 21:31

Thank you for your response.So far this solvesthe issue.

I will highjack this thread to ask additional questions.

Ido not know if this is also connected with 1.9.0 or it is a known issue (samePLLSAI1 clk config, but with additional peripherals, on 1.6.0 works).I am using custom board with STM32L476 on it.

I use CubeMX to generate code, i only set SD, JTAG, and RCC peripherals Clock config as shown on provided image:

0690X00000608a6QAA.png

Generated project (without changing anything in it) successfully builds, but itfails in file

''stm32l4xx_hal_rcc_ex.c'' line 2948(using 1.9.0 package)

#if !defined(RCC_PLLSAI1M_DIV_1_16_SUPPORT)
 || 
 (((READ_BIT(RCC->PLLCFGR, RCC_PLLCFGR_PLLM) >> RCC_PLLCFGR_PLLM_Pos) + 1U) != PllSai1->PLLSAI1M)
#endif�?�?�?�?

(it eventually evaluatesto ''[7]+1 !=1'').

I admit i did not research this further, but it is the first time i generated project with CubeMX and peripheral timing asserts failed on such configuration. And a general question. What is the state of STM provided eMMC (with possible FatFs) peripheral code for L4 family of cards? Will it beprovided at anytime, or will it always generate placeholders in code?
    This topic has been closed for replies.

    1 reply

    Miha Mohor?i?
    Miha Mohor?i?Author
    Associate
    October 23, 2017
    Posted on October 23, 2017 at 14:32

    quick updates, if in future somebody gets to similar problem.

    There is a missing line in system clock config*

    PeriphClkInit.PLLSAI1.PLLSAI1M = 1;

    Second issue was not setting 'SDMMCCLK divider factor' in 'Configuration->SDMMC1' window.

    I set it to 250 so i am under 200KHz (i didn'texperiment with other values), for beginning of communication with eMMC card. This seems tobe OK for my configuration. Adapt as need for your PLL config. I will try higher freqs when my eMMC driver will be stable.

    That sadly also means myquestion about stable eMMC driver for L4 is still valid

    :)

    * i recall i found the issue already reported somewhere on this forum, but i can not find the thread again...Something with new CubeMX version not including this line...

     

     

    Edit: Found the thread:

    https://community.st.com/thread/43671-cubemx-4221-bug

    Terms & ConditionsAccessibility statement