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

eric_green · ‎2025-10-23

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 · ‎2025-10-24

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

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.

eric_green · ‎2025-10-24

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.