Skip to main content
Dave Nadler
Dave Nadler
Senior III
September 26, 2019
Solved

BUG: CubeMX doesn't mark IOC 'changed' when pin function or user-label changed

  • September 26, 2019
  • 4 replies
  • 875 views

Editing an IOC in CubeMX IDE and using Pin & Configuration view, changing a pin's special-function or user label does not mark the IOC as changed. Consequently File Save remains grayed-out and it is not possible to save the changes.

@Markus GIRDLAND​ - Please confirm you can reproduce this and a ticket has been opened, Thanks!

Best Regards, Dave

PS: IOC attached illustrates the problem.

STM32CubeIDE, Version: 1.0.2, Build: 3566_20190716-0927

Try changing pin PA4

This topic has been closed for replies.
Best answer by Dave Nadler

Thanks @Markus GIRDLAND​ - Windows 10 Pro.

Now I can't reproduce it either. Restarted IDE and it works now.

Two oddities possibly related but...

1) I did Windows sleep/resume cycle after last save and before it got into this state

2) The clock calculation is quite deranged after I disabled PH1 (clock is externally generated so PH1 is not used for OSC-OUT function)

Aaarrrgggg.....

4 replies

Pavel A.
Pavel A.
September 26, 2019

Which Cube version and which pins? CubeMX or CubeIDE?

Cannot reproduce here with STM32CubeMX 5.3.0 on Ubuntu.

-- pa

Dave Nadler
Dave NadlerAuthor
Senior III
September 26, 2019

@Pavel A.​ - Thanks, I clarified the question.

Markus GIRDLAND
Markus GIRDLAND
ST Employee
September 26, 2019

I can't reproduce this either. What is PA4 currently and what are you changing it to in your tests?

What OS are you using?

Dave Nadler
Dave NadlerAuthorBest answer
Senior III
September 26, 2019

Thanks @Markus GIRDLAND​ - Windows 10 Pro.

Now I can't reproduce it either. Restarted IDE and it works now.

Two oddities possibly related but...

1) I did Windows sleep/resume cycle after last save and before it got into this state

2) The clock calculation is quite deranged after I disabled PH1 (clock is externally generated so PH1 is not used for OSC-OUT function)

Aaarrrgggg.....

Terms & ConditionsAccessibility statement