Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Beware of STM32F410/411 - errata with DMA2 & GPIO can cause glitches #14

Open
GIPdA opened this issue Jul 27, 2021 · 0 comments
Open

Beware of STM32F410/411 - errata with DMA2 & GPIO can cause glitches #14

GIPdA opened this issue Jul 27, 2021 · 0 comments

Comments

@GIPdA
Copy link

GIPdA commented Jul 27, 2021

Hello,

Just a notice about a silicon errata from ST for STM32F410 and 411 (and maybe others): using DMA2 and GPIO as done in this project can cause glitches in the generated pulses. Errata says "DMA2 data corruption occurs when managing AHB and APB2 peripherals in a concurrent way", specifically with GPIO when doing memory-to-peripheral transfers (exactly what we need...).

The workaround given in the errata is not suitable: memory-to-memory transfers doesn't support requests, so it can't be used.
And DMA1 cannot write to the GPIO peripheral, so can't avoid it.

It's tricky to know when you're "managing AHB and APB2 peripherals in a concurrent way", but I managed to avoid glitch issues (for now) by compiling in "-Ofast". Not very robust, I'm afraid this "workaround" can break easily.
We'll see, I'll report if I find something else.

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

No branches or pull requests

1 participant