Skip to content

Conversation

boondocklabs
Copy link

I noticed that the first overflow ISR was corrupting the time on a G474 when using TIM5 as a monotonic.

All stm32 with TIM5 are 32bit timers to the best of my knowledge. This changes the type from u16 to u32 which has resolved the issue.

@burrbull
Copy link
Contributor

All stm32 with TIM5 are 32bit timers

All except F1, L0, L1 series and F410.

@boondocklabs
Copy link
Author

boondocklabs commented Oct 13, 2025

All stm32 with TIM5 are 32bit timers

All except F1, L0, L1 series and F410.

Well that complicates things. Any clean way to do this without listing each device in #[cfg] directives? It would be nice if stm32-metapac had associated types on the timers or from the metadata module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants