STM32CubeMX and syscalls.c

[pgregson1]

Posted on January 14, 2017 at 18:34

Hello,

Why doesn't STM32CubeMX not provide a copy of syscalls.c in the application directory tree as part of the code generation step?  Presumably, all users of STM32 are developing bare-metal systems and so there must be some way of resolving the sys calls.  STM32CubeMX should have at least a tick-box that allows the developer to choose to include syscalls.c in the application build.

Further, syscalls.c is found only in  

STM32Cube/Repository/STM32Cube_FW_F1_V1.4.0/Projects/<board>/Applications/... and STM32Cube/Repository/STM32Cube_FW_F1_V1.4.0/Projects/<board>/Examples/... , however it (or its equivalent) is required for every bare-metal project.  Somehow, hiding an essential file in these locations seems silly and unhelpful.

Regards,

Peter

[Imen.D]

Posted on January 16, 2017 at 15:19

Dear

Gregson.Peter

,

Please note that your requestis already shared internally withCubeMx team.

We apologize for any inconvenience this may cause and thank you for your understanding.

Best Regards

Imen

[Jeanne Joly]

Posted on January 26, 2017 at 12:02

Hello

Gregson.Peter

,

The point you raised is interesting and is under study in CubeMX right now.

We will keep you informed as soon as we have a target release.

BR. Eric

[Julien NGUYEN]

Posted on December 08, 2017 at 17:14

Hi Eric and Imen,

Is there an update on this? We believe this is a valid user request and we share the same concern as Peter.

Julien and Pierre-Yves