cancel
Showing results for 
Search instead for 
Did you mean: 

Is this a bug in cubemx (V6.2)?

one V
Associate III

0693W000007ZgPLQA0.png

6 REPLIES 6
Haithem Rahmani
ST Employee

Hi @one V​,

for MX_AZRTOS_Init() & MX_AZRTOS_Process() you'll need to unselect the "Generate Code" check box. If you don't want to generate them.

regards

Haithem.

Are you sure? I tried but it didn't work.

Hello @one V​ 

Thank you for raising this issue to our attention, the Do not generate Function Call problem was detected with all packs.

I have reproduce it, sorry for any inconvenience this may have caused, issue will be fixed.

Khouloud

yes it works.

with the "Generate Code enabled"

0693W000008vxDjQAI.png 

without the "Generate Code" option

0693W000008vxDPQAY.png 

regards

one V
Associate III

This seems to be wrong. If you do not check "generate code", the corresponding code should not be generated. For example, if you do not check USART3, there will be no code such as MX_USART3_UART_Init in usart.c. And "Do Not Generate Function Call" refers to the code that does not generate related calls in main.c.

one V
Associate III

In addition, tx_initialize_low_level.S generated by CUbeMX is not suitable for MDK to use, and some errors occur when directly compiling. You may not have tested it well before you release it. I look forward to your improvements as soon as possible so that everyone can use threadx.