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.

Sign up for GitHub

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

Jump to bottom

Refactor TIMER/DMA framework #3833

Merged
merged 14 commits into from
Sep 24, 2018
Merged

Refactor TIMER/DMA framework #3833

merged 14 commits into from
Sep 24, 2018

Conversation

digitalentity
Copy link
Member

Preparation for DSHOT

@digitalentity digitalentity added this to the 2.1 milestone Sep 1, 2018
@digitalentity digitalentity mentioned this pull request Sep 1, 2018
Closed
@digitalentity
Copy link
Member Author

F3/F4/F7 works. F7 refactoring needed.

@digitalentity digitalentity mentioned this pull request Sep 10, 2018
Closed
@digitalentity
Copy link
Member Author

@TwoToneEddy code is generally ready to start implementing DSHOT on top of this branch.

@digitalentity
Copy link
Member Author

F4 & F7 mostly verified to work. F3 not tested

@digitalentity
Copy link
Member Author

Almost done 😄

@digitalentity
Copy link
Member Author

Ok, this should be ready for testing. SoftSerial + PPM in not tested. Motor output + Ledstrip works

@digitalentity
Copy link
Member Author

Ready for testing

@digitalentity digitalentity mentioned this pull request Sep 22, 2018
Merged
@digitalentity
Copy link
Member Author

All motor protocols verified on COLIBRI_RACE (F3), REVO (F4) and OMNIBUSF7NXT (F7).
SoftSerial verified to work on REVO (F4, SmartPort, LTM)
If nobody objects I intend to merge this.

@digitalentity digitalentity merged commit 78bc53f into development Sep 24, 2018
@digitalentity digitalentity deleted the de_timer_dma_and_cleanups branch September 24, 2018 13:11
@TwoToneEddy
Copy link

Daft question, if I now build the development branch is dshot ready to try out?

@TwoToneEddy
Copy link

Sorry I'm an idiot, I see you have a branch for dshot. Can I test this if I add the USE_DSHOT to the target of the board I want to test with?

@digitalentity
Copy link
Member Author

digitalentity commented Sep 24, 2018 •
edited
Loading

@TwoToneEddy Defining USE_DSHOT should be enough to allow DSHOT for a target (if all timer mappings are compatible). Use caution - I didn't test the code with actual ESCs

@stronnag
Copy link
Collaborator

I flew the new timer/dma stuff today (without USE_DHSOT) on a couple of F4 FCs. No adverse affects, no regressions.

@digitalentity
Copy link
Member Author

@stronnag good to know, thanks!

@alexeystn alexeystn mentioned this pull request Oct 23, 2018
Closed
@alexeystn alexeystn mentioned this pull request Nov 27, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
Enhancement Testing Required
Projects
None yet
Milestone
2.1
Development

Successfully merging this pull request may close these issues.
3 participants
@digitalentity @TwoToneEddy @stronnag