# STM32G030 build failure in stm32\_adc\_utils.cpp (#539)

**URL:** https://community.simplefoc.com/t/stm32g030-build-failure-in-stm32-adc-utils-cpp-539/8359
**Category:** developement
**Created:** [October 7, 2026, 6:53pm UTC](https://community.simplefoc.com/t/stm32g030-build-failure-in-stm32-adc-utils-cpp-539/8359 "2026-10-07T18:53:30Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![wentx333](https://community.simplefoc.com/user_avatar/community.simplefoc.com/wentx333/32/10127_2.png) [@wentx333](https://community.simplefoc.com/u/wentx333)
#### Post date: [October 7, 2026, 6:53pm UTC](https://community.simplefoc.com/t/stm32g030-build-failure-in-stm32-adc-utils-cpp-539/8359/1 "2026-10-07T18:53:30Z")

</div>

Hi, I’d like to work on #539.

I checked the current dev branch at commit ae7b3add. stm32\_adc\_utils.cpp still calls LL\_ADC\_INJ\_IsTriggerSourceSWStart() unconditionally, and ADC\_ChannelConfTypeDef::Offset is still assigned on non-F1 targets. This matches the compiler errors reported for STM32G030.

The issue has no linked PR. I also checked the open PRs and found none addressing this G0 build failure. PR #554 touches the same file but changes different code.

Before I start, would you prefer a small compatibility patch that:

1）guards APIs and fields unavailable on STM32G0

2）adds STM32G030 to CI to catch the regression

I can set up the Arduino toolchain, reproduce the build failure, and target the dev branch once the direction is confirmed.

---

<div class="post-metadata">

### Author: ![Antun\_Skuric](https://community.simplefoc.com/user_avatar/community.simplefoc.com/antun_skuric/32/21_2.png) [@Antun\_Skuric](https://community.simplefoc.com/u/Antun_Skuric)
#### Post date: [October 7, 2026, 6:56pm UTC](https://community.simplefoc.com/t/stm32g030-build-failure-in-stm32-adc-utils-cpp-539/8359/2 "2026-10-07T18:56:06Z")

</div>

Hi there!

Thanks for the initiative.

The ideal would be to make it in a way to change the minimum and add the g0 to the GitHub CI workflows so that we test it automatically.