-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
H730 ADC3 Oversampling configuration bug #256
Comments
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, |
Hello @KubeckPL, Could you please share the code you have used to reproduce the problem? Regards |
Hello @KubeckPL, |
Hi @RJMSTM. |
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, |
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:
MX_ADC3_Init() function:
Final value in CFGR2 register (equal to 4):
Notice
Oversampling ratios for ADC3 in the H730 MCU are predefined, so CubeMX should only propose predefined values:
The text was updated successfully, but these errors were encountered: