Pin user label disappears when I change the pin function in the cubeMX GUI.
This is not an expected behavior, since the already given name of the pin has not changed.
cubeMX Version is 4.17.0
I have defined e.g. a
label 'ANA_VOLTAGEBRIDGE' for Pin PA3.
If I change the function
of a Pin, e.g. PA3 from ADC_Input to e.g. GPIO_Input,
its label changes to 'GPIO_Input' and my previously defined label
'ANA_VOLTAGEBRIDGE' is lost.
I too find this behavior undesirable and would like to see it changed.
Hello bischof.arnold and all,
Thanks for your feedbacks.
It is indeed a good idea to change the Pin label behavior as you mentioned.
We don't know yet when it will be corrected and delivered but this idea is kept on our side and will be handled later.
Any update on this?
Just started using CubeMX...and losing the User Labels is extremely annoying. Have always developed the startup code from scratch on previous projects, but was asked to try and migrate to CubeMX and the Cube libraries. So far, this has saved me negative time.
Given the fact that if you change a pin function, the name gets blown away, what is the proper way to interact with this tool? My board is already designed, I want the pin names to match the net names on my board. The 1st thing I do is name all of the pins and give them best-guess functionality, then I come back to provision the system. This is obviously not the flow that the designers of this tool had in mind.
Is there a workflow documented somewhere that I could refer to.
I see absolutely no reason to change (delete) the user labels when you use it in the manner I am using it. Therefore, I must be using it wrong.
Any pointers would be appreciated
For ST: Here's the issue. I have a bunch of pins with names that are on ADC1. To do a multi-channel simultaneous conversion, some of these pins are switched over to ADC2. What is the effect? Anybody? Craig Reed? Yes, correct, all of your labels are removed.
There is a quick (relative) way to put them back. If you go into the Configuration/ADC2 widget, under GPIO Settings, you can put the labels back in without a lot of clicking. (yes this works for other subunits, give it a try) But the preferred response would be to NOT scrub the labels.
I feel that if you change the function of the pin, it is a drastic change.
I think that CUBEMX is correct to change the pin name to the new function.
otherwise in the code, stuff wont work but the names all look correct, when the pin function is now different.
So, give and take,
the Cubemx people want to make sure that you know what you are doing and you are maybe doing the wrong thing.
This way, Cubemx has not buried a bug for you, and you are conscious of your pin function and name change.
It definitely gives you compile errors, if you use the symbols that it generates.
In our situation, the EE puts together the model and the firmware person works with it. So maybe you'd like to blow up the project for someone else, maybe.
I think the bigger issue is the loss of the name. If the pin name was altered by adding an underscore to the front say, you'd still know what the name WAS and programmer guy could fix the appropriate section of code. Or you could acknowledge the change in the model by deleting the underscore intentionally.
Blowing away the name doesn't pass the "choice of least surprise" test.
Yes, combine the best of both worlds.
1. you are still forced to be responsible for the new function and
2. you can see what the old name used to be.
excellent request for the cube engineers.
Retrieving data ...