cancel
Showing results for 
Search instead for 
Did you mean: 

CubeMX and Keil Project Settings

Greg Cloutier
Associate
Posted on January 19, 2017 at 14:26

It seems that CubeMX is getting better about retaining some of the Keil project settings upon regeneration of the code.  There is an issue that I just came across.  We sometimes use multiple named Project Targets in Keil.  Would anybody have experience keeping the names intact when CubeMX regenerates code?  All but the first have their name removed.  With one extra target, the name just goes away.  With multiple extra targets, all names go away, but the project won't open due to conflicting duplicate target names (which of course are all named nothing).

4 REPLIES 4
Nesrine M_O
Lead II
Posted on January 20, 2017 at 18:13

Hi

nggreg

,

please refer to this thread:

STM32CubeMX supports project generation for only onetarget at a time.

https://community.st.com/0D50X00009XkhEcSAJ

-Nesrine-

Greg Cloutier
Associate
Posted on January 20, 2017 at 18:48

Thanks for the link.  Same issue.  Maybe this is a feature request then.

I use CubeMX to generate a Keil Project for a particular microcontroller.  Once in the Keil project I can alter settings such as memory areas.  These are set in the 'Options for Target' dialog (also listed by name as a Project Target in the Manage Project Items dialog).  When CubeMX is used to regenerate the project, those modified settings are retained.  We can set multiple Project Targets to accommodate a variety memory areas.  When CubeMX regenerates one of these projects, all the settings are still valid, just the Project Target name is wiped out.  This can be brought back to life by a quick edit to the uvision project xml just as the other link stated.  Perhaps CubeMX could accommodate this in a future revision?

Posted on January 23, 2017 at 10:43

Hi

Cloutier.Greg

,

Thanks for the suggestion! I will forward this to our MX team.

-Nesrine-

Jeanne Joly
Senior III
Posted on March 30, 2017 at 11:34

Hi

Cloutier.Greg

,

Thanks for your post.

This issue will be corrected in CubeMX 4.21 that will be delivered soon.

BR. Eric