[BUG] STM32 F0 - ADC_INJECTED_RANK_1 not declared

[runger1101001]

[Candas1]

Hi,

I came accross this issue.
My fork for ADC was meant to make it easier in the future to support more STM families, but I couldn't progress on this topic in 2025.
I will probably be able to contribute again to SIMPLEFOC in 2026, and can continue this work if there is interest.

Some details from my notes for the F0 familly:

• as described, it doesn't have injected ADC, but my fork can work with regular ADC + DMA as well
• if the timer being used has no repetition counter, it means a DMA interrupt is required to manage to pick the right current sample, which is not implemented yet in the fork
• this chip familly seems to use a single/common sampling time (code)

If you want to try it with my fork, you would need to add the new familly here.
This chip familly might be slow and lack memory for motor control use.

[thieringpeti]

Hi,

I have the same problem, I would like to operate an STEVAL-SPIN3201 with simpleFOC and PlatformIO, and I bumped into the same error.
STSPIN3201 is an STM32F031C6T with integrated hi/lo mosfet drivers. It may be usable with 6PWM mode, all of the gate drivers are connected to TIM1 (CH1-3, H/L). See attached picture from STM32CubeMX.

[Candas1]

Hi,

I don't think it's a bug.
It's just that F0 familly is not supported yet ?
https://docs.simplefoc.com/stm32_mcu

[askuric]

The dev branch should be ok now.

[thieringpeti]

Confirmed, OK, compiles. At the linker stage, stops with FLASH size overflow. Now I have to decrease the FLASH usage. Any ideas? I cannot fit into 32kB of the STM32F031C6T, even though I've set the commander and the serial off.
My goal is to do a 6PWM open loop control with the STEVAL_SPIN3201 board. (I cannot upscale the MCU, it's the only one with the integrated gate drivers). Or forget it, and use another board with separate drivers?

[askuric]

OK, How much does it overflow?

If its not too much, maybe you can try disabling the debugging. Use the SIMPLEFOC_DISABLE_DEBUG flag.

[thieringpeti]

Added, compiler errors occurred.
SIMPLEFOC_STM32_DEBUG was still defined, causing unresolved definitions in the stm32 mcu drivers. Could not remove it by adding
build_unflags = -DSIMPLEFOC_STM32_DEBUG, but commenting out in stm32_mcu.h

Disabling debug almost helped, instead of approx. 3700 bytes, overflow is now 684 bytes. Code is almost nothing, just initializing simpleFOC and a delay.

[askuric]

you could maybe go into the simplefoc.h and comment out the things you dont need. This might help.

EDIT: btw. I've just updated the dev branch to correct for this issue with SIMPLEFOC_STM32_DEBUG you just described

[thieringpeti]

Everything except the BLDC 6PWM driver is commented out. No sensors, debug, feedback or current sensing is now included. Example is only initialisation, and starting the motor with a fixed frequency.

The flash overhead remained the same 684 bytes.
Maybe the Arduino framework which is consuming so much FLASH, and porting the whole library to STM32CubeMX with LL drivers would help, which seems a lot of work to do.

Motor which I would like to power up with this devkit is an old 3-phase induction linear actuator, used in german pipe organs, which originally required a 3-phase transformer and two relays per actuator with limit switches. Worked with a Blue Pill and two stepper drivers 2 years ago, but I wanted something more efficient and professional. Only requirement is a 3-phase sinusoidal PWM signal to be generated. I still cannot understand where this huge amount of FLASH goes. Finally I would like to add a generic current sense to exclude the limit switches to sense the endpoints.

[askuric]

Hmm. You could maybe also try deleting the sensors and communication directory and the Stepper and Hybrid stepper classes. Just in case that they are compiles still somehow.

[thieringpeti]

Your fix with the definitions, after resyncing the library, decreased the overhead to 496 Bytes.
Commenting out functions which are not used in the project, or deleting those source files also did not affect the FLASH size after linking.

[askuric]

Ha! So how much do you still need? :D

EDIT: You could go in the BDLCMotor class and comment out all the SIMPLEFOC_DEBUG calls. All the strings in their calls are storred to flash (The F()) funciton.

[thieringpeti]

Thanks, commented out every debug call, in BLDCMotor.cpp and FOCDriver.cpp. Exactly the same overhead. I think that the linker is intelligent enough to exclude the unused variables. Which I would be able to do, is to remove all debug conditions, which would take a bit more time to understand.

After the holidays, I would give another attempt to trace back what occupies so much FLASH in case of a single open loop setup. If I succeed, support to this devkit can be added to the project later, strictly without debug or logging.

EDIT: checked the compiled .o ELF files. No debug strings were found. I think, that the Arduino framework with the HAL drivers simply not able to be fit into this small MCU. Thanks for Your help, after vacation I will check if I would be able to save up more space by commenting out all of the variable cheks and compares which are only used by the debug functionality.