There seem to be a bug in STM32F3 HAL library for comparator power mode. Or else the reference manual is misleading
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-04-03 10:29 AM
In reference manual, comparator power mode is not the same for all comparators. High Speed is (binary) 00 for comparators COMP1 and COMP2, and 11 for the others.
In stm32f3xx_hal_comp_ex.h, high speed is 00 and this is applied to all comparators.
Solved! Go to Solution.
- Labels:
-
COMP
-
STM32Cube MCU Packages
-
STM32F3 Series
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-04-04 4:18 AM
Hello,
I confirm that we have no bug in STM32F3 HAL library for comparator power mode and the RM must be corrected.
For all comparator, The bit value for High Speed is fixed to '00'
- 00: High speed / full power
I have already raised this error internally to take in consideration.
We will correct the error in the coming release of the RM.
Best regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-04-03 12:24 PM
This appers to be error in RM.
https://community.st.com/s/question/0D50X0000C9fYgkSQE/f3-compxmode10-discrepancy
JW
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-04-04 4:18 AM
Hello,
I confirm that we have no bug in STM32F3 HAL library for comparator power mode and the RM must be corrected.
For all comparator, The bit value for High Speed is fixed to '00'
- 00: High speed / full power
I have already raised this error internally to take in consideration.
We will correct the error in the coming release of the RM.
Best regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2020-04-06 12:21 AM
Thank you both @Community member and​ @Imen GH​ for your replies. I can be no more afraid to use the library constants
