Wrong constants in HAL ADC initialization (adc.c)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-08-24 2:45 AM
In adc.c (HAL driver), line 89 there are wrong constants generated:
LL_ADC_SetCommonPathInternalCh(__LL_ADC_COMMON_INSTANCE(ADC1), LL_ADC_PATH_VREFINT|LL_ADC_PATH_TEMPSENSOR);
correct is:
LL_ADC_SetCommonPathInternalCh(__LL_ADC_COMMON_INSTANCE(ADC1), LL_ADC_PATH_INTERNAL_VREFINT|LL_ADC_PATH_INTERNAL_TEMPSENSOR);
Solved! Go to Solution.
- Labels:
-
ADC
-
Bug-report
-
STM32CubeMX
-
STM32L4 series
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-08-25 4:26 AM
Hi @straubm​ ,
Thanks for sharing the details.
It is simple and you were able to fix it manually, but it needs to be fixed at STM32CubeMX side.
Internal ticket was submitted to keep track of the issue.
Internal ticket number: 133589 (This is an internal tracking number and is not accessible or usable by customers).
-Amel
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-08-24 3:57 AM
Hi @straubm​ ,
Which STM32 product are you using please, or STM32Cube FW package?
-Amel
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-08-24 4:57 AM
Hi Amel,
OMG, I forgot that crucial info.
CubeMX ​and STM32L4(1.17.2).
Btw, no big deal,​ I fixed it manually.​
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-08-25 4:26 AM
Hi @straubm​ ,
Thanks for sharing the details.
It is simple and you were able to fix it manually, but it needs to be fixed at STM32CubeMX side.
Internal ticket was submitted to keep track of the issue.
Internal ticket number: 133589 (This is an internal tracking number and is not accessible or usable by customers).
-Amel
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-08-25 5:13 AM
but it needs to be fixed at STM32CubeMX side.
​
That's why I reported it :D
​
Over and out.
Take care.​
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-11-28 8:24 AM
Hello @straubm​
I want to inform you that the issue is fixed in the 6.7.0 CubeMX release available on the ST web site under this link.
Semer.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-11-28 8:50 AM
I followed the link and installed the MX 6.7.0 version. But the STM32CubeIDE still uses 6.6.1-RC2. How do I fix it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-11-28 9:07 AM
Nevermind. It is in the STM32CubeIDE update 1.11.0. Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-11-28 9:43 AM
Hello @Semer CHERNI​,
thanks for fixing it and for the info.
Take care
Martin.
