Hi, @Amel NASRI
By the way, RCC clock auto configuration is also wrong.
but result showing:
which will mess up UART baud rate ( I have to chage UART clock source to HSI to get correct UART output, the old is PCLK1), same issue as the post yo...
Hi there, i configure power as PWR_DIRECT_SMPS_SUPPLY, but after generating project, both PWR_USE_LDO_SUPPLY and PWR_DIRECT_SMPS_SUPPLY are defined. This will cause program exception sometime, i have to remove USE_PWR_LDO_SUPPLY. I took several day...
Originally a reply in this thread: https://community.st.com/t5/stm32cubemx-mcus/bug-cubemx-should-warn-h7-users-against-pc2-c-pc3-c-pitfalls/td-p/708817 Hi,What's wrong with PC2_C and PC3_C??? I am using them as normal GPO on my board, but it's not ...
Hi Expert, syntax coloring is not functional when the code is long. Is this IDE restriction? How to fix this issue?for example, the hal_uart.c is not coloring.ThanksPeter
Hi, @Amel NASRI @Tesla DeLorean The above are not problems, this is routing step for MCU lockout. This is not stress of my post. I am asking why Both USE_PWR_LDO_SUPPLY and USE_PWR_DIRECT_SMPS_SUPPLY are defined during code generation. This will caus...
Hi, @djanovy I ran into same issue as you1. RCC clock generation is wrong.2. Both USE_PWR_LDO_SUPPLY and USE_PWR_DIRECT_SMPS_SUPPLY are defined.Not understand why ST has sucu low level issue. After you tried out FW_H7_1.12.1, are these issue resolved...
i was using code comparison, and no any clue found. Finally, i found the difference in complier setup inside of IDE.The consequence is board will never boot up, and ST-LINK can not find target. You have to set to boot from system memory to recover ...
