cancel
Showing results for 
Search instead for 
Did you mean: 

STM32CubeMX generates conflicted prototypes for SystemClock_Config

Hiroshi Sakurai
Associate II
Posted on March 28, 2017 at 02:36

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

#stm32cubemx
9 REPLIES 9
Khouloud GARSI
Lead II
Posted on March 28, 2017 at 11:42

Hi

Sakurai.Hiroshi

,

You are using old versions of CubeMX and F7 firmware package:

0690X00000606dwQAA.png

Please use the most recent versions:

  • CubeMX V4.0
  • STM32Cube FW_F7 V1.6.0

-> No issue detected using updated versions.

Khouloud.

Posted on March 28, 2017 at 13:12

Hi Khouloud,

Isn't it a regression in CubeMX 4.20 because CubeMX 4.16 didn't have such a problem. 

I'd appreciate If you could make the CubeMX compatible with older versions of FW_F7 as much as possible. Catching up with the latest version is not always an option, especially in developing firmware. Even a minor change requires a lot of testing as it may cause a timing problem or a crash. 

If you don't have plan to support older versions of FW_F7, please provide us the link to download older versions of CubeMX. I've only found the link to download the latest version. 

Hiroshi

Khouloud GARSI
Lead II
Posted on March 28, 2017 at 15:54

Hi

Sakurai.Hiroshi

‌,

Thanks for your understanding.

Khouloud.

Posted on March 29, 2017 at 02:34

Hi Khouloud,

Every version of CubeMX is dedicated to a specified firmware package versions.

OK. Then, will you provide the link to download older versions of CubeMX?

I've updated to 4.20 to prevent the nasty bug in 4.16. I'll try to find a version that works with 

FW_F7 V1.4.1.

Hiroshi

Khouloud GARSI
Lead II
Posted on March 29, 2017 at 17:07

Hi

Sakurai.Hiroshi

‌,

The

STM32Cube FW_F7 V1.4.1 is only compatible with the CubeMX V4.0 and V4.1.

Sorry, but we provide only the last updated version of CubeMX.

Thanks for your understanding.

Khouloud.

Posted on March 30, 2017 at 08:36

Hi Khouloud,

Do you mean that there's no way to use CubeMX v4.16 anymore once you updated to CubeMX 4.20?

You don't understand what firmware development is.

If you provide only the latest version of CubeMX, the latest version should support older versions of FW. Or you shoud put a big warning on the download page which describes this pitfall.

I'm disappointed by the support which doesn't support a user. 

stm32cube-t
Senior III
Posted on March 30, 2017 at 18:40

Dear user,

Please find here the 4.16 version:

https://drive.google.com/open?id=0B3TGwFlypwI6NE5ncXVOV0ZpMjg

To avoid such situation, you may want to download CubeMX installations from st.com instead of the self-upgrade. This way you can keep both, your previously installed version and the newly released.

A 4.20.1 patch release will be delivered soon to fix 4.20 issues.

Best regards

Posted on March 29, 2018 at 14:30

Good day!

Problem of duplicate SystemClock_Config is actual now in version 4.25.0

Joerg Schwedes
Associate
Posted on May 10, 2018 at 07:23

Hello,

i have the same issue with CubeMx 4.25.0 and firmware package 'stm32cube_fw_f0_v140'.

It is also no option for me updating firmware to latest version.

Unfortunately I lost the old CubeMx 4.11 which was working with firmware v140.

So could you please send me a download link for 4.11, or do you plan to fix the '

SystemClock_Config' issue in CubeMx soon for any older firmware ?

regards,

Joerg