syscalls.c File Not Generated or Deleted After Using X-Cube-AI Pack v10.2.0

[eric_green]

Hi,

I'm experiencing an issue with the X-Cube-AI Pack (version 10.2.0) on Windows 10.

After using the X-Cube-AI Pack, the syscalls.c file is either not generated at all, or if it already existed in the project, it gets deleted during the process.

This is causing build failures since the file is required for proper compilation. I've tried this on multiple projects and observed the same behavior consistently.

Could you please investigate this issue? It would be helpful if you could confirm whether this is a known problem or if there are any workarounds in the meantime.

Thanks in advance for your support!

Best regards

[Mahmoud Ben Romdhane]

Hello @eric_green ,

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

For more investigation, I suggest please that you provide your Ioc.File.

Thanks.

Mahmoud

[eric_green]

Thank you for your prompt reply.

I used the original problematic .ioc file and generated a new project in a fresh folder (containing only that .ioc file). In this case, the syscalls.c file was successfully generated. However, without making any changes, I regenerated the code once again—and this time, the syscalls.c file disappeared.

Additionally, I noticed that X-CUBE-FREERTOS is unable to retain newly created tasks. Even after saving the .ioc file, when I reopen it, all the newly added tasks are gone—only the default task that was originally present remains.

[Mahmoud Ben Romdhane]

Hello @eric_green 

Let me thank you for bringing those issues to our attention.

First Issue: Tasks,Queues,Timers,Semaphores,Mutexes are missing when reloading the ioc.

Internal Ticket Number ( Ticket 214187 )

Second Issue: Syscalls.c is not generated after the second code generation while enabling X-Cube-AI Pack

Internal Ticket Number ( Ticket 220679 )

I will keep you up to date when the problems are solved.

Thanks.

Mahmoud

[Mahmoud Ben Romdhane]

Hello @eric_green ,

For the second issue, I suggest that you delete the cache folders placed under: C:\Users\

I will be waiting for your feedback.

Thanks.

Mahmoud

[eric_green]

Hi, @Mahmoud Ben Romdhane ,

It does not work.

THX.

[Mahmoud Ben Romdhane]

Hello @eric_green ,

Could you please reproduce your request with this Ioc.File.

You find in attachment a screen recording which mentions the generation of syscall.c file.

Thanks.

Mahmoud

[eric_green]

Hi, @Mahmoud Ben Romdhane ,

Thanks for your reply.

I followed your screen recording and regenerated the project from your .ioc file in an empty folder. The result indeed matched yours.

However, I noticed one important detail: in your demo, you kept STM32CubeMX open the entire time and simply re-generated the code without closing the application.

When I closed CubeMX after the first generation, reopened the same .ioc file later, and regenerated the code in the same project folder, the syscalls.c file disappeared again.

Interestingly, when I completely cleared the folder, reopened the .ioc file in CubeMX, and generated the code fresh, syscalls.c reappeared.

Based on this behavior, I suspect there might be a bug related to regenerating code in an existing project folder after reopening the .ioc file—specifically, if CubeMX was previously closed and then relaunched.

THX again.

[Mahmoud Ben Romdhane]

Hello @eric_green,

I made tests like you described on your last comment on other machines, and the syscalls.file is well generated.

Could you please redelete those folders and regenerate the code.

Thanks.

Mahmoud