cancel
Showing results for 
Search instead for 
Did you mean: 

inconsistent designation of registers

pkoevesdi
Senior

In the CubeProg, (for instance) the RCC_D1CCIPR value names (*SRC) are different than in the RM 0433 (*SEL). Such things are a bit annoying, if one tries to find things by a keyword search, of if unsure about "is it really the same entity"? Can someone here pass this to the authors for fixing? Thank You!

pkoevesdi_0-1730451210735.png - CubeProgrammer v2.17.0

pkoevesdi_1-1730451330120.png- RM0433 Rev. 8, p. 496

 

1 ACCEPTED SOLUTION

Accepted Solutions
STTwo-32
ST Employee

Hello @pkoevesdi 

Thank you for feedback that has been escalated for correction on one of the future releases of the STM32CubeProgrammer (under internal ticket number 195558 ).

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

View solution in original post

4 REPLIES 4
STTwo-32
ST Employee

Hello @pkoevesdi 

Thank you for feedback that has been escalated for correction on one of the future releases of the STM32CubeProgrammer (under internal ticket number 195558 ).

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Andrew Neil
Evangelist III

Does this also apply to the names used in the generated source code?

You mean in CubeMX? Didn't try that, because I don't develop in C. I only use CubeProg for reading and saving registers.


@pkoevesdi wrote:

You mean in CubeMX?


Yes - the code generated by CubeMX.