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

Fix ADC DMA SEQUREH7V2 #618

Merged
merged 10 commits into from
Nov 29, 2024
Merged

Conversation

swagprincess
Copy link
Contributor

While the target works well normally, if you try to use burst dshot, betaflight always puts the TIMUP3 peripheral on the first DMA stream, and for some reason it doesn't move the ADC DMA stream away from the first, and betaflight reads bad data and all the voltage readings go crazy. The solution is just to assign streams 8 and 9 as most other targets do.

Another point is that, I don't know if this is a general bug or just this FC but burst dshot only works with motors 1-4 and not in bidirectional mode, timer based works with all 8 and bidirectional mode apparently, but it gives DSHOT_TELEM arming flag. For now the only working bidirectional mode is bitbang. I have tried various things, from assigning manually every DMA stream, to adding manual DMA assigments for the SPI busses and everything in between, I cannot get anything other than bitbang to work. Another peculiar thing is that, locally compiling, the first SPI bus never appears when typing dma show in CLI, but it does when cloud building, both done with the exact same configuration.

@haslinghuis haslinghuis requested a review from ot0tot November 27, 2024 13:34
@haslinghuis haslinghuis merged commit f4739e2 into betaflight:master Nov 29, 2024
1 check passed
@swagprincess swagprincess deleted the sequreh7v2 branch November 29, 2024 21:42
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.

3 participants