Skip to main content
Associate II
April 11, 2025
Question

STCUBEMX incomplete ThreadX code generation error on linux

  • April 11, 2025
  • 2 replies
  • 1268 views

Hi,

When I tried to generate a project with ThreadX for STM32N6, STCUBEMX generated incomplete code.

CubeMX Ver : 6.14.0

MCU: STM32N6

Platform: Ubuntu 24.04

ioc file attached.

2 replies

Technical Moderator
April 11, 2025

Hello @sai2 ,

 

First let me thank you for posting and welcome to the ST Community.

Your request is under investigation, and I will get back to you ASAP.

I suggest also that you provide a capture of the issue.

 

Best Regards.

Mahmoud

 

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
sai2Author
Associate II
April 14, 2025

I attached a build log and screenshot of the folder structure. As you can see in the screenshot, there are duplicated cortex_m55 and cortex_M55 folder generated under middleware/ST/threadx/ports and there are no source code generated under middleware/ST/threadx/ports/cortex_M55/gnu/src. Generating project under window environment works and dont have duplicated "cortex_M55" folder.

There is another issue surfaced when I tried to import example application, which also result in incompleted project and was unable to build. Again, importing example project under window environment works fine.

Steps to reproduce:

1. Import STM32Cube Example

2. select "Ux_Host_VIDEO" example for "STM32N6570-DK"

3. build (fail)

error (for some reason I was unable to post the log file for example project)

make: *** No rule to make target '/home/sai/STM32CubeIDE/workspace_1.16.1/Ux_Host_VIDEO/Middlewares/ST/threadx/ports/cortex_m55/gnu/src/tx_misra.s', needed by 'Middlewares/ThreadX/Port/tx_misra.o'. Stop.
make: *** Waiting for unfinished jobs....
"make -j14 all" terminated with exit code 2. Build might be incomplete.

 

Technical Moderator
April 16, 2025

Hello @sai2 ,

 

Thank you for bringing this issue to our attention.

An internal ticket is raised to the Development team under this number: 207773.

 

Thanks.

Mahmoud

 

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
Associate II
August 18, 2025

Poking this thread to see if anyone has found a permanent solution to this issue. Using MX 6.15.0 and ThreadX, there are still two paths generated for the middleware, cortex_m55, which is correct, and cortex_M55, which fails. I can just delete the failing paths, but they come back when regenerating, which is incredibly annoying.

Technical Moderator
August 19, 2025

Hello @chornbeck ,

 

Let me thank you for posting and welcome to the ST Community.

I suggest that you provide you Ioc.File.

 

Thanks.

Mahmoud

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.