Browse
STMicroelectronics Community
FAQs
Sign In
Product forums
STM32 MCUs
STM32 MCUs Products
STM32 MCUs Boards and hardware tools
STM32 MCUs Software development tools
STM32 MCUs Embedded software
STM32 MCUs TouchGFX and GUI
STM32 MCUs Motor control
STM32 MCUs Security
STM32 MCUs Wireless
STM32 MPUs
STM32 MPUs Products
STM32 MPUs Boards and hardware tools
STM32 MPUs Embedded software and solutions
STM32 MPUs Software development tools
MEMS and sensors
MEMS (sensors)
Imaging (sensors)
Automotive and Transportation
Automotive MCUs
AutoDevKit Ecosystem
GNSS positioning
Edge AI
Interface and connectivity ICs
Power management
ST25 NFC/RFID tags and readers
STM8 MCUs
Others: hardware and software
Analog and audio
Knowledge base
STM32 MCUs
STM32 MPUs
MEMS and sensors
Analog and audio
EMI filtering and signal conditioning
Interface and connectivity ICs
Power management
Quality & reliability
Academy
About
Community guidelines
Feedback forum
Community blog
Developer news
RudiH
Associate
since
2019-10-20
2024-05-03
User statistics
2
Posts
0
Solutions
0
Kudos given
1
Kudos received
View all badges
STMicroelectronics Community
About RudiH
Options
Report User
User Activity
Posts
Replies
ADC watchdog: with STM32CubeMX 6.4 and STM32CubeF7 Firmware V1.16.2 it is no longer possible to enter a lower threshold value other than 0.
2022-02-23
The problem exists for ADC1, ADC2 and ADC3. It works with Firmware V1.16.0
Since STM32CubeF7 Firmware V1.16.1 it is no longer possible to enable ADC2 or ADC3 continuous conversion mode, when ADC1 is enabled.
2022-02-23
I tested it with CubeMX version 6.2, 6.3 and 6.4, they all work up to STM32CubeF7 Firmware V1.16.0, but not newer versions.See also: https://github.com/STMicroelectronics/STM32CubeF7/issues/63
No replies to display.
Kudos from
User
Count
Legacy member
1
View all
