QUERY · ISSUE

STM32: machine.freq unsupported on F0, L0, L4 and WB

openby 459548764opened 2019-11-29updated 2019-12-02

port-stm32

When I set pyb.freq(30000000) it occurs an error that I can't change the frequency. How should I do?

CANDIDATE · ISSUE

stm32/machine.freq: Only one argument accpted.

closedby robert-hhopened 2024-02-12updated 2024-02-12

port-stm32

As part of the harmonization of the machine.freq() method, the ability was lost for the STM32 port to define APB1 and APB2 frequencies as well. They are now always SYCLK/2 and SYSCLK/4. The function mp_machine_set_freq() in modmachine.c still attempts to evaluate additional arguments, but they are rejected in extmod/modmachin.c.

Assessment

Q Qwen · high

Both issues concern the STM32 port's machine.freq() functionality, but they describe different problems. Issue #5366 reports that machine.freq() is unsupported on specific STM32 variants (F0, L0, L4, WB) - a feature availability issue. Issue #13646 reports a regression where the ability to set APB1/APB2 frequencies separately was lost during API harmonization, causing argument validation errors. While both involve machine.freq() on STM32, the root causes and solutions are different: #5366 needs implementation of frequency scaling for specific MCU families, while #13646 needs fixing of argument handling logic. They are related topics but neither resolves the other.

Suggested action

Keep both issues open as they address different problems. Consider linking them in comments to show the relationship between the feature gap and the API regression.

STM32: machine.freq unsupported on F0, L0, L4 and WB

stm32/machine.freq: Only one argument accpted.

Keyboard