cancel
Showing results for 
Search instead for 
Did you mean: 

Why would syscalls.c generated by newly installed STM32CubeMX 4.26.1 break the build in Eclipse (SW4STM32)?

APagl
Associate II

On my Mac, I just now upgraded to STM32CubeMX 4.26.1 which generates code with a file Src/syscalls.c. Nearly every function there (_close, _exit, _isatty, _kill, ...) show up in the "Problems" view of my Ac6 SystemWorkbench (aka SW4STM32). If I delete syscalls.c, the build seems to finish.

Interestingly, before I upgraded CubeMX, a syscalls.c file was never even generated.

I don't know much at all about the need or purpose for a syscalls.c file. I can't imagine that it's intended that I delete the file (and it certainly would be tedious to remember to delete it, since it must be there for a reason).

However, why was it never there before, with the previous version of STM32CubeMX?

I'm a bit reluctant to continue developing until I understand how to fix this. Thanks.

Alan

0 REPLIES 0