Why does the ST software have different names for registers than the documentation does? I am trying to program the STM32G031 I read the documentation then I have to search in the files for what you renamed it to.

[KiptonM]

I am looking at RM0444 page 402 and 404 (Rev 5)

Documentation Software

ADC_ISR ADC1->ISR

ADC_IER ADC1->IER

ADC_CR ADC1->CR

ADC_CFGR1 ADC1->CFGR1

ADC_CFGR2 ADC1->CFGR2

ADC_SMPR ADC1->SMPR

ADC_AWD1TR ADC1->TR1 ?????

ADC_AWD2TR ADC->TR2 ?????

ADC_CHSELR ADC->CHSELR

ADC_AWD3TR ADC->TR3 ?????

ADC_DR ADC1->DR

ADC_AWD2CR ADC->AWD2CR

ADC_AWD3CR ADC->AWD3CR

ADC_CALFACT ADC->CALFACT

ADC_CCR ADC->CCR

Why make all but three match the documentation?

  I found them defined in stm32g031xx.h Lines 122 to 148

[Nikita91]

Probably a failure of the quality review of the project... Probably the consistency between the doc and the software is not an acceptability criterion.

There are many like that. Most frustrating are the reference manuals moved from one family to another without updating the specific characteristics of the target family.

[ssipa.1]

these are the different registers which are operating for a specific purpose.

[KiptonM]

[KiptonM]

I wonder if anyone will fix this...

[KiptonM]

[Breakthecake]

Ooops! Same with stm32L476RG on SPI ... Reliable ecosystem! These silicon companies throw new chips on the market year by year, but the customers have problems to use them. ... We tend to desolder the used "old" µC from pcb as you do not get the hot stuff on the market, anyway. Exploring bugs like the quoted one does not make happy engineers.

[KiptonM]

It has been up for almost a week and nobody from ST has acknowledged there may be a problem and a fix is on the way.

[waclawek.jan]

I know it won't make you happier, but with some searching I could probably find threads complaining of the same kind of inconsistency, dating maybe 10 years ago.

It does not mean that ST should not care more, but it is what it is.

JW

[Walid ZRELLI]

Hello @KiptonM​ 

Thank you for having reported this point.

We are actively working on it. Analysis is ongoing to identify the origin of this discrepancy.

We will get back to you as soon as possible.

BeST Regards,

Walid

[Walid ZRELLI]

Hello @KiptonM​ 

Regarding the STM32G0, the issue was confirmed on 3 ADC registers naming {TR1; TR2; TR3}

We have updated the drivers to be aligned with the reference manual as follows:

• CMSIS: change from {TR1; TR2; TR3} to {AWD1TR; AWD2TR; AWD3TR} with aliases on initial naming to ensure backward compatibility
• LL and HAL drivers: use updated CMSIS naming

The fix will be present in the next STM32G0 FW package release.

Thank you again for your contribution.

BeST Regards,

Walid