AnsweredAssumed Answered

STM32CubeMX generates conflicted prototypes for SystemClock_Config

Question asked by Sakurai.Hiroshi on Mar 28, 2017
Latest reply on May 10, 2018 by Joerg Schwedes

main.c generated by STM32CubeMX creates two different prototypes for SystemClock_Config. One with static and one without static.

 

/* Private function prototypes -----------------------------------------------*/
void SystemClock_Config(void);
void Error_Handler(void);
static void MX_GPIO_Init(void);
static void SystemClock_Config(void);

 

 

In addition, SystemClock_Config() is called twice in main.c.

 

int main(void)
{

...

/* Configure the system clock */
SystemClock_Config();

/* Initialize all configured peripherals */
MX_GPIO_Init();
SystemClock_Config();

 

 

Please try the attached .ioc file.

 

STM32CubeMX version is 4.20.0

STM32Cube FW_F7 V1.4.1

Attachments

Outcomes