search

STMicroelectronics / STM32CubeH7

STM32Cube MCU Full Package for the STM32H7 series - (HAL + LL Drivers, CMSIS Core, CMSIS Device, MW libraries plus a set of Projects running on all boards provided by ST (Nucleo, Evaluation and Discovery Kits))
https://www.st.com/en/embedded-software/stm32cubeh7.html
Other
479 stars 298 forks source link

H730 ADC3 Oversampling configuration bug #256

Closed KubeckPL closed 1 month ago

KubeckPL commented 1 year ago

Caution There is an error in the oversampling configuration for the ADC3 in the H730VBT processor in the HAL library. In the attached screenshots, I have shown the configuration in CubeMX, in the ADC3 handler, and the final values written to the ADC3 registers. Tools used:

Screenshots

CubeMX ADC oversampling configuration: obraz

MX_ADC3_Init() function: obraz

Final value in CFGR2 register (equal to 4): obraz

Notice Oversampling ratios for ADC3 in the H730 MCU are predefined, so CubeMX should only propose predefined values:

obraz

KubeckPL commented 1 year ago

The proposed solution in the MX_ADC3_Init() function - using a predefined macro:

obraz

RJMSTM commented 1 year ago

Hello @KubeckPL,

Thank you for this report. We will get back to you as soon as we analyze it further. This may take some time. Thank you for your comprehension.

With regards, Rania

RJMSTM commented 11 months ago

Hello @KubeckPL,

Could you please share the code you have used to reproduce the problem?

Regards

RJMSTM commented 6 months ago

Hello @KubeckPL, Any update please, you resolve your problem??

KubeckPL commented 6 months ago

Hi @RJMSTM. The bug is still present in the latest version of CubeIDE and CubeMX (V1.14) - I have just checked this. This problem relates to the code generator built into CubeMX.

obraz

RJMSTM commented 6 months ago

Hello @KubeckPL,

Thank you for this report. The point you reported is actually related to the CubeMX generation problem and not to the firmware published in this repository. Unfortunately, we don't treat aspect related to CubeMX tool in our GitHub repositories. They are rather treated at the STM32CubeMX dedicated page of the ST Community .

Since this issue is not directly related to the STM32Cube firmware but rather to our ecosystem, please allow me then to close this thread. Thank you for your comprehension.

With regards,