CubeMX bug when configurating ADC for stm32u031

[another_user]

Hello,

I get error messages in Cube MX trying to configure the ADC in STM32U031F6Px to Not Fully Configurable.

To reproduce:

1. Start a new project, choose STM32U031F6P6 as MCU
2. Go to ADC, check any channel (e.g. temperature)
3. Change sequencer to "sequencer set to not fully configurable"

The steps create error marks identical to this post (assigned ticket numbers 186012 and 186009 and should be fixed in CubeMX v6.13.0). Its also described in this post, linking to the first and saying it should be solved in v6.12.1.

The error messages do not appear if I use the same procedure for e.g. STM32G031F6P6 or STM32C031F6P6.

Can you confirm this is a bug in CubeMX, or do I have to configure something more to use the ADC in not fully configurable? If it is a bug, is it safe to generate code with the error flags in CubeMX present?

I use stm32CubeMX v6.13.0 and v1.2.0 of "STM32Cube MCU Package for STM32U0 Series". Running windows 10 if that's interesting.

Best regards

Edit: I also can't see or choose Ain ch0-3 even though it looks like they exist in RM0503 Rev 2 fig 36. In cube MX it starts with IN4. This is not an issue for me since I can choose other ADC channels, but I don't know if this is expected or not.

[Mahmoud Ben Romdhane]

Hello @another_user ,

First let me thank you for posting and welcome to the ST Community.

Your request is under investigation, and I will get back to you ASAP.

Thanks.

Mahmoud

[Mahmoud Ben Romdhane]

Hello @another_user ,

Thank you for your detailed explanation.

By changing sequencer to "sequencer set to not fully configurable", users should have the ability to complete the ADC Configuration.

I am escalating an internal ticket to the detailed team (198832).

Also, the Vbat channel is available on STM32CubeMX 6.13 for STM32U031F6P6 MCU.

Thanks.

Mahmoud

[another_user]

Thank you for your reply and ticket escalation.

I am already using the Vbat sense. :)