CubeMX 4.13.0 bug - com.st.microxplorer.codegenerator.fctDefinition@2f970d

[vromanov]

Posted on March 15, 2016 at 13:53

After I switch to new CubeMX version code generation is broken.

In main.c file stange function names generated instead of init functions.

@@ -78,11 +78,11 @@ int main(void)

   SystemClock_Config();

   /* Initialize all configured peripherals */

-  MX_GPIO_Init();

-  MX_CAN1_Init();

-  MX_CAN2_Init();

-  MX_IWDG_Init();

-  MX_USART1_UART_Init();

+  com.st.microxplorer.codegenerator.fctDefinition@2f970d();

+  com.st.microxplorer.codegenerator.fctDefinition@1147aa8();

+  com.st.microxplorer.codegenerator.fctDefinition@12a4992();

+  com.st.microxplorer.codegenerator.fctDefinition@b16b36();

+  com.st.microxplorer.codegenerator.fctDefinition@cc1652();

   /* USER CODE BEGIN 2 */

@@ -97,7 +97,7 @@ int main(void)

[Nesrine M_O]

Posted on March 15, 2016 at 14:09

Hi Vladimir Romanov,

Thank you for your feedback. The issue has been reported internally.

-Syrine-

[stm32cube-t]

Posted on March 16, 2016 at 11:25

Hello Vladimir,

Can you please send us the .ioc file so that we reproduce your issue.

Can you also provide the log files saved under .stm32cubemx in your user directory.

thank you.

[vromanov]

Posted on March 17, 2016 at 07:52

How to reproduce

1) Open usb2can.ioc. Generate code. Observe src\main.c file

2) Close

3) Edit usb2can.ioc. Change

ProjectManager.FirmwarePackage=STM32Cube FW_F4 V1.1

to

ProjectManager.FirmwarePackage=STM32Cube FW_F4 V1.0

4) Open & generate. Problem gone

________________

Attachments :

STM32CubeMX.log : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006Htis&d=%2Fa%2F0X0000000aW9%2FATYcwymfFkUUqq5tXqunF6p0uQRUpbY_F8sUvCd9zcg&asPdf=false

usb2can.ioc : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006Htj2&d=%2Fa%2F0X0000000aWD%2FtquugVCUhuhnV7diKgHNgI3Lgs5isGViYwKifQ.U0pc&asPdf=false

[stm32cube-t]

Posted on March 17, 2016 at 09:42

Hello Vladminir,

This problem will be fixed in next CubeMX release 4.14.

Best regards