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

chore: use single target to support nv14/el18/pl18/pl18ev/nb4p #5397

Draft
wants to merge 36 commits into
base: main
Choose a base branch
from

Conversation

richardclli
Copy link
Collaborator

@richardclli richardclli commented Aug 7, 2024

Summary of changes:

  • Unified drivers for all supported Flysky radios
  • Configured NV14/EL18 in pl18 target

pl18 target and nv14 target has a lot on common, unifying them into one target can easy maintenance in the future.

This PR is based on NB4+ PR, so the merge order is:

  • NB4+ PR
  • nv14/el18 support in pl18 target PR

This branch just extend the pl18 target to handle 2 more PCBREV: nv14 and el18, i.e. one can still build nv14/el18 firmware using old target.

Old targets:

  • EL18: PCB=NV14, PCBREV=EL18
  • NV14: PCB=NV14

New targets:

  • EL18: PCB=PL18, PCBREV=EL18
  • NV14: PCB=PL18, PCBREV=NV14

@richardclli richardclli added this to the 2.11 milestone Aug 7, 2024
@richardclli richardclli self-assigned this Aug 7, 2024
@pfeerick pfeerick changed the title feat(nv14/el18): Use pl18 target to support nv14/el18 chore: use single target to support nv14 & el18 Aug 7, 2024
@pfeerick pfeerick added compilation Related to compiling the firmware and firmware options house keeping 🧹 Cleanup of code and house keeping labels Aug 7, 2024
@richardclli richardclli changed the title chore: use single target to support nv14 & el18 chore: use single target to support nv14/el18/pl18/pl18ev/nb4p Aug 7, 2024
@richardclli richardclli force-pushed the fs_nv14_on_pl18 branch 3 times, most recently from 353b5c3 to f45e91e Compare August 8, 2024 09:12
@pfeerick pfeerick marked this pull request as draft August 9, 2024 02:38
@richardclli richardclli force-pushed the fs_nv14_on_pl18 branch 2 times, most recently from d22f954 to c1b4733 Compare August 10, 2024 04:19
@richardclli richardclli force-pushed the fs_nv14_on_pl18 branch 2 times, most recently from 80e3a66 to eb2040e Compare August 18, 2024 23:27
@richardclli richardclli force-pushed the fs_nv14_on_pl18 branch 2 times, most recently from 29e2bf2 to 6507fc1 Compare August 22, 2024 02:53
@richardclli
Copy link
Collaborator Author

@pfeerick Please check if the tap counting problem gone with this PR.

@richardclli richardclli force-pushed the fs_nv14_on_pl18 branch 3 times, most recently from d0a97c5 to e55ceef Compare August 28, 2024 03:03
@richardclli richardclli force-pushed the fs_nv14_on_pl18 branch 5 times, most recently from 0596596 to fe96973 Compare September 6, 2024 08:14
@richardclli richardclli force-pushed the fs_nv14_on_pl18 branch 2 times, most recently from 464892b to 30049d2 Compare September 12, 2024 01:51
richardclli and others added 29 commits October 16, 2024 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compilation Related to compiling the firmware and firmware options house keeping 🧹 Cleanup of code and house keeping
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants