Skip to main content
AndFel
Associate
March 30, 2025
Question

STM32G0 ADC channels availability and GPIO mapping

  • March 30, 2025
  • 2 replies
  • 1710 views

Hi There, 

I am currently using the STM32G050C8T6 (LQFP48) and would like to use PA11 as an ADC input, based on the datasheet: DS13514 - Rev 2 specifically table 12, it appears it can be used as ADC_IN15, However in STM32Cube IDE , PA11 can not be assigned to ADC_IN15, I understand that in fully configurable sequencer mode only inputs from 0 to 14 can be used, however in either mode PA11 can not be assigned to ADC_IN15 in Cube. 

AndFel_0-1743370150027.png

AndFel_1-1743370433676.png

Finally, the main question is which is correct Cube or the datasheet, and would like to make sure this is not a hardware limitation or mistake in the documentation ? 

Thanks in advance, 

 

2 replies

AndFel
AndFelAuthor
Associate
April 1, 2025

Anybody from ST to confirm/correct or deny the datasheet inconsistency ? , it seems important enough to have an inconsistency around ADC channels availability and GPIO mapping in the datasheet, However the latest update to the datasheet for the STM32G050C8T6 was done on June 2022. 


Karl Yamashita
Lead III
April 2, 2025

Probably a typo. PA11 looks to be an alternative pin to the Regular EXTI Conversion Trigger. By default PB11 is selected but you can override and select PA11.

 

ANx inputs are typically on 1 pin only. If you do a search and IF there is an alternative pin, it'll highlight (shaded black) more than one pin. In this case, ADC1_IN15 only highlights 1 pin, PB11. 

KarlYamashita_0-1743572395297.png

 

An example is if I wanted to see if there is another alternative pin for USART2_RX. This shows there are 2 pin locations indicated by shading the pin black.

KarlYamashita_1-1743572614364.png

 

 

 

If a reply has proven helpful, click on Accept as Solution so that it'll show at top of the post.CAN Jammer an open source CAN bus hacking toolCANableV3 Open Source
AndFel
AndFelAuthor
Associate
April 2, 2025

Hi @Karl Yamashita , 

Thanks for your response. 

It is not only more than a typo, it is incorrect and misleading on the Datasheet, which should be the source of truth for any part. 

I would have thought something like this should be fixed and updated on the Datasheet, are there any plans to update this by ST ? (Last update done on June 2022). 

Otherwise as users where do we look for the source of truth ?