Skip to main content
Associate III
November 1, 2024
Solved

inconsistent designation of registers

  • November 1, 2024
  • 2 replies
  • 1110 views

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

 

Best answer by STTwo-32

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

2 replies

STTwo-32
STTwo-32Best answer
Technical Moderator
November 1, 2024

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

Andrew Neil
Super User
November 1, 2024

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

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
pkoevesdiAuthor
Associate III
November 2, 2024

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

Andrew Neil
Super User
November 2, 2024

@pkoevesdi wrote:

You mean in CubeMX?


Yes - the code generated by CubeMX.

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.