Bug in CubeMX with STM32H747 DualCore and AzureRTOS

[AZorn.1]

Hello, maybe I found a bug in CubeMX.

Actually it is not possible for me to generate Code for the DualCore derivates to get AzureRTOS active on BOTH cores.

After activating a new project with AzureRTOS selected for both cores, all of the port-*.c and *.h files are removed after further changes in GUI with new code generation.

This bug is very annoying, because using dualCore Azure an each Core is not usable in fact.

bestRegards

Alexander

[Haithem Rahmani]

Hi @AZorn.1​ 

Which STM32CubeMX version are you using?

could you share a sample .ioc project that shows the issue.

[AZorn.1]

Hello,

and thank you, for the fast response. Hopefully we can find a solution for this problem.

this is the first *.ioc directly after creating a new project.

[AZorn.1]

*.ioc after activating threadX for M4 AND M7 both Ports are available in Project Explorer, everything seems ok so far.

[AZorn.1]

*.ioc file after activating TIM1. Now the port-files for cortex_m4 are missing, the project is broken. Both Azure SoftwarePacks are still activated, but will not be exported correctly.

I am using STM32CubeIDE V1.7.0 with STM32CubeMX 6.3.0-RC5

best Regards

[Haithem Rahmani]

Hi,

Issue reproduced, could you try to remove the file '.mxproject' located under the root folder of your project then regenerate?

regards

Haithem.

[AZorn.1]

Hello,

thank you for this hint, seems that, after deleting .mxproject both ports are generated correct. But only once, after changing anything else in cubeMX, the port is missing again.

Is it necessary to delete this file, prior to every code generation, to be sure, all code is generated correctly?

br

[Haithem Rahmani · Accepted solution]

this issue is internally tracked and will be fixed in the coming STM32CubeMX version. So for the moment, you'll need to delete that file each time before regenerating the project.

Sorry for the inconvenience.

regards

Haithem.

[AZorn.1]

Ok, thank you for the information and the support.