cancel
Showing results for 
Search instead for 
Did you mean: 

STM32CubeMX Feature request: possibility to specify relative paths or our own paths.

Jan Humpl
Associate II
Posted on September 01, 2017 at 16:21

Hello,

we want to set path for 'Mcu and Firmware Package' to path relative to CubeMX project directory. Rationale - in case you store CubeMX and other source files into VCS, the absolute path to the Firmware package may be different on each computer. The relative path is always same.

We also want to set 'Toolchain Folder Location' - now this field is not editable.

Thanks a lot.

5 REPLIES 5
Imen.D
ST Employee
Posted on September 04, 2017 at 11:13

Hello

jan.humpl

Thank you for your participation. Iwill raise your request internally to the CubeMx team.

Best Regards

Imen

When your question is answered, please close this topic by clicking "Accept as Solution".
Thanks
Imen
Jeanne Joly
Senior III
Posted on January 30, 2018 at 10:11

Hello

jan.humpl

,

In the latest CubeMX release (CubeMX4.24), open File/Project Settings, the toolchain folder can be changed and for the Firmware location, you can untick the button ''Use Default Firmware Location'' and set the path you want :

0690X00000609XhQAI.png

I hope it will help you.

BR. Jeanne

Posted on January 30, 2018 at 10:23

The behavior is identical to previous version. I cannot set path relative to the current directory (e.g. '..\..\..\..\3party\STM32Cube_FW_H7'). If I try to set relative path I will get this error:

0690X00000609UtQAI.png

But the message is not true - I am sure that the folder contains mentioned directories.

Posted on January 30, 2018 at 11:02

Please, have a look to

http://www.st.com/content/ccc/resource/technical/document/user_manual/10/c5/1a/43/3a/70/43/7d/DM00104712.pdf/files/DM00104712.pdf/jcr:content/translations/en.DM00104712.pdf

 doc, paragraph 5.8.1 Project tab, you will have an explanation on how to reuse the same Drivers folder across all projects that use the same firmware location.

It should help you.

BR. Jeanne

I still have the same problem with CubeMx version 6.11.1.