Associate II

Question

BUG in STM32CubeMX STM32L4 OPAMP ADC PROBLEM

Forum|Forum|9 years ago
June 8, 2016
3 replies
1126 views

Posted on June 08, 2016 at 16:48

Hi,

setting the ADC1_IN8 or ADC_IN15 as OPAMP x Output Differential or OPAMP x Output Single-ended in STM32CubeMx v 4.15 with NUCLEO-L476RG doesn't generate the correct GPIO setup.

The OPAMP output pins are configured as GPIO_MODE_ANALOG under HAL_OPAMP_MspInit in stm32l4xx_hal_msp.c while they should be configured as

GPIO_MODE_ANALOG_ADC_CONTROL to feed the ADC.

There is also another error: setting the the ADC1_IN8 or ADC_IN15 as OPAMP x Output Differential generates the wrong regular channel configuration as ADC_SINGLE_ENDED. It should be ADC_DIFFERENTIAL_ENDED.

Regards

#stm32-cubemx-opamp-adc

STM32CubeMX

This topic has been closed for replies.

Visitor II

Posted on June 09, 2016 at 10:45

Hi dallagiovanna.luca,

Thnak you for the feedback. I report this internally to our CubeMx team.

-Hannibal-

Oleg Lozhechkin

Associate II

Posted on December 28, 2016 at 12:59

Hi!

In CubeMX v.4.18.0 this problem present.

The OPAMP output pins are configured as GPIO_MODE_ANALOG under HAL_OPAMP_MspInit in stm32l4xx_hal_msp.c while they should be configured as

GPIO_MODE_ANALOG_ADC_CONTROL to feed the ADC.

Associate II

Posted on July 06, 2017 at 09:28

Hi,

the GPIO_MODE_ANALOG / GPIO_MODE_ANALOG_ADC_CONTROL Bug was reported in June, 2016, one Year ago.

Now, in CubeMX 4.21.0 with firmware V1.8.1 it still exists. Is there a chance that this will be fixed?

Associate

Posted on January 18, 2018 at 13:55

Hi

Dallagiovanna.Luca

and

Zottmann.Nils

,

Sorry for the late answer.

I confirm that the 2 points

Dallagiovanna.Luca

you highlighted are taken into account by the development team.

I can't give you any delivery date butI will keep you inform as soon as both corrections are integrated in a new CubeMX release.

BR. Jeanne