add TBS_LUCID_H7_V3 target

[bkleiner]

This pull requests adds support for TBS_LUCID_H7_V3

• Samples received
• Flash firmware
• Calibrate
• Orientation matches
• Gyro working
• Accel working
• Voltage correct
• Current correct
• Baro working
• Mag I2C Bus
• Additional I2C2 Buses (Airspeed/other accessories)
• UART1
• UART2
• UART3
• UART4
• UART6
• UART7
• UART8
• Analog Camera working
• Video Out working
• OSD working
• LEDs working
• Buzzer working
• Motor outputs
• DShot support on m1-4
• Servo outputs
• Blackbox
• PINIO1
• PINIO2
• PINIO3

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[github-actions]

Branch Targeting Suggestion

You've targeted the master branch with this PR. Please consider if a version branch might be more appropriate:

• maintenance-9.x - If your change is backward-compatible and won't create compatibility issues between INAV firmware and Configurator 9.x versions. This will allow your PR to be included in the next 9.x release.

• maintenance-10.x - If your change introduces compatibility requirements between firmware and configurator that would break 9.x compatibility. This is for PRs which will be included in INAV 10.x

If master is the correct target for this change, no action is needed.

---

This is an automated suggestion to help route contributions to the appropriate branch.

[github-actions]

Test firmware build ready — commit 0f6100b

Download firmware for PR #11635

239 targets built. Find your board's .hex file by name on that page (e.g. MATEKF405SE.hex). Files are individually downloadable — no GitHub login required.

Development build for testing only. Use Full Chip Erase when flashing.

[daijoubu]

Does this board support CANbus? If so, can you include the pin definitions for it?
// *************** CANBUS ****************************
#define USE_DRONECAN
#define CAN1_RX PD0
#define CAN1_TX PD1
#define CAN1_STANDBY PD3

If targeting maintenance-9.x or release-9.1 they can be commented out but I will have canbus support in v10.

[bkleiner]

Does this board support CANbus? If so, can you include the pin definitions for it?

i figured i would just do a MR for all of our flight controllers (most of them support CAN) to maintenance-10.x once we have these merged and rebased.

EDIT: ah i just saw you already got them in #11631, ok, sure lets add them then.

[daijoubu]

Either way works. I did a sweep of all boards that exist in AP and Inav and put in placeholders. Just looking for new boards to try and get the developer to put them in based on the schematics rather than me assuming AP has the correct hwdef.

[bkleiner]

Either way works. I did a sweep of all boards that exist in AP and Inav and put in placeholders. Just looking for new boards to try and get the developer to put them in based on the schematics rather than me assuming AP has the correct hwdef.

there any need for them to be commented out? i am happy to confirm all the pins right away.

[daijoubu]

No, I have not pushed any dronecan code to release/9.1 so it should not be an issue.