Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.